You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm having a compiler panic when trying to run tests that move __invmod to native rust code.
Expected Behavior
The test is not even running because the compiler panics.
Interestingly enough, when the oracle is returning badly formatted values the panic doesn't happen (the test doesn't pass).
Bug
To Reproduce
Switch to the reproduction branch git checkout kb/failing_oracle
git pull
switch the rust oracle directory cd oracle
run the rust RPC server cargo build && RUST_LOG=info cargo run
move back to the main dir cd ..
run the divmod test with the correct Oracle resolver
nargo test invmod --oracle-resolver http://127.0.0.1:3000
Workaround
None
Workaround Description
No response
Additional Context
No response
Project Impact
None
Blocker Context
No response
Nargo Version
nargo version 0.37.0, 1.0.0-beta.0 , and nightly
NoirJS Version
No response
Proving Backend Tooling & Version
No response
Would you like to submit a PR for this Issue?
None
Support Needs
No response
The text was updated successfully, but these errors were encountered:
Aim
I'm having a compiler panic when trying to run tests that move
__invmod
to native rust code.Expected Behavior
The test is not even running because the compiler panics.
Interestingly enough, when the oracle is returning badly formatted values the panic doesn't happen (the test doesn't pass).
Bug
To Reproduce
git checkout kb/failing_oracle
git pull
cd oracle
cargo build && RUST_LOG=info cargo run
cd ..
divmod
test with the correct Oracle resolvernargo test invmod --oracle-resolver http://127.0.0.1:3000
Workaround
None
Workaround Description
No response
Additional Context
No response
Project Impact
None
Blocker Context
No response
Nargo Version
nargo version 0.37.0, 1.0.0-beta.0 , and nightly
NoirJS Version
No response
Proving Backend Tooling & Version
No response
Would you like to submit a PR for this Issue?
None
Support Needs
No response
The text was updated successfully, but these errors were encountered: