Ethan Setnik
Ethan Setnik
Same issue in v7.6.0
Not stale. Still an issue in v8.7.0
I'm not sure if this is related but I am also seeing some errors when `Interval.after` ends up calculating an end range in a different timezone and generates an error...
This occurred in production to one of our users and i've been unable to reproduce it. However, I think the timezones shouldn't actually matter in this case and the function...
Ok, could a browser bug have caused this issue? I don't have any other information other than what's provided in our Sentry report. But one of our users definitely crashed...
Here's another example with as much detail as I can gather: Crash occurred at: Jun 5, 2024 2:45:16 AM UTC according to the client browser Error message: Invalid Interval: end...
Hi I just wanted to report we are still seeing this issue in production. 26 instances across three users. I have no idea what could be going on.
FYI I am also able to reproduce this with the following code. ```ts // instead we move both start and end date to the local zone to ensure the //...
@diesieben07 I am seeing very strange results when adding debug information: Using the following code: ```tsx const startDate = item.scheduledDateLocal.toLocal(); const endDate = startDate.plus({ milliseconds: item.duration }).toLocal(); const systemZone =...
> I am again begging you to please provide the input I have requested: As I cannot reproduce this on my own system I have to wait for it to...