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
Commit 4ae7368
Browse filesBrowse the repository at this point in the historyBrowse files
fix(limrun): answer one delete for one instance, with its reason
The instance delete joins the create under the same request contract: one
attempt at the SDK, because a lost answer is ambiguous and this runtime
retries deletes at its own budgets, not the SDK's. A 404 is Limrun answering
that the instance is already gone — exactly what the delete was after — so it
confirms the end instead of holding the lease for a retry that can only fail
again. The recovery route that ends a lease from its labels keeps the same
contract.
Every refusal that says an instance is not confirmed deleted now carries the
delete's own error as its cause, where a cause renders, beside the text in
details; a create that both failed and could not be undone reports both
reasons, not only the delete's. The disposal outcome records the delete's
cause so each route can raise it without re-deriving anything.
A replacement creation is observed the moment it is published, so the owner's
promise that a creation cannot reach the process unobserved holds by
construction on every path that installs one.
Docs and shape: the teardown-scope marker and the reverse route keep their
own comments, the capture lifecycle's paragraph sits on its class, shutdown's
snapshot names its binding, and the close's report lists every lease it could
not end with each of their reasons.
0 commit comments