Repository navigation
chore(cora): silence validated false-positive rules and guard tole-core stdout - #399
Merged
Merged
Conversation
…re stdout with a custom rule
🔍 Cora AI Code Review✅ No issues found. Code looks good! Review powered by cora-code · BYOK · MIT |
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
Tune the deterministic cora rules for this repo after a full
cora scan --no-llmwith cora 0.19.0.Why
cora scannow runs the rules engine, so it reported 457 deterministic findings (1 critical). Each rule family was validated against the code before anything was silenced; almost all of it was noise that would bury real findings.Changes
.cora.yamlignore.rules(every entry documents why):bug-todo: matches the word "todo" (the todo_write/TodoState feature); 22 of 22 hits were false positives.qual-clone: 306 info hits, the intended Arc/String ownership model.bug-expect: 37 hits, each stating a local invariant (expect("stdout piped above"), lock and runtime expects).bug-println: the CLI's stdout is its interface and eprintln! is the diagnostics channel.core-no-stdout(rules_engine.custom):println!/print!(noteprintln!) in tole-core is a major finding, so the design rule that the core never writes to stdout stays enforced afterbug-printlnis silenced. Excludescrates/tole-cli/**,evals/**and tests. It currently matches nothing in the repo.openai.rsENV_API_KEY(an env var name, the only critical finding,sec-hardcoded-secret) andapprover.rs(a prompt flush,qual-error-ignore).bug-unwrapminors left visible (3WebSearchTool::from_env().unwrap()calls guarded by anis_some()check, 3 in the evals replay tool).Notes
rules_engine.customtakeslanguagesas file extensions (["rs"]) and requiresexclude;rules:must stay a list of strings in this version. The 0.19.0 docs and changelog describe both differently, so the config was verified empirically (a probe tree withprintln!/eprintln!/print!in core and cli).Testing
cora scan --no-llmbefore and after (457 to 6);cora config validatepasses.Refs the cora 0.19.0 agent-reviewer trial