Repository navigation
fix: monitoring UI improvements, poller prompt quality, and timestamp fixes - #43
Merged
Merged
Conversation
…rror-aware dedup keys
… keys in repeated tests
… in monitoring UI
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
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
opendevops-test-failure) so duplicate entries are identifiable at a glanceZsuffix; frontend now appends it before parsing sotimeAgo(),toLocaleString(), and sidebar/history relative times all show correct local time (was 3 hours off for UTC+3)test_pipeline.pygains--error-messageflag to inject a custom error into the synthetic SQS event, useful for testing different dedup key pathsevidencecolumn added toalertstable (migration 013); stored and returned by both SQLite and Postgres backends; older rows show empty evidence gracefullyTest plan
scripts/test_pipeline.py— alert detail page shows Evidence, numbered Mitigation Steps, and green/amber/red sections matching Slack message layout--error-messagevalues — both appear separately on/monitoringevidencecolumn added automatically, no DB wipe needed