Other organizations make this information available. For example IERS should be a drop in replacement.
Potential impacts should be minimal at the moment. Users should, at most, see two warning messages related to leapseconds when using the toolkit (see below). A default leapsecond.dat file is included in the repository and no additional GPS / UTC leapseconds have been added since 2016. The next opportunity for a leap second change is December 31st.
> Leapsecond data update failed. This may cause problems with some functionality
> Continuing with out of date leap second data
For backwards compatibility we should consider creating a CLI utility that users can leverage to manually update this if they're unwilling to take a more recent software version.
GPS / UTC Leapsecond object generation in
dmcis currently failing because the retrieved resource (https://www.ietf.org/timezones/data/leap-seconds.list) is no longer available.Other organizations make this information available. For example IERS should be a drop in replacement.
Potential impacts should be minimal at the moment. Users should, at most, see two warning messages related to leapseconds when using the toolkit (see below). A default
leapsecond.datfile is included in the repository and no additional GPS / UTC leapseconds have been added since 2016. The next opportunity for a leap second change is December 31st.For backwards compatibility we should consider creating a CLI utility that users can leverage to manually update this if they're unwilling to take a more recent software version.