feat(gateway): add support for connecting to other gateways #158
Conversation
Gateways can now connect to other gateways for network entry, similar to how workers and schedulers connect. The gateway attempts to connect to all provided gateway addresses during startup. By deploying more than one gateway and connecting them together, one can improve the systems reliability. Co-Authored-By: Claude <[email protected]>
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| let gateway_results = join_all( | ||
| config | ||
| .gateway_addresses() | ||
| .iter() | ||
| .map(|address| { |
There was a problem hiding this comment.
The new gateway dial block binds the join_all result to gateway_results but never uses it, so the compiler emits an unused-variable warning. With the repository’s standard cargo clippy -- -D warnings check this warning becomes a build error, blocking the binary from compiling. Either consume the results (e.g., check for at least one success) or prefix the binding with _ to avoid failing the linted build.
Useful? React with 👍 / 👎.
Gateways can now connect to other gateways for network entry, similar to how workers and schedulers connect. The gateway attempts to connect to all provided gateway addresses during startup. By deploying more than one gateway and connecting them together, one can improve the systems reliability.