We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When using MTR inside a Docker container on MacOS, it's possible to have negative latency values.
The MTR command used is mtr -4 -i 0.2 -c 20 --json google.com.
mtr -4 -i 0.2 -c 20 --json google.com
Maybe this is related to the way Docker deals with the clock on MacOS: https://www.docker.com/blog/addressing-time-drift-in-docker-desktop-for-mac/
I thought the PR #281 about the monotonic clock would solve the issue but it's not working.
A reproducer is available at https://github.com/levesquejf/mtr-bug-negative-latency
The text was updated successfully, but these errors were encountered:
No branches or pull requests
When using MTR inside a Docker container on MacOS, it's possible to have negative latency values.
The MTR command used is
mtr -4 -i 0.2 -c 20 --json google.com.Maybe this is related to the way Docker deals with the clock on MacOS: https://www.docker.com/blog/addressing-time-drift-in-docker-desktop-for-mac/
I thought the PR #281 about the monotonic clock would solve the issue but it's not working.
A reproducer is available at https://github.com/levesquejf/mtr-bug-negative-latency
The text was updated successfully, but these errors were encountered: