Cause (Documented platform behavior): RA expands proc macros through the toolchain's rust-analyzer-proc-macro-srv discovered in the sysroot and runs build scripts for analysis; failures surface as status warnings pointing to server logs. Fix status: documented_behavior Limitation
Cause (Documented platform behavior): Stream completes without usable data; Claude Code falls back to non-streaming (silently before v2.1.239). Fix status: documented_behavior Misleading approaches: - Ignoring the one-time warning — every affected request is duplicated Evidence (
Cause (Documented platform behavior): Documented reasons: nightly/snapshot wrapper without allow-snapshots, unverifiable jars from Gradle 3.3–4.0, jar stored in Git LFS but checkout without lfs: true (only pointer file), or a jar not published by Gradle. Fix status: documented_be
Cause (Documented platform behavior): The gateway blocks requests until the cap period resets; 'unavailable' is a precautionary block. Fix status: documented_behavior Other error fragments: - spend limit unavailable Evidence (public sources, summarized; not reproduced by this con
Cause (Documented platform behavior): For most events only exit code 2 blocks; any other non-zero exit without valid JSON is a non-blocking error and the action proceeds. A hook that can't start (missing or non-executable path) lands in the same
Cause (Documented platform behavior): Doc: check systemctl status of sysbox-mgr/sysbox-fs and restart; after a sysbox-fs restart, recreate all active Sysbox containers. Fix status: documented_behavior Limitations: - Derived from the Sysbox user-guide troubleshooting doc at one ma
Cause (Documented platform behavior): RA discovers sysroot via `rustc --print sysroot` and needs lib/rustlib/src/rust/library; if absent and auto-install fails, it errors; if core is missing it blames RUST_SRC_PATH when set. Only latest stable std source officially supported. Fix
Cause (Documented platform behavior): Non-API body in the non-streaming fallback path; no retry. Fix status: documented_behavior Limitations: - Docs: text/plain gateway replies accepted since v2.1.271. Evidence (public sources, summarized; not reproduced by this contributor): - h
Cause (Documented platform behavior): The default admin/admin password is no longer used; a strong initial admin password must be supplied. Fix status: documented_behavior Misleading approaches: - Using admin:admin from older tutorials. Limitations: - Source/docs-derived; not rep
Cause (Documented platform behavior): Usage credits are capped by the named spend limit; on usage-based orgs the text says 'usage limit'. Fix status: documented_behavior Other error fragments: - You've hit your individual spend limit · ask your admin for a
Cause (Documented platform behavior): Stale checksum after a version bump, or a genuinely different (corrupted/intercepted) download. Fix status: documented_behavior Misleading approaches: - Deleting distributionSha256Sum to 'fix' it — removes the integrity check. Limitations: -
Cause (Documented platform behavior): The official client verifies it talks to Elasticsearch and refuses unknown products. Fix status: documented_behavior Limitations: - Source/docs-derived; not reproduced. - Version where the product check started (7.14) is from general knowledg
Cause (Documented platform behavior): Since v2.1.217 the guard resolves symlinks (previously writes via symlinks could land in the shared checkout). Fix status: documented_behavior Misleading approaches: - Reading the terse 'Error editing file' as a generic edit failure Other err
Cause (Documented platform behavior): loadModule tries the extensions in order, then require.resolve from the app root; MODULE_NOT_FOUND is wrapped as ImportModuleError and SyntaxError as UserCodeSyntaxError; other errors are rethrown unchanged. Fix status: documented_behavior Li
Cause (Documented platform behavior): Sysbox always uses a user namespace and a single subuid range for the sysbox user; the doc lists both errors. Fix status: documented_behavior Limitations: - Derived from the Sysbox user-guide troubleshooting doc at one master commit;
Cause (Documented platform behavior): current_status sets Health::Error when fetch_workspace_error is set; when linkedProjects are configured it lists them as possibly incorrect. Docs: many 'nothing works' problems are RA failing to understand project structure. Fix status: docum
Cause (Documented platform behavior): Before v2.1.214 Claude Code did not retry this failure. Fix status: released_fix (fixed in v2.1.214) Evidence (public sources, summarized; not reproduced by this contributor): - https://code.claude.com/docs/en/errors#socket-is-closed (officia
Cause (Documented platform behavior): mvnw downloads the Maven distribution with wget, else curl, else a Java downloader compiled with javac; each needs network access (and the last needs a JDK). Fix status: documented_behavior Limitations: - Source-derived; not reproduced. Other
Cause (Documented platform behavior): Session and weekly limits are shared across models; Opus/Sonnet limits apply only to that family. Fix status: documented_behavior Other error fragments: - You've hit your weekly limit · resets Mon 12:00am - You've hit your Opus