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
log::error!("Failed to figure out correct wait hold bound");
return;
}
This log::error can be called in case message have not enough gas to be added in the wait list. In most cases this is restricted by core-processor checks, but it does not protect cases when message will be added to waiting init list.
So, if some program or user will send error to uninitialised program with specific amount of gas, than message will be forgotten. So, it will be never consumed and gas node will stay forever in storage.
Problem
There can be some cases when waiting init message is not going to be appended into wait list because of lock of gas.
gear/pallets/gear/src/internal.rs
Lines 338 to 348 in 9a37ccb
This
log::error
can be called in case message have not enough gas to be added in thewait list
. In most cases this is restricted by core-processor checks, but it does not protect cases when message will be added towaiting init
list.So, if some program or user will send error to uninitialised program with specific amount of gas, than message will be forgotten. So, it will be never consumed and gas node will stay forever in storage.
Steps
You can try this test in pallet-gear:
Gas limit amount
210_105_500
has been found, so that the case would happen.Possible Solution
wait list
then reply with an error.The text was updated successfully, but these errors were encountered: