Closed
Conversation
Contributor
Author
|
Agent failed. See run: https://github.com/6/nitrocop/actions/runs/23405918144 |
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.
Task prompt (5551 tokens)
Fix Style/MixinUsage — 3 FP, 0 FN
Instructions
You are fixing ONE cop in nitrocop, a Rust Ruby linter that uses Prism for parsing.
Current state: 2,834 matches, 3 false positives, 0 false negatives.
Focus on: FP (nitrocop flags code RuboCop does not).
Workflow
behavior on BOTH the specific FP case AND the general pattern:
tests/fixtures/cops/style/mixin_usage/offense.rbwith^annotationtests/fixtures/cops/style/mixin_usage/no_offense.rbcargo test --lib -- cop::style::mixin_usagesrc/cop/style/mixin_usage.rscargo test --lib -- cop::style::mixin_usage///doc comment on the cop struct documenting what you found and fixedFixture Format
Mark offenses with
^markers on the line AFTER the offending source line:The
^characters must align with the offending columns. The message format isStyle/MixinUsage: <message text>.If your test passes immediately
If you add a test case and it passes without code changes, the corpus mismatch is
caused by config/context differences, not a detection bug.
Do NOT loop trying to make the test fail. Instead:
src/config/or the cop's config handling, not detection logica
///comment on the cop struct and commitCRITICAL: Avoid regressions in the opposite direction
When fixing FPs, your change MUST NOT suppress legitimate detections. When fixing FNs,
your change MUST NOT flag code that RuboCop accepts. A fix that eliminates a few issues
in one direction but introduces hundreds in the other is a catastrophic regression.
Before exempting a category of patterns, verify with RuboCop that the general case
is still an offense:
If RuboCop flags the general pattern but not your specific case, the difference is in
a narrow context (e.g., enclosing structure, receiver type, argument count) — your fix
must target that specific context, not the broad category.
Rule of thumb: if your fix adds an early
returnorcontinuethat skips a wholenode type, operator class, or naming pattern, it's probably too broad. Prefer adding a
condition that matches the SPECIFIC differentiating context.
Rules
src/cop/style/mixin_usage.rsandtests/fixtures/cops/style/mixin_usage/cargo test --lib -- cop::style::mixin_usageto verify your fix (do NOT run the full test suite)git stashPrism Notes
Foo) and ConstantPathNode (qualifiedFoo::Bar). If you handle one, check if you need the other.Pre-diagnostic Results
Diagnosis Summary
Each example was tested by running nitrocop on the extracted source in isolation
with
--force-default-configto determine if the issue is a code bug or config issue.Note: source context is truncated and may not parse perfectly. If a diagnosis
seems wrong (e.g., your test passes immediately for a 'CODE BUG'), treat it as
a config/context issue instead.
FP #1:
ged__linguistics__b0b119c: experiments/lafcadio_plural.rb:13CONFIRMED false positive — CODE BUG
nitrocop incorrectly flags this pattern in isolation.
Fix the detection logic to not flag this.
Enclosing structure: BEGIN {} block (Prism: PreExecutionNode) (line:
BEGIN {)The offense is inside this structure — this is likely WHY
RuboCop does not flag it. Your fix should detect this context.
Full source context (add relevant parts to no_offense.rb):
Message: ``include
is used at the top level. Use insideclass` or `module`.`FP #2:
ged__linguistics__b0b119c: experiments/lprintf.rb:17CONFIRMED false positive — CODE BUG
nitrocop incorrectly flags this pattern in isolation.
Fix the detection logic to not flag this.
Enclosing structure: BEGIN {} block (Prism: PreExecutionNode) (line:
BEGIN {)The offense is inside this structure — this is likely WHY
RuboCop does not flag it. Your fix should detect this context.
Full source context (add relevant parts to no_offense.rb):
Message: ``include
is used at the top level. Use insideclass` or `module`.`FP #3:
ged__linguistics__b0b119c: experiments/conjunct-with-block.rb:13CONFIRMED false positive — CODE BUG
nitrocop incorrectly flags this pattern in isolation.
Fix the detection logic to not flag this.
Enclosing structure: BEGIN {} block (Prism: PreExecutionNode) (line:
BEGIN {)The offense is inside this structure — this is likely WHY
RuboCop does not flag it. Your fix should detect this context.
Full source context (add relevant parts to no_offense.rb):
Message: ``include
is used at the top level. Use insideclass` or `module`.`Current Rust Implementation
src/cop/style/mixin_usage.rsRuboCop Ruby Implementation (ground truth)
vendor/rubocop/lib/rubocop/cop/style/mixin_usage.rbRuboCop Test Excerpts
vendor/rubocop/spec/rubocop/cop/style/mixin_usage_spec.rbCurrent Fixture: offense.rb
tests/fixtures/cops/style/mixin_usage/offense.rbCurrent Fixture: no_offense.rb
tests/fixtures/cops/style/mixin_usage/no_offense.rb