Add a mechanism to exclude forks at serialization time #3063
+111
−62
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.
Previously, only the forks listed in the
forks
parameter were included; they were restored on deserialization.This doesn't work too well if there is a large number of fork to serialize, because listing them explicitly requires cumbersome bookkeeping. And really, if the history has 1000 forks, we don't want to know about them.
So I am changing the default so that all the forks rooted at a trajectory are serialized, except those listed in the
excluded
parameter. The ones that we are interested in, i.e., the ones that we want to restore on deserialization, are listed intracked
.