Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Start of tower-based networking. #5

Closed
wants to merge 9 commits into from
Closed

Start of tower-based networking. #5

wants to merge 9 commits into from

Conversation

hdevalence
Copy link
Contributor

@hdevalence hdevalence commented Sep 10, 2019

This PR adds a new connect command to zebrad. This command is explicitly intended to be thrown away later -- it will not be part of the finished code, and it is not intended to cleanly integrate with the rest of the binary, etc.

Instead, it's intended to be a stub that we can hook into to poke at a running zcashd instance, send whatever messages, dump their bytes, extract test vectors, etc.

@hdevalence hdevalence changed the base branch from main to message-enum September 12, 2019 11:15
@hdevalence
Copy link
Contributor Author

Changed base to message-enum to just show the changes on-top-of-branch.

@hdevalence hdevalence changed the base branch from message-enum to main September 19, 2019 13:45
@hdevalence hdevalence force-pushed the network-tower branch 3 times, most recently from 2e7d275 to a2a8376 Compare September 19, 2019 16:48
This seems to be an issue with `pin-project` resolved in the git branch
of `hyper` (but not yet released).
Running zcashd with -debug=net -logips=1 shows

Added connection to 127.0.0.1:58476 peer=1
connection from 127.0.0.1:58476 accepted
disconnecting peer=1
With `./src/zcashd -debug=net -logips=1`:
```
2019-09-19 15:24:38 Added connection to 127.0.0.1:35932 peer=1
2019-09-19 15:24:38 connection from 127.0.0.1:35932 accepted
2019-09-19 15:24:38 socket closed
2019-09-19 15:24:38 disconnecting peer=1
```

With `RUST_LOG="trace"`, `cargo run connect`:
```
Sep 19 08:24:24.530  INFO zebrad::commands::connect: version=Version { version: Version(170007), services: Services(1), timestamp: 2019-09-19T15:24:24.530059300Z, address_recv: (Services(1), V4(127.0.0.1:8233)), address_from: (Services(1), V4(127.0.0.1:9000)), nonce: Nonce(1), user_agent: "Zebra Connect", start_height: BlockHeight(0), relay: false }
Sep 19 08:24:24.530 TRACE Task::run: tokio_executor::threadpool::task: state=Running
Sep 19 08:24:24.530 DEBUG Task::run: tokio_net::driver::reactor: adding I/O source token=0
Sep 19 08:24:24.530  INFO zebrad::commands::connect: version_bytes="24e9276476657273696f6e000000000063000000cb30ab03179802000100000000000000a89d835d00000000010000000000000000000000000000000000ffff7f0000012029010000000000000000000000000000000000ffff7f000001232801000000000000000d5a6562726120436f6e6e6563740000000000"
Sep 19 08:24:24.530 TRACE Task::run: log: registering with poller
```
@hdevalence
Copy link
Contributor Author

I rewrote a bunch of these commits and I'm going to close this draft PR in favor of a few smaller, more focused ones.

@hdevalence hdevalence closed this Sep 20, 2019
@hdevalence hdevalence mentioned this pull request Sep 20, 2019
@dconnolly dconnolly deleted the network-tower branch January 4, 2021 21:26
skyl added a commit to skyl/zebra that referenced this pull request Sep 25, 2024
## What

Switch to GSQL postgres instance

## Why

Kill vultr stuff completely, database instance for all time.

Let's try stage ...

Note: switch cloud build after ONE run one prod that copies ;9
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant