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
Azle itself seems to have a query caching issue. If you create a query method in Azle using the class or functional API, without parameters, that just prints, you can only call the function once...and then after a long while (I think it has to be more than 5 minutes) you can finally log again. If you create a similar method in the Rust code in Azle directly, this issue does not present itself. It seems to be something to do with the Wasm binary manipulation and the execute_method_js...but I am not sure what the issue is.
The text was updated successfully, but these errors were encountered:
Azle itself seems to have a query caching issue. If you create a query method in Azle using the class or functional API, without parameters, that just prints, you can only call the function once...and then after a long while (I think it has to be more than 5 minutes) you can finally log again. If you create a similar method in the Rust code in Azle directly, this issue does not present itself. It seems to be something to do with the Wasm binary manipulation and the execute_method_js...but I am not sure what the issue is.
The text was updated successfully, but these errors were encountered: