Closed
Bug 867797
Opened 12 years ago
Closed 11 years ago
Syncing when viewing an event can sometimes cause event to disappear when it has been edited on server
Categories
(Firefox OS Graveyard :: Gaia::Calendar, defect, P1)
Firefox OS Graveyard
Gaia::Calendar
Tracking
(blocking-b2g:leo+, b2g18+ verified, b2g-v1.1hd fixed)
People
(Reporter: jlal, Assigned: jlal)
References
Details
(Keywords: regression, Whiteboard: c=regression, [TD-25987])
Attachments
(1 file)
Event will re-appear after restarting calendar.
Assignee | ||
Updated•12 years ago
|
blocking-b2g: --- → leo?
Comment 1•12 years ago
|
||
(In reply to James Lal [:lightsofapollo] from comment #0)
> Event will re-appear after restarting calendar.
Does syncing again bring it back? Is this a regression?
Assignee | ||
Comment 2•12 years ago
|
||
its not really a sync error- the event _does_ exist in the calendar but there is some bug that prevents it from displaying. Its probably a regression between v1-train / v1.0.1
Comment 3•12 years ago
|
||
Actually, didn't read comment 0 when I requested qawanted in triage. I know what's going on here.
Sounds like this is temporary lack of display of the event if:
1. The imported calendar is being synced
2. The event being viewed during sync has been edited on the server
3. The event is no longer displayed until the calendar is restarted
This is a combination of an edge case and only temporary display issue while the calendar is active. I'm leaning towards not blocking on this as a result.
Keywords: qawanted
QA Contact: jsmith
Updated•12 years ago
|
Keywords: regression
Updated•12 years ago
|
Updated•12 years ago
|
Whiteboard: c= → c=regression
I believe, we need to block on this issue.
If the user wants to view his events after syncing, he will have to restart the application, which i think is not acceptable.
Practically the user is getting an impression, that he doesn't have any upcoming events, until he restart the application.
There is no guarantee that the user restarts the application everytime after syncing the calendar.
blocking-b2g: - → leo?
Updated•11 years ago
|
Whiteboard: c=regression, [TD]25987 → c=regression, [TD-25987]
Target Milestone: --- → 1.1 QE2
Assignee | ||
Comment 7•11 years ago
|
||
This does happen but not consistently (at least not on my account) some sort of race condition... I will continue testing but additional help narrowing it down would be useful.
Keywords: qawanted
Comment 8•11 years ago
|
||
(In reply to James Lal [:lightsofapollo] from comment #7)
> This does happen but not consistently (at least not on my account) some sort
> of race condition... I will continue testing but additional help narrowing
> it down would be useful.
I think the STR I did here to reproduce this easily was something like:
1. Import a google calendar
2. Select a day with google calendar events
3. Edit one of the events for the day selected on google calendar
4. Sync
Result - the day's calendar events disappear.
If that doesn't work, let me know.
Keywords: qawanted
Assignee | ||
Comment 9•11 years ago
|
||
That was my own STR but it is not consistently failing
Updated•11 years ago
|
QA Contact: jsmith
Comment 11•11 years ago
|
||
Yeah, the STR in comment 8 reproduces the bug for me. What I noticed was:
1. The event remained visible on the month view, but if I selected it, I would get the infamous broken calendar UI (many UI pieces in wrong positions)
2. The event was not present in the week or day views
Keywords: qawanted
Comment 12•11 years ago
|
||
As per Jason's comment 8, this bug reproduces on Inari.
Gmail, Yahoo, CaDav accounts are used for the test.
Events are disappeared in the calendar application, after syncing the accounts and then editing the events on the server account.
The events are not visible neither in "Month", "Week" or "Day" views
Environmental Variables:
Inari Build ID: 20130515070203
Gecko: http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/0b6bcb1f4175
Gaia: 9648799c2e45917ff150fa9eef8aeac79a9ac008
Updated•11 years ago
|
Assignee: nobody → gaye
Comment 13•11 years ago
|
||
Gareth - Dylan mentions you are running into issues reproducing this. If you would like, we could meet up and debug this if need be.
Comment 14•11 years ago
|
||
That would be great! I'm planning on being in the SF office on Thursday and Friday... will you be around? If that doesn't work, a video where you walk through reproducing the issue would be hugely helpful. Let me know.
Flags: needinfo?(jsmith)
Updated•11 years ago
|
Status: NEW → ASSIGNED
Comment 15•11 years ago
|
||
(In reply to gaye from comment #14)
> That would be great! I'm planning on being in the SF office on Thursday and
> Friday... will you be around? If that doesn't work, a video where you walk
> through reproducing the issue would be hugely helpful. Let me know.
I'm actually in NY this week, but I could still do a vidyo call. I'm on PTO on Thursday though. Name the day and time this week (Wednesday or Friday) and I'll be there.
Flags: needinfo?(jsmith)
Comment 16•11 years ago
|
||
(In reply to gaye from comment #14)
> a video where you walk
> through reproducing the issue would be hugely helpful. Let me know.
We have a video for STR in the bug 870349. Could you check if that is helpful else let me know if more information required to reproduce.
Flags: needinfo?(gaye)
Updated•11 years ago
|
Assignee: gaye → jlal
Flags: needinfo?(gaye)
Comment 17•11 years ago
|
||
Leo - James mentioned he had an idea for what he wanted to do here, so I'm passing it off now that he's back from PTO.
Assignee | ||
Comment 18•11 years ago
|
||
I found what appears to be a race in caldav_pull_events.js in the method handleEventSync. Seems like we attempt to delete the old busytimes but we are not waiting for that operation to complete... This often means we hit conditions where we actually end up removing the _new_ busytime/event information from the cache rather then the old... this is fixed during restart.
Patch soon...
Assignee | ||
Comment 19•11 years ago
|
||
Pointer to Github pull-request
Assignee | ||
Comment 20•11 years ago
|
||
Comment on attachment 758860 [details]
Pointer to Github pull request: https://github.com/mozilla-b2g/gaia/pull/10223
This is working well for me but I wanted your feedback / concerns before I clean up the patch...
the one change I plan on making is prefixing the busytime ids' with the event id which should dramatically reduce the likelihood UUID collisions.
Attachment #758860 -
Flags: feedback?(gaye)
Assignee | ||
Updated•11 years ago
|
Attachment #758860 -
Flags: review?(gaye)
Comment 21•11 years ago
|
||
The function "busytimeIdFor" removed from file "store/event.js" is used for modifying the events. This breaks the edit event feature.
Flags: needinfo?(jlal)
Comment 22•11 years ago
|
||
(In reply to Leo from comment #21)
> The function "busytimeIdFor" removed from file "store/event.js" is used for
> modifying the events. This breaks the edit event feature.
Please ignore my comments i tested the patch with v1-train
Assignee | ||
Comment 23•11 years ago
|
||
Clearing my needinfo- I think #22 answers #21?
Flags: needinfo?(jlal)
Updated•11 years ago
|
Attachment #758860 -
Flags: review?(gaye)
Attachment #758860 -
Flags: review+
Attachment #758860 -
Flags: feedback?(gaye)
Attachment #758860 -
Flags: feedback+
Assignee | ||
Comment 24•11 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Comment 25•11 years ago
|
||
I was not able to uplift this bug to v1-train. If this bug has dependencies which are not marked in this bug, please comment on this bug. If this bug depends on patches that aren't approved for v1-train, we need to re-evaluate the approval. Otherwise, if this is just a merge conflict, you might be able to resolve it with:
git checkout v1-train
git cherry-pick -x -m1 cdeb777ff57c85fa236da621c179a1fd751cff20
<RESOLVE MERGE CONFLICTS>
git commit
Flags: needinfo?(jlal)
Updated•11 years ago
|
Flags: in-moztrap?
Assignee | ||
Comment 26•11 years ago
|
||
in v1-train: 43c9be6643ca5a649b04baeb23e53bc71cfe005b
Comment 27•11 years ago
|
||
1.1hd: 43c9be6643ca5a649b04baeb23e53bc71cfe005b
status-b2g-v1.1hd:
--- → fixed
Comment 28•11 years ago
|
||
lgtm on b2g18 on 6/18 - tried testing syncing while viewing events both not modified on server vs. modified on server.
Keywords: verifyme
Assignee | ||
Comment 29•11 years ago
|
||
backed out of v1-train here: 258db40f9850558638c0fb3addbe7a203cbb14c4 there is a missing dependency that causes regressions on v1-train but not master.
Assignee | ||
Comment 30•11 years ago
|
||
Adding missing dep this is needed for v1-train (otherwise we see the regressions)
Comment 31•11 years ago
|
||
Reopening for backout in comment 29
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 32•11 years ago
|
||
landed back in v1-train here 30cf7138224dcfe8d731bef319227113606733f3. I tested out the path with the previous regressions and it looks good now that the dep has landed.
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Flags: in-moztrap? → in-moztrap+
You need to log in
before you can comment on or make changes to this bug.
Description
•