I am trying to make an inter-canister call to call another canister on a successful upgrade. However, it looks like post_upgrade cannot be async. This is the error that I’m seeing: [image] #[post_upgrade] must be above a function. expected one of: for, parentheses, fn, unsafe, extern, identifie…

Use spawn. [image] Heartbeat improvements / Timers [Community Consideration] Developers Is there a way to call async functions (i.e. raw_rand()) within the function invoked by set_timer/set_timer_interval?

Maybe use the new timer api to call your function after 1 nano second…it should be the next thing called most of the time. You can add a halt blocker if you need a guarantee.

This might work. Let me try. Although, seems to be a total hack. What’s a “halt blocker”? @skilesare

Just do a check of a bool at the top of every update function. Set it to false at the end of your post upgrade and true at the end of your timer.

It does not work. Basically, a timer expects a function that doesn’t return anything whereas an async fuction returns a type of Future. The function has to be an async function because inter canister calls are async and need to be await-ed. This is the error message I see: error: expected fn() -> …

Thank you. This worked. Although there’s a minor caveat. Calling spawn directly from the post_upgrade doesn’t work. It generates the following error. [image] “ic0_call_new” cannot be executed in init mode However, calling the timer with a nanosecond delay and using spawn with the async functi…

This has come up in other threads too: [image] Cross-canister compatible Post-Init hook Developers TLDR; Would a post-init hook that allows cross-canister calls be beneficial? I have a need to make a cross-canister call one time, at canister initialization (see this pos…

I think the caveat with this approach based on the threads I linked to is that it doesn’t guarantee that other messages aren’t processed before your timer function is called. That might be fine for this use case depending on what you want to do.

Yep, this is a HACK. But it gets me unstuck for now. Would definitely appreciate a well thought out alternative, though.

Put it another way, perhaps if all messages were to be dropped for all update calls to the canister, that might work? I will make a change to dos( GitHub - icdev2dev/dos: Some Denial of Service Defenses for SmartCanisters on IC ) to add a proposal type of ‘*’ to accommodate this. The query calls wo…

Question: How do I make an inter_canister call from the post upgrade hook?

Developers Rust

mparikh January 2, 2023, 4:15pm 6

Use spawn.

Topic		Replies	Views
Issues with ic_cdk::spawn and Inter-Canister Calls Rust	3	116	September 25, 2024
Will an upgrade timer Developers rust	9	123	November 9, 2024
Cross-canister compatible Post-Init hook Developers	11	1109	December 7, 2022
Question regarding timing of intercanister update calls during heartbeat Language Support Motoko	4	535	May 11, 2022
Any possibility to run an async function inside `#[pre_upgrade] fn pre_upgrade() {}` function? Developers Discussing	4	235	February 20, 2024

Question: How do I make an inter_canister call from the post upgrade hook?

Related topics