This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/

[mat-wg] New on RIPE Labs: Reviewing the 2016 Leap Second

• Previous message (by thread): [mat-wg] [atlas] RIPE Atlas APIs
• Next message (by thread): [mat-wg] New on RIPE Labs: Reviewing the 2016 Leap Second

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Mirjam Kuehne mir at ripe.net
Mon Jan 16 10:11:22 CET 2017

Dear colleagues,

Last month we covered the 2015 leap second ahead of the insertion of a
leap second at the very end of 2016. As stated previously, leap seconds
can trigger poorly-tested code paths; leap second handling always
unearths bugs and issues. This one was no exception!

Please find more details on RIPE Labs:

https://labs.ripe.net/Members/stephen_strowes/reviewing-the-2016-leap-second

Kind regards,
Mirjam Kuehne
RIPE NCC

• Previous message (by thread): [mat-wg] [atlas] RIPE Atlas APIs
• Next message (by thread): [mat-wg] New on RIPE Labs: Reviewing the 2016 Leap Second

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ mat-wg Archives ]