Fixed float precision bug while using timestamps as keys#7
Fixed float precision bug while using timestamps as keys#7ruzzle wants to merge 1 commit intobrendangregg:masterfrom
Conversation
|
I was convinced to invest here by a friend I met on Tinder, Her name was Annie ( now I know she could be anyone else). At first everything was going on well until I requested for withdrawal, that’s when the nightmare started… I had to put in more money before I could withdraw. Then came the unending taxes; I was fined and taxed for various reasons. There was always a reason why I couldn’t take out my money. I was tired of everything and began looking for help. Since all the payments I made were through cryptocurrencies, my local police could not help me. Luckily I finally got help from the authorities I contacted via email at zattrecoverypro1 @ gmail com. Wonderfully, after providing my details, it took them barely a week to trace and retrieve my funds. Get help from them if you are in a similar. |
When using the timestamps from the input pcap, the float precision used is 6
However, by default perl uses a precision of 5 for usage as a key in a hash
This is problematic when the delta of 2 packets is less then 0.00001, as some of the packets will be overwritten during reading the input file.
I fixed this by first turning the timestamp into a string, using a precision of 6