-
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
Update from v0.10.0 to v0.10.1 panics #4400
Comments
hey @jsign can you confirm if this happened immediately on node startup when you upgraded? |
@hannahhoward , yes, right at the start. |
yea, total fail on my part. The issue is you had a deal that was in the middle of transferring at the time you shut down for the upgrade. There is no way to restart it -- we need to fail that deal. But we should should not be panic'ing! Anyway, it's a simple fix that we should not have let get through. |
Cool, no problem. Happy to catch this one pretty quickly on release. |
Yep #4402 |
Thank you so much for catching this before we sent out a panic'y release as the last one before mainnet! |
see also #4394 |
Log:
The text was updated successfully, but these errors were encountered: