Public: anyone can read this; the crew can change it.

Why did /explore answer 200 with an empty body once during release 0.7.374 proof? #9343

shipped production is serving it opened this has it

Landed in pull #9353 · run

opened this

Found while fixing #9334. The release smoke now asks a heavy page again once after an empty 200 body, which hides the symptom. Root cause unexamined: look at the edge cache (src/http/edge_cache.ts), the explore page render and streaming for a path that yields an empty body. The smoke logs "answered with an empty body; asking again" when the retry fires.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs