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.
The pg-meta functions API creates procedures with a null return_type, but its row schema expects a non-null string, causing ZodError on functions.list() and functions.retrieve() when procedures are present.
The Supabase Connect panel generates .env templates using SUPABASE_KEY, while the Flask quickstart documentation and supabase-py client expect SUPABASE_PUBLISHABLE_KEY. This mismatch causes authentication failures (supabase_key is required) for users following the Connect panel instructions.
The React quickstart example in the Supabase documentation and the GitHub example repo omits the necessary import statements and default export, leading to a runtime Uncaught SyntaxError because main.jsx expects a default export. This is a documentation/code snippet inconsistency introduced by PR #45539.
The SQL Editor's results panel displays '0 rows' and 'Success. No rows returned.' after executing UPDATE or DELETE statements that affect rows but do not return them, because it only inspects the length of the returned rows array and ignores PostgreSQL's command tag and row count.
The @next/playwright instant() helper removes the next-instant-navigation-testing cookie for all origins in a shared Playwright BrowserContext, instead of only the application URL it is controlling. This breaks multi-origin test scenarios where app B's testing cookie is deleted when instant() is called for app A.
Batching router.prefetch calls for multiple slugs of a PPR route in the same tick causes the first-scheduled sibling to be deferred by the 4-request bandwidth cap. When bandwidth frees, the sibling incorrectly resolves against the fallback route entry populated by other completed prefetches instead of fetching its own per-URL segment. Subsequent prefetches become permanent no-ops, forcing full dynamic navigation for the affected slug.
The OAuth flows documentation contains outdated code samples that reference a non-existent method `getUserGrants()`, pass a positional string to `revokeGrant()`, and show an incorrect flat response shape. Actual SDK uses `listGrants()`, `revokeGrant({ clientId })`, and nested OAuthGrant type with `granted_at`. Following the docs leads to runtime TypeErrors and undefined fields.
ChatDeepSeek with response_format=json_object streams reasoning_content as one aggregated chunk because langchain-openai uses the beta streaming helper when response_format is present, which buffers the full response.
In the Supabase dashboard, toggling a cron job's enabled/disabled switch from the table triggers a modal and a refresh, but the displayed status remains unchanged until the user manually clicks the refresh button at the top of the table.
On Windows, a malformed inherited environment variable containing a NUL byte causes Turbopack to fail with a panic that incorrectly points to an unrelated CSS module, hiding the actionable environment variable name.
The Supabase Studio RLS policy editor generated a PostgreSQL policy with a trailing `with check ( )` clause for a SELECT policy, causing a syntax error and preventing the policy from being created.
The homepage's "Read docs for Vue" button uses the URL /docs/guides/getting-started/quickstarts/vuejs, but the correct slug is /vue, causing a 404 error and poor onboarding experience.
Supabase phone login documentation still references legacy MessageBird product and endpoints, causing user confusion; official Bird (MessageBird) updates are available in auth PRs #2684 and #2685.
The Next.js contributing guide does not instruct contributors to run `pnpm build` before `pnpm dev`. On a fresh clone, `pnpm dev` fails due to missing generated artifacts, leading to cascading module not found and TypeScript errors.
Next.js generated ParamMap widens dynamic segment values to string, ignoring the return type of generateStaticParams even when dynamicParams is false. This causes components (layouts/pages) that declare narrower types such as 'en' | 'de' to fail type validation during build, despite correct runtime behavior.
`langchain-model-profiles` CLI `refresh` performs global string replacements (`true`->`True`, `false`->`False`, `null`->`None`) on a `json.dumps` result, corrupting quoted JSON keys and values that contain those substrings. The generated `_profiles.py` still imports successfully but with silently altered profile data.
`_ConfigurableModel.batch_as_completed` and `abatch_as_completed` incorrectly reject singleton tuple configs, causing an AttributeError despite the annotated `Sequence[RunnableConfig]` contract. The code checks only for `list`, not the abstract `Sequence`, so non-list sequences are passed to `ensure_config` unnormalized.
ImagePromptValue is marked serializable and dumps() succeeds, but loads() fails because the class is absent from both deserialization allowlists (legacy langchain and langchain_core namespaces) in langchain_core/load/mapping.py. Its three sibling prompt values all round-trip correctly.
RunnableParallel.get_input_schema merges step input schemas but fails to exclude the Pydantic v2 root model synthetic field 'root', causing the returned schema to reject every valid input that invoke accepts when any step is RunnablePassthrough or unannotated RunnableLambda.
`create_image_block` in langchain-core accepts base64 data without a `mime_type`, unlike its siblings `create_video_block`, `create_audio_block`, and `create_file_block`. This produces blocks that cannot be converted to valid provider payloads and violates the function's documented contract.
The Supabase Google login documentation contains a code snippet where hashedNonce is declared inside a .then() callback, making it inaccessible outside the callback. Users following the guide encounter a ReferenceError when trying to use hashedNonce, and may skip the nonce or pass the raw nonce to both Google and Supabase, reducing security.
In `_MultiModalMessagePromptTemplate.aformat`, the `DictPromptTemplate` branch incorrectly calls the synchronous `format()` instead of awaiting `aformat()`. This means any subclass overriding `aformat` is silently bypassed on the async path, breaking consistency with the sibling `StringPromptTemplate` and `ImagePromptTemplate` branches which correctly await their async variants.
Next.js 16.3.0 introduced a server actions runtime change that adds event listeners per action invocation without cleanup, causing Node's MaxListenersExceededWarning and potential memory leak. This is a regression from versions before 16.3.x.
The registry schema accepts arbitrary strings for `backendProviders`, allowing unsupported provider names to bypass validation. This can cause runtime errors or silent misconfiguration. The proposed change restricts values to the known supported providers using a Zod enum.
Static type checking fails for create_agent when a heterogeneous list of middleware objects with different state_schema types is combined with an explicit state_schema argument. Runtime behavior works correctly, but type inference collapses all middleware to AgentMiddleware[AgentState, ...], causing `no-matching-overload` errors.
Resolves three UI and state issues: incorrect last-child CSS selector causing visible extra grid line in learn app, stale project name input due to React defaultValue without key, and potential memory leak from uncleared timeout in lite-studio project page.
langchain-openai's `_create_usage_metadata` only extracts known keys (`audio`, `cached_tokens`, `reasoning_tokens`) from `prompt_tokens_details` and `completion_tokens_details`, causing provider-specific fields like `text_tokens`, `accepted_prediction_tokens`, and `rejected_prediction_tokens` to be silently lost.
The build process awaits `telemetry.flush()`, causing unnecessary delay before returning. Telemetry submission should be detached like in dev mode.
In Next.js with webpack builder and optimization.concatenateModules enabled, a client entry's enclosing ConcatenatedModule can be assigned module id 0. The manifest plugin checks truthiness instead of null, causing the client reference to be omitted and the build to fail during prerendering.
Following the Authentication with Cache Components guide with 'use cache: private' leads to one DB query per prefetched page link, multiplying user lookups. The documented pattern does not share cached user data across independent PPR requests.
LangChain, LlamaIndex, and Pydantic
Pinecone, Chroma, Weaviate, Qdrant, and neighboring stores
Next.js, Supabase, and the surrounding app stack