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

Allow building client crates without rocksdb #4892

Merged
merged 4 commits into from
Oct 9, 2024
Merged

Conversation

cronokirby
Copy link
Contributor

This required:

  • feature gating cnidarium in penumbra-app
  • removing the stateless transaction check in the view crate
  • removing the ceremony contribution command from pcli

Closes #4885

Checklist before requesting a review

  • If this code contains consensus-breaking changes, I have added the "consensus-breaking" label. Otherwise, I declare my belief that there are not consensus-breaking changes, for the following reason:

    Only client code was changed, the non-client code that was changed was only changed to have the public API be reduced without certain default features enabled. PD should be completely unchanged by this fix.

How to test this:

run cargo build --bin pcli -p pcli (and pclientd, and pindexer) and observe that rocksdb is not built.

This required:
- feature gating `cnidarium` in `penumbra-app`
- removing the stateless transaction check in the view crate
- removing the ceremony contribution command from `pcli`

Closes #4885
The first point of three was removed, along with the associated
functionality of performing stateless checks, so let's renumber the
comments to make sense.
@conorsch
Copy link
Contributor

conorsch commented Oct 9, 2024

Great work. I recorded some of the research findings in #4885. Testing locally, cargo build -p pcli generates a lot of warnings, so I'll stick with cargo build --bin pcli myself for the nonce.

@conorsch conorsch merged commit 705ad9e into main Oct 9, 2024
13 checks passed
@conorsch conorsch deleted the 4885-app-crate-deps branch October 9, 2024 20:00
@cronokirby
Copy link
Contributor Author

I think a lot of the warnings might just be that certain package code paths become unused without certain features

conorsch added a commit that referenced this pull request Oct 10, 2024
Follow-up to #4892. During review of that PR, I noticed that `cargo run
-p pcli` was emitting a lot of warnings about unused imports.
Here I try to address those warnings, by adding more conditional
imports based on the `component` feature.
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.

app crate doesn't keep component code behind feature flag
2 participants