Closed Bug 1203868 Opened 7 years ago Closed 7 years ago

SyncEngine not retrieving latest records

Categories

(Firefox OS Graveyard :: Sync, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: mbdejong, Unassigned)

References

Details

Attachments

(2 files)

irc log from #fxos-sync attached.
Assignee: nobody → mbdejong
Blocks: 1200539
I'll leave the ?_since= header commented out in https://github.com/michielbdejong/gaia/tree/1200539-sync-app-integration-tests until the 6-original-ids branch lands into Syncto master, then it should all work together.
Hi Michiel,

After applying Natim's patch at https://github.com/mozilla-services/syncto/pull/19, I still got JSON.parse error.

So I provide my patch for fixing the error in SyncEngine. Could you give me a feedback? Thank you!
Attachment #8659970 - Flags: feedback?(mbdejong)
Comment on attachment 8659970 [details]
Fixing JSON.parse error

Hi Sean,

(In reply to Sean Lee [:seanlee] from comment #3)
> After applying Natim's patch at
> https://github.com/mozilla-services/syncto/pull/19, I still got JSON.parse
> error.
> 
> So I provide my patch for fixing the error in SyncEngine. Could you give me
> a feedback? Thank you!

RemoteTransformer.decode should never be called with data that does not need decoding. If that is happening then we need to fix that in kinto.js rather than working around it in this way.

I also saw JSON.parse errors yesterday morning, but last time I tested with the latest version of https://github.com/michielbdejong/gaia/tree/1200539-sync-app-integration-tests I did not see any JSON parse errors. Can you provide the steps to reproduce?
Attachment #8659970 - Flags: feedback?(mbdejong) → feedback-
Closing this as UNCONFIRMED since I haven't seen it happen in the last two weeks.

Please reopen if we can reproduce it!
Status: NEW → UNCONFIRMED
Ever confirmed: false
Assignee: mbdejong → nobody
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.