Closed juansensio closed 2 months ago
Maybe a problem with the date set in the production environment?
do you have an example? for us it shows "Created 3 months ago" and similar...
I will upload a dataset and share in Discord the dates.
created shows some day offset, updated seems to be correct?!?
It looks like so... the code that creates a dataset can be found here.
As you can see, the creation date is not set and it is using the default value set by pydantic here.
Just created a dataset and I can see a shift of 3 hours (the updatedAt is the correct date).
Again, running the API locally works just fine but for some reason in the production environment there is that offset. Any ideas?
we just checked
there is no shift - it obviously uses the startup time of the process (at the moment 15d ago)
createdAt: datetime = datetime.now()
is not correct in https://github.com/earthpulse/eotdl/blob/main/api/api/src/models/dataset.py
thanks @totycro for example
Thanks. Changes are applied and working fine.
The Creation dates of datasets/models in the UI is not correct, some issue regarding the creation date may be happening.