-
Notifications
You must be signed in to change notification settings - Fork 198
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
JS Test Schema not matching #2578
Comments
There might be a chance this is not our fault |
When trying to run this failing test locally, I'm finding that txns fail because the max_fee is set too low. When overriding the overall_fee by 2*overall_fee, the txns pass, and I am able to replicate the error. It looks like we return
but steps is NOT allowed to be zero according to the specs
It looks like blockifier is returning a 0 value for steps. Which is fine for the rpcv8 spec because it doesn't have any notion of "steps", but it's a breaking change for rpcv7 which requires a non-zero value for steps. Overriding the steps causes the starknet.js test to pass, specifically |
@rianhughes What result did your experimental PR give ? |
@hudem1, the starknet.js tests passed in the CICD pipeline. https://github.com/NethermindEth/juno/actions/runs/13590192622/job/37994941475 (Note: that my hack broke the starknet.rs test, but I only wanted to quickly confirm that this solves the problem, not propose a concrete solution) |
The trace transaction test for v0_7 fail due to not matching schema:
The text was updated successfully, but these errors were encountered: