Skip to content
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

Fix timings begin_date and end_date JSON export #2699

Closed
jcamiel opened this issue Apr 18, 2024 · 0 comments · Fixed by #2709
Closed

Fix timings begin_date and end_date JSON export #2699

jcamiel opened this issue Apr 18, 2024 · 0 comments · Fixed by #2709
Labels
bug Something isn't working
Milestone

Comments

@jcamiel
Copy link
Collaborator

jcamiel commented Apr 18, 2024

With --json option, timings are serialized to JSON like this:

          "timings": {
            "app_connect": 0,
            "begin_call": "2024-04-18 14:09:00.513250 UTC",
            "connect": 2412,
            "end_call": "2024-04-18 14:09:00.521567167 UTC",
            "name_lookup": 31,
            "pre_transfer": 2459,
            "start_transfer": 8035,
            "total": 8185
          }

begin_call and end_callshould be serialized to string using RFC-3339, with a microseconds maximum precision (nanoseconds are not supported in Python for instance):

          "timings": {
            "app_connect": 0,
            "begin_call": "2024-04-18T15:48:53.981976Z",
            "connect": 2376,
            "end_call": "2024-04-18T15:48:53.990433Z",
            "name_lookup": 23,
            "pre_transfer": 2418,
            "start_transfer": 8312,
            "total": 8389
          }
@jcamiel jcamiel added the bug Something isn't working label Apr 18, 2024
@jcamiel jcamiel added this to the 4.3.0 milestone Apr 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant