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
This issue can be observed in the following blocks:
160079
160033
Background
This issue seems to specifically affect deploy syscalls called in an invoke transaction.
It occurs in this hint:
pubconstCHECK_NEW_DEPLOY_RESPONSE:&str = indoc!{r#" # Check that the actual return value matches the expected one. expected = memory.get_range( addr=ids.response.constructor_retdata_start, size=ids.response.constructor_retdata_end - ids.response.constructor_retdata_start, ) actual = memory.get_range(addr=ids.retdata, size=ids.retdata_size) assert expected == actual, f'Return value mismatch; expected={expected}, actual={actual}.'"#};
The issue seems to constructor_args being an empty vector.
Next steps
Write integration tests covering deploy_contact syscall in an invoke transaction.
Attempt to do a deploy with empty args?
The text was updated successfully, but these errors were encountered:
Affected blocks
This issue can be observed in the following blocks:
Background
constructor_args
being an empty vector.Next steps
The text was updated successfully, but these errors were encountered: