-
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] Runtime Segregation cause panic and crash #6792
Comments
Note: we've been using this component and the Given that the JSON-RPC methods use I believe the EOF bug was not triggered previously because we knew exactly how many bytes to consume from the I think the solution here is to make Thoughts, @magik6k? |
We were reading up until getting EOF previously as well. I think the reason this is crashing now is because the JSON-RPC client is closing the stream as @raulk suggests, and previously we had not tested this with a separate |
Describe the bug
Runtime Segregation cause panic with subsystems of mining/sealing/proving node when publishing deals.
Version (run
lotus version
):To Reproduce
Expected behavior
Only lotus-miner mining/sealing/proving node shuts down.
Logs
miner with mining/sealing/providing log:
miner with markets log:
worker log:
Additional context
Lotus-Miner info results in an error corresponding to separating section.
lotus-miner info with mining/sealing/providing:
lotus-miner info with markets:
The text was updated successfully, but these errors were encountered: