After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 219643 - is_overdue() does not handle DATE values correctly
is_overdue() does not handle DATE values correctly
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Tasks
pre-1.5 (obsolete)
Other All
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2002-01-31 01:35 UTC by Federico Mena Quintero
Modified: 2013-09-10 14:02 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Federico Mena Quintero 2002-01-31 01:35:44 UTC
Description of Problem:
The tasks table marks tasks that are due tomorrow as being due today if the
current UTC time is past midnight.  E.g. a user at UTC offset -6 will start
seeing tasks due tomorrow as being due today starting around 18:00.
This happens because calendar-model.c:is_overdue() does not handle DATE
values correctly.

Steps to reproduce the problem:
1. Add a task.  Make it due tomorrow; make sure this is a DATE value and
not a DATE-TIME value by not assigning a time to it.
2. Wait until it is midnight in England.
3. Look at the blue tasks!

Extra info:
calendar-model.c:is_overdue() is not checking for dt.is_date being set.  In
this case, dt.tzid will be NULL (DATE values don't have a timezone) and
thus it will look like we are requesting the UTC timezone.  It should be
using model->priv->zone if dt.is_date is set.
Comment 1 Richard Zach 2002-02-06 08:23:59 UTC
This is probably the same bug as bug 218875, so please fix that when
you fix this one.  
Comment 2 JP Rosevear 2002-08-01 18:35:43 UTC
We should now handle all the cases correctly, including when a task is
due during the day some time.