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

Inconsistent time format in API output #1093

Closed
1 of 13 tasks
tbnguyen1407 opened this issue Aug 17, 2022 · 3 comments
Closed
1 of 13 tasks

Inconsistent time format in API output #1093

tbnguyen1407 opened this issue Aug 17, 2022 · 3 comments
Labels
bug Something isn't working

Comments

@tbnguyen1407
Copy link

Which version are you using?

v0.20.0

Which operating system are you using?

  • Linux amd64 standard
  • Linux amd64 Docker
  • Linux arm64 standard
  • Linux arm64 Docker
  • Linux arm7 standard
  • Linux arm7 Docker
  • Linux arm6 standard
  • Linux arm6 Docker
  • Windows amd64 standard
  • Windows amd64 Docker (WSL backend)
  • macOS amd64 standard
  • macOS amd64 Docker
  • Other (please describe)

Describe the issue

Inconsistent time formats used by "created" and "lastRequest" of hlsMuxer

GET {{baseUrl}}/v1/hlsmuxers/list

{
  "items": {
    "path1": {
      "created": "2022-08-17T15:16:08.122224+08:00",
      "lastRequest": "2022-08-17 15:16:39 +0800 +08"
    }
  }
}

Describe how to replicate the issue

  1. start the server
  2. publish with any valid url
  3. read HLS output with ffplay
  4. call API to list hlsMuxers

Did you attach the server logs?

no

Did you attach a network dump?

no

Additional notes

Would be better if there is an option for raw epoch instead of formatted string for time fields.

@aler9 aler9 added the bug Something isn't working label Aug 23, 2022
aler9 added a commit that referenced this issue Aug 23, 2022
this fixes "lastRequest" in /v1/hlsmuxers/list that was encoded in a
wrong format
aler9 added a commit that referenced this issue Aug 23, 2022
this fixes "lastRequest" in /v1/hlsmuxers/list that was encoded in a
wrong format
@aler9
Copy link
Member

aler9 commented Aug 23, 2022

Thanks, now timestamps are always encoded with RFC3339.

@aler9
Copy link
Member

aler9 commented Oct 25, 2022

fixed in v0.20.1

@aler9 aler9 closed this as completed Oct 25, 2022
@github-actions
Copy link
Contributor

This issue is being locked automatically because it has been closed for more than 6 months.
Please open a new issue in case you encounter a similar problem.

@github-actions github-actions bot locked and limited conversation to collaborators Apr 29, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants