-
-
Notifications
You must be signed in to change notification settings - Fork 37
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
Add mtr #127
Comments
I'm not sure if that's gonna be a problem, but seems worth mentioning:
|
Yeah, it should be fine inside our containers :) But let me know if something unexpected comes up |
another note: |
It also makes it not-real time :( |
What should we do with MTR's ASCI color characters? They polute the output, to the point it makes it unreadable. Naturally, we gotta get rid of them for the parsed output, but should we keep them for the
|
definitely no, the question is if we need to do this manually or there is an option to disable it |
I can easily filter them out with single regex query, that's not an issue. I just wasn't sure if we want to manipulate the |
There is no value in keeping the colors and it will make the life easier for many people if its regular readable text. So lets remove it :) |
|
It happened randomly, and was especially noticible on production probes - it didn't happen on my local dev serv. If I'm right, it was caused by the fact we have to asynchroniously query ASN values, while we tried to keep progress events going, so we ended up overriding the result. Fixed.
fixed.
True, but not true. Some routes point to the same server, and MTR responds with... new routes under the same address. MTR in UI mode merges them together (i think?), but that doesn't seem right since they are seperate routes. Here's an example on I added a list of raw outputs to the measurement response, so we can debug it. We might delete or keep it later.
done. |
Here's another example of this duplication on https://gist.github.com/patrykcieszkowski/9afa8a01456096ccfd27dc924e992424 |
Another issue with private IPs when running mtr to google.com
|
Current state:
|
Some tests are randomly broken:
Also need to test cases when the endpoint doesnt resolve correctly. |
I believe this issue is now resolved. Have you noticed anything else wrong with MTR cmd? |
It looks good to me, but given the many edge-cases we encountered how about @MartinKolarik @ayuhito you also test our mtr? |
btw I don't think we've released any new probe version, and we changed a lot in the input, response schema etc. Maybe we should do it before testing anything. |
Everything was merged and deployed. You can now all test again MTR and maybe even the rest of the commands too to make sure the latest changes didn't break anything. |
Example binary command:
echo $?
The text was updated successfully, but these errors were encountered: