fix event storage for concurrent execution #43
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.
BEGINRELEASENOTES
ENDRELEASENOTES
The pipeline running function introduced in #29 was reusing the parsed graph (graph topology and description) instead of creating a new instance for each event. It went unnoticed that the
schedule_graph
methods mutates the graph by using it for storing algorithms` futures.As a fix two new structs are introduces:
DataFlowGraph
to held immutable information about graph topology and algorithms, and possibly do some graph topology cachingEvent
holding mutable event specific storage and access to immutableDataFlowGraph
schedule_graph
is renamed toschedule_graph!
to indicate it mutatesEvent