Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
feat(store/v2): Add Pruning Tests & Fix SQLite & PebbleDB Pruning #18459
feat(store/v2): Add Pruning Tests & Fix SQLite & PebbleDB Pruning #18459
Changes from 25 commits
ff31990
b93cbcf
20a687d
a4e2e6e
18983d5
1120a92
18c5e20
1836016
e8296c0
168d0c4
7d7ac92
224998f
cd14557
b85d911
8fc7e93
49c6c6c
3a11bb9
08113b4
035fafd
ba3cab5
930dbd4
b65a4c1
cb6aa04
582b11a
c44fd82
94bc2bb
d903a1e
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
in most environments this would be true, is there a reason to setting this to false for testing?
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.
Yes, just to make the unit tests faster. Not a strong reason, but it helps speed up CI testing time. (11.994s vs 1.214s)
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.
amazing!! could you add a short comment saying this. Would help for future readers
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.
gotcha
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.
The change to set the database sync behavior to false for speeding up CI tests is reasonable, but it should be documented in the code as per the discussion in the comments. A comment should be added to explain why
db.SetSync(false)
is being called, to provide context for future maintainers.if err == nil && db != nil { + // Set sync to false to speed up CI tests (11.994s vs 1.214s) db.SetSync(false) }
Commitable suggestion