I ran into a very strange problem. I am using the latest commit of ic-wasi-polyfill: 5e986cb3b95a58fbbf9386582f5c48847f22dcca
When I deploy my canister, in this case a Kybra canister using the RustPython library, I always get a [Canister rrkah-fqaaa-aaaaa-aaaaq-cai] Panicked at 'calledResult::unwrap()on anErrvalue: (CanisterError, "Canister rrkah-fqaaa-aaaaa-aaaaq-cai trapped: stack overflow")', src/lib.rs:164:12 (the important part is the stack overflow) in my post_upgrade function.
The post_upgrade function initializes the RustPython VM and does general setup. This function worked just fine before I upgraded to the latest ic-wasm-polyfill commit.
The crazy thing is that when I turn on the report_wasi_calls feature, the stack overflow goes away.
I ran into a very strange problem. I am using the latest commit of
ic-wasi-polyfill
: 5e986cb3b95a58fbbf9386582f5c48847f22dccaWhen I deploy my canister, in this case a Kybra canister using the RustPython library, I always get a
[Canister rrkah-fqaaa-aaaaa-aaaaq-cai] Panicked at 'called
Result::unwrap()on an
Errvalue: (CanisterError, "Canister rrkah-fqaaa-aaaaa-aaaaq-cai trapped: stack overflow")', src/lib.rs:164:12
(the important part is the stack overflow) in my post_upgrade function.The post_upgrade function initializes the RustPython VM and does general setup. This function worked just fine before I upgraded to the latest ic-wasm-polyfill commit.
The crazy thing is that when I turn on the
report_wasi_calls
feature, the stack overflow goes away.