Repository navigation
Conversation
🤖 CodeAnt AI — Review Status
|
Thanks for using CodeAnt! 🎉We're free for open-source projects. if you're enjoying it, help us grow by sharing. Share on X · |
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (4)
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThis pull request adds configurable label examples and effective-label reporting to detection, adds formatted CLI output with optional trace and failed-record exports, and updates linked-issue checks for external pull requests. It also revises anonymizer skill benchmark results and related metadata. ChangesEntity Label Configuration and Detection
CLI Run and Preview Output
External Pull Request Issue Checks
Anonymizer Skill Benchmark Refresh
Priority: ➖ Normal Estimated code review effort: 4 (Complex) | ~60 minutes Change: Feature Sequence Diagram(s)sequenceDiagram
participant AnonymizerInterface
participant EntityDetectionWorkflow
participant Validator
participant Augmenter
AnonymizerInterface->>EntityDetectionWorkflow: configured labels and examples
EntityDetectionWorkflow->>Validator: resolved labels and examples
EntityDetectionWorkflow->>Augmenter: active labels and configured examples
sequenceDiagram
participant CLI
participant AnonymizerPipeline
participant OutputWriters
participant RunSummary
CLI->>AnonymizerPipeline: run with input and output options
AnonymizerPipeline-->>CLI: result
CLI->>OutputWriters: write requested trace and failed records
CLI->>RunSummary: print output metadata and grouped failures
sequenceDiagram
participant GitHubEvents
participant LinkedIssueWorkflow
participant GitHubAPI
GitHubEvents->>LinkedIssueWorkflow: PR or referenced-issue event
LinkedIssueWorkflow->>GitHubAPI: fetch PR body and issue states
GitHubAPI-->>LinkedIssueWorkflow: references, states, and labels
LinkedIssueWorkflow->>GitHubAPI: update check or comment
LinkedIssueWorkflow->>GitHubAPI: close PR if no valid issue and no exemption
Suggested reviewers: Merge Risk: ⚪ Minimal · up to The CLI run summary, preview output, and side-file export changes show no remaining merge-blocking concerns in the reviewed files. Security Architecture ReviewSecurity architecture risk: 🔵 Low · up to The new exports are optional and use existing local file permissions. Their file-separation checks can miss different names referring to the same file, allowing an export to overwrite input or the main result. Exposure is localized; broader detection and automation changes were not fully assessed. Retained concerns
Security review detailsSecurity Blast Radius
Security Findings and Attack Paths
Trust Boundaries and Controls
Resilience and Maintainability Implications
Hardening Proposals
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Full details: Docstring CoverageExplanation Docstring coverage is 29.75% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 158 functions across 29 files. (1 skipped: 1 unsupported.)
✨ Finishing Touches 💡 1📝 Generate docstrings 💡
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
codeant-ai
Bot
added
the
size:XL
User descriptionRelated IssueN/A (fork PR) Plan Document
SummaryThe CLI output is hard to read. This builds on the earlier CLI-display plan and folds in its four review comments.
C0 and C1 control bytes are stripped from every record-derived string before printing, so a reason like Left out on purpose:
Limitation: truncation counts characters, not terminal cells, so wide CJK text can still wrap. Type of Change
Contributor Checklist
Validation
Documentation and Artifacts
CodeAnt-AI DescriptionMake CLI run results easier to understand and troubleshoot What Changed
Impact
💡 Usage GuideChecking Your Pull RequestEvery time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later. Talking to CodeAnt AIGot a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask: This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code. ExamplePreserve Org Learnings with CodeAntYou can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input: This helps CodeAnt AI learn and adapt to your team's coding style and standards. ExampleRetrigger reviewAsk CodeAnt AI to review the PR again, by typing: Check Your Repository HealthTo analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health. |
![codeant-ai[bot]](https://avatars.githubusercontent.com/in/646884?s=60&v=4){kind=small}
CodeAnt Nitpicks3 code suggestions1. A side-file path whose parent is unwritable or a regular file passes validation, so the expensive pipeline runs before the command discovers the invalid destination.Incomplete implementation · 2. If a trace or failed-record write fails, the command exits after leaving the main output and earlier side files, creating partial results despite reporting failure.Incomplete implementation · 3. Long column names are never bounded, so preview lines can exceed the terminal width even though the value width is calculated from that width.Logic error · |
b37bff5 to
bc8d267
Compare
|
Replies to the three CodeAnt nitpicks, all in bc8d267:
|
codeant-ai
Bot
added
size:XXL
User descriptionRelated IssueN/A (fork PR) Plan Document
SummaryThe CLI output is hard to read. This builds on the earlier CLI-display plan and folds in its four review comments.
C0 and C1 control bytes are stripped from every record-derived string before printing, so a reason like Left out on purpose:
Limitation: truncation counts characters, not terminal cells, so wide CJK text can still wrap. Type of Change
Contributor Checklist
Validation
Documentation and Artifacts
CodeAnt-AI DescriptionAdd guided entity examples, readable CLI results, and stricter linked-issue checks What Changed
Impact
💡 Usage GuideChecking Your Pull RequestEvery time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later. Talking to CodeAnt AIGot a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask: This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code. ExamplePreserve Org Learnings with CodeAntYou can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input: This helps CodeAnt AI learn and adapt to your team's coding style and standards. ExampleRetrigger reviewAsk CodeAnt AI to review the PR again, by typing: Check Your Repository HealthTo analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health. |
bc8d267 to
adbdf62
Compare
User descriptionRelated IssueUpstream issue Plan Document
SummaryThe CLI output is hard to read. This builds on the earlier CLI-display plan and folds in its four review comments.
C0 and C1 control bytes are stripped from every record-derived string before printing, so a reason like Left out on purpose:
Limitation: truncation counts characters, not terminal cells, so wide CJK text can still wrap. Before / AfterCaptured with Before, After, this PR @ bc8d267 (the ESC/BEL bytes in the crafted reason are stripped; Review fixes, previous PR head b37bff5 vs bc8d267: Type of Change
Contributor Checklist
Validation
Documentation and Artifacts
CodeAnt-AI DescriptionAdd domain-specific detection examples, readable CLI results, and stricter linked-issue checks What Changed
Impact
💡 Usage GuideChecking Your Pull RequestEvery time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later. Talking to CodeAnt AIGot a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask: This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code. ExamplePreserve Org Learnings with CodeAntYou can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input: This helps CodeAnt AI learn and adapt to your team's coding style and standards. ExampleRetrigger reviewAsk CodeAnt AI to review the PR again, by typing: Check Your Repository HealthTo analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health. |
|
Review fixes pushed in adbdf62 (the branch was rebased with
I checked that each new test fails on bc8d267 and passes on adbdf62. Not changed here, because they are outside this branch:
|
adbdf62 to
26664d4
Compare
codeant-ai
Bot
added
size:XL
User descriptionRelated IssueUpstream issue Plan DocumentSummaryThe CLI output is hard to read. This builds on the earlier CLI-display plan and folds in its four review comments.
C0 and C1 control bytes are stripped from every record-derived string before printing, so a reason like Left out on purpose:
Limitation: truncation counts characters, not terminal cells, so wide CJK text can still wrap. Before / AfterCaptured with Before, After, this PR @ bc8d267, now be6b32a after a sign-off rebase with an identical tree (the ESC/BEL bytes in the crafted reason are stripped; Review fixes, previous PR head b37bff5 vs bc8d267: Second review round, bc8d267 vs adbdf62: Type of Change
Contributor Checklist
Validation
Documentation and Artifacts
CodeAnt-AI DescriptionMake CLI run results easier to understand and troubleshoot What Changed
Impact
💡 Usage GuideChecking Your Pull RequestEvery time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later. Talking to CodeAnt AIGot a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask: This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code. ExamplePreserve Org Learnings with CodeAntYou can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input: This helps CodeAnt AI learn and adapt to your team's coding style and standards. ExampleRetrigger reviewAsk CodeAnt AI to review the PR again, by typing: Check Your Repository HealthTo analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health. |
26664d4 to
88f4878
Compare
User descriptionRelated Issue
Plan Document
Summary
Left out, already covered above or in the plan: a per-label entity table, rewrite averages, a source row count (the result does not carry one), side-file flags on Limitations: truncation counts characters, not terminal cells, so wide CJK text can still wrap. Before / AfterBoth blocks come from one driver, Before, After, this PR at 88f4878: The ESC and BEL bytes in the crafted reason are gone. Type of Change
Contributor Checklist
Validation
Documentation and Artifacts
CodeAnt-AI DescriptionMake CLI run results easier to read and troubleshoot What Changed
Impact
💡 Usage GuideChecking Your Pull RequestEvery time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later. Talking to CodeAnt AIGot a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask: This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code. ExamplePreserve Org Learnings with CodeAntYou can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input: This helps CodeAnt AI learn and adapt to your team's coding style and standards. ExampleRetrigger reviewAsk CodeAnt AI to review the PR again, by typing: Check Your Repository HealthTo analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health. |
run keeps its "Output written to:" first line (never styled) and adds a short context block (mode, source, output rows and size, elapsed), failed records grouped by step and reason, and --trace / --failed-output side files. Side-file paths are validated before the pipeline starts. preview prints one block per record with values cut to the terminal width. C0/C1 control bytes from record text are stripped before printing. Styling is on only for a TTY with NO_COLOR unset and --no-color absent; --color/--no-color exists on run and preview only. Signed-off-by: ChethanUK <chethanuk@outlook.com>
88f4878 to
b97e3fa
Compare
Related Issue
Upstream issue 105 will be linked with a closing keyword when this is raised upstream. Issue is not yet triaged; the branch name should follow CONTRIBUTING (for example
chethanuk/feature/105-cli-run-summary) at raise time.Plan Document
plans/105/cli-run-summary.md. It supersedes the plan in the open upstream draft PR 125, following its review threads.Summary
previewprintsresult.dataframe.to_string(max_colwidth=80), which wraps into a wide block, andrunprints onlyOutput written to: <path>. The CLI never showsfailed_records, and control bytes in record text go straight to the terminal.runkeepsOutput written to: <path>as its first line (never styled), so scripts that parse it still work. Below it come Mode, Source, Output rows and size, aFailedcount and Elapsed, then failed records grouped by(step, reason)with a count, most frequent first.result.replace_method/result.rewrite_config, not from column names.--trace PATHwrites the trace dataset and--failed-output PATHwritesrecord_id, step, reason.--output,--traceand--failed-outputare validated before the pipeline starts: bad suffix, existing directory, unwritable parent, existing file that is read-only, or a path equal to--sourceor another output.Error:message instead of a traceback, and the summary lists only files actually written.previewprints one block per record with onecolumn : valueline per output column, values cut toshutil.get_terminal_size(), andfinal_entitiesshown as labels.NO_COLORunset or empty and no--no-color.--color/--no-coloris onrunandpreviewonly. No new dependencies.docs/troubleshooting.mdno longer says the CLI cannot show failed rows; it points at--traceand--failed-output.Left out, already covered above or in the plan: a per-label entity table, rewrite averages, a source row count (the result does not carry one), side-file flags on
preview.Limitations: truncation counts characters, not terminal cells, so wide CJK text can still wrap.
--traceparquet is only tested with synthetic traces, not a real pipeline trace. If a side-file write fails after the run, the main output is kept and the command exits 1.Before / After
Both blocks come from one driver,
drive.py, run for real at each commit. It calls the realanonymizer.interface.cli.main.app(sys.argv[1:])withAnonymizerpatched to return one synthetic result, because the pipeline needs live model endpoints. The result has 2 records (the first contains a newline), matchingtext_replacedandfinal_entities, and 4 failures, one with a reason containing\x1b]0;pwned\x07\x1b[2J.COLUMNS=100, output piped throughcat -v.Before,
mainat d13d260:After, this PR at 88f4878:
The ESC and BEL bytes in the crafted reason are gone.
Type of Change
Contributor Checklist
fix: handle empty entity listskills/anonymizer/SKILL.mdupdated if neededValidation
pytest(full suite): 1514 passedmake format-check(format and ruff),make typecheck,make copyright-check,uv lock --check: all cleanmkdocs build --strict: passestests/interface/cli/drivesapp(["run", ...])with the pipeline patched out; the new tests are table-driven and cover context rows per mode, failure grouping and order, Tip variants, truncation and control-byte stripping, entity labels, side-file round trips (csv, parquet, header-only), bad or read-only side-file and output paths rejected before the run, trace files parquet cannot store (mixed struct/str and all-empty dict columns), and the colour gate over TTY,NO_COLOR(including empty) and--no-colorfor bothrunandpreview.make test-e2eneeds live model endpoints; this change is output formatting after the pipeline returns.Documentation and Artifacts
make docs-buildpasses locallymake convert-notebooks