Commit e715a4d
Retry in-flight metadata that fails under the old gateway preference
The gateway-flip retry effect only invalidated cache entries that had
already failed. An entry whose fetch was still in flight was skipped —
so a request started while the option was off could reject after the
toggle had run, caching a failure that nothing would ever retry until
remount (Bugbot, PR Chia-Network#3029).
In-flight entries now get a rejection handler: if the pending fetch
fails, it is invalidated and refetched under the new preference, while
a result that arrives successfully is kept instead of being thrown away
and refetched. Repeated toggles can stack handlers on one promise, but
each retry goes through invalidate, so the worst case is a redundant
refetch, not an inconsistent cache.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017NXWAjaHb9SFafLeguTHd81 parent bfbd0ca commit e715a4d
1 file changed
Lines changed: 10 additions & 2 deletions
Lines changed: 10 additions & 2 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
174 | 174 | | |
175 | 175 | | |
176 | 176 | | |
177 | | - | |
| 177 | + | |
| 178 | + | |
| 179 | + | |
| 180 | + | |
178 | 181 | | |
179 | | - | |
| 182 | + | |
180 | 183 | | |
181 | 184 | | |
182 | 185 | | |
| 186 | + | |
| 187 | + | |
| 188 | + | |
| 189 | + | |
| 190 | + | |
183 | 191 | | |
184 | 192 | | |
185 | 193 | | |
| |||
0 commit comments