Emit Core Accessories columns in a fixed order - #2176
Merged
Conversation
Both Core Accessories artifacts built their report headers from a set, so the column order after eventTime changed with the interpreter's hash seed. The keys are now sorted after the event time column, which keeps its datetime type. Rows and row counts are unchanged. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
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
1 participant
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.
The two Core Accessories artifacts (AccessoryD and UserEventAgent) now emit their columns in a fixed order. Both built their headers from a Python set, so the columns after the event time changed between runs with the interpreter's hash seed. The keys are now sorted after the event time column, which keeps its datetime type. Rows and row counts are unchanged.
🤖 Generated with Claude Code