Repository navigation
Conversation
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.
What changed
Execution-history search filtered the serialized JSON payload in SQL before checking the user-visible fields. JSON escaping hid quoted text, Windows paths, ampersands, markup and line breaks, and SQLite's ASCII case folding hid Unicode case-insensitive matches. Apply the indexed job/status/time filters, then match the decoded fields with the existing Unicode-aware matcher before computing the total and page. Each job's history remains bounded by the existing 200-execution retention policy.
Scope
Compatibility
No schema, API, dependency, or runner-protocol changes.
Validation
go test ./internal/repo -run TestSchedule -count=1(SQLite; MySQL tests skip when its DSN is absent).git diff --check.Safety