store in sync.js called twice #61
Labels
Comments
|
Did some research into the issue. Disabling atom packages did not solve the issue. store() in sync.js is indeed called twice. Turns out onDidChangeFiles in sync,js lines 18.19: is called twice, first time with 1, second time with 2 "modified" events. If this is an issue only I encounter, I suggest closing it, since it's probably some peculiarity of my machine (or Windows). Not closing it myself yet in case the above leads to a hint on how to solve it. |
|
I also encounter this issue, running:
The sync works but the warning is a bit annoying ;-) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Having Sync on in Atom.
Whenever I save a local file, I get a message from busy-signal:
"Status .... is already set..."
caused by line 70 in syn.js:
this.emit("status",
Uploading ${file} to ${relPath} as ${contentType}...);Not an busy-signal issue (see similar problems in busy-signal git).
Files are actually synced to eXist, no problems there.
Replacing the lines in sync.js with:
console.log('hi')
var d = new Date()
this.emit("status",
Uploading ${d.getTime()}: ${file} to ${relPath} as ${contentType}...);resolves the busy-signal error, however the console does say 'hi' twice for every save.
Seems the underlying problem is store being called twice.
Atom 1.34.0 x64 on Win10, eXist 4.3.1, atom existdb package 0.12.0
The text was updated successfully, but these errors were encountered: