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

Start - Timestamps with different formats #348

Closed
felix2507 opened this issue Jun 27, 2022 · 5 comments
Closed

Start - Timestamps with different formats #348

felix2507 opened this issue Jun 27, 2022 · 5 comments
Assignees
Labels
bug Something isn't working

Comments

@felix2507
Copy link

When subscribing to the different topics, we receive many different formats for the "start"-property in the "data"-Element. We would have expected to receive 1 format or at least patterns following the same ISO-Standard.
for example:
YouFM: 2022-06-15T08:36:33 (LocalDateTime)
MDR Sachsen: 2022-06-24 11:16:58 (LocalDateTime)
1Live: 2022-06-24T11:40:42.482+02:00 (OffsetDateTime)

Our expectation was to always receive an OffsetDateTime.

@frytg frytg added the bug Something isn't working label Jun 27, 2022
@frytg
Copy link
Member

frytg commented Jul 19, 2022

RFC for the ISO8601 specs: https://datatracker.ietf.org/doc/html/rfc3339#section-5.8 for our investigation

@rafaelmaeuer
Copy link
Contributor

Waiting for rollout of Eventhub v1.3.6 to identify all LRAs using wrong timestamps (adds filter-option for publisher-ids)

@rafaelmaeuer
Copy link
Contributor

rafaelmaeuer commented Jul 25, 2022

This is the current state of timestamp usage from all sending broadcasters:
Bildschirmfoto 2022-07-25 um 16 53 29
With the suggestion to use OffsetDateTime this results in a call to action for:

  • BR: use correct offset (+02:00)
  • HR: use correct format (OffsetDateTime)
  • MDR: use correct format (OffsetDateTime)
  • RadioBremen: use correct offset (+02:00)
  • RBB: use correct format (OffsetDateTime)

@saerdnaer
Copy link
Contributor

saerdnaer commented Aug 3, 2022

@rafaelmaeuer Danke für den Hinweis, wir haben das Problem für den BR jetzt auf TEST + PROD behoben.

@frytg
Copy link
Member

frytg commented Mar 7, 2023

Expecting all partners to have resolved this problem. If not, please coordinate between each other.

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

No branches or pull requests

4 participants