Open sweebee opened 2 months ago
That is indeed an invalid timestamp. Are you generating that timestamp or is there a stack trace associated with this to see what line of code is generating that timestamp?
I guess I should say, it is probably invalid due to the year but I don't know what database you're leaving.
If you can provide me with some information like your database and the stack trace, tell me what date you're trying to put into the database (if it really is the date you want, why? Please use reasonable data to replicate the issue, I am unlikely to release a bugfix because dates 10k years in the future don't work).
The issue propably is caused by timestamp in your frontend which is in miliseconds
I'm trying this package, but it doesnt seem to work when pushing changes: