[network] Remove socket bench

[gregnazario]

Motivation

Remove socket bench, as we won't be maintaining it for now. This is a PR to test out bors

Have you read the Contributing Guidelines on pull requests?

Yes

Test Plan

None, just cargo x build

[netlify]

✔️ Deploy Preview for aptos-developer-docs canceled.

🔨 Explore the source changes: cc63fe4

🔍 Inspect the deploy log: https://app.netlify.com/sites/aptos-developer-docs/deploys/6226a4806d42460007039a33

[gregnazario]

/land

[aptos-bot]

@gregnazario ❗ This PR is still missing approvals, unable to queue for landing

[gregnazario]

/land

[aptos-bot]

💥 Tests timed-out

[gregnazario]

/land

[aptos-bot]

💥 Tests timed-out

[gregnazario]

/land

[aptos-bot]

💥 Tests timed-out

[gregnazario]

/land

[gregnazario]

/land

[gregnazario]

/land

[aptos-bot]

@gregnazario 💡 This PR is already queued for landing

[aptos-bot]

💔 Test Failed - build-test-deploy

[gregnazario]

/help

[aptos-bot]

Bors help and documentation

Bors is a Github App used to manage merging of PRs in order to ensure that CI is always green. It does so by maintaining a Merge Queue. Once a PR reaches the head of the Merge Queue it is rebased on top of the latest version of the PR's base-branch (generally master) and then triggers CI. If CI comes back green the PR is then merged into the base-branch. Regardless of the outcome, the next PR is the queue is then processed.

General

• This project's Merge Queue can be found here.
• This project requires PRs to be Reviewed and Approved before they can be queued for merging.
• Before PR's can be merged they must be configured with "Allow edits from maintainers" enabled. This is needed for Bors to be able to update PR's in-place so that Github can properly recognize and mark them as "merged" once they've been merged into the upstream branch.

Commands

Bors actions can be triggered by posting a comment which includes a line of the form /<action>.

Command	Action	Description
Land	land, merge	attempt to land or merge a PR
Canary	canary, try	canary a PR by performing all checks without merging
Cancel	cancel, stop	stop an in-progress land
Cherry Pick	cherry-pick <target>	cherry-pick a PR into <target> branch
Priority	priority	set the priority level for a PR (high, normal, low)
Help	help, h	show this help message

Options

Options for Pull Requests are configured through the application of labels.

Option	Description
	Indicates that the PR is high-priority. When queued the PR will be placed at the head of the merge queue.
	Indicates that the PR is low-priority. When queued the PR will be placed at the back of the merge queue.
	Before merging the PR will be squashed down to a single commit, only retaining the commit message of the first commit in the PR.

[aptos-bot]

Bors help and documentation

Bors is a Github App used to manage merging of PRs in order to ensure that CI is always green. It does so by maintaining a Merge Queue. Once a PR reaches the head of the Merge Queue it is rebased on top of the latest version of the PR's base-branch (generally master) and then triggers CI. If CI comes back green the PR is then merged into the base-branch. Regardless of the outcome, the next PR is the queue is then processed.

General

• This project's Merge Queue can be found here.
• This project requires PRs to be Reviewed and Approved before they can be queued for merging.
• Before PR's can be merged they must be configured with "Allow edits from maintainers" enabled. This is needed for Bors to be able to update PR's in-place so that Github can properly recognize and mark them as "merged" once they've been merged into the upstream branch.

Commands

Bors actions can be triggered by posting a comment which includes a line of the form /<action>.

Command	Action	Description
Land	land, merge	attempt to land or merge a PR
Canary	canary, try	canary a PR by performing all checks without merging
Cancel	cancel, stop	stop an in-progress land
Cherry Pick	cherry-pick <target>	cherry-pick a PR into <target> branch
Priority	priority	set the priority level for a PR (high, normal, low)
Help	help, h	show this help message

Options

Options for Pull Requests are configured through the application of labels.

Option	Description
	Indicates that the PR is high-priority. When queued the PR will be placed at the head of the merge queue.
	Indicates that the PR is low-priority. When queued the PR will be placed at the back of the merge queue.
	Before merging the PR will be squashed down to a single commit, only retaining the commit message of the first commit in the PR.

[gregnazario]

/land

[aptos-bot]

@gregnazario 💡 This PR is already queued for landing

[aptos-bot]

❗ Land has been canceled due to this PR being updated with new commits. Please issue another Land command if you want to requeue this PR.

[gregnazario]

/land

[aptos-bot]

@gregnazario 💡 This PR is already queued for landing