▸case-04 In our Python file processor, temporary file cleanup deletes files created before a specific timestamp threshold (older than 1 hour). However, crashed runs leave partial files with recent creation times that block new jobs. How should we refactor the artifact cleanup logic? | fail→fail | 15,995 | 16,927 | +6% | 1 | 1 | 0% | 2,828 | 3,126 | +11% | 0 | 0 | — |
▸case-10 We manage an asset build tool that cleans build outputs by picking the oldest directories by file creation date. This causes stale files to persist if a build crashes mid-generation. What rule should govern how build artifacts are compared during cleanup? | fail→pass | 13,651 | 6,659 | -51% | 1 | 1 | 0% | 2,293 | 1,311 | -43% | 0 | 0 | — |
▸case-21 I am writing a pure utility function in TypeScript that parses a JWT token and returns a decoded payload object. Does this function need convergent startup scanning or PID-based stale lock detection? | pass→pass | 8,765 | 5,677 | -35% | 1 | 1 | 0% | 1,575 | 1,192 | -24% | 0 | 0 | — |
▸case-22 In an event-sourced architecture, domain events like `OrderPlaced` are written into an immutable append-only event log. Should the event log writer perform content-based deletion of prior event records when appending new events? | pass→pass | 11,704 | 8,733 | -25% | 1 | 1 | 0% | 1,951 | 1,708 | -12% | 0 | 0 | — |
▸case-23 We are exposing a Prometheus HTTP `/metrics` endpoint in a Python web app to export counter and gauge metrics. Does serving metric values require a convergent startup session adoption phase or state reconciliation step? | pass→pass | 11,486 | 13,102 | +14% | 1 | 1 | 0% | 1,999 | 2,448 | +22% | 0 | 0 | — |
▸case-01 I have an automated database migration and data sync worker that occasionally fails mid-process during container restarts. When it retries, it produces duplicate records and leaves orphaned temp tables. Could you review my architecture plan and provide a structured refactoring guide with specific design patterns to ensure the worker can be re-run safely multiple times from any crash point? | fail→fail | 21,717 | 17,057 | -21% | 1 | 1 | 0% | 3,766 | 3,360 | -11% | 0 | 0 | — |
▸case-02 We are building an event processing pipeline that frequently retries failed jobs, but right now a retry after a partial failure causes inconsistent state downstream. Please provide a blueprint and verification questions I can use to audit this pipeline so that multiple executions always resolve to the exact same outcome. | fail→fail | 17,332 | 17,022 | -2% | 1 | 1 | 0% | 2,698 | 3,424 | +27% | 0 | 0 | — |
▸case-03 We are designing an edge daemon startup routine in C++ for Linux systems. The previous developer suggests simply wiping all state files on startup or relying on timestamps to sort leftover state. How should the startup sequence handle existing state, stale locks, and active worker sessions upon restart? | fail→pass | 21,430 | 18,044 | -16% | 1 | 1 | 0% | 3,646 | 3,234 | -11% | 0 | 0 | — |
▸case-05 Our distributed task runner uses fixed Redis TTL locks (30 seconds) to prevent dual execution. But long tasks crash leaving locks active, or run long and lose locks. A colleague suggested switching to strict lease renewal timers. What lock design pattern ensures self-healing when a worker process dies unexpectedly? | fail→fail | 14,032 | 14,476 | +3% | 1 | 1 | 0% | 2,360 | 2,979 | +26% | 0 | 0 | — |
▸case-06 We have a Go background scheduler that pulls batch jobs every 5 minutes. When a job fails, the scheduler queues the exact same cached payload for the next cycle. Is this caching approach resilient to state drift, or how should job input be managed across scheduling cycles? | pass→pass | 15,634 | 15,795 | +1% | 1 | 1 | 0% | 2,631 | 3,041 | +16% | 0 | 0 | — |
▸case-07 We need a standard checklist for senior code reviewers evaluating mutating API endpoints for crash resilience. Model writers tend to only test happy paths. What specific questions must every state-mutating operation answer during review? | fail→pass | 16,771 | 13,568 | -19% | 1 | 1 | 0% | 2,650 | 2,481 | -6% | 0 | 0 | — |
▸case-08 Our cloud resource sync daemon checks local configuration against cloud APIs. How do we know if a resource provisioning operation needs an explicit reconciliation step added to its architecture? | fail→pass | 16,749 | 12,822 | -23% | 1 | 1 | 0% | 2,771 | 2,280 | -18% | 0 | 0 | — |
▸case-09 When our Kubernetes pod restarts during a sync run, it currently creates brand new background sessions, leaving orphaned running processes. What convergent startup behavior should the container entrypoint implement regarding active background sessions? | pass→pass | 14,524 | 14,146 | -3% | 1 | 1 | 0% | 2,362 | 2,743 | +16% | 0 | 0 | — |
▸case-11 A Node.js background worker creates file lock records containing timestamps. If a worker crashes, other workers must wait until the lock expires after 10 minutes. How can worker locks self-heal immediately when a process crashes? | pass→pass | 17,305 | 15,138 | -13% | 1 | 1 | 0% | 3,317 | 3,179 | -4% | 0 | 0 | — |
▸case-12 An ETL pipeline reads a static snapshot at midnight and retries the snapshot if errors occur throughout the day. Is this safe for idempotency across long retry windows, and how should input generation be handled? | fail→fail | 15,612 | 12,951 | -17% | 1 | 1 | 0% | 2,675 | 2,355 | -12% | 0 | 0 | — |
▸case-13 We are adding automated retries to a gRPC mutating service in Go. The team is arguing over what tests to write to prove the endpoint is safe for retries. What three core scenario tests prove convergence? | fail→pass | 13,636 | 9,208 | -32% | 1 | 1 | 0% | 2,386 | 1,842 | -23% | 0 | 0 | — |
▸case-14 In a SQL migration script runner, running the runner twice fails because `CREATE TABLE` and `ADD COLUMN` throw duplicate errors. Developers want to add `IF NOT EXISTS` everywhere, but leftovers from half-applied migrations still break data state. What comprehensive startup and execution pattern ensures schema migration safety? | fail→fail | 17,212 | 17,594 | +2% | 1 | 1 | 0% | 3,048 | 3,353 | +10% | 0 | 0 | — |
▸case-15 A file sync agent cleans up duplicate temporary downloads by sorting files by file modification time and keeping the newest. When uploads fail halfway, corrupt older files are kept while newer partial files are deleted. How should artifact cleanup compare files? | pass→pass | 13,811 | 8,970 | -35% | 1 | 1 | 0% | 2,429 | 1,677 | -31% | 0 | 0 | — |
▸case-16 We are designing an in-memory lock manager for local daemon processes on Linux hosts. Should we base lock expiration solely on heartbeats or timeouts, or is there a host process indicator that makes stale lock detection self-healing? | pass→pass | 16,134 | 13,091 | -19% | 1 | 1 | 0% | 2,757 | 2,461 | -11% | 0 | 0 | — |
▸case-17 In an SQS worker queue, when a message processing loop encounters a mid-flight failure, the worker currently marks the message as permanently failed and drops it. How should failed work be handled in an idempotent scheduling system? | pass→pass | 15,228 | 14,781 | -3% | 1 | 1 | 0% | 2,508 | 2,717 | +8% | 0 | 0 | — |
▸case-18 An Ansible playbook for provisioning bare metal servers fails when executed repeatedly because it appends lines to configuration files on every run. What principle and test questions should guide the refactoring of this deployment playbook? | fail→fail | 11,613 | 6,243 | -46% | 1 | 1 | 0% | 2,015 | 1,282 | -36% | 0 | 0 | — |
▸case-19 When reviewing an infrastructure provisioning script, how does an engineer determine whether a reconciliation step must be added to the operation flow? | fail→pass | 13,933 | 10,830 | -22% | 1 | 1 | 0% | 2,264 | 2,025 | -11% | 0 | 0 | — |
▸case-20 We are writing an SQL query for a BI dashboard that computes daily active user (DAU) metrics over historical user log tables. Should we implement PID locks and content-based artifact cleanup in this read-only SQL query? | pass→pass | 13,442 | 7,583 | -44% | 1 | 1 | 0% | 2,147 | 1,527 | -29% | 0 | 0 | — |