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
Remove --captive-core-reuse-storage-dir flag #3798
Comments
If this is fixed in core 17.3.0 why do you need to wait for protocol 18 to go live? Older core releases are not supported per our security release model (30 days after a release we publish details of any potential security issue) . So it's fine to require newer core versions. As 17.4.0 is out, you can require 17.4.0 in your next Horizon release no problem. |
I was just running CC locally and this output reminded me about your comment:
As you can see there are still many Tier 1 validators running 17.0.0 and 17.1.0 and this GH issue requires 17.3.0 or later. |
Network is now at Protocol 18: moving this to Current Sprint. |
In #3715 we added a feature flag
--captive-core-reuse-storage-dir
(false
by default) to allow disabling permament buckets directory of Captive Stellar-Core. This was done because stellar/stellar-core#3085 could leave buckets dir corrupted. Now that bug is fixed in 17.3.0 we can schedule removing the feature flag when Protocol 18 is live (this will require everyone to upgrade to Stellar-Core 18.0.0 that contains a fix).The text was updated successfully, but these errors were encountered: