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
ingest/ledgerbackend: Captive-Core fixes to support Stellar-Core 17.1.0 #3694
ingest/ledgerbackend: Captive-Core fixes to support Stellar-Core 17.1.0 #3694
Changes from 3 commits
93857c9
666b1e5
ca4365d
2c0e5e0
12be118
ed5e878
3d28e9e
3200baf
2162bf3
5bc56f9
226839c
e8525cd
36251ee
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.
if the buckets are corrupted what happens if we don't remove the directory? will captive core be unable to start at all? should we also remove the directory on linux in the scenario that captive core does not shutdown gracefully and we have to use sigkill?
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.
Good point. I believe the change in 3d28e9e should fix it (remove folder if there was an error terminating the process).
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.
I don't see how
r.processExitError != nil
implies that the process must have been terminated by sigkill. Isn't the scenario below possible?r.processExitError
is assigned the context error which is non nilThere 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.
I forgot about
context.Cancelled
- does 3200baf look good now?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.
@bartekn I ran it locally and it seems to work. it might be worth adding an assertion in the integration tests here:
https://github.com/stellar/go/blob/master/services/horizon/internal/test/integration/integration.go#L252
if we're running the integration tests on windows with captive core then we expect that the buckets directory to still exist after horizon has shut down