Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 330244 - Daily Tasks Invisible in Scheduled View on Week Rollover
Summary: Daily Tasks Invisible in Scheduled View on Week Rollover
Status: RESOLVED DUPLICATE of bug 250865
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Mylyn Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-15 08:54 EST by Emerson Murphy-Hill CLA
Modified: 2014-05-02 19:10 EDT (History)
2 users (show)

See Also:


Attachments
Video of bug (20.77 MB, video/avi)
2011-02-13 11:08 EST, Emerson Murphy-Hill CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Emerson Murphy-Hill CLA 2010-11-15 08:54:10 EST
Build Identifier: I20100608-0911

Last night (Sunday), I had a bunch of tasks scheduled for "This Week" and some scheduled for Monday. This morning (Monday), there are no tasks displayed under the "Monday-Today" category of the scheduled tasks, or any other day this week.

For example, I've got a task "Change dropbox." It shows up in the Categorized view, and mousing over, I see that it's scheduled for "Monday." When I switch to the Scheduled view, it doesn't appear under "Monday - Today", nor does it appear in this view at all when searched for. The "Change dropbox" task is in my .tasks.xml file. Now after I edit the scheduled date for Today (not really a change, but the task editor marks it as dirty), the task will show up under the "Monday-Today" category.

I'm not sure how to reproduce this.

Tried exporting and importing tasks. It caused about 30 stack traces of the form (and a very incomplete set of tasks being imported):

java.lang.NullPointerException
at org.eclipse.mylyn.internal.tasks.core.TaskList.fireDelta(TaskList.java:260)
at org.eclipse.mylyn.internal.tasks.core.TaskList.notifySynchronizationStateChanged(TaskList.java:494)
at org.eclipse.mylyn.internal.tasks.core.sync.SynchronizeQueriesJob.updateQueryStatus(SynchronizeQueriesJob.java:336)
at org.eclipse.mylyn.internal.tasks.core.sync.SynchronizeQueriesJob.run(SynchronizeQueriesJob.java:195)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)



Reproducible: Didn't try
Comment 1 Emerson Murphy-Hill CLA 2010-11-15 10:48:38 EST
I've upgraded to Eclipse M20100909-0800 and mylyn 2.4.0.v20100608, then imported my tasks. Same problem, so this is reproducible. I can share those tasks with someone at Tasktop, but I'm uncomfortable attaching it.
Comment 2 Emerson Murphy-Hill CLA 2011-02-13 11:08:40 EST
Created attachment 188849 [details]
Video of bug

Gah! This bug keeps biting me every week! I'd be content with just a workaround! Please!
Comment 3 Steffen Pingel CLA 2011-02-15 23:03:58 EST
Sorry for not getting back earlier Emerson. I'll try to take a look and reproduce this locally this week.
Comment 4 Emerson Murphy-Hill CLA 2013-03-13 07:06:51 EDT
This bug doesn't seem to happen to me as frequently as it did a year ago, but it just hit me again today when I rebooted my system today.

Version: 4.2.2
Build id: M20130204-1200

Mylyn 3.8.3.v20130107-0100
Comment 5 Sam Davis CLA 2013-08-22 19:43:46 EDT
Hi Emerson! I wonder if this is a duplicate of bug 250865 which was fixed in May. The issue there was that scheduled dates only worked in the timezone in which the task was scheduled, so if you scheduled tasks while travelling in a different time zone, you would see exactly the behaviour in your video when you got home and changed your computer's timezone back.
Comment 6 Emerson Murphy-Hill CLA 2013-08-23 11:34:13 EDT
Very well could be the same thing -- my intuition is that the problem does spring up when I'm traveling. I'll upgrade to 3.9 and see if it happens next time I travel.
Comment 7 Leo Dos Santos CLA 2014-05-02 19:10:46 EDT
I'm assuming this was fixed with bug 250865 since there's been no indication that the bug has sprung up again. Let us know if that's not the case.

*** This bug has been marked as a duplicate of bug 250865 ***