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
Due to the Message Queue Limit on subnets and canisters, the operation of the contract will be blocked. But the developer can't know when this limit is triggered by the code. So it is suggested to add messageQueueLeft() method to ExperimentalInternetComputer.
This would allow application scenarios like the following:
if (ExperimentalInternetComputer.messageQueueLeft().subnet < 100 or ExperimentalInternetComputer.messageQueueLeft().canister < 10) {
throw Error.reject("Network is busy!");
};
The text was updated successfully, but these errors were encountered:
Thank you for your reply! IC exposing some key information to Canister will help developers better control the business logic, and hopefully the dfinity foundation will move forward with this internally.
Due to the Message Queue Limit on subnets and canisters, the operation of the contract will be blocked. But the developer can't know when this limit is triggered by the code. So it is suggested to add
messageQueueLeft()
method to ExperimentalInternetComputer.messageQueueLeft : () -> { subnet: Nat; canister: Nat }
This would allow application scenarios like the following:
The text was updated successfully, but these errors were encountered: