Closed
Bug 482878
Opened 15 years ago
Closed 15 years ago
service (_remoteSetup) needs to migrate payload formats
Categories
(Cloud Services :: General, defect, P1)
Cloud Services
General
Tracking
(Not tracked)
RESOLVED
FIXED
0.3
People
(Reporter: hello, Assigned: Mardak)
References
Details
Attachments
(1 file)
1.28 KB,
patch
|
hello
:
review+
|
Details | Diff | Splinter Review |
We now wrap payloads in an array, and _remoteSetup doesn't deal with that case. It needs to.
Assignee | ||
Comment 1•15 years ago
|
||
XX comment because we shouldn't need this down the line.
Assignee | ||
Comment 2•15 years ago
|
||
P1 as bug 478327 breaks existing profiles and prevents them from syncing.
Reporter | ||
Comment 3•15 years ago
|
||
Comment on attachment 366975 [details] [diff] [review] v1 looks great
Attachment #366975 -
Flags: review?(thunder) → review+
Assignee | ||
Comment 4•15 years ago
|
||
http://hg.mozilla.org/labs/weave/rev/430ce13b63f3
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 5•15 years ago
|
||
Erm. We might need to do something similar again now that I pushed a fix for bug 482670. But then I realized, there won't be a problem if we just bump up the version as it causes a server wipe. Might as well get rid of this now-old migration code.
Depends on: 482670
Assignee | ||
Comment 6•15 years ago
|
||
Backed out changeset 430ce13b63f3 (bug 482878) http://hg.mozilla.org/labs/weave/rev/1edebdd5553f Bug 482670 restored un-wrapped payloads, so until a version bump, those using trunk will need to do a manual server wipe.
Reporter | ||
Comment 7•15 years ago
|
||
>- // XXX Bug 482878 Old payloads weren't array-wrapped, so migrate by wiping
>- if (meta && meta.payload == null) {
>- this._log.debug("Migrating to minimal payloads by wiping the server");
>- meta = null;
>- }
>
> let remoteVersion = (meta && meta.payload.storageVersion)?
> meta.payload.storageVersion : "";
The problem was that even if you bumped the payload, existing old meta records would fail with 'meta.payload is undefined', and execution would stop rather than causing a wipe.
However, by now we've done a lot of version upgrades, and pretty much everyone should be using a version where meta.payload is defined. So we can leave the extra check out.
Reporter | ||
Comment 8•15 years ago
|
||
> The problem was that even if you bumped the payload, existing old meta records
...even if you bumped the *version*...
Updated•15 years ago
|
Component: Weave → General
Product: Mozilla Labs → Weave
Version: Trunk → unspecified
Updated•15 years ago
|
QA Contact: weave → general
You need to log in
before you can comment on or make changes to this bug.
Description
•