-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error out deals that are not activated by proposed deal start epoch #5061
Conversation
ffda847
to
37eb405
Compare
37eb405
to
e02a366
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's worth investingating the timeout functionality builtin to Events.Called, though, I guess I wouldn't hold up merge on it.
67f9b58
to
6bbb8ec
Compare
0d6eb2d
to
cb044f8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just 1 thing
Co-authored-by: Łukasz Magiera <magik6k@users.noreply.github.com>
Is it a better practice to specify a startepoch much later to allow more time to seal? |
It depends on the individual miner. If the miner is already overloaded and struggling to seal in time, setting the proposed deal start epoch to a later time may not help much. |
Fixes #4990
When a deal is terminated by the miner, the client can get stuck in
StorageDealSealing
.This PR adds functionality to the functions that wait for pre-commit and prove-commit such that they will callback with an error if the chain reaches the proposed start epoch for the deal without the deal being activated.
Fixes #4977
Provides a better error message for when the deal is not found.
Old: "deal 12345 not found"
New: "deal 12345 not found - deal may not have completed sealing before deal proposal start epoch, or deal may have been slashed"