A sourced fix-playbook workspace for AI and agent engineers. Find the root cause, the affected version, the rollback-safe next step, and edge-case audits.
ChatDeepSeek only overrides sync `_generate` and `_stream` to translate `JSONDecodeError` from the OpenAI SDK into a DeepSeek-specific message. The inherited async `_agenerate` and `_astream` are not wrapped, so async callers still receive the opaque `json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)`.
The parse_json_markdown function in langchain_core.utils.json uses a case-sensitive regex to identify fenced code blocks, causing parsing failures when models output fences with uppercase 'JSON' or 'Json'. This affects users of JsonOutputParser and other utilities relying on this function.
MarkdownHeaderTextSplitter incorrectly includes CommonMark optional closing hash sequences in header metadata values, e.g. '# Title ##' yields metadata 'Title ##' instead of 'Title'. This breaks filtering and grouping by header.
When a piece cannot be split further because no separators remain, it is appended directly to the output without applying strip_whitespace, causing inconsistent leading/trailing whitespace compared to merged chunks.
11 of 12 branching endpoints document only 500 while API returns 401/403/429; GET /v1/branches/{id}/diff uniquely requires environment:write scope but docs don't explain why, causing generated clients to mishandle auth failures and integrators to request excessive permissions.
Next.js 16.4.0-canary.22 with Turbopack and experimental cacheComponents reports a dev validation error when a page uses a dynamic import for a client component. The page renders but the validation worker fails with 'module factory is unavailable'. Static imports or disabling devValidationWorker resolve the issue.
When using dynamic(..., { ssr: false }) in the Pages Router, if a sibling Suspense boundary throws during hydration and React retries after the dynamic import has resolved, the loader's useSyncExternalStore uses the current loaded state as the server snapshot. This causes React to see a mismatch between the server-rendered loading state and the now-loaded client state, discarding the server-rendered DOM and falling back to client rendering.
Client-side next/form string actions append FormData entries to URLSearchParams without normalizing line endings according to the HTML specification, causing LF-only line breaks instead of CRLF.
26 unit tests across test_shell_tool.py and test_shell_execution_policies.py fail on Windows because ShellToolMiddleware hardcodes /bin/bash, uses POSIX-only signals and the resource module, and the tests lack platform skip markers or proper patching of the _HAS_RESOURCE flag.
The standard chat model integration tests in langchain-tests 1.1.9 verify that input_tokens, output_tokens, and total_tokens are integers but do not assert that total_tokens equals the sum of input_tokens and output_tokens. A model can report inconsistent usage metadata (e.g., input_tokens=10, output_tokens=105, total_tokens=15) and still pass both test_usage_metadata and test_usage_metadata_streaming.
During background revalidation of partially prerendered (PPR) routes, Next.js reads the Link header from the already-finished response object instead of from the values React passed to appendHeader, causing Flight-triggered regenerations to store no Link header and lose font preload hints.
The observability/inspect documentation page contains a Query performance section with multiple broken links and lists several deprecated Supabase CLI inspect subcommands. This misleads users into using outdated commands and leads to dead links. The fix updates the section to reflect the current CLI subcommands, removes deprecated entries from the main list, and adds a deprecation notice.
Blob.as_string() uses the default 'utf-8' encoding, which does not strip a UTF-8 byte order mark (BOM). Files written by Windows tools (Notepad, PowerShell, etc.) often include a BOM, and this BOM is returned as part of the string, contaminating downstream processing such as Markdown heading parsing.
The `_convert_content_block` function in `langchain.mcp` silently discards metadata fields (name, title, description, size, and URI for embedded resources) when converting MCP `ResourceLink` and `EmbeddedResource` objects to LangChain content blocks, leading to loss of information.
In Next.js 16.3.5-16.4.0-canary.32, a redirect() inside a Suspense boundary in a layout triggers an instant navigation validation error on every warm request, although redirect is intentional control flow. This suppresses genuine blocking-prerender-dynamic findings on the same route.
Supabase documentation for AI tools suggests installing plugins via `npx plugins`, but the npm package `plugins` is unmaintained and its GitHub repository returns 404. Vercel has moved this functionality to the `skills` CLI, so the docs should be updated.
The Supabase local development configuration documentation still shows `[inbucket]` even though the CLI was updated to use `[local_smtp]` backed by Mailpit. This causes confusion and misconfiguration when users copy outdated settings.
In Supabase Dashboard Authentication > Users, the user details drawer cannot be closed using the top-right close/collapse control. The panel remains open until navigating away; no JavaScript errors are logged.
After #50516, legacy JWT API keys are masked in ConnectSheet, but reveal/copy actions incorrectly call the secret key reveal API which fails on Supabase-managed projects, preventing users from accessing their service_role key.
ChatGroq in langchain-groq allows n=2 during construction for non-streaming requests, sending an invalid parameter to the Groq API which returns HTTP 400.
ModelRouterMiddleware._latest_human_message uses next() without a default, causing StopIteration to be converted into an opaque RuntimeError on both sync and async paths when no HumanMessage exists in the state. The error does not identify the middleware or the remedy.
本地开发时，Studio 由于 PG_META_CRYPTO_KEY 环境变量在 Docker Compose 和 Studio 之间不一致，导致无法读取数据库元数据。文档未提供同步说明，造成开发者环境不可用。
On Android Chrome, the Authentication → Users filter form has no visible submit button, and pressing the keyboard's enter/go key does not trigger the filter. The form does not submit on mobile or desktop versions, but the issue is most severe on mobile where no button exists.
langchain-typesafe's ModelRouterMiddleware adds model_route to the agent input JSON schema even though the middleware unconditionally overwrites any caller-provided value in before_agent. This advertises an input field that is silently ignored, causing schema-driven clients to pass a route choice that has no effect.
In Next.js development mode, soft navigation to a route whose server component redirects after async work triggers an uncaught TypeError because React Server Components client code calls performance.measure with a negative end timestamp.
In langchain-xai, ChatXAI.validate_environment creates two separate openai.OpenAI clients (and two openai.AsyncOpenAI) for each instance, rather than deriving client from root_client like sibling integrations. This causes duplicated resources, inconsistent close behavior, and potential connection pool waste. The fix is to build root clients first and set client/async_client as views.
When using the browser back button to return to a page with a URL hash, Next.js erroneously scrolls to the anchor element, disregarding the preserved scroll position. This is caused by the Container component's componentDidUpdate triggering scrollToHash even on popstate navigations.
The @next/next/no-html-link-for-pages rule does not work when next.config.js specifies custom pageExtensions because the rule hardcodes default page extensions and fails to identify custom page files, leading to false negatives.
In Next.js dev with Turbopack, using next/dynamic to load a component that contains a plain import() causes the page HTML to reference a chunk that the dev server never emits, resulting in 404 errors on every page load. This affects both App Router (preload link) and Pages Router (script src). The actual dynamic import still works because the emitted loader chunk has a different hash.
The convert_to_openai_messages utility in langchain-core omits AIMessage.invalid_tool_calls from the converted OpenAI message, while the corresponding ToolMessage replies are retained, leading to orphaned tool_call_id references in exported conversations.
LangChain, LlamaIndex, and Pydantic
Pinecone, Chroma, Weaviate, Qdrant, and neighboring stores
Next.js, Supabase, and the surrounding app stack