-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Validate tick_duration
millisecond resolution
#178
Open
sgbalogh
wants to merge
2
commits into
tokio-rs:main
Choose a base branch
from
sgbalogh:validate-tick-duration
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -193,6 +193,11 @@ impl Builder { | |
panic!("Maximum message latency must be greater than minimum."); | ||
} | ||
|
||
if self.config.tick.as_nanos() % Duration::from_millis(1).as_nanos() != 0 { | ||
// Tick duration is used for tokio::time::sleep, which requires millisecond resolution. | ||
panic!("Tick duration resolution is in milliseconds, but value provided would require higher.") | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Consider adding the provided value in the panic message to aid in debugging. |
||
} | ||
|
||
let world = World::new( | ||
self.link.clone(), | ||
rng, | ||
|
@@ -218,4 +223,12 @@ mod tests { | |
.max_message_latency(Duration::from_millis(50)) | ||
.build(); | ||
} | ||
|
||
#[test] | ||
#[should_panic] | ||
fn invalid_tick_duration() { | ||
let _sum = Builder::new() | ||
.tick_duration(Duration::from_micros(500)) | ||
.build(); | ||
} | ||
} |
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it be simpler to just check
< Duration::from_millis(1)
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think someone could provide a value that was > 1 ms, but had a higher resolution, e.g.
Duration::from_micros(1500)
, which I believe we would want to disallow still given that comment ontokio::time::sleep
.Though, we might want to disallow
Duration::ZERO
in addition I suppose?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think it needs to be this restrictive. Given that the runtime is paused we aren't actually running for the duration, we are simply advancing time by it.
Duration::ZERO
is a good callout, and I'm not actually sure what would happen in that case. My guess is that nothing runs.