Repository navigation
Conversation
Signed-off-by: dkm <2094657017@qq.com>
The new tests have no stdout or stderr output. Use empty expected files instead of files containing a newline.
NearCai
force-pushed
the
pr/depart-offset
branch
from
October 30, 2026 15:46
3cb0b6e to
19fb671
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #10374.
As suggested in the issue, the departure offset tool now supports shifting departures
in both directions:
--random-depart-offset MIN,MAXshifts every departure by a random value chosenuniformly from
[MIN,MAX[(e.g.-1800,900);--seed(default 42) makes thesequence reproducible
--depart-offsetas wellbegin/end) are clamped to 0Documentation and two tests (
offset_random,offset_negative) are included.Local verification: ran both cases and compared the output with the recorded
fixtures; identical.