-
Leap seconds are not yet correctly treated in data checks and data treatment at all. Should be related to the way how python datetime works with leap seconds.
Question by Hiro Toh
-
I was running a calendar conversion for Islamic hijri calendar. I stumbled across an error in interpreting one of the dates, which is between JD = 1976791,1976792. In julian calendar, that date is sup…
-
At the time of writing, the documentation reads
> represents the number of seconds that have elapsed
and
> does not take leap seconds into account
I found this wording confusing. At first …
-
I'm writing this issue to try and summarize all the possibilities for leap seconds handling in chrono, hopefully this will help making a decision :) (I can't find a checkbox to allow edits by maintain…
-
### What should you do if you want leap second support in Jiff?
The most effective thing you can do is leave a comment in this issue with a _detailed_ account of why you want leap second support. L…
-
### What happened?
I have two desktops both running Fedora 41, Gnome, and Wayland. I start the first as the server and second as the client. I accept the dialog for input/interaction from Gnome on bo…
edgan updated
3 weeks ago
-
The standards.md document currently states:
> Structure is:
> ```yaml
> time: 2016-082T23:59:60Z
> type: +
> description: Positive leap-second (a 61-second minute)
> correction_data:
> - …
-
It happened that a Muflus killed a h4ck while the 1st one was already dead, but did the leap right before dying.
Seems like the leap still triggered when landed, but the muflus was dead at the beginn…
-
[Primitive Values](https://zed.brimdata.io/docs/v1.18.0/formats/zson#23-primitive-values) in the 1.18 docs show that "month" is not included unit in the type:
> Valid time units are "ns" (nanosecon…
-
Migrated from [rt.cpan.org #71272](https://rt.cpan.org/Ticket/Display.html?id=71272) (status was 'open')
Requestors:
* zefram@fysh.org
From zefram@fysh.org on 2011-09-27 12:05:51:
$ perl -MDateTime…