You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In this particular case, it looks like the timestamp is out by a factor of a thousand. That's harder to detect, and I'm not entirely sure what would cause it. We could try and detect the situation and multiply dates by a thousand if they seem too small, but I think before we invest in that we want to understand why this is happening.
holly-cummins
changed the title
Should not show '1970' if an extension date can't be determined
Should not show '1970' if bad data comes back for an extension date
Sep 15, 2023
See, for example (for the moment), https://quarkus.io/extensions/io.quarkiverse.ironjacamar/quarkus-ironjacamar
I assume we're getting a 0 for the date, but we should turn that into an undefined and display nothing.
Edit:
There are two parts to the fix:
The text was updated successfully, but these errors were encountered: