Cluster member identifiers are not directly usable by the suggested show command
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 73/100
Research direction
Start by tracing how plan cluster show NAME formats member identifiers and how desloppify show resolves them; the generated ENRICH instructions are another named entry point. Reproduce with the short identifier from the issue and compare it with the quoted-glob lookup. Done means the printed guidance leads to the open finding, or exact short identifiers resolve successfully.
Written by the indexing model from the issue text.
Description
Problem
In desloppify 1.0 / skill v7, plan cluster show NAME prints review members as their short identifiers, then recommends desloppify show <member-id> --no-budget. Running that printed identifier returns No open issues matching with exit status 0 even though the issue is open and belongs to that cluster. This also stopped the generated Codex ENRICH workflow after it followed the printed lookup literally.
Reproduction
- Import a holistic review finding with an identifier such as
example_contract_mismatchand assign it to a manual cluster. - Run
desloppify plan cluster show NAME. - Run
desloppify show example_contract_mismatch --no-budgetusing the member text printed in step 2. - Observe no match.
desloppify show '*example_contract_mismatch*' --no-budgetor the complete review issue ID returns the same open finding.
Expected behavior
Print a directly usable full ID/hash or quoted glob in cluster details and the generated ENRICH instructions, or explicitly support exact short identifiers in show. A failed lookup should not be treated as evidence that the issue is missing. The quoted-glob workaround allows manual triage to continue.
Environment: macOS arm64, installed desloppify 1.0, skill v7. No source or review findings were changed to work around the lookup.
- Dominant language
- Python
- Stars
- 3.8k
- Forks
- 301
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 peteromallet/desloppify
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
peteromallet/desloppify#947 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
peteromallet/desloppify#946 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
peteromallet/desloppify#942 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
peteromallet/desloppify#936 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
peteromallet/desloppify#930 ·
All issues in peteromallet/desloppify
Similar issues
-
request-theme
Difficulty 1/5 Under an hour Newbie friendliness 78/100
LizardByte/ThemerrDB#9883 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Project-MONAI/MONAI#9258 ·
Maintainers usually reply within 3 days
-
catalog:deprecation
Difficulty 1/5 Under an hour Newbie friendliness 88/100
surendranb/free-inference#31 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
fritzprix/libr-agent#2612 ·
Maintainers usually reply within 1 day
-
needs-triage presubmit-gate
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
gke-labs/kube-agents#5001 ·
Maintainers usually reply within 1 day