Closed Bug 847866 Opened 11 years ago Closed 11 years ago

[Dialer] Avoid race conditions in overlays

Categories

(Firefox OS Graveyard :: Gaia::Dialer, defect)

ARM
Gonk (Firefox OS)
defect
Not set
major

Tracking

(b2g18+ fixed)

RESOLVED FIXED
Tracking Status
b2g18 + fixed

People

(Reporter: gtorodelvalle, Assigned: gtorodelvalle)

References

Details

Attachments

(1 file)

The current libraries used to show overlays in the Communications app may suffer for race conditions (if the overlay is hidden before the animation to show it has completed, for example) and do not support re-showing an already shown overlay (for example to change the message shown).
Assignee: nobody → gtorodelvalle
Attached file Associated PR.
Attachment #721641 - Flags: review?(etienne)
Comment on attachment 721641 [details]
Associated PR.

Comments on github, can't wait to play with the updated, rebased and linted version ;)
Attachment #721641 - Flags: review?(etienne)
Comments included in the PR ;-) Would you be so kind to review them? Thanks!
Attachment #721641 - Flags: review+
Merged! ;-)
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Should this be tracking-b2g18 so that it could land in v1.1 ?
It should ;-) In fact, I was about to ask for the approval-gaia-v1 :)
Comment on attachment 721641 [details]
Associated PR.

NOTE: Please see https://wiki.mozilla.org/Release_Management/B2G_Landing to better understand the B2G approval process and landings.

[Approval Request Comment]
Bug caused by (feature/regressing bug #): Uncomplete management of overlay messages in the Comms app
User impact if declined: Comms app may become unusable
Testing completed: Tested in the device
Risk to taking this patch (and alternatives if risky): Low risk as a consequence of heavy testing in the device
String or UUID changes made by this patch: None
Additional info: 2 changed files with 196 additions and 104 deletions.
Attachment #721641 - Flags: approval-gaia-v1?
Comment on attachment 721641 [details]
Associated PR.

Looks like a low risk win for email performance, approving for uplift.
Attachment #721641 - Flags: approval-gaia-v1? → approval-gaia-v1+
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 3444dd7ff1467e7b09e4c0bc3185a46f0a20b188
  <RESOLVE MERGE CONFLICTS>
  git commit
Flags: needinfo?(gtorodelvalle)
(In reply to John Ford [:jhford] from comment #10)
> 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 3444dd7ff1467e7b09e4c0bc3185a46f0a20b188
>   <RESOLVE MERGE CONFLICTS>
>   git commit

Hi John ;-) This bug and patch solves cases not previously considered in bug 816941 (this one inclues 2 patches).
Flags: needinfo?(gtorodelvalle)
Depends on: 816941
BTW, I am solving the conflicts, John ;-) I have started with bug 816941
Hi John, again ;-) Conflicts should be solved and successfully landed in v1-train :-) Would you be so kind to confirm it? Thanks!
Flags: needinfo?(jhford)
Could you please add the commit hash here ? thanks
Flags: needinfo?(gtorodelvalle)
That looks reasonable, but I'm not the expert on what these changes do and how they fit in with the rest of the v1-train branch.
Flags: needinfo?(jhford)
gtorodelvalle> the easiest to check if this is ok is you pushing the v1-train version on your device and testing this specific bug :)
Yeah, yeah, I mean I did that (the testing in the device :-D) Just wanted to let John have the last word about my cherry-picking ;-) I am 100% confident about it, and of course it works in the device ;-)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: