Repository navigation
Log every dropped report, at a bounded length - #27
Merged
Merged
Conversation
These fail until the client logs the reports Close gives up on and cuts an overlong name, so CI records them red before the fix lands. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Drain swallowed the cancellation, so reports still queued behind the in-flight request were the one drop nothing logged. An overlong event name reached the log whole, though the same size check cuts a tag key. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Member
Author
|
Self-review rubric (plain comment; not an independent review):
Findings noted, not changed:
Local anchor: UNVERIFIED (no .NET SDK in the dispatch sandbox), so CI on the exact head SHA was used as the gate. This comment was drafted during a Gardener session (https://github.com/Stephenson-Software/gardener). drafted by Claude on behalf of Daniel Stephenson |
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.
Summary
Every drop is now logged, and at a bounded length. The change is confined to log messages: the wire format,
Close()'s time bound and the public API are untouched.Close()times out are counted in the log.Drainused to swallow the cancellation, so everything behind the in-flight request was lost silently, against the README's "Drops go to the optionallogcallback". One line is now logged:close timed out, dropped N queued report(s).MaxLengthin the log.dropped <name>andcould not queue <name>used to copy the whole name. A name within the limit is logged unchanged, and a longer one ends in....CloseXML doc and the READMEClose()row now say that the dropped remainder is logged.Closes #25
Closes #26
Test plan
Buildworkflow red on the test-only first commit, namingClose_LogsHowManyReportsItGaveUpOn,Report_LogsAnOverlongNameCutAtTheLimitandReport_NeverThrowsWhenTheTagsDoAndLogsAnOverlongNameCut(run 41763538443;Failed: 3, Total: 102on ubuntu-latest, with the windows-latest leg cancelled by fail-fast)Buildworkflow green on the fix commit on ubuntu-latest (net8.0), 102 tests against 97 on mainBuildworkflow green on the fix commit on windows-latest (net8.0 + net48), 102 tests each against 97 on mainThe local anchor is UNVERIFIED: no .NET SDK is installed in the dispatch sandbox, so the CI matrix is the gate. The first commit was pushed alone on purpose, so that FAIL→PASS is recorded by CI without a temporary revert or a force-push.
The Unity (Mono/IL2CPP) runtime is not covered by CI. No threading or HTTP behaviour is changed here, so no Unity-specific risk is expected.
Deferred
User-Agent) was not picked. It changes the wire-format contract that the Java and Python clients share, so a maintainer has to decide it.This PR description was drafted during a Gardener session (https://github.com/Stephenson-Software/gardener).
🤖 Generated with Claude Code
drafted by Claude on behalf of Daniel Stephenson