-
Notifications
You must be signed in to change notification settings - Fork 235
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
feature: CancellationToken
-based shutdowns
#5325
Conversation
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.
I wonder what the impact is when now switching to not-dropguard behaviour by default? I know in the vpn client we seem to hit the drop guards for the gateway-client
@@ -447,6 +448,10 @@ impl NymNode { | |||
wireguard: Some(wireguard_data), | |||
config, | |||
accepted_operator_terms_and_conditions: false, | |||
shutdown_manager: ShutdownManager::new("NymNode") |
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.
Is there a reason why this one PascalCase while the others are kebab-case?
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.
I'm not sure I've been particularly consistent, but I think with recent changes I attempted to use PascalCase for the top level name and kebab-case or snake_case for any child components
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 2 Skipped Deployments
|
i think it would have to be dealt with on case-by-case basis, because with those changes on-drop behaviour is explicit |
this PR introduces scaffolding for using
CancellationToken
andTaskTracker
for our graceful shutdowns rather than the existingTaskClient
andTaskManager
.it focues on creating the new API and migrating some of the existing tasks inside
NymNode
This change is