Repository navigation
Add viewer traffic meter and stalled-session diagnostics - #1
Merged
Merged
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
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.
Mac connections can stop updating while the viewer remains responsive and TCP stays connected. This change adds a visible incoming traffic meter and opt-in connection-progress diagnostics to distinguish missing data, unfinished updates, pending requests, and socket event dispatch problems.
-ShowStats; include buffered incoming data and avoid rate-calculation overflow.-ConnectionDiagnosticswith monotonic timing, update progress, socket readiness, callback counts, and slow-processing records.Validation: the viewer builds on Linux and Windows. The integration replay passes on Linux and on pf-omen using the packaged Windows executable, including pending-request and socket-readiness assertions. The user reports the latest deployed version is working well.
The original freeze's cause remains unconfirmed. Diagnostics are disabled by default, and the meter measures incoming socket payload rather than outgoing traffic or TCP/IP overhead.