You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Usage of "publish_time" field in BasePublishedQuerySet.get_published (and get_unpublished) may sometime returns an empty queryset.
It does not happen in tests since we forced a fixed neutral datetime, it is only reproducible for now on frontend when running development server.
This is often raised during night around after midgnight. This is likely to be caused by the fact we use a combination of a date field and a time field which are not technically the same thing that a singular datetime in a queryset.
First thing it to create an unittest to reproduce this wrong behavior in test environment, then fix it.
The text was updated successfully, but these errors were encountered:
The better way to fix would be to get back to a datetime but for now i don't even remember why did i splitted this to distinct date and time fields and so i don't see what the migration would involve..
Usage of "publish_time" field in
BasePublishedQuerySet.get_published
(and get_unpublished) may sometime returns an empty queryset.It does not happen in tests since we forced a fixed neutral datetime, it is only reproducible for now on frontend when running development server.
This is often raised during night around after midgnight. This is likely to be caused by the fact we use a combination of a date field and a time field which are not technically the same thing that a singular datetime in a queryset.
First thing it to create an unittest to reproduce this wrong behavior in test environment, then fix it.
The text was updated successfully, but these errors were encountered: