Accumulate run signals with scoped labels not objects #173
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.
The scoped label will always be unique, so just store that.
The point is that as we move towards storage and serialization, this gives one less complex object that needs to live on the node.
Right now I lean towards restoring graphs by re-executing from the top, but just not actually re-running nodes who have the same input as they had at their last execution (optional (for slow nodes), evaluated by hash comparison). In that case, we don't need to reload this data as the set will get re-populated at run-time. However, IMO it doesn't hurt to have it serialized, and it will be necessary for finding graph state if we wind up taking a different path to reloading.