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 suspect a massive point of inefficiency with Azle is serialization/deserialization of nat8[]/blob. This presenting with this error when trying to send in blobs/nat8[]s as parameters to canister methods:
Error: The Replica returned an error: code 5, message: "Canister rrkah-fqaaa-aaaaa-aaaaq-cai exceeded the cycles limit for single message execution."
The limit seems to be between 10kb-25kb, but I believe in Rust and Motoko you can go all the way to the message limit and pass things in around 1-3mb in size. So we're a good couple orders of magnitude off.
The text was updated successfully, but these errors were encountered:
AzleIntoJsValue for all number vecs using ArrayBuffer
AzleTryFromJsValue fro all number vecs using ArrayBuffer
Open up issues or pull requests into boa to make conversion of Vec etc easier
Deal with non-public boa branch (open up issues to get this addressed)
Add AzleIntoJsValue and AzleTryFromJsValue vec transformations for all custom struct and enums (add to the derive macros) (might not have to do this because of the one weird trick)
Consider not converting everything into an ArrayBuffer, but instead into the actual typed arrays...we might need to mess with the TypeScript types to get this to work, I am not sure if we can alias nat8[] to something that isn't an array of numbers
I suspect a massive point of inefficiency with Azle is serialization/deserialization of nat8[]/blob. This presenting with this error when trying to send in blobs/nat8[]s as parameters to canister methods:
Error: The Replica returned an error: code 5, message: "Canister rrkah-fqaaa-aaaaa-aaaaq-cai exceeded the cycles limit for single message execution."
The limit seems to be between 10kb-25kb, but I believe in Rust and Motoko you can go all the way to the message limit and pass things in around 1-3mb in size. So we're a good couple orders of magnitude off.
The text was updated successfully, but these errors were encountered: