Uses centralized store for multi-instance

Describes a valid algorithm

Returns correct HTTP headers

Returns 429 status code

No incorrect information

Function is async

Uses await on db.query

Preserves not-found check

Returns the user row

Error propagation via throw or rejection

No callback parameter in signature

Identifies seconds vs milliseconds mismatch

Provides correct fix

Correct comparison direction

No incorrect information

Explains write-through or write-behind

Explains cache-aside with invalidation

Recommends invalidation on write for this case

Addresses consistency vs performance tradeoff

No incorrect information

Suggests parallelizing independent steps

Recommends dependency caching

Proposes test splitting or sharding

Mentions conditional or incremental steps

No incorrect information

Explains the preflight (OPTIONS) request

Identifies missing Allow-Headers

Mentions Allow-Methods needed

Server must handle OPTIONS method

No incorrect information

Identifies the margin-auto centering limitation

Provides a working solution

Solution achieves true centering

No incorrect information

Uses expand-contract (multi-phase) approach

Explains why direct rename is risky

Includes backfill step

Mentions dual-write period

No incorrect information

Identifies Docker DNS isolation

Suggests checking container DNS config

Mentions Docker's embedded DNS (127.0.0.11)

Provides debugging commands

No incorrect information

Has build stage

Has separate runtime stage

Uses slim or alpine base for runtime

Copies only production artifacts

Runs TypeScript compilation

Valid Dockerfile syntax

Uses class component

Implements getDerivedStateFromError or componentDidCatch

Renders fallback UI on error

Retry button resets state

Logs error details

No incorrect information

Explains merge creates a merge commit

Explains rebase replays commits

Mentions history linearity tradeoff

Warns about rebase on shared branches

No incorrect information

Identifies blocked channel send as the leak

Suggests buffered channel fix

Mentions context cancellation as alternative

No incorrect information

Explains why N+1 happens in GraphQL

Recommends DataLoader or batching

Explains DataLoader mechanism

Mentions per-request DataLoader instances

No incorrect information

Identifies shared mutable state as primary bug

Recommends ThreadLocal

Identifies double-checked locking issue

No incorrect information

Configures startup probe for slow start

Separates liveness from readiness concerns

Readiness checks dependency health

Accounts for GC pauses in liveness config

Uses correct YAML or probe spec syntax

No incorrect information

Stateless API: Round Robin

Mixed servers: Weighted or Least Connections

Chat app: Sticky Sessions / IP Hash

Explains why each algorithm fits

No incorrect information

Describes log collection from containers

Includes a log processing/transport layer

Recommends searchable storage

Addresses request correlation

No incorrect information

Mentions operational complexity increase

Suggests profiling first

Mentions data consistency challenges

Mentions team structure consideration

Does not unconditionally recommend microservices

No incorrect information

Creates compound index with correct field order

Explains field ordering rationale

Sort direction matches query

Mentions explain() for verification

No incorrect information

Correct proxy_pass to upstream

Sets proxy headers

WebSocket upgrade handling

HTTPS/SSL configuration

Timeout configuration

Valid Nginx syntax

Server-side app: Authorization Code flow

SPA: Authorization Code with PKCE

CLI: Device Authorization flow

Explains security rationale

No incorrect information

Uses pg Pool

Configures pool size

Configures timeouts

Includes error handling

Shows query usage pattern

No incorrect information

Identifies SQL injection

Recommends parameterized queries

Shows fixed code

Mentions missing error handling

No incorrect information

Decorator accepts role parameter

Extracts and decodes JWT

Returns 401 for missing/invalid token

Returns 403 for wrong role

Uses functools.wraps

No incorrect information

Identifies DataFrame retention as likely cause

Recommends diagnostic tools

Mentions garbage collection considerations

Suggests chunked processing

No incorrect information

Uses pyproject.toml with build-system

Specifies Python version requirement

Declares dependencies correctly

Configures CLI entry point

Configures pytest

Valid TOML syntax

Identifies read-then-write as the problem

Recommends atomic UPDATE RETURNING

Mentions alternative: transactions with row locking

No incorrect information

Identifies referential equality as root cause

Mentions React.memo

Mentions useMemo or useCallback

Explains shallow comparison limitation

No incorrect information

Proposes cache key structure

Sets appropriate TTL

Describes invalidation strategy

Addresses cache stampede or thundering herd

No incorrect information

Identifies the closure capture issue

Fix 1: move keyword

Fix 2: Arc or clone

No incorrect information

Recommends remote backend with locking

Shows backend configuration

Explains lock behavior

Addresses stuck lock recovery

No incorrect information

Correctly defines stub

Correctly defines mock

Correctly defines fake

Provides concrete examples for the email/DB scenario

No incorrect information

Correct generic signature

Correct grouping logic

Handles key value to string conversion

Includes usage example

No incorrect information

Implements exponential backoff

Adds jitter to backoff

Handles missed message recovery

Detects connection loss

No incorrect information

Asks for more information or provides diagnostic steps

Does not prescribe a single fix without context

Covers multiple possible causes

Identifies that requests.cache() does not exist

Suggests a real alternative

Does not hallucinate a working requests.cache() implementation

Refuses or redirects the request

Suggests defensive alternative