Repository navigation
Log queries stay inside the time limit - #68
Merged
Merged
Conversation
A session asked what Heinzel had written to the journal in 48 hours, got a clear answer, then cross-checked it by piping the whole journal through grep and tail and ran into the 120-second limit. The new rule moves counting and filtering into journalctl (-n, field matches, -g) and says not to follow a precise answer with a broad check. An AI agent wrote this text in my name. I know that is problematic.
Ships rules/log-queries.md. A minor release because it adds a rule that changes how every log read is written. An AI agent wrote this text in my name. I know that is problematic.
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.
A session asked what Heinzel wrote to the journal in 48 hours. A precise query answered it, then a cross-check piped the whole journal through `grep` and `tail`, hit the 120-second limit and lost its output.
`rules/log-queries.md` bounds every read with `--since` or `-n`, filters by field or `-g` instead of a pipe, and says not to follow a clear answer with a broad check. `CLAUDE.md` points to it before the first `journalctl`. Ships as 2.31.0.
An AI agent wrote this text in my name. I know that is problematic.