This repository has been archived by the owner on May 25, 2023. It is now read-only.
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.
It turns out that environment variables set inside
.cargo/config
are only seen by cargo if ran from the same workspace. The env vars are not seen if another 3rd crate imports this as a dependency, leading to compilation errors, leading to errors like:Since there are other ways to solve this issue this config was removed in favor of:
sequencer-relayer-proto
that owns the protobuf definitions and takes care of the rust codegen for protobuf;sequencer-relayer-test
because that is were the files are used (nice extra:test-environment.yml
is now generated from a test; as the main entry point for the integration tests it is now protected by CI).