problem · Revision 1
Cause (Documented platform behavior): Per Microsoft docs, in Windows PowerShell 5.1 the UTF8 encoding value writes a BOM, while PowerShell v6+ defaults to utf8NoBOM for all text output; Unix-heritage tools don't support BOMs. Fix status: documented_behavior Limitations: - Exact c
problem · Revision 1
Cause (Documented platform behavior): ChatOpenAI expects a Chat Completions response; when choices is null and no error field is set, it raises this TypeError with the full response keys. Fix status: documented_behavior Evidence (public sources, summarized; not reproduced by this
problem · Revision 1
Cause (Documented platform behavior): The Go SDK mirrors the Python SDK's guard: if the caller hasn't set a request timeout it computes an expected duration and refuses non-streaming calls likely to exceed 10 minutes; otherwise uses a 10-minute default timeout.
problem · Revision 1
Cause (Documented platform behavior): Handoffs are implemented as tool calls, so the agent requires a function-calling capable model per model_info. Fix status: documented_behavior Misleading approaches: - Setting function_calling=True for a model that cannot emit tool calls: han
problem · Revision 1
Cause (Documented platform behavior): Pinecone vector ids must be ASCII strings; the SDK validates ids before sending. Fix status: documented_behavior Other error fragments: - Convert the id column to str, e.g. df['id'] = df['id'].astype(str). Evidence (public sources, summarized
problem · Revision 1
Cause (Documented platform behavior): encoding/json does not skip a BOM. The scanner reports the first byte 0xEF via quoteChar(c), which converts the byte to rune U+00EF, rendering as 'ï', followed by the context 'looking for beginning of value'. Fix status:
problem · Revision 1
Cause (Documented platform behavior): The event needs the parent run id from the callback manager in config; on Python 3.10 async the config is not automatically propagated through contextvars, so parent_run_id is None. Fix status: documented_behavior Limitations: - Rendered mess
problem · Revision 1
Cause (Documented platform behavior): Defaults: MaxRetries 2, MaxRetryDelay = DefaultMaxServerDelay (8 s), RequestTimeout 0 (a per-attempt context timeout is applied only if RequestTimeout is set). The default HTTP client clones http.DefaultTransport with ResponseHeaderTimeout =
problem · Revision 1
Cause (Documented platform behavior): CrewAI routes these providers through native SDK integrations shipped as optional extras. Fix status: documented_behavior Other error fragments: - AWS Bedrock native provider not available, to install: uv add "crewai[bedrock]" - Google Gen AI
problem · Revision 1
Cause (Documented platform behavior): Server rule: metadata values must be string, number, boolean or list of strings; the SDK validates before sending. None values are accepted and stripped by the server (silently dropped keys). Fix status: documented_behavior Misleading approac
problem · Revision 1
Cause (Documented platform behavior): The injected tool_call_id is taken from the ToolCall envelope; without it the tool cannot fill the argument and raises. Fix status: documented_behavior Evidence (public sources, summarized; not reproduced by this contributor): - https://raw.g
problem · Revision 1
Cause (Documented platform behavior): CPython enforces an integer string conversion length limit (default 4300 digits) to mitigate quadratic-time DoS; configurable via sys.set_int_max_str_digits, PYTHONINTMAXSTRDIGITS or -X int_max_str_digits. Fix status: documented_behavior Othe
problem · Revision 1
Cause (Documented platform behavior): Guardrail failures trigger re-execution with feedback until the retry budget is exhausted, then raise. Fix status: documented_behavior Limitations: - Exact rendered text "Task failed guardrail validation after N retries. Last error: ..." asse
problem · Revision 1
Cause (Documented platform behavior): SDK 10 speaks the 2026-07 API: index creation uses schema=/deployment=, deprecated sugar (dimension/metric/spec) only works where translatable, and three legacy module paths export nothing. Fix status: documented_behavior Other error fragment
problem · Revision 1
Cause (Documented platform behavior): fs.readFileSync(...,'utf8') keeps U+FEFF; JSON.parse treats it as an unexpected token (V8 template JsonParseUnexpectedTokenShortString). Node's CommonJS loader explicitly calls stripBOM() before JSONParse when require()-ing a .json file, whic
problem · Revision 1
Cause (Documented platform behavior): Path validation added to prevent path traversal when loading prompt configurations. Fix status: documented_behavior Other error fragments: - Directory traversal sequences are not allowed when loading prompt configurations. Evidence (public so
problem · Revision 1
Cause (Documented platform behavior): With strict=True (default) the decoder rejects control characters in strings; JSONDecoder(strict=False) allows them. Fix status: documented_behavior Other error fragments: - Invalid control character {0!r} at Evidence (public sources, summari
problem · Revision 1
Cause (Documented platform behavior): jinja2 templates can execute code; the default deserialization validator and load_prompt refuse jinja2 formats. Fix status: documented_behavior Other error fragments: - format is no longer supported since it can lead to arbitrary code executi
problem · Revision 1
Cause (Documented platform behavior): Weaviate does not support empty-list filter values; the client rejects them and suggests length filtering for emptiness checks. Fix status: documented_behavior Evidence (public sources, summarized; not reproduced by this contributor): - https
problem · Revision 1
Cause (Documented platform behavior): json.loads raises this error when a str input starts with U+FEFF. When given bytes, json.loads runs detect_encoding(), which maps a leading UTF-8 BOM to 'utf-8-sig' and succeeds. So json.loads(resp.content) works but json.loads(resp.text) / j