Node has a reference to its executor #218
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds a property
node.executor
which accesses the executor the node has been added to. Internally the node stores the executor as a weak reference to avoid a reference cycle.The purpose is to allow something with a node reference call executor functions. Specifically I want to make another PR where
TimeSource
callsnode.executor.create_task()
with time jump callbacks.A nice side effect is
node.executor
enforces that a node has only been added to one executor. This should prevent the same entities from being waited on in multiple wait sets.CI