Verbosity finding advertises `tj optimize --validate`, which rejects verbosity
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 35/100
Research direction
The bad advice is rendered by _render_verbosity in cli/cmd_optimize.py around lines 2956-2962, and the --validate option is a click.Choice(['downsize']) at lines 156-162. Start by reading the advertised-commands test in tests/unit/test_advertised_commands_are_invocable.py to see why it accepts a bare --validate. The fix direction is unsettled: the issue leans toward extending the feature, but the maintainer has not chosen between the options, so confirm the direction before editing. Done means no rendered screen advertises a flag value the command rejects, and the test fails before the change and passes after.
Written by the indexing model from the issue text.
Description
Symptom
_render_verbosity tells the user to measure the remedy with tj optimize --validate:
Remedy to review (not applied): add a terse system-prompt line and/or a
max_tokens cap near ~620, then measure with tj optimize --validate.
cli/cmd_optimize.py:2956-2962.
The flag does not accept verbosity. --validate is type=click.Choice(["downsize"]) (cmd_optimize.py:156-162), so both forms a reader would try fail:
$ tj optimize --validate
Error: Option '--validate' requires an argument.
$ tj optimize --validate verbosity
Error: Invalid value for '--validate': 'verbosity' is not 'downsize'.
Why it matters beyond the typo
This is the Critical Rule 44 shape: a rendered screen advertises a command, and the command does not resolve. The verbosity finding is explicitly non-committal about its own figure — the caveat tells you to treat it as $0 until measured — so the --validate line is the one actionable next step the card offers. It is the step that does not work.
tests/unit/test_advertised_commands_are_invocable.py parses commands out of rendered screens and fails unless each resolves against the real command tree. It did not catch this one; worth understanding why before fixing, since the gap matters more than the instance. My guess is the bare tj optimize --validate with no argument parses as a resolvable command, so the check passes on a string that cannot actually be run.
Options
- Extend
--validateto verbosity. The honest version of the feature: re-run a sample of the user's own calls under amax_tokenscap and report the measured delta. Most useful, most work, and it spends the user's money so it needs the same confirmation flow downsize has. - Change the line to name a command that works. Smallest fix.
- Drop the sentence. The caveat already says to treat the figure as $0 until measured.
I lean 1, with 2 shipping immediately so the dead instruction is not in a release while 1 is built.
Also
Our Verbosity product page copies this instruction, so it is wrong on the site too. Tracked at Metabuilder-Labs/tokenjam-website#140; that half should not be fixed until this one is settled, or the page will just be wrong in a different direction.
Acceptance
- No rendered screen advertises
--validatefor an analyzer the flag rejects. - The advertised-commands test fails against the current behaviour before the fix, and passes after. If it cannot, widen it so a command with an invalid argument value counts as unresolvable.
- Dominant language
- Python
- Stars
- 122
- Forks
- 35
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 8
Getting set up
- Ships a 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 Metabuilder-Labs/tokenjam
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Metabuilder-Labs/tokenjam#786 ·
Maintainers usually reply within 1 day
-
enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Metabuilder-Labs/tokenjam#759 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Metabuilder-Labs/tokenjam#728 ·
Maintainers usually reply within 1 day
-
bug help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Metabuilder-Labs/tokenjam#591 ·
Maintainers usually reply within 1 day
-
bug good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Metabuilder-Labs/tokenjam#559 ·
Maintainers usually reply within 1 day
All issues in Metabuilder-Labs/tokenjam
Similar issues
-
[Bug] Unit tests reach real Bedrock call paths without patching the modelPossibly taken @proton0210 claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
aws-samples/sample-aws-genai-db-modernizer#1318 · 1 comment ·
Maintainers usually reply within 1 day
-
pyarrow-25.0.1-cp310-cp310-manylinux_2_28_x86_64.whl: 1 vulnerabilities (highest severity is: 5.3)OpenMend: dependency security vulnerability
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
capitalone/locopy#394 ·
-
[Bug] Unhandled ValueError terminates watchdog thread when GISRC value contains multiple colonsOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
sdk-typescript: unquoted COPY globs in shell form are silently dropped from the image build contextOpenbug javascript
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
ietf-tools/datatracker#11922 · 1 comment ·
Maintainers usually reply within 1 day