Closed Bug 1050097 Opened 10 years ago Closed 10 years ago

[Camera] Add error handling while |videoStorage.addNamed| occurs error.

Categories

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

x86
macOS
defect
Not set
normal

Tracking

(blocking-b2g:-, b2g-v1.4 wontfix, b2g-v2.0 wontfix, b2g-v2.1 fixed)

RESOLVED FIXED
2.1 S2 (15aug)
blocking-b2g -
Tracking Status
b2g-v1.4 --- wontfix
b2g-v2.0 --- wontfix
b2g-v2.1 --- fixed

People

(Reporter: GaryChen, Assigned: GaryChen)

References

Details

Attachments

(1 file)

There is no error handling/message while |videoStorage.addNamed| occurs error.
This issue is a follow up from bug 147228.
Assignee: nobody → gchen
Hi Diego,
   This is my patch for fixing this issue.
   Since |videoStorage.addNamed| occurs error, then all UI will be stuck.
   So I emit 'storage:createVideoError' and use |onRecordingError| to 'prompt dialog' let user know current status.

   I'm not sure this is a best way for fixing this issue, please help to review this patch and give me some feedback.
   
   Thanks.
Attachment #8469070 - Flags: review?(dmarcos)
[Blocking Requested - why for this release]:
since this blocks bug 1047228 which is 1.4+. should we also include this is v1.4?
blocking-b2g: --- → 1.4?
Comment on attachment 8469070 [details] [review]
pull request: https://github.com/mozilla-b2g/gaia/pull/22612

Thanks for the patch. I left my comments on github. r- because:

It's be better to pass the error on the function callback instead of triggering an event
Attachment #8469070 - Flags: review?(dmarcos) → review-
Comment on attachment 8469070 [details] [review]
pull request: https://github.com/mozilla-b2g/gaia/pull/22612

Hi Diego,
   I've addressed your comment and fixed unit tests, please help to review my patch again.
  
   Thanks.
Attachment #8469070 - Flags: review- → review?(dmarcos)
Comment on attachment 8469070 [details] [review]
pull request: https://github.com/mozilla-b2g/gaia/pull/22612

This starts to look really sweet! We're close. I made more suggestions on github. Mostly to keep consistency with the rest of the code base.
Attachment #8469070 - Flags: review?(dmarcos) → review-
Comment on attachment 8469070 [details] [review]
pull request: https://github.com/mozilla-b2g/gaia/pull/22612

Hi Diego,
   Please help to review this patch again, thanks.
Attachment #8469070 - Flags: review- → review?(dmarcos)
Comment on attachment 8469070 [details] [review]
pull request: https://github.com/mozilla-b2g/gaia/pull/22612

Yeah! It looks great. This needs to be uplifted right?
Attachment #8469070 - Flags: review?(dmarcos) → review+
Hmmmmm... Need to get v1.4+ and approval then we can uplift.
Thanks for your review again.
blocking-b2g: 1.4? → 1.4+
merged in gaia master:
https://github.com/mozilla-b2g/gaia/commit/9ce01d8fa33acf4fad5a6a43cfeca1a8d715de7b.
Status: NEW → RESOLVED
blocking-b2g: 1.4+ → 1.4?
Closed: 10 years ago
Resolution: --- → FIXED
landed in v1.4
https://github.com/mozilla-b2g/gaia/commit/ec395d47cee9234ae93d2410d8ef8724dfc5d6cb

Hi Wayne,
   Sorry, I made a mistake with changed v1.4+ to v1.4?, please help me to change it to right way.
   Thanks.
Flags: needinfo?(wchang)
Thanks Gary.
blocking-b2g: 1.4? → 1.4+
Flags: needinfo?(wchang)
Is this needed for v2.0 as well? If so, please nominate the patch for gaia v2.0 uplift.
status-b2g-v2.0: --- → ?
Flags: needinfo?(gchen)
Target Milestone: --- → 2.1 S2 (15aug)
Hi Pike,
  I've added v1.4 patch with new string, maybe we need l10n team support.
  Could you help to take a look? 
  Please refer to comment 10.
Thanks
Flags: needinfo?(l10n)
(In reply to Ryan VanderMeulen [:RyanVM UTC-4] from comment #12)
> Is this needed for v2.0 as well? If so, please nominate the patch for gaia
> v2.0 uplift.

And then you commit on 2.0...

Please back it out. You can't land string changes on branches that are string frozen (anything besides master).
Flags: needinfo?(l10n) → needinfo?(gchen)
Thanks. I'm honestly confused by this bug: am I reading it wrong or this bug got approvals for 1.4 without any release-driver being involved? Is this supposed to happen?
(In reply to Francesco Lodolo [:flod] from comment #17)
> Thanks. I'm honestly confused by this bug: am I reading it wrong or this bug
> got approvals for 1.4 without any release-driver being involved? Is this
> supposed to happen?

Wayne is one of the 1.4 drivers.

That said, I'm backing this out from v1.4 as well until the string situation is sorted out. We're way past string freeze.

v1.4: https://github.com/mozilla-b2g/gaia/commit/296f95231db42d25d9b92867489d5ba954c663e0

And like flod said, this *must* have v2.0 approval before landing there. 1.4 blocking status does not grant auto-approval as of a few weeks ago. It was announced on dev-gaia when the change was made and the B2G Landing Page also says the same.
https://wiki.mozilla.org/Release_Management/B2G_Landing
Flags: needinfo?(wchang)
Apologies for missing the string changes implied by this bug. I'll talk to Gary and clarify the string situation and update here.
Wayne, please adhere to string freeze here. For 2.0 I don't think flame is impacted by 1047228, so this bug would be a wontfix as the primary reason for blocking this on 1.4 was 1047228
After discussing with Gary and others, this bug is a fail safe for cases where 1047228 do not cover. Ideally bug 1047228 should resolve situations where this bug would occur.
Removing 1.4+ here, the two bugs are not dependent on each other. Leaving bug 1047228 as POVB for partner to pick up.
blocking-b2g: 1.4+ → -
Flags: needinfo?(wchang)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: