Closed
Bug 952224
Opened 11 years ago
Closed 10 years ago
[Session Restore] Remove calls to |_ensureInitialized()| and no longer throw a "Session Store is not initialized." error
Categories
(Firefox :: Session Restore, defect)
Firefox
Session Restore
Tracking
()
People
(Reporter: smacleod, Assigned: tyler.colgan, Mentored)
Details
(Whiteboard: [good first bug][lang=js])
Attachments
(1 file)
2.49 KB,
patch
|
smacleod
:
review+
|
Details | Diff | Splinter Review |
Bug 918024 Removed the synchronous start up fallback for sessions store. We left the calls to |_ensureInitialized()| so we would throw an error if someone attempted to trigger the removed code path.
Since Bug 918024 landed, we haven't seen reports of these errors and we should eventually remove this code if everything stays quiet.
Reporter | ||
Updated•11 years ago
|
Flags: firefox-backlog?
Whiteboard: [good first bug][mentor=smacleod][lang=js]
Updated•11 years ago
|
Flags: firefox-backlog? → firefox-backlog+
Updated•10 years ago
|
Mentor: smacleod
Whiteboard: [good first bug][mentor=smacleod][lang=js] → [good first bug][lang=js]
Updated•10 years ago
|
Whiteboard: [good first bug][lang=js] → [good first bug][lang=js] p=1
Assignee | ||
Comment 1•10 years ago
|
||
If I'm interpreting this correctly, it sounds like we want to remove _ensureInitialized() and any calls to it. I went ahead and did that in this patch; let me know if I'm on the right track.
Assuming that this is the right approach, it looks like doRestore() would no longer have a possibility of throwing an error, so I removed its |@throws| line as well.
Attachment #8465594 -
Flags: feedback?(smacleod)
Reporter | ||
Comment 2•10 years ago
|
||
Comment on attachment 8465594 [details] [diff] [review]
Remove calls to _ensureInitialized() (version 1)
Review of attachment 8465594 [details] [diff] [review]:
-----------------------------------------------------------------
Hey Tyler, this looks great. Thanks for the patch! I've pushed it to Try for you[1].
You should consider applying for Level 1 Commit access[2] so that you can push
to Try as well. Tim or I would vouch for you.
Please let me know if you'd like any help finding more stuff to work on.
Thanks!
[1] https://tbpl.mozilla.org/?tree=Try&rev=5a00ca10c01c
[2] https://www.mozilla.org/hacking/commit-access-policy/
Attachment #8465594 -
Flags: feedback?(smacleod) → review+
Reporter | ||
Comment 3•10 years ago
|
||
If you'd like to apply for commit access you should also take a look at https://www.mozilla.org/hacking/committer/
Comment 5•10 years ago
|
||
Comment 6•10 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 34
Updated•10 years ago
|
Iteration: --- → 34.1
Points: --- → 1
QA Whiteboard: [qa?]
Whiteboard: [good first bug][lang=js] p=1 → [good first bug][lang=js]
Reporter | ||
Updated•10 years ago
|
QA Whiteboard: [qa?] → [qa-]
You need to log in
before you can comment on or make changes to this bug.
Description
•