-
Notifications
You must be signed in to change notification settings - Fork 4
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
Parsing dont work right, time hopping... #5
Comments
Okay my fault, is a problem of the used parser approxidate... the microtime is to long for correct parsing with approxidate edit: microtime = nanotime |
The issue with trying to parse millis and nanos is that you don't know if it is millis or nanos without it being explicitly stated. Hence the reason we chose millis because it more suited the purpose at the time. Are you asking if I can add a ParseNano function? |
Yes, maybe it would nice to have the function. Because i use this in JSON and get only hopping dates. We have over 40k req/s so we need the exact time for problem reports. And cause of the given TimestampNano i thought it will also parse it correct. |
the
tts.String()
Time hopping always around, we have now 11:54 but the output hopping to 12:07, 11:50 etc.EDIT: Info to system: Alpine Linux (Linux 4.5.7-std-3 x86_64 ); go version go1.8.1 linux/amd64
The text was updated successfully, but these errors were encountered: