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
Limit network actions to tracked chains (in main) (#2393)
* Add a `tracked_chains` field to `ChainWorkerState`
Prepare to only create network actions for the set of tracked chains.
* Add a `tracked_chains` field to `WorkerState`
Share it with the created chain worker actors.
* Add a `tracked_chains` field to `Client` type
Keep track of the chains that client is interested in.
* Select tracked chains when starting
Specify which chains should be tracked by a new `Client`.
* Forward tracked chains to `WorkerState`
Configure the worker based on the client's selection.
* Only create network actions for tracked chains
Avoid handling chains that aren't interesting to the client.
* Add `retry_pending_cross_chain_requests` helper
Allow resending messages intended for chains that weren't tracked when
the outgoing message was scheduled, but became tracked later.
* Add `Client::track_chain` method
Allow adding more chains to the initial set of tracked chains.
* Track newly created chains
Ensure that chains that the client open are tracked.
* Ensure newly assigned chain is tracked
So that the worker can properly handle it.
* Track chains used in benchmark
Ensure that they are properly executed during the benchmark.
* Add a TODO to merge tracked chains set
Remember to replace the quick-fix with a more comprehensive refactor.
* Track chains created during block execution
Check all executed blocks for messages that open new chains, and add the
new chain IDs to the set of tracked chains.
0 commit comments