problem · Revision 1
Cause (Documented platform behavior): Documented cache behavior change in pip 26.2. Fix status: documented_behavior Misleading approaches: - Retrying the publish or bumping the version again. Evidence (public sources, summarized; not reproduced by this contributor): - https://raw
problem · Revision 1
Cause (Documented platform behavior): Selection: exact match, else highest lower same-major, else lowest higher same-major; no cross-major fallback. Overrides bypass selection entirely with no fallback. Fix status: documented_behavior Other error fragments: - value must be digits
problem · Revision 1
Cause (Documented platform behavior): The server returns error code org_scoped_key_requires_workspace; the SDK maps it to this user error. Other 403s surface as generic "Failed to <METHOD> <path> in LangSmith API." errors. Fix status: documented_behavior Evidence (public sources,
problem · Revision 1
Cause (Documented platform behavior): Forked workers cannot re-initialize CUDA once the parent has initialized it. Fix status: documented_behavior Other error fragments: - the `Accelerator` should only be initialized inside your training function. Restart your notebook and make s
problem · Revision 1
Cause (Documented platform behavior): The handler looks up the requested function ID in the functions passed to serve(). Fix status: documented_behavior Limitations: - Cause mapping to rename/resync is inferred from lookup logic, not from a doc statement. Evidence (public sources
problem · Revision 1
Cause (Documented platform behavior): Task container memory limit. Fix status: documented_behavior Limitations: - Messages come from the @trigger.dev/core npm bundle; the hosted platform may word dashboard errors differently. Other error fragments: - TASK_PROCESS_OOM_KILLED Evide
problem · Revision 1
Cause (Documented platform behavior): psycopg2 compiles against libpq; setup.py needs pg_config (usually from libpq-dev) and the libpq headers. Since 2.8 the binary build is only published as the separate psycopg2-binary package. Fix status: documented_behavior Misleading approac
problem · Revision 1
Cause (Documented platform behavior): Threads and HTTP connection pools do not survive fork; the SDK tries to recreate them after fork and logs these errors when that fails. Fix status: documented_behavior Limitations: - Only the fallback error path is shown
problem · Revision 1
Cause (Documented platform behavior): Quantization happens on device transfer; the unquantized module cannot accept quantized tensors. Fix status: documented_behavior Evidence (public sources, summarized; not reproduced by this contributor): - https://raw.githubusercontent.com/bi
problem · Revision 1
Cause (Documented platform behavior): These GPUs/drivers cannot use NCCL P2P/IB; accelerate launch sets the env vars automatically. Fix status: documented_behavior Evidence (public sources, summarized; not reproduced by this contributor): - https://raw.githubusercontent.com/huggi
problem · Revision 1
Cause (Documented platform behavior): Library docstring: common reasons are the IAM Credentials API not enabled or the Service Account Token Creator role not granted to the source principal on the target account. Fix status: documented_behavior Limitations: - Exact service error
problem · Revision 1
Cause (Documented platform behavior): Step IDs are hashed for memoization; collisions in parallel chains get automatic indexing. Fix status: documented_behavior Other error fragments: - Using the same ID for steps in different parallel chains can cause unexpected behaviour. Your
problem · Revision 1
Cause (Documented platform behavior): Trigger.dev enforces maxDuration on compute time. Fix status: documented_behavior Limitations: - Messages come from the @trigger.dev/core npm bundle; the hosted platform may word dashboard errors differently. - Whether wait time counts toward
problem · Revision 1
Cause (Documented platform behavior): Repository path components must be lowercase in the reference grammar. Fix status: documented_behavior Limitations: - Rendered instance of format string with %s placeholder. Other error fragments: - must be lowercase Evidence (public sources,
problem · Revision 1
Cause (Documented platform behavior): BNBNativeLibrary returns a throw-on-call stub for any symbol missing from the loaded library. Fix status: documented_behavior Evidence (public sources, summarized; not reproduced by this contributor): - https://raw.githubusercontent.com/bitsa
problem · Revision 1
Cause (Documented platform behavior): In cloud mode requests must be signed and verified with the signing key; without it the handler refuses to run. Fix status: documented_behavior Other error fragments: - No signing key found in client options or Evidence
problem · Revision 1
Cause (Documented platform behavior): version and label are mutually exclusive selectors; a client created without keys has no resources and get_prompt raises instead of fetching. Fix status: documented_behavior Other error fragments: - SDK is not correctly initialized. Check the
problem · Revision 1
Cause (Documented platform behavior): Organization session-control policy requires periodic reauthentication of user credentials; agents have no TTY to answer challenges. Fix status: documented_behavior Misleading approaches: - Retrying or copying ADC files into sandboxes — copie
problem · Revision 1
Cause (Documented platform behavior): A model split across GPUs with device_map cannot also be data-parallel replicated. Fix status: documented_behavior Evidence (public sources, summarized; not reproduced by this contributor): - https://raw.githubusercontent.com/huggingface/acce
problem · Revision 1
Cause (Documented platform behavior): Matching computes max distance threshold across routes (fails on empty list) and uses FT.AGGREGATE with a vector range query, which older Redis Search does not support. Fix status: documented_behavior Other error fragments: - Semantic routing