You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
A source fetch that outlives its 10-second hold can discard the next fetch's fresher result #4368
When a caching table's source fetch is still running after its 10-second hold, the next request for that record starts a second fetch. If the first fetch then commits before the second, the second fetch's commit fails the exact-version check, and its fresher result is dropped. The record keeps the older value until it expires again.
This race predates #4366: before it, a waiting request's timeout also let a second fetch start beside the first.
Possible fixes: let a later fetch's result replace an earlier one on a version conflict, or have a fetch whose hold has ended skip its commit when a newer fetch has started.
Activity