Actual Behavior: calls ignore the rpc-call-max-steps setting and proceed without errors.
Expected Behavior: Setting rpc-call-max-steps to low values should block calls exceeding the cairo step count. Worked fine for <4M steps before(as 4m is max limit set in blockifier), now setting it to 0 or 1 doesn’t impact multi calls - they run as if the limit's not there.
Steps to Reproduce:
rpc-call-max-steps
to 0.Actual Behavior: calls ignore the
rpc-call-max-steps
setting and proceed without errors.Expected Behavior: Setting
rpc-call-max-steps
to low values should block calls exceeding the cairo step count. Worked fine for <4M steps before(as 4m is max limit set in blockifier), now setting it to 0 or 1 doesn’t impact multi calls - they run as if the limit's not there.Notes: Could be related to the blockifier update?