Relationships
#2726 issue --extension: documented example @adam/cfgmgmt is unroutable (no repo), so -x against it no-ops at exit 0
Opened by kneel · 9/29/2026· Shipped 9/29/2026
The -x/--extension help for issue bug/feature/security gives @adam/cfgmgmt as the example, and the references/issue docs use it too.
@adam/cfgmgmt is a real published extension whose registry repository is null (repository, repositoryVerified, repositoryVerifiedUrl all null via swamp extension search cfgmgmt). Per the current routing rules, a third-party extension with no declared repo is refused cleanly -- and refusals exit 0. So copying the documented example verbatim files nothing, with no error, indistinguishable from success.
Fixes:
- Use an example that actually routes --
@swamp/aws(-> Lab), or a third-party extension with a verified repo (e.g.@shrug/serial-port). - Make a
refusedoutcome distinguishable from a successful file -- non-zero exit, or a clear stderr/banner in text mode, not juststatus:"refused"at exit 0.
Shipped
Click a lifecycle step above to view its details.
stack72 commented 9/29/2026, 9:19:22 PM
Thanks @kneel for reporting this! We shipped: When swamp issue bug/feature/security cannot file the report, throw a UserError that says why, in place of a status refused payload at exit 0. This covers the -x refusals (not-pulled, no-repository, pvr-disabled; code set to the reason) and the not-logged-in abort path. Delete the dead refusal renderer and update the four skill docs that describe exit-0 refusals.. The fix has been merged and a release is on its way. We appreciate your contribution to swamp.
Sign in to post a ripple.