10 years ago, someone wrote a test for servo that included an expiry in 2026
mastodon.social - 78 poäng - 41 kommentarer - 73583 sekunder sedan
Kommentarer (6)
- andai - 2224 sekunder sedanInteresting, from the title I thought it was intentional, as a "forced code review." Apparently not, but now I really like that idea!
- samlinnfer - 661 sekunder sedani had to plant a 10 year time bomb in our SAML SP certificate because AFAIK there is no other way to do it. It’s been 7 years since then. Dreading contacting all the IDPs and getting them to update the SAML config.
- Alupis - 3348 sekunder sedanJust skimmed the PR, I'm sure the author knows more than I - but why hard code a date at all? Why not do something like `today + 1 year`?
- bombcar - 7572 sekunder sedanAny time constant will be exceeded someday.
An impossibly short period of time after the heat death of the universe on a system that shouldn’t even exist: ERROR TIME_TEST FAILURE
- db48x - 67894 sekunder sedanClassic!
But before you judge the fix too hashly, I bet it’s just a quick and easy fix that will suffice while a proper fix (to avoid depending on external state) is written.
- kristofferR - 3378 sekunder sedan[flagged]
Nördnytt! 🤓