ref(flags): Remove organizations:normalize_segment_names_in_span_enrichment#114809
ref(flags): Remove organizations:normalize_segment_names_in_span_enrichment#114809
Conversation
…chment The flag scanner classified this as flagpole-disabled. The flag gated the entire _normalize_segment_name helper (early return when False); removes the helper, its call site, unused imports, and the three corresponding tests. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
github-actions
Bot
added
the
Scope: Backend
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit ae5a9b5. Configure here.
| # Enable higher limit for workflows | ||
| manager.add("organizations:more-workflows", OrganizationFeature, FeatureHandlerStrategy.FLAGPOLE, api_expose=False) | ||
| # Normalize segment names during span enrichment | ||
| manager.add("organizations:normalize_segment_names_in_span_enrichment", OrganizationFeature, FeatureHandlerStrategy.FLAGPOLE, api_expose=False) |
There was a problem hiding this comment.
Dangling comment left after removing feature flag
Low Severity
The comment # Normalize segment names during span enrichment on line 186 was left behind after removing the manager.add("organizations:normalize_segment_names_in_span_enrichment", ...) call it described. It now sits as an orphaned comment between the more-workflows feature and the # Extract on demand metrics comment, which could confuse future readers.
Reviewed by Cursor Bugbot for commit ae5a9b5. Configure here.
1 participant
The flag scanner classified this as flagpole-disabled. The flag gated the entire _normalize_segment_name helper (early return when False); removes the helper, its call site, unused imports, and the three corresponding tests.