core: spacing-requirements: handle several zones before first signal #7480
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.
Fix a rare bug that has been identified by the fuzzer, there's a regression test on the branch
ech/ts2-fuzzer
(though it's not related to train schedules v2).We properly generate requirement only from the first seen signal, with a special case for the first zone. That special case needs to be generalized to all zones between the start and first signal.