chore(db): purge accidentally ingested GLM-5.2 test runs#595
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Note
Low Risk
Config-only ETL override with no runtime or auth changes; only affects exclusion of two known-bad runs from the database.
Overview
Adds two GitHub Actions run IDs to
PURGED_RUNSinrun-overrides.tsso the ingest pipeline skips them on future ingest and removes any data already loaded for those runs.Both entries are dated 2026-07-18 and documented as accidental ingest while testing (GLM-5.2 test runs).
Reviewed by Cursor Bugbot for commit fab890f. Bugbot is set up for automated code reviews on this repo. Configure here.