Gadoes wires Mike to bail on a failing source fast
When an outside data source starts misbehaving, the fork now cuts it off instead of waiting on it.
Mike pulls from external sources to answer questions. Gadoes has added a safety valve: if one of those sources fails three times in a row inside a minute, the fork stops calling it and immediately tells the interface that the source is unavailable - rather than leaving the user staring at a spinner while a dead connection times out over and over.
It's a sensible reliability move, but the trigger is aggressive. Three strikes is easy to hit: one slow network patch or a brief outage at the source can trip it, and from the commentary it isn't clear how quickly the source is allowed back in. Anyone adopting this should sanity-check whether three failures matches how reliable their own sources actually are. The same change also clears out a pile of development scratch files that had been committed by accident.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?