- Issue created by @endless_wander
- πΊπΈUnited States owenbush Denver, CO
What version of core have you upgraded to? I just upgraded my local to 10.2.4 and I do not see these issues.
The event registration field is effectively a date range item under the hood with some additional columns. My initial thought was that it was related to reworking timestamp fields to prevent the 2038 bug, but it doesn't look like that has landed yet: π Timestamp field items are affected by 2038 bug Needs work
I wish there was a way to identify which of the columns is problematic, in the past it has shown that, but from your error it doesnt seem to?