-
Notifications
You must be signed in to change notification settings - Fork 301
fix(server): start each connection's network measurements fresh #2048
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
Closed
Greg Lamberson (glamberson)
wants to merge
1
commit into
Devolutions:master
from
lamco-admin:fix/server-autodetect-per-connection
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
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.
[protocol] Bandwidth-handle reset is invisible to embedders watching the generation counter — low 🟡 — reset_connection_state stores u32::MAX into autodetect_rtt/autodetect_baseline_rtt/autodetect_bandwidth with Relaxed and, unlike every measurement mutation (server.rs:3975, 3989), performs no paired autodetect_bandwidth_generation increment. Not incrementing is correct per the counter's documented meaning ('increments every time a Bandwidth Measure transaction completes', lines 764-766) and the PR body's stated rationale. The residual issue is that the store has no release at all, so an embedder relying on the documented Release/Acquire pattern to observe bandwidth changes will never learn that the previous connection's figure was cleared for the new connection. Wire behavior is unaffected: the fresh AutoDetectManager ensures Network Characteristics Results are correct (MS-RDPBCGR 2.2.14.1.5). An embedder-facing doc note on the reset, or an Acquire-visible signal, would close the gap.