Recommended action: Verify subscription at claude.ai/settings; ask Console admin for Claude Code/Developer role; Enterprise owner assigns a custom role granting Claude Code (or standard User role), then log in again; check proxy config. Option: Verify subscription at claude.ai/se
Recommended action: Check the id/tag exists (e.g. with `devcontainer features info manifest <id>`), `docker login` to private registries (the CLI uses docker credentials), and remove cyclic dependsOn/installsAfter or overrideFeatureInstallOrder mistakes. Option: Check the id/tag
Recommended action: Pre-install extensions during image build (INSTALL x) or download the .duckdb_extension file and INSTALL from local path; set extension_directory/extension_directories to a writable/bundled path; for 404s check version/platform availability or INSTALL x FROM c
Recommended action: On headless hosts set VSCODE_CLI_USE_FILE_KEYCHAIN=1 for the CLI (tokens saved to a 0600 file), or run a Secret Service keyring; expect in-memory secrets on servers without a keyring. Option: Use file keychain on headless hosts [evidence: official_recommended_
Recommended action: Run the awsAuthRefresh command named (e.g. aws sso login --profile X) or refresh your credential yourself; verify with aws sts get-caller-identity in the same shell/profile. Option: Run the awsAuthRefresh command named (e.g. aws sso login --profile X) or
Recommended action: Copy the database to local disk for writing (then copy back), or open read-only on the shared mount; avoid sharing a DuckDB file across OSes/NAS as the docs caution. Option: Write on local disk [evidence: official_recommended_action] Applies when:
Recommended action: Pass protocol=2 (or ?protocol=2 in the URL) for such servers, or upgrade the server/proxy; legacy_responses keeps Python response shapes separate from wire protocol. Option: Force RESP2 [evidence: official_recommended_action] Applies when: See record scope. St
Recommended action: Close the other connection/process (restart the notebook kernel, close the IDE/UI), or open read-only (duckdb.connect(path, read_only=True) / CLI -readonly) for readers; for multi-writer needs use a server approach (per docs: Quack remote protocol beta or Duck
Recommended action: Increase shm: docker run --shm-size=256m (compose shm_size; Kubernetes: mount an emptyDir with medium: Memory at /dev/shm), or reduce parallel workers / maintenance_work_mem for the operation. Option: Raise /dev/shm [evidence: official_recommended_action] Appl
Recommended action: Reduce request size (smaller bulk batches, fewer concurrent requests), give the node more heap (ES_JAVA_OPTS / container memory), and check _cat/nodes heap usage; retry with backoff on 429. Option: Smaller batches and more heap [evidence: official_recommended_
Recommended action: Enable systemd in WSL ([boot] systemd=true), install dbus-user-session and reboot, run systemctl --user enable dbus --now; in containers run `code tunnel` in the foreground under your own supervisor instead of the service installer. If already registered, run
Recommended action: Upgrade pip inside the venv and retry. If building: install Rust via rustup (not old distro packages), plus gcc, musl-dev/python3-dev, libffi-dev, openssl-dev, pkgconfig; Rust is only needed at build time (multi-stage Dockerfile). Option: Upgrade pip to pick t
Recommended action: Move the Feature under .devcontainer/ (e.g. .devcontainer/local-features/foo) and reference it as "./local-features/foo"; publish shared Features to an OCI registry instead. Option: Move the Feature under .devcontainer/ (e.g. .devcontainer/local-features/foo)
Recommended action: wsl.exe --shutdown; wsl.exe --mount <path-to-ext4.vhdx> --vhd --bare; find the device with wsl.exe lsblk; run e2fsck on it (e.g. wsl.exe sudo e2fsck -f /dev/sdX); wsl.exe --unmount; restart the distro. Evidence basis (self-declared by the contributing chat cli
Recommended action: Remove --node-compat/node_compat and add `compatibility_flags = ["nodejs_compat"]` (with a recent compatibility_date) to the Wrangler config. Option: Switch to nodejs_compat [evidence: official_recommended_action] Applies when: See record scope. Steps: 1. Dele
Recommended action: Scroll up to the first error from install.sh; check the Feature supports the base image (Debian/Ubuntu vs Alpine, arm64), install prerequisites earlier, and pin a Feature version; follow the documentation URL in the message. Option: Scroll up to
Recommended action: Prefer getting a wheel (upgrade pip/uv, use a supported Python/arch). For intended source builds, preinstall Rust (rustup) and put cargo on PATH; in offline or locked-down sandboxes set MATURIN_NO_INSTALL_RUST=1 so the failure is immediate and explicit rather
Recommended action: Pass --accept-server-license-terms (after reviewing the terms); consent is then persisted in the CLI data dir's license_consent.json. Option: Add --accept-server-license-terms [evidence: official_recommended_action] Applies when: Automated tunnel/serve-web sta
Recommended action: Use a signed/notarized upstream release or another distribution channel; don't script Gatekeeper bypasses. If you must run a locally trusted binary, that's a deliberate user security decision outside Homebrew. Evidence basis (self-declared by the contributing