problem · Revision 1
Cause (Documented platform behavior): The SDK maps every 401 from the upload request to this fixed free-trial-credits message instead of surfacing the server body. An invalid/missing API key also produces 401, so the message may not reflect the real cause.
problem · Revision 1
Cause (Documented platform behavior): langchain-aws prefers api_key and only logs a warning; bearer auth is injected by mutating botocore's private token_provider._providers list, which raises AttributeError if botocore changes. Fix status: documented_behavior Limitations: - Note
problem · Revision 1
Cause (Documented platform behavior): MCP elicitation schemas are restricted to a flat object of primitive properties; the Go SDK enforces this with detailed validators on both sides. Fix status: documented_behavior Other error fragments: - only string, number, integer, boolean,
problem · Revision 1
Cause (Documented platform behavior): Early stopping needs a baseline eval, warmup evals and patience non-improving evals on a validation set. Fix status: documented_behavior Other error fragments: - Early stopping requires n_evals >= patience + warmup_evals + 1 = Evidence (publi
problem · Revision 1
Cause (Documented platform behavior): The SDK runs local dataset checks per purpose: CSV only for eval, Parquet not for eval, extensions limited to .jsonl/.parquet/.csv, UTF-8 and size (50.1 GB) checks. Fix status: documented_behavior Other error fragments: - Only JSONL and
problem · Revision 1
Cause (Documented platform behavior): gRPC servers send GOAWAY with ENHANCE_YOUR_CALM when clients send too many 'bad' pings. grpc-js maps NGHTTP2_ENHANCE_YOUR_CALM on a stream to Status.RESOURCE_EXHAUSTED 'Bandwidth exhausted or memory limit exceeded', and on a too_many_pings GO
problem · Revision 1
Cause (Documented platform behavior): The platform proxy connects to the machine's external interface on internal_port; servers bound to loopback refuse it. Next.js standalone server.js uses the HOSTNAME and PORT environment variables for binding, and container runtimes typically
problem · Revision 1
Cause (Documented platform behavior): The Mantle endpoint is regional; the SDK builds https://bedrock-mantle.{region}.api.aws/anthropic and refuses to guess. API keys for Mantle are read from AWS_BEARER_TOKEN_BEDROCK or ANTHROPIC_AWS_API_KEY. Fix status: documented_behavior Limit
problem · Revision 1
Cause (Documented platform behavior): Documented release lines: 2.0.x tracks 2025-11-25, 1.1.x and 0.18.x track 2025-06-18 (security patches only); 2026-07-28 support (server/discover, SEP-2575 stateless lifecycle) is planned for 3.x. The client errors when the server answers ini
problem · Revision 1
Cause (Documented platform behavior): When api_key is None the client falls back to os.environ['AWS_BEARER_TOKEN_BEDROCK']; API-key (bearer) auth and SigV4 credentials are mutually exclusive, so the constructor raises. Fix status: documented_behavior Misleading approaches: - Pass
problem · Revision 1
Cause (Documented platform behavior): The runner accepts only null/"", the literal string "json", or a raw JSON object starting with '{'; any other string raises the invalid-format error. Fix status: documented_behavior Evidence (public sources, summarized; not reproduced by this
problem · Revision 1
Cause (Documented platform behavior): Since pnpm 9, pnpm checks packageManager and errors on mismatch (package-manager-strict settings). In v11 these settings (managePackageManagerVersions, packageManagerStrict, packageManagerStrictVersion) were collapsed into pmOnFail: download
problem · Revision 1
Cause (Documented platform behavior): Gemini API mode reads GOOGLE_API_KEY (preferred) or GEMINI_API_KEY; Vertex mode needs project+location or API key and loads ADC scoped to cloud-platform. Fix status: documented_behavior Other error fragments: - Authentication is not set up. P
problem · Revision 1
Cause (Documented platform behavior): The chat helper validates that history starts with user and contains only user/model roles. Fix status: documented_behavior Other error fragments: - The role of the message must be either 'user' or 'model'. Evidence (public sources, summarize
problem · Revision 1
Cause (Documented platform behavior): Those hosts only support sign-in through claude.ai connectors; Claude Code matches them by URL and refuses the local OAuth flow. Fix status: documented_behavior Misleading approaches: - Retrying OAuth or changing callback ports — the flow is
problem · Revision 1
Cause (Documented platform behavior): Converse responses always contain 'output'; any other JSON means the request went to a non-runtime endpoint. Fix status: documented_behavior Limitations: - Message truncated in record; full text continues with endpoint guidance. Evidence (pub
problem · Revision 1
Cause (Documented platform behavior): PnP strict mode only lets packages access their declared dependencies; hoisting previously hid the missing declaration. Fix status: documented_behavior Misleading approaches: - Deleting .pnp.cjs / reinstalling: the dependency graph is still m
problem · Revision 1
Cause (Documented platform behavior): Parameter names are read via reflection and are only present when compiled with -parameters; AFC invokes static methods directly and needs an instance for instance methods. Fix status: documented_behavior Limitations: - Verbatim check against
problem · Revision 1
Cause (Documented platform behavior): Gemini Developer API batches accept exactly one source (uploaded file name or inline requests); job names follow backend-specific formats. Fix status: documented_behavior Limitations: - The 'Expected format like ...' strings are suffixes of t
problem · Revision 1
Cause (Documented platform behavior): process_schema converts const to enum only for STRING type and raises otherwise; _process_enum rebuilds int enums as str enums (str(member.value)) because Gemini enums are string-valued. Fix status: documented_behavior Evidence (public source