-
-
Notifications
You must be signed in to change notification settings - Fork 289
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
fix: prune invalid ssz objects #6875
Conversation
Performance Report✔️ no performance regression detected Full benchmark results
|
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
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.
@twoeths Looks like these two tests are failing
test/unit/util/pruneOldFilesInDir.test.ts > pruneOldFilesInDir > should delete old files in nested directories
test/unit/util/pruneOldFilesInDir.test.ts > pruneOldFilesInDir > should handle empty directories
Can we fix it?
unit tests are broken because we also delete the directory now if there are no files in it, anyways questionable to me, if we receive an new invalid ssz object the directory has to be created again, downside of just keeping it around is negligible imo as it's part of |
🎉 This PR is included in v1.20.0 🎉 |
Motivation
We implemented a feature to prune invalid ssz objects but still see a lot of them there
Description
persistInvalidSszObjectsDir
from chain options instead ofargs