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

[Draft] Running experiments using latest env in core and flipping curr to latest env in rust bridge #4286

Draft
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

anupsdf
Copy link
Contributor

@anupsdf anupsdf commented Apr 16, 2024

What?

Running an experiment to see if core can be build with latest env and curr can point to that in the rust bridge. Doing this experiment only for core-vnext feature.
On limitation is that when latest env is bumped to a new version which hasn't been released, we will see errors like this,

anuppani@Anups-MBP stellar-core % ./src/stellar-core version                                                                                                
thread '<unnamed>' panicked at src/rust/src/lib.rs:594:10:
calculating global dep tree of Cargo.lock: Resolution("failed to find dependency: soroban-env-macros 21.0.0 (git+https://github.com/stellar/rs-soroban-env?branch=main)")
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
fatal runtime error: failed to initiate panic, error 5
zsh: abort      ./src/stellar-core version

Checklist

  • Reviewed the contributing document
  • Rebased on top of master (no merge commits)
  • Ran clang-format v8.0.0 (via make format or the Visual Studio extension)
  • Compiles
  • Ran all tests
  • If change impacts performance, include supporting evidence per the performance document

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.

None yet

1 participant