Add leashing 0.27.0.0 leash#13
Merged
axman6 merged 3 commits intoadd-leashing-0.27.0.0from Feb 19, 2026
Merged
Conversation
This was referenced Feb 6, 2026
tweag-ev-ak
reviewed
Feb 6, 2026
| traceM $ "idle: handle acquire" | ||
| traceM $ "idle: handle acquire" | ||
| handleAcquire tgt leashed | ||
| , recvMsgDone = return () |
There was a problem hiding this comment.
We need to check the leashing client id here, to make sure other clients can't unleash.
| close | ||
| -- TODO: Is this right? I think we need to make unleashing explicit | ||
| atomically $ writeTVar leashingPointVar Nothing | ||
| return idle |
There was a problem hiding this comment.
Same as in recvMsgDone — we need to check the leashing client id.
| | otherwise -> do | ||
| requestedLeashPoint <- requestedPoint mpt | ||
| let newLeashState = (messageLeashId, requestedLeashPoint) | ||
| if requestedLeashPoint < currentLeashPoint |
There was a problem hiding this comment.
I think this might be incorrect as there is a scenario when we have tried to leash at volatile tip but then decided to leash on immutable tip. There is a window when the node haven't reached the volatile tip yet.
axman6
force-pushed
the
add-leashing-0.27.0.0-leashId
branch
from
0a4a7a1 to
20365b0
Compare
axman6
force-pushed
the
add-leashing-0.27.0.0-leashId
branch
from
20365b0 to
4124c40
Compare
axman6
force-pushed
the
add-leashing-0.27.0.0-leashId
branch
from
4124c40 to
b77f827
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds support for specifying a LeashID when using the leashed version of the LocalStateQuery protocol. The idea is that any node which can provide the current LeashID is able to control the lashing, and any other node will be rejected. If no node is currently leashing the node, this will begin leashing.
(For anyone not familiar with the project, this is part of an experiment for the plutus-script-reexecutor (PSR) project which aims to leash a node's progress until the PSR has completed processing each block. This implementation is just a proof of concept.)
Description
Please include a meaningful description of the PR and link the relevant issues
this PR might resolve.
Also note that: