Skip to content

Conversation

@vbar
Copy link
Collaborator

@vbar vbar commented Jul 25, 2024

Should fix #104 .

@vbar vbar requested a review from zeapoz July 25, 2024 06:09
members = ["state-reconstruct-fetcher", "state-reconstruct-storage"]

[profile.release]
panic = 'abort'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure if this should be the default behaviour. When possible, I think each task should run to completion to make sure that the state won't get corrupted. For tasks that may panic I'd prefer to handle the error.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I totally agree the threads shouldn't panic - if there is code that panics on invalid network data, disk failure or whatever we should fix that. But I don't know where the code might be; #104 happened just once - it could be some irreproducible cosmic ray... This change is just to find it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

reconstruct command runs without progress

3 participants