-
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
[BUG] Unsealing is always needed if miner has set the unsealing price to non-zero #5821
Comments
@xinaxu Thanks for the issue! Were you running the miner for this retrieval effort too? If so, can you please share the deal logs from the provider side too? |
While the client is waiting, I can see jobs of type "RD" from |
with 1.5.3 Mar 17 17:38:36 miner4 lotus-miner[14143]: 2021-03-17T17:38:36.041Z INFO markets loggers/loggers.go:30 retrieval provider event {"name": "ProviderEventOpen", "deal ID": "15", "receiver": "12D3KooWLb3vya3V3ZU39jZRfVsTEY6KB93czht8AdVAF3pMCgqA", "state": "DealStatusNew", "message": ""} |
Closing as it seems this has the same root cause as #5829: The underlying issue is the error Note that the names of the states here are a little confusing: Looking at the logs that @flyworker posted, the time between |
Describe the bug
Unsealing is always needed if the miner has set the unseal price to non-zero.
This happens even when fast-retrieval is enabled and the miner keeps the unsealed copy.
Version (run
lotus version
):1.5.0+mainnet+git.55b85f314.dirty+api1.1.0
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Unseal should not be needed and the retrieval should succeed
Logs
When the unseal price is set to 0.1
When the unseal price is set to 0
The text was updated successfully, but these errors were encountered: