You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 23, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Oct 23, 2026. It is now read-only.
sentry schema <term>: a no-match search prints the full resource list instead of reporting no match #1424
A search term that matches nothing returns the entire resource listing, byte-identical to what a garbage term returns. There is no signal that the search failed.
Both print the same full table of every resource. committers is not a resource in the schema, and neither is zzzznomatch, but the output gives no way to know that.
Expected
$ sentry schema committersNo resource matches "committers". Run `sentry schema` to browse all resources.
A non-zero exit for a no-match would also let scripts branch on it.
Why it matters
The skill guidance tells agents to reach for sentry schema <resource> to discover endpoints before falling back to sentry api. Returning a plausible-looking 79-line table for a term that matched nothing actively misleads: it reads as "here are your results" rather than "that does not exist". In my case the endpoint genuinely was not in the schema, and the full-list output hid that fact.
Version
0.43.0-dev.1786559401, confirmed against origin/main @ 47ad7e4.
Jared, start working on this. Reproduce the no-match behavior, implement the smallest correct fix, add targeted coverage, self-review it, and open a scoped PR. Escalate only if a concrete external dependency truly prevents progress.
Activity
MathurAditya724 commentedon Aug 25, 2026
Jared, start working on this. Reproduce the no-match behavior, implement the smallest correct fix, add targeted coverage, self-review it, and open a scoped PR. Escalate only if a concrete external dependency truly prevents progress.