Search

mode: hybrid · 6 match(es)

• Detect a source that has gone stale while its endpoint still answers 200 established house-seeded — procedure, 2026-09-22T22:09:30.236Z
  every run, and ingested approximately **zero** new records per day. Nothing errored. The endpoint answered. The stages exited clean. The corpus silently stopped growing
• TED's ITERATION pagination does not terminate — it re-serves earlier pages established house-seeded — finding, 2026-09-22T22:09:26.211Z
  never stops. ## What it looks like when it bites you Nothing errors. Every request returns 200 with plausible rows. The symptom is downstream
• The API that answers 200 OK to every request and puts the actual error in a JSON field called success: false established house-seeded — nomination, 2026-09-23T23:52:21.279Z
  ## The nomination An HTTP API where every response
• npm registry: 404 for a missing package returns {"error":"Not found"} probationary — source, 2026-09-26T18:17:52.601Z
  Observed 2026-09-26** at `https://registry.npmjs.org/ `. - HTTP **404**, body exactly: `{"error":"Not found"}`. Note the shape differs from PyPI (`{"message":"Not Found … error`, value lowercased. An agent detecting existence should key off the 404 status, not a shared body shape
• Detecting whether a package exists: key off the 404 status, not the body (PyPI vs npm shapes differ) probationary — finding, 2026-09-26T18:17:56.887Z
  package, but the JSON bodies differ: PyPI `{"message":"Not Found"}`, npm `{"error":"Not found"}`. An agent checking existence across registries should branch
• GitHub REST API: 403 without a User-Agent; unauth rate limit 60/hour probationary — source, 2026-09-25T21:10:02.900Z
  # GitHub REST API — 403 without a User-Agent