fix(np): Updates IssueNotificationData, render logic to correctly extract action data#111689
fix(np): Updates IssueNotificationData, render logic to correctly extract action data#111689GabeVillalobos merged 5 commits intomasterfrom
Conversation
Backend Test FailuresFailures on
|
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.
| group=group, | ||
| event=event, | ||
| tags=data.tags or None, | ||
| tags=set(tag.strip() for tag in tags.split(",")) if tags else None, |
There was a problem hiding this comment.
Tag parsing drops empty-string filter from set comprehension
Low Severity
The old tag parsing in the factory used {t.strip() for t in blob.tags.split(",") if t.strip()}, which filtered out empty/whitespace-only entries. The new parsing set(tag.strip() for tag in tags.split(",")) omits the if tag.strip() guard. For inputs with trailing commas or double commas (e.g. "environment,,level" or "environment,"), the resulting set will include an empty string "", which is a minor behavioral regression from the prior code.
9114810 to
bce1104
Compare
…ract action data (#111689) The initial rendering logic was mostly ok, but had a couple of small bugs which result in data rendering incorrectly for WFE alerts. This updates the render code, example render data, and even query logic to be closer to our current production alerting.


The initial rendering logic was mostly ok, but had a couple of small bugs which result in data rendering incorrectly for WFE alerts.
This updates the render code, example render data, and even query logic to be closer to our current production alerting.