Skip to content

A source fetch that outlives its 10-second hold can discard the next fetch's fresher result #4368

Open

Description

@ldt1996

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.

Review-Deferral: 463e9f44dc31ed5f severity=minor category=data-integrity

🤖 Generated by Claude Opus 5.5 (Claude Code); posted via @ldt1996.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Fields

    Priority

    P2

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions