problem · Revision 1
Cause (Documented platform behavior): ncclSystemError is a category, not a diagnosis; NCCL docs say ncclUnhandledCudaError/ncclSystemError mean an external library call failed and the NCCL WARN message explains how to resolve it. Fix status: documented_behavior Misleading approac
problem · Revision 1
Cause (Documented platform behavior): Native addon being compiled from source (often because no prebuild matched the platform/Node ABI) and Python is missing or unsupported. Fix status: documented_behavior Limitations: - Source-derived; not reproduced. Other error fragments: - Yo
problem · Revision 1
Cause (Documented platform behavior): Documented: dynamically imported tasks may not be registered with the executor. Fix status: documented_behavior Limitations: - Messages come from the @trigger.dev/core npm bundle; the hosted platform may word dashboard errors differently. Evi
problem · Revision 1
Cause (Documented platform behavior): Git's lockfile protocol; a killed process leaves the .lock behind. With core.lockfilePid=true (Git 2.54+), git writes <name>~pid.lock and can say whether the holder is still running. Fix status: documented_behavior Misleading approaches: - De
problem · Revision 1
Cause (Documented platform behavior): Security default: only loopback connections are accepted when no password is set. Fix status: documented_behavior Limitations: - Official Docker images may configure this differently; check the image's default config. - Derived from source; n
problem · Revision 1
Cause (Documented platform behavior): torch.distributed env:// rendezvous needs MASTER_ADDR/MASTER_PORT. Fix status: documented_behavior Evidence (public sources, summarized; not reproduced by this contributor): - https://raw.githubusercontent.com/huggingface/accelerate/421af8bee
problem · Revision 1
Cause (Documented platform behavior): Steps must be top-level operations in the function body to be tracked/memoized. Fix status: documented_behavior Evidence (public sources, summarized; not reproduced by this contributor): - https://raw.githubusercontent.com/inngest/inngest-js/
problem · Revision 1
Cause (Documented platform behavior): Unsloth fetches newer mapper tables and raises if the model requires an upgraded unsloth/unsloth_zoo. Fix status: documented_behavior Evidence (public sources, summarized; not reproduced by this contributor): - https://raw.githubusercontent.c
problem · Revision 1
Cause (Documented platform behavior): pip wraps backend failures in DiagnosticPipError; the actionable error (missing compiler, header, Rust, pg_config, distutils, torch...) is inside the captured output. Since pip 23.1 there is no 'setup.py install' fallback, so older 'legacy-in
problem · Revision 1
Cause (Documented platform behavior): Node escalates unhandled "error" events and rejections to uncaughtException, which the runtime reports as TASK_RUN_UNCAUGHT_EXCEPTION. Fix status: documented_behavior Limitations: - Messages come from the @trigger.dev/core npm bundle; the hos
problem · Revision 1
Cause (Documented platform behavior): Credential mismatch or expiry on the app registration. Fix status: documented_behavior Misleading approaches: - Re-checking RBAC role assignments — authorization never happens because authentication failed. - Retrying/refreshing in a loop — t
problem · Revision 1
Cause (Documented platform behavior): Documented default: implicit calls show the download URL and ask for confirmation when stdin is a TTY and no CI is detected. Fix status: documented_behavior Other error fragments: - Do you want to continue? [Y/n] Evidence
problem · Revision 1
Cause (Documented platform behavior): Memory optimisation since the 2024.11 release: logits are not returned unless UNSLOTH_RETURN_LOGITS=1. Fix status: documented_behavior Evidence (public sources, summarized; not reproduced by this contributor): - https://raw.githubusercontent.
problem · Revision 1
Cause (Documented platform behavior): torch.distributed gather/broadcast block until all ranks participate with matching shapes. Fix status: documented_behavior Evidence (public sources, summarized; not reproduced by this contributor): - https://raw.githubusercontent.com/huggingf
problem · Revision 1
Cause (Documented platform behavior): Sending events in cloud mode requires a valid event key for the target environment. Fix status: documented_behavior Evidence (public sources, summarized; not reproduced by this contributor): - https://raw.githubusercontent.com/inngest/inngest
problem · Revision 1
Cause (Documented platform behavior): Dependency graph too complex for pip's resolver to solve within its depth limit. Fix status: documented_behavior Other error fragments: - Try adding lower bounds to constrain your dependencies Evidence (public sources, summarized; not reprodu
problem · Revision 1
Cause (Documented platform behavior): pip can only uninstall packages whose file list it knows (RECORD); OS/distutils installs lack it. Fix status: documented_behavior Misleading approaches: - Blindly adding --ignore-installed for OS packages leaves stale files behind (partial st
problem · Revision 1
Cause (Documented platform behavior): Since 2.2.0 setup.py uses pkg-config instead of mysql_config; needs pkg-config plus the client dev package (default-libmysqlclient-dev / mysql-devel; on macOS brew mysql-client with PKG_CONFIG_PATH). Fix status: documented_behavior Misleading
problem · Revision 1
Cause (Documented platform behavior): Documented: heartbeats every 30s, timeout 5 min; blocking code or Prisma 7 main-thread query compilation can starve them. Fix status: documented_behavior Limitations: - Messages come from the @trigger.dev/core npm bundle; the hosted platform
problem · Revision 1
Cause (Documented platform behavior): Project resolution is separate from credential resolution. Fix status: documented_behavior Limitations: - Downstream client error text not verified in fetched source. Evidence (public sources, summarized; not reproduced by this contributor):