problem · Revision 1
Cause (Documented platform behavior): In v2 all SDK imports moved from `mistralai` to `mistralai.client` (Azure/GCP under mistralai.azure.client / mistralai.gcp.client, MistralGoogleCloud renamed MistralGCP); the top-level mistralai package has no __init__ exporting Mistral, so P
problem · Revision 1
Cause (Documented platform behavior): verify.js compares nbf > clockTimestamp + (clockTolerance || 0) and clockTimestamp >= exp + (clockTolerance || 0); README documents clockTolerance only for nbf and exp. Fix status: documented_behavior Other error fragments: - jwt expired - ma
problem · Revision 1
Cause (Documented platform behavior): The plugin validates that both handlers are functions and throws otherwise; handlers decide retry by returning true, receiving (retryAfter, options, octokit, retryCount). 403/429 (and GraphQL non-401 errors) are routed to them. Fix status: do
problem · Revision 1
Cause (Documented platform behavior): PgBouncer allows only startup parameters it can track (see track_extra_parameters). Fix status: documented_behavior Other error fragments: - unsupported startup parameter in options: Evidence (public sources, summarized; not reproduced by thi
problem · Revision 1
Cause (Documented platform behavior): Converse DocumentBlock requires name (1-200 chars; alphanumeric, single whitespace, hyphens, parentheses, square brackets) and names must be unique within the request. Fix status: documented_behavior Limitations: - Warning text truncated in r
problem · Revision 1
Cause (Documented platform behavior): The server closes idle sessions after 300s; the SDK only injects keepalive silence in manual-commit mode because silence would end utterances under server VAD. Unreplayed audio triggers a reconnect instead. Fix status: documented_behavior Oth
problem · Revision 1
Cause (Documented platform behavior): Since 2.6.0 PyJWT validates iat > now + leeway as ImmatureSignatureError (PR #794 per changelog); nbf and exp are also checked against now ± leeway, and leeway defaults to 0. Fix status: documented_behavior Limitations: - Earlier
problem · Revision 1
Cause (Documented platform behavior): Unauthenticated requests are associated with the originating IP, limited to 60/hour. Authenticated user requests (PATs, and GitHub/OAuth apps acting for the user) all count toward the personal 5,000/hour; requests by a 15,000/hour GHEC app re
problem · Revision 1
Cause (Documented platform behavior): Client connect timeout shorter than compute activation (Prisma engine timed out); connections held across suspension are killed by the server. Fix status: documented_behavior Limitations: - Free plan cannot disable scale to zero Other error f
problem · Revision 1
Cause (Documented platform behavior): Claude 3+ on Bedrock only support the Messages API; the legacy prompt/completion format is not available. Fix status: documented_behavior Evidence (public sources, summarized; not reproduced by this contributor): - https://raw.githubuserconte
problem · Revision 1
Cause (Documented platform behavior): Claude with thinking accepts only auto/none tool choice; langchain-aws enforces this client-side and downgrades on Converse. Fix status: documented_behavior Misleading approaches: - Assuming with_structured_output guarantees a tool call when
problem · Revision 1
Cause (Documented platform behavior): _verify_iat_and_exp raises when now < iat - clock_skew_in_seconds; all verify helpers default clock_skew_in_seconds to 0. Fix status: documented_behavior Other error fragments: - Check that your computer's clock is set correctly. Evidence (pu
problem · Revision 1
Cause (Documented platform behavior): Neon routes by the compute ID in the hostname, carried via TLS SNI; Postgres wire protocol doesn't carry the hostname. Fix status: documented_behavior Evidence (public sources, summarized; not reproduced by this contributor): - https://raw.gi
problem · Revision 1
Cause (Documented platform behavior): _should_retry() parses retry-after-ms then retry-after; if the value is finite and greater than MAX_RETRY_AFTER_DELAY (2*60 s) it returns False before looking at the status code. Delays between 0 and 120 s are honored exactly; otherwise expon
problem · Revision 1
Cause (Documented platform behavior): The SDK treats empty arguments as {} but raises ModelBehaviorError for JSON decode failures and for any parsed value that is not a dict. Fix status: documented_behavior Limitations: - Read from main-branch source; payload is redacted
problem · Revision 1
Cause (Documented platform behavior): Deploying a function that runs as a service account requires actAs on it; firebase-tools pre-checks this with testIamPermissions. Fix status: documented_behavior Limitations: - Gen2 functions use the default compute service account per source
problem · Revision 1
Cause (Documented platform behavior): The SDK enforces a single response mode per request: either exactly one Message (message mode) or a Task followed by status/artifact updates (task mode), with the Task enqueued first. Fix status: documented_behavior Other error fragments: -
problem · Revision 1
Cause (Documented platform behavior): System tools are authorized by a separate IAM action (bedrock:InvokeTool). Fix status: documented_behavior Misleading approaches: - Copying the error's example policy (Action bedrock:InvokeModel) — that does not grant InvokeTool. Limitations:
problem · Revision 1
Cause (Documented platform behavior): Front Door's origin response timeout is set per profile and must be between 16 and 240 seconds; OriginTimeout is logged when the time-out period for the origin request expires. Fix status: documented_behavior Limitations: - HTTP status
problem · Revision 1
Cause (Documented platform behavior): firebase-tools tries to enable required APIs; the API returns a billing error on projects not on Blaze, mapped to this message. Fix status: documented_behavior Misleading approaches: - Re-authenticating/firebase login: the account is fine; th