Fix incorrect requirements.txt and latency calculations when old ping replies come in after new pings are sent. #118
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 issue #114 and fixes issue #116
#116: Updated requirements pexpect version to 4.8.0 rather than 4.0.8
#114: Fixed a bug in which the latency in ms would be calculated incorrectly where upon receiving a reply, the latency since last packet was sent (not necessarily the packet the reply is for) would be calculated and displayed.
Packet send times are now stored and retrieved per packet sequence number, meaning latency calculations will use them instead of whenever the most recent packet was sent out. This retains accurate measurements among poor network conditions where packets arrive out of order (like in #114) as well as the case where the delay between pings is shorter than the real-world latency (such as pinging a JP server from US, where ping is over 200ms and ping delay is only 200).
This is my first open source contribution, any feedback or changes are welcome.