-
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
itests: retry deal when control addr is out of funds #7454
Conversation
3013fed
to
42017b9
Compare
propcid := *deal | ||
|
||
go func() { | ||
time.Sleep(20 * time.Second) |
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.
Can we subscribe to deal events, and watch for publish, rather than using a sleep here? (or maybe subscribe to deal events and use a shorter sleep)
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 will certainly use a shorter sleep. We can monitor for Publish, but you can't really tell if the Publish handler did something or not, and this is really what we are interested in.
Codecov Report
@@ Coverage Diff @@
## master #7454 +/- ##
=======================================
Coverage 39.80% 39.81%
=======================================
Files 631 631
Lines 66851 66894 +43
=======================================
+ Hits 26611 26631 +20
- Misses 35618 35641 +23
Partials 4622 4622
Continue to review full report at Codecov.
|
f4f5c12
to
4938e2f
Compare
4938e2f
to
a19dbb8
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.
LGTM 👍
Should fix: #7102
Related: filecoin-project/go-fil-markets#638
I am trying to come up with a solution that doesn't involve adding another 1-2 states to
go-fil-transfer
and another 1-2 events and adding more state transitions.I think a deal being stuck in the
Publish
state is the natural thing to happen in case we fail to transition to thePublishing
state, i.e. we fail to initiate the PSD message.Having discussed within the #ignite team, we decided against automatically trying to retry PSD messages. With this PR, a PSD message would be retried only if the node is bounced, as a
Restart
event is sent to deals that are not in a terminal state.TODO:
Publish
state, unless we callMarketRetryPublishDeal
go-fil-markets
ref when related PR is merged so that we don't refer to a commit that's not onmaster