-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Conversation
There is no reason for this function, tokio already blocks automatically until all tasks are ended. Another reason to remove this feature is `mpsc_background_tasks` unbounded channel. Recently this channel was reporting too many unprocessed elements. We assume that this was a result of a lot of very shot lived tasks that somehow flooded this channel.
I don't quite get why Also, do you think a burn-in is justified here? |
Me neither. I checked the code that is called there and we don't use anything self build, most of the stuff is coming from the futures crate directly. Basically it maps down to a
This is nothing critical. This stuff was only used to ensure that all tasks are stopped before the node shuts down, nothing more. |
bot merge |
Error: It's not possible to meet the minimal approval count of 1 in paritytech/polkadot#4336 |
* Companion for Taskmanager: Remove `clean_shutdown` paritytech/substrate#10314 * Update Substrate * Remove warning
* Companion for Taskmanager: Remove `clean_shutdown` paritytech/substrate#10314 * Update Substrate * Remove warning
There is no reason for this function, tokio already blocks automatically until all tasks are ended. Another reason to remove this feature is `mpsc_background_tasks` unbounded channel. Recently this channel was reporting too many unprocessed elements. We assume that this was a result of a lot of very shot lived tasks that somehow flooded this channel.
There is no reason for this function, tokio already blocks automatically until all tasks are ended. Another reason to remove this feature is `mpsc_background_tasks` unbounded channel. Recently this channel was reporting too many unprocessed elements. We assume that this was a result of a lot of very shot lived tasks that somehow flooded this channel.
There is no reason for this function, tokio already blocks automatically until all tasks are ended.
Another reason to remove this feature is
mpsc_background_tasks
unbounded channel. Recently thischannel was reporting too many unprocessed elements. We assume that this was a result of a lot of
very shot lived tasks that somehow flooded this channel.
polkadot companion: paritytech/polkadot#4336
skip check-dependent-cumulus