problem · Revision 1
Cause (Documented platform behavior): The scanner reaches end of input before a closing quote and raises 'Unterminated string starting at' with the string's start position. Fix status: documented_behavior Limitations: - The link to token-limit truncation is a common cause, not
problem · Revision 1
Cause (Documented platform behavior): Deserialization now checks each constructor class path against an allowlist; the default "core" only permits classes in langchain_core mappings because instantiating arbitrary classes from a manifest is a code-execution/SSRF risk. Fix status:
problem · Revision 1
Cause (Documented platform behavior): The v3 API was removed from the v4 package; weaviate.Client is a stub that raises with migration pointers. Fix status: documented_behavior Other error fragments: - Upgrade your code to use Python client v4 `weaviate.WeaviateClient` connection
problem · Revision 1
Cause (Documented platform behavior): urllib3 emits InsecureRequestWarning on each unverified HTTPS request made from a connection pool. Fix status: documented_behavior Misleading approaches: - Suppressing the warning with urllib3.disable_warnings() while leaving verification off
problem · Revision 1
Cause (Documented platform behavior): The decoder requires a double-quoted string after '{' or ','; comments, trailing commas and single quotes are not JSON. Fix status: documented_behavior Misleading approaches: - Using ast.literal_eval as a generic fix: accepts Python literals,
problem · Revision 1
Cause (Documented platform behavior): Documented troubleshooting item. Fix status: documented_behavior Limitations: - Error strings are generic; retrieval relies on context. - Cookie-sharing cause inferred; docs only give the workaround. Evidence (public sources, summarized; not
problem · Revision 1
Cause (Documented platform behavior): The middleware requires exactly one decision per interrupted tool call, in order, and validates the count before rebuilding tool calls. Fix status: documented_behavior Evidence (public sources, summarized; not reproduced by this contributor):
problem · Revision 1
Cause (Documented platform behavior): Superuser setup requires explicit non-default credentials. Fix status: documented_behavior Other error fragments: - Username and password must be set Evidence (public sources, summarized; not reproduced by this contributor): - https://raw.git
problem · Revision 1
Cause (Documented platform behavior): Documented: Langflow 1.11.0 allowed fastapi>=0.139.0,<1.0.0. Fix status: released_fix (fixed in 1.11.1) Other error fragments: - NameError: name 'get_body_field' is not defined Evidence (public sources, summarized; not reproduced by this cont
problem · Revision 1
Cause (Documented platform behavior): Chroma collection names follow S3-bucket-like naming rules. Fix status: documented_behavior Evidence (public sources, summarized; not reproduced by this contributor): - https://raw.githubusercontent.com/chroma-core/chroma/e122af79fd42216d6319
problem · Revision 1
Cause (Documented platform behavior): Build queue lives in one worker memory; follow-up GET /api/v1/build/<job_id>/events may hit another worker. Fix status: documented_behavior Evidence (public sources, summarized; not reproduced by this contributor): - https://raw.githubusercon
problem · Revision 1
Cause (Documented platform behavior): ClientSession.__del__ emits ResourceWarning 'Unclosed client session ...' and calls the loop exception handler with message 'Unclosed client session' if the session was not closed; BaseConnector's finalizer does the same with 'Unclosed connec
problem · Revision 1
Cause (Documented platform behavior): JSONDecoder.decode calls raw_decode and raises 'Extra data' if anything other than whitespace remains after the first value. Fix status: documented_behavior Limitations: - exact string is generic; match together with product/context Evidence
problem · Revision 1
Cause (Documented platform behavior): Since 1.5, API requests require an API key unless LANGFLOW_SKIP_AUTH_AUTO_LOGIN=true (documented). Fix status: documented_behavior Other error fragments: - An API key must be passed as query or header - Invalid or missing API key Evidence (pu
problem · Revision 1
Cause (Documented platform behavior): Fractions are resolved against the model profile max_input_tokens; when no profile limit is available the middleware refuses at init. Fix status: documented_behavior Evidence (public sources, summarized; not reproduced by this contributor): -
problem · Revision 1
Cause (Documented platform behavior): Chroma caches one System per identifier per process and requires matching settings for reuse. Fix status: documented_behavior Limitations: - Exact string fragment chosen because the full message embeds the identifier. Evidence (public sources
problem · Revision 1
Cause (Documented platform behavior): Stream.__stream__ raises APIError(message=error.message or 'An error occurred during streaming', body=error) for any data chunk containing 'error'; _iter_events converts httpx2 timeout/request exceptions during iteration into APITimeoutError/
problem · Revision 1
Cause (Documented platform behavior): JSONDecodeError messages are '%s: line %d column %d (char %d)' built from the raw message; 'Expecting value' is raised when no JSON value starts at the position. requests re-raises it as requests.exceptions.JSONDecodeError from Response.json(
problem · Revision 1
Cause (Documented platform behavior): init_chat_model only infers the provider from a known "provider:model" prefix or a fixed set of model-name prefixes; otherwise it raises. Fix status: documented_behavior Misleading approaches: - Installing more integration packages does not h
problem · Revision 1
Cause (Documented platform behavior): Chroma persists the embedding function config with the collection and refuses a conflicting one to prevent mixing vector spaces. Fix status: documented_behavior Misleading approaches: - Forcing a different embedding function on an existing co