-
Notifications
You must be signed in to change notification settings - Fork 11.2k
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
[Traffic Control] Support on bridge node #19291
base: main
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
3 Skipped Deployments
|
|
||
let (server_config, client_config) = config.validate(bridge_metrics.clone()).await?; | ||
let traffic_controller = server_config.policy_config.map(|policy_config| { | ||
Arc::new(TrafficController::spawn( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
in a future PR, we will decide whether to spawn
or init
based on the actual acl policy?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, once I merge and rebase on the other PR which introduces the spawn/init, this logic will no longer be valid since spawn
should no longer be public, and will need to be replaced with init
, which will do the right thing based on the policy
@@ -489,87 +547,154 @@ async fn handle_add_tokens_on_evm( | |||
String, | |||
String, | |||
String, | |||
)>, | |||
)>, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
revert?
64189ad
to
78de8cc
Compare
78de8cc
to
fbc7cf4
Compare
1e120c5
to
e5c9bd5
Compare
Description
Step 1 of adding traffic controller support in bridge node. This version only supports socket address based IPs. Followup PRs:
Test plan
TODO (soon)
Release notes
Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.