Skip to content
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: update rocksdb from v0.19 to v0.21 #2822

Merged
merged 1 commit into from
Jul 12, 2023
Merged

fix: update rocksdb from v0.19 to v0.21 #2822

merged 1 commit into from
Jul 12, 2023

Conversation

cronokirby
Copy link
Contributor

Depending on the C++ toolchain used by the underlying system, builds of rocksdb might fail because of an issue documented in:

facebook/rocksdb#11118

(In short, the code relied on headers importing other headers, rather than what the standard guarantees headers to export; thus code may not compiler on all toolchains).

Version 0.21 of the crate fixes this issue, by relying on a later version of the underlying rocksdb library.

For the rust crate, this issue showed up in:

rust-rocksdb/rust-rocksdb#772

On Linux/Manjaro I ran into this issue as well, but I expect that other people following along with the docs might run into it as well, so probably worth updating, unless there's some issue with doing so.

Depending on the C++ toolchain used by the underlying system, builds of
rocksdb might fail because of an issue documented in:

facebook/rocksdb#11118

(In short, the code relied on headers importing other headers, rather
than what the standard guarantees headers to export; thus code may not
compiler on all toolchains).

Version 0.21 of the crate fixes this issue, by relying on a later
version of the underlying rocksdb library.

For the rust crate, this issue showed up in:

rust-rocksdb/rust-rocksdb#772

On Linux/Manjaro I ran into this issue as well, but I expect that other
people following along with the docs might run into it as well, so
probably worth updating, unless there's some issue with doing so.
@cronokirby cronokirby temporarily deployed to smoke-test July 12, 2023 14:52 — with GitHub Actions Inactive
Copy link
Member

@redshiftzero redshiftzero left a comment

Choose a reason for hiding this comment

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

When CI passes this LGTM!

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.

2 participants