Distillation

Date: Sep 10, 2026

• 🟡 (12:21) CLI unit-test output verified span view warns when a combined AAAA1111BBBB2222CCCC3333DDDD4444/A1B2C3D4E5F67890 argument is interpreted as <trace-target>/<span-id> and directs users to use separate arguments: sentry span view AAAA1111BBBB2222CCCC3333DDDD4444 a1b2c3d4e5f67890; it also logged inability to fetch details for span a1b2c3d4e5f67890.
• 🟡 (12:21) CLI unit-test output showed event view detects an event belonging to acme/frontend and suggests sentry event view acme/frontend abc123; a separate event2 fetch correctly produced Error: not found.
• 🟡 (12:21) CLI tests exercised local server/Spotlight behavior: when no server was detected, the CLI started one in the background; SENTRY_SPOTLIGHT=http://127.0.0.1:19880/stream; one fixture logged Process exited before sending any events.
• 🟡 (12:21) CLI API tests logged that JSON-looking positional request bodies are accepted but warn users to pass inline JSON with --data/-d next time.
• 🟡 (12:21) CLI local database behavior: logged Warning: Sentry CLI local database is read-only. Caching and preferences won't persist.
• 🟡 (12:21) CLI auth tests logged migration of stored credentials to the host-scoped model for https://sentry.io; when SENTRY_AUTH_TOKEN is present, stored OAuth login is used by default, with SENTRY_FORCE_ENV_TOKEN=1 available to prefer the environment token.
• 🟡 (12:21) CLI debug-file validation test rejected type bogus; valid debug file types are dsym, elf, pe, pdb, portablepdb, sourcebundle, breakpad, proguard, jvm, and wasm.
• 🟡 (12:21) CLI test output showed dif.zip skips /tmp/df-zip-test-fxEXMv/syms.zip/example.sym when its uncompressed size (174) exceeds maximum file size (1).
• 🟡 (12:21) CLI trace-view behavior: CLI-G5 is recognized as an issue short ID rather than a trace ID, so the CLI looks up the issue’s trace.
• 🟡 (12:21) Dashboard behavior under test: grouped widgets auto-default --limit to 5; users may override with --limit <n>.
• 🟡 (12:21) Compatibility-flag behavior under test: --org my-org maps to SENTRY_ORG=my-org.
• 🟡 (12:21) Snapshot test output showed snapshots.download downloading snapshot resolved-art....
• 🟡 (12:21) Search-query compatibility tests rewrote OR clauses into in-list syntax, including message:[me,unresolved], transaction:[warning,resolved], release:[resolved,resolved], level:[info,fatal], os.name:[warning,error,debug], transaction:[me,none,me], transaction:[fatal,resolved,Chrome], and transaction:[Chrome,none,unresolved]; explicit AND was removed because Sentry search implicitly ANDs terms, yielding assigned:me http.status:500.
• 🟡 (12:21) Monitor-run test fixture logged failure to send an in-progress check-in because the network was down.