Fix Dashboard drill-down: Unicode arrow in story path split#618
Merged
erikdarlingdata merged 1 commit intodevfrom Mar 18, 2026
Merged
Fix Dashboard drill-down: Unicode arrow in story path split#618erikdarlingdata merged 1 commit intodevfrom
erikdarlingdata merged 1 commit intodevfrom
Conversation
SqlServerDrillDownCollector was splitting on ASCII ' -> ' but story
paths use Unicode ' → '. The split produced the entire path as one
key, so pathKeys.Contains("DEADLOCKS") always returned false.
Single character fix: ' -> ' → ' → '. All 8 applicable findings
now have populated drill-down data.
Co-Authored-By: Claude Opus 4.6 (1M context) <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.
Summary
Single character fix —
SqlServerDrillDownCollectorwas splitting story paths on ASCII->instead of Unicode→. All path key lookups failed silently.Result
Before: 2/10 findings had drill-downs (only bad actors, which use
StartsWithinstead ofContains)After: 8/10 findings have drill-downs (the 2 nulls are
RUNNING_JOBSandANOMALY_CPU_SPIKEwhich have no applicable drill-down methods)🤖 Generated with Claude Code