Better logging - #1085
Merged
Merged
Conversation
asqui
reviewed
May 12, 2025
asqui
left a comment
asqui
left a comment
Contributor
There was a problem hiding this comment.
Nice docs, as always.
Made a couple of unsolicited drive-by-review comments 😜
dvarrazzo
added a commit
that referenced
this pull request
May 12, 2025
As per kind dive-by review in #1085.
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
2 participants
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.
After the struggle in figuring out slowness on connection (#888, #1055), improving and documenting connection logging.
See the docs change for an example of the logging produced. It should help to figure out the connection attemtps and where any stops.