repo CLI: --json before the leaf name prints no document
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 76/100
Research direction
Start with the root extras check at dokimi/cli.py:83 and trace how the --json flag is stored when it appears before the repo leaf name. Reproduce with dokimi --json repo validate . --bogus and compare with the flag after the name. Done when the command emits the expected JSON error document regardless of flag position.
Written by the indexing model from the issue text.
Description
Raised in the review of PR #590 (intel/dokimi), thread PRR_kwDOVBg7g88AAAABXrLtSQ.c: https://github.com/intel/dokimi/pull/590
Found in PR #590 review. On main and on the PR, dokimi --json repo validate . --bogus exits 2 with empty stdout: the root extras check reads json from the leaf namespace (dokimi/cli.py:83), which is unset when the flag comes before the name. Outside the PR's lines.
Not fixed in PR #590: it is outside the lines that PR changes (another component, a design change, or too large for the round).
- Dominant language
- Python
- Stars
- 39
- Forks
- 13
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 519
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 intel/dokimi
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
dgunning/edgartools#2019 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
topoteretes/cognee#6818 · 1 comment ·
Maintainers usually reply within 1 day
-
source_verification_agent: no outcome when the publisher confirms a work but its DOI resolves to a different recordPossibly taken @pinjun99 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Imbad0202/academic-research-skills#1159 · 1 comment ·
Maintainers usually reply within 1 day
-
[Bug]: DoubleMLData.from_arrays checks the treatment d with force_all_x_finite instead of force_all_d_finitePossibly taken @leninworld claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 88/100
DoubleML/doubleml-for-py#471 ·
Maintainers usually reply within 1 day
-
bug needs-triage
Difficulty 1/5 Under an hour Newbie friendliness 65/100
superdesigndev/treg#1879 ·
Maintainers usually reply within 1 day