So guess who wrote a convoluted date comparison conditional instead of using `Temporal.ZonedDateTime.compare()` like an intelligent human being and ended up hitting an edge case where future scheduled calls started getting cleaned off the database instead of past ones?

Iโ€™ll give you a hint: has two thumbs and his name is Aral ๐Ÿคฆโ€โ™‚๏ธ

Anyway, just restored things from yesterdayโ€™s backup and sent a direct message to everyone scheduled for a Gaza Verified video verification call apologising for the confusion and explaining what happened.

Moral of the story: stick to the Temporal API and use its methods if youโ€™re implementing anything even remotely non-trivial involving dates, especially if there are timezones involved. (You can use a Temporal API polyfill in Node.js โ€“ Iโ€™ve been using temporal-polyfill.)

Now Iโ€™m going to expire for the evening.

๐Ÿ’•

0

If you have a fediverse account, you can quote this note from your own instance. Search https://mastodon.ar.al/users/aral/statuses/115968665356893336 on your instance and quote it. (Note that quoting is not supported in Mastodon.)