Closed ofir123 closed 7 years ago
After a bit of testing, I am not convinced this is a working fix
@msh100 Thanks for testing. I thought it was a bit odd.
@msh100 what was the problem? I'm using this fix for about 2 months now, and it's holding well..
@ofir123 Looked the same as the original issue, nodes were not present in syncs
Honestly I didn't dig much into this, but first appearance is that this does nothing
From what I experienced, Amazon's API was turning on the reset flag for certain nodes (no idea why). But when ignoring it, everything works find and the nodes get synced..
Happy to retry. But I'm not convinced.
I'll get back to you.
Sent from my iPhone
On 22 Apr 2017, at 12:50, Ofir notifications@github.com wrote:
From what I experienced, Amazon's API was turning on the reset flag for certain nodes (no idea why). But when ignoring it, everything works find and the nodes get synced..
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.
Hey @ofir123 is this still holding well?