Closed
Bug 1050684
Opened 10 years ago
Closed 10 years ago
[Contacts-FTU] When FTU import Facebook Friends the next sync cycle must be scheduled
Categories
(Firefox OS Graveyard :: Gaia::Contacts, defect)
Tracking
(b2g-v2.1 verified)
VERIFIED
FIXED
2.1 S3 (29aug)
Tracking | Status | |
---|---|---|
b2g-v2.1 | --- | verified |
People
(Reporter: jmcf, Assigned: hola)
References
Details
Attachments
(2 files)
We need to set a flag in the ImportStatusData datastore. That flag will be read during an idle cycle in contacts and, then the new sync will be scheduled.
Reporter | ||
Updated•10 years ago
|
Summary: When FTU import Facebook Friends the next sync cycle must be scheduled → [Contacts-FTU] When FTU import Facebook Friends the next sync cycle must be scheduled
Assignee | ||
Comment 1•10 years ago
|
||
Attachment #8470787 -
Flags: review?(jmcf)
Reporter | ||
Comment 2•10 years ago
|
||
Comment on attachment 8470787 [details]
Pull request #22730
the solution implemented has many flaws. please see comments on GH.
Attachment #8470787 -
Flags: review?(jmcf) → review-
Assignee | ||
Updated•10 years ago
|
Attachment #8470787 -
Flags: review- → review?(crdlc)
Comment 3•10 years ago
|
||
Comment on attachment 8470787 [details]
Pull request #22730
Minor change on github, good job as usual, thanks a lot Adrian
Attachment #8470787 -
Flags: review?(crdlc) → review+
Comment 4•10 years ago
|
||
Sorry for giving my comments now, I don't follow github comments anymore, you could flag me for f?, will be much more responsive.
With that said, unfortunately I would like to backout this commit.
Despite that is being executed asynchronously, the lazyload and the code parsed and executed is on the critical path of the app and we don't need it there.
A place for doing this could be when the list is fully loaded, or at least when we are above the fold. Will prefer actually when the list finished loading, remember you have a custom event that is triggered when this happens.
Can we sync tomorrow before backing it out?
Flags: needinfo?(hola)
Assignee | ||
Comment 5•10 years ago
|
||
First of all, I'm sorry, I'm pretty new to this codebase, so sorry for messing up. Nonetheless I'm willing to learn so it would be great if we can meet on Skype tomorrow morning to discuss about this and the other contacts bug.
Thanks.
Flags: needinfo?(hola)
Comment 6•10 years ago
|
||
(In reply to Adrián de la Rosa from comment #5)
> First of all, I'm sorry, I'm pretty new to this codebase, so sorry for
> messing up. Nonetheless I'm willing to learn so it would be great if we can
> meet on Skype tomorrow morning to discuss about this and the other contacts
> bug.
>
> Thanks.
Hei Adrian, no worries mate, we all need to learn, and that's where I can help you, to grow and learn on the currect codebase.
Tomorrow we have the contacts daily, we can sync there, and after that we can chat about this bug.
Cheers!
Comment 7•10 years ago
|
||
We were talking about leaving this bug as it is right now, it's working perfectly and open a new one for moving the code outside the critical path.
That work can be done through the stabilisation phase.
Thanks everyone folks!
Comment 8•10 years ago
|
||
Wooot, totally wrong bug here xD
Assignee | ||
Comment 9•10 years ago
|
||
(In reply to Francisco Jordano [:arcturus] [:francisco] from comment #7)
> We were talking about leaving this bug as it is right now, it's working
> perfectly and open a new one for moving the code outside the critical path.
>
> That work can be done through the stabilisation phase.
>
> Thanks everyone folks!
Should we merge this and mark it fixed now? I don't know if you prefer to change this only when we land bug 1056647.
Comment 10•10 years ago
|
||
(In reply to Adrián de la Rosa from comment #9)
> (In reply to Francisco Jordano [:arcturus] [:francisco] from comment #7)
> > We were talking about leaving this bug as it is right now, it's working
> > perfectly and open a new one for moving the code outside the critical path.
> >
> > That work can be done through the stabilisation phase.
> >
> > Thanks everyone folks!
>
> Should we merge this and mark it fixed now? I don't know if you prefer to
> change this only when we land bug 1056647.
Adrian you are right, this morning I got confused with so many tabs.
Let's land and we do the follow up in bug 1056647 moving the things around.
Thanks!
Comment 11•10 years ago
|
||
Merged in master:
https://github.com/mozilla-b2g/gaia/commit/e99b0c0b707470271ddc5d03b48140084f518271
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
status-b2g-v2.1:
--- → fixed
Target Milestone: --- → 2.1 S3 (29aug)
Comment 12•10 years ago
|
||
This issue has been verified successfully on Flame2.1
Verify video:"verify_1050684.mp4".
Flame2.1 build:
Gaia-Rev dbaf3e31c9ba9c3436e074381744f2971e15c7bf
Gecko-Rev https://hg.mozilla.org/releases/mozilla-b2g34_v2_1/rev/ebce587d2194
Build-ID 20141203001205
Version 34.0
Device-Name flame
FW-Release 4.4.2
FW-Incremental eng.cltbld.20141203.034907
FW-Date Wed Dec 3 03:49:18 EST 2014
Bootloader L1TC00011880
Status: RESOLVED → VERIFIED
Comment 13•10 years ago
|
||
You need to log in
before you can comment on or make changes to this bug.
Description
•