SirBrenton

5 ms·

1. 1.▲
   Retryable Is Not Enough: A Genkit Case Study in AI Execution Semantics(blog.pitstop.dev)

   2 points by SirBrenton 4mo ago|0 comments
2. 2.▲
   by SirBrenton 5mo ago

   Durable workflows that survive crashes are the right foundation. The failure mode we see most: the loop survives the crash but retries into an active rate-limit window — WAIT signal present, ignored by the retry layer. 60 documented instanc
3. 3.▲
   by SirBrenton 6mo ago

   Thanks Rahmi — saw EZThrottle a while back, been thinking about how the layers relate. Your coordinated retry layer assumes the failure is classified correctly upstream — that’s the gap I’ve been working on. Would be curious if you’re seein
4. 4.▲
   by SirBrenton 7mo ago

   If you want to try it on your own code: npx pitstop-check ./src — no config, no install. Works on any TS/JS repo. Happy to answer questions about the pattern or false positives.
5. 5.▲
   Show HN: Pitstop-check – finds the retry bug that turns 429s into request storms

   3 points by SirBrenton 7mo ago|4 comments