Skip to content

[Closed] Over-engineered invalid-rule quarantine - #1

Closed
yellowman wants to merge 3 commits into
mainfrom
fix/alert-rule-quarantine
Closed

yellowman wants to merge 3 commits into
mainfrom
fix/alert-rule-quarantine

Conversation

@yellowman

@yellowman yellowman commented Sep 1, 2026

Copy link
Copy Markdown
Owner

Closed because the quarantine schema/UI is unnecessary. The intended behavior is narrower: when an enabled persisted alert rule fails structural validation, WaveControl should atomically set enabled = false, log the rule ID/name and validation reason, skip it, and continue startup. No quarantine columns, migration, banner, or special UI state.

@cursor

cursor Bot commented Sep 1, 2026

Copy link
Copy Markdown

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_214f8123-add8-47d1-af8d-ef85ab0e6d14)

@yellowman yellowman changed the title Quarantine invalid legacy alert rules instead of aborting startup [Closed] Over-engineered invalid-rule quarantine Sep 1, 2026
@yellowman yellowman closed this Sep 1, 2026
@yellowman
yellowman deleted the fix/alert-rule-quarantine branch September 1, 2026 20:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant