[bugfix] Tunnel not waiting on MixnetClient to shut down cleanly #6225
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
|
simonwicky
changed the base branch from
develop
to
release/2025.21-mozzarella
benedettadavico
modified the milestones:
Niolo (est. mainnet 9.12.2025),
Mozzarella (est. mainnet 25.11.2025)
simonwicky
force-pushed
the
simon/mixnet_client_shutdown_final
branch
from
bca2836 to
02fc9b9
Compare
tommyv1987
approved these changes
Nov 21, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When there is a wireguard registration error, the mixnet client is signalled to shut down, but the tunnel doesn't wait.
Now on errors, the registration client doesn't return until everything is properly stopped
This change is