probe lint has no way to fail CI on warnings (--fail-on-warning covers agent warnings only)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
Start by locating the probe lint command, its warning reporting and exit-status logic, then read the CLI reference and CI guides named in the acceptance criteria. Check how probe validate and the MCP lint tool expose lint warnings. Done means lint keeps exit 0 by default, --strict exits 1 on warnings with the same output, and the specified docs and changelog are updated.
Written by the indexing model from the issue text.
Description
What happens
probe lint reports warnings (since 0.26.0 this includes the unanchored count and zero-state text check, for example a see "250 ml" that also passes on "1250 ml") but exits 0 when it finds only warnings. A project with dozens of such warnings cannot make CI fail on new ones.
probe test --fail-on-warning does not help: its documented scope is agent warnings at run time (a tap that did nothing, press enter with no focus, go back at the root), and it does not look at lint results. The behaviour matches the docs; the gap is that no flag turns lint warnings into a failing exit status.
Found while running a real project's suite against 0.26.0-next.1: 30 lint warnings, exit status 0, and --fail-on-warning unchanged.
Proposal
- Add
probe lint --strict(or--fail-on-warning, same name as the test flag but documented for lint): exit non-zero when any warning is reported. Default unchanged. - Say in the CLI reference for
probe test --fail-on-warningthat it covers agent warnings only, and point toprobe lint --strictfor lint. - Optionally let
probe testrun the same check before the run (--lint-strict), so one command is enough in CI. Out of scope for the first change.
Acceptance
probe lintwith warnings only: exit 0 (unchanged); with--strict: exit 1 and the same output.probe validateand the MCPlinttool report the same warnings; the tool gains astrictoption or says exit status is not applicable.- Docs: CLI reference (
lint,test --fail-on-warning), the CI guides' lint step, CHANGELOG.
- Dominant language
- Go
- Stars
- 6
- Forks
- 3
- Avg merge
- 6h 28m
- Merged PRs (30d)
- 362
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from AlphaWaveSystems/flutter-probe
-
agent: is checked on a wrapper holding several checkables answers from the first one in tree orderOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
AlphaWaveSystems/flutter-probe#865 ·
Maintainers usually reply within 1 day
-
area/cli bug
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
AlphaWaveSystems/flutter-probe#424 ·
Maintainers usually reply within 1 day
-
area/docs documentation
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
AlphaWaveSystems/flutter-probe#409 ·
Maintainers usually reply within 1 day
-
Dial timeout error should say how long it waited and name the timeout settingPossibly taken @jay23606 claimed this 2 days ago. Openarea/cli bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
AlphaWaveSystems/flutter-probe#408 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
AlphaWaveSystems/flutter-probe#888 ·
Maintainers usually reply within 1 day
All issues in AlphaWaveSystems/flutter-probe
Similar issues
-
agent-review-finding chore
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
jordansmall/spindrift#7254 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
pg-sharding/spqr#3275 ·
Maintainers usually reply within 1 day
-
create_or_update_file rejects explicitly empty file contentPossibly taken @Elon-Jiang claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
github/github-mcp-server#3883 ·
Maintainers usually reply within 4 days
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
databricks/terraform-provider-databricks#6210 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
IBM-Cloud/terraform-provider-ibm#7115 ·
Maintainers usually reply within 2 days