Repository navigation
Cover the tag-merge helpers and the first enabled: line - #14
Merged
Merged
Conversation
withVersion's null-dropping and own-version branches, withInstall's four outcomes, and the rule that the first enabled: line is the switch had no direct test. One test characterizes withVersion adding a tag to an event already at MAX_TAGS, which #13 questions. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Member
Author
|
Self-review rubric (performed inline in the same session, so it is not an independent review):
Findings (judgment calls, not blocking):
Merge-gate note: no do-not-auto-merge path is modified. This dispatch is not authorized to merge, so the PR is left open for human review. This review 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
This is a Stage B (unit-test expansion) cycle. The issue backlog was empty at triage, so no issues were deferred. The change is test-only:
TraceClient.javais untouched.Four tests are added for branches that had no direct test:
withVersion_dropsNullKeysAndValuesAndKeepsTheEventsOwnVersion: null keys and values are dropped from the copy, an event's ownversionis kept, and the caller's map is left unmodified.withVersion_addsTheVersionEvenToAnEventAlreadyAtMaxTags: a characterization test. Current behaviour is pinned: an event withMAX_TAGStags of its own goes out withMAX_TAGS + 1. This looks like a bug and is filed as withVersion pushes an event already at MAX_TAGS over the server's tag limit #13. Production code is deliberately left unchanged, because fixing it alters what is sent on the wire and that is a maintainer decision. When withVersion pushes an event already at MAX_TAGS over the server's tag limit #13 is resolved, this test is expected to be updated.withInstall_addsTheIdOnlyWhenThereIsOneAndRoomAndNoneAlready: covers all four outcomes, which are added, no ID, the event's owninstallwins, and already atMAX_TAGS. It also checks that the caller's map is not modified.serverWideConfig_theFirstEnabledLineIsTheSwitch: the firstenabled:line decides, and a commented-out line does not count.No tracking issue exists for the coverage itself; the gaps were found during triage.
Test plan
mvn -B verifyrun locally on JDK 21:Tests run: 66, Failures: 0, Errors: 0, Skipped: 0(62 before, plus 4)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