Skip to content

A lease held after the work is done blocks the queue, and nothing tells the holder it is still running #33

Open

Description

@tannevaled

A lease costs its holder nothing, so nothing reminds the holder that it is
running. Its whole cost falls on the sessions waiting for it, who see only
held until HH:MM and cannot tell that the lease is empty.

What happened, twice in two days, on go-fleettools/fleettools

  1. 2026-11-19 19:53. A background agentsync claim --wait obtained the
    lease on attempt 132 — and the session's turn ended there. Nothing used it
    until the next morning. Held empty 19:53 → 20:38, while another session
    was queued for the same lease to cut a release tag.
  2. 2026-11-20 08:47. The same session wrote, one turn earlier, that it
    would release the lease immediately after its three publishing steps. The
    steps finished at 08:49. The release did not happen. Held empty
    08:49 → 09:32.

The second is the instructive one: the rule had been written down, by the
holder, about this exact case, a turn before. A stated intention is a second
action, and the second action is the one that gets skipped.

Proposed gates, cheapest first

  1. A reminder at the moment it is cheap to act. The publishing gate already
    checks the claim before gitpush / ghmerge / ghpr. After one of them
    succeeds, print "you still hold go-x/y until 09:32 — agentsync release go-x/y if you are done". No refusal, no state: one line, at the instant
    the holder is most likely to be finished.
  2. Make an empty lease visible to the queue. Record the time of the
    holder's last publish into the repository. In claims and in a refusal,
    say "held by S until 09:32 — idle 41 min since its last publish". A waiter
    can then tell the holder with a fact rather than a guess.
  3. Optionally, let claim --wait take an idle lease. A lease with no
    publish for N minutes (N stated, say 15) could be treated as lapsed by a
    waiter. This is the strongest and the most contentious — a holder in a long
    test run publishes nothing for a while — so it should be opt-in or come
    after (2) has shown what idle durations actually look like.

Prior art

priorart -n 40 --repo go-agentsync/agentsync "idle lease release" reads 17
entries, all listed; none concerns a held lease left idle. The nearest are
#19 (claim --wait, merged — the tool that produced occurrence 1) and #28
(the publish gate, merged — where proposal 1 would live).

🤖 Generated with Claude Code

Prior art: priorart "idle lease release" at 2026-11-20 11:07 CET reported prior art; checked: priorart -n 40 'idle lease release' reads 17 entries, all listed, none about a held lease left idle; nearest are #19 (claim --wait, merged) and #28 (publish gate, merged), which this extends.

Activity

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

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions