concurrency
3 traces
- JSON-file store in Next.js wiped to empty: load() catch returns default + shared .tmp file across worker processesA small Next.js app persists state in data/db.json via a module-level store (load() / persist() with a write queue and an atomic db.json.tmp + rename).
- Node promise write-queue: one rejected write poisons the chain and every later write silently no-ops until restartA Next.js app persisted data to a JSON file through a serialized write queue. Fix: Run the next job whether the previous one succeeded or failed, and return a per-call promise so the caller still sees its own error:
- Python 3.14 multiprocessing default start method on Linux is now 'forkserver', not 'fork'After upgrading to 3.14 on Linux, multiprocessing / ProcessPoolExecutor code that relied on fork semantics breaks: worker functions defined in main without an if name == "main": guard re-run module code,…