If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Status

Cloud Services
Firefox Sync: Backend
RESOLVED INVALID
7 years ago
7 years ago

People

(Reporter: rnewman, Assigned: philikon)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

7 years ago
2010-12-09 16:04:44	Engine.History       WARN	Error processing record: uri is undefined JS Stack trace: GUIDForUri((void 0))@history.js:232 < _findDupe([object Object])@history.js:68 < ([object Object])@engines.js:214 < SyncEngine__reconcile([object Object])@engines.js:658 < ([object Object])@engines.js:214 < ([object Object])@engines.js:498 < innerBind([object Object])@util.js:1369 < ()@collection.js:154 < Channel_onDataAvail([object XPCWrappedNative_NoHelper],null,[object XPCWrappedNative_NoHelper],8192,5390)@resource.js:451


This when I'm faking history items:

    let visitType = Ci.nsINavHistoryService.TRANSITION_LINK;
    for (var i = 0; i < 30; i++) {
      let id = 'record-no-' + i;
      let modified = Date.now()/1000 - 60*(i+10);
      let payload = encryptPayload({
        id: id,
        histUri: "http://foo/bar?" + id,
        title: id,
        sortindex: i,
        visits: [{date: (modified - 5), type: visitType}],
        deleted: false});
      
      let wbo = new ServerWBO(id, payload);
      wbo.modified = modified;
      history[id] = wbo;
    }

Feel free to close as invalid, but thought you might want to check to see if you've missed a guard.
(Reporter)

Comment 1

7 years ago
This was happening because decryption was failing, but I wasn't throwing an exception at that point. History engine can probably expect its calling code to work :D

Closing.
Status: ASSIGNED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.