-
-
Notifications
You must be signed in to change notification settings - Fork 391
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not working with VSCode 1.31 #762
Comments
I was able to get it working by uninstalling |
I have the same problem, now I temporarily disable this extension. |
I can confirm that it's not working with 1.31 |
you are all using Mac ? of not please write the details. Code Settings Sync Version : [ 2.3.4 ] |
Can confirm. No problems in Code 1.30.2 |
Latest css version |
Yes, I am using Mac. Visual Studio Code Version : [ 1.31.0 ] |
@Spacebody and @fuzzy76 Try using 1.30.2 ? |
Anyway, thanks for reporting - Its working on 1.30 but not in 1.31. I use Linux and Windows to test Settings Sync. |
It seems to be caused by chokidar.
Update the dependency to latest(v2.1.0) may fix this problem. |
I tried this change in my local Mac, but it does not resolve this problem, umm... 😢 |
v2... i see... |
I fixed this problem, but the verification is not enough. In addition, I don't know how to contribute to this repository yet. (I'm reading https://github.com/shanalikhan/code-settings-sync/wiki/Contributing now...) |
would be great to know steps to resolve. |
Chokidar 2.1.0 released 4 days ago is supposed to have fixed it (by using a newer fsevents). |
If you are macOS user and want to use Settings Sync right now, consider to install my patch. WARNING: This patch overwrites v3.2.4. So, if you are trouble with this patch, you might want to reinstall official Settings Sync. git clone https://github.com/nekonenene/code-settings-sync.git -b v3.2.4-patch && cd code-settings-sync
npm i
npm i -g vsce
vsce package
/Applications/Visual\ Studio\ Code.app/Contents/Resources/app/bin/code --install-extension code-settings-sync-3.2.4.vsix
# Then, restart Visual Studio Code |
I havent tried fix of @nekonenene but I wonder if I'm having the same error. |
@renannprado Oh, it's other error. It is reported in #765. (And I haven't seen that error...) |
Me too. |
I'm getting the exact same issue as the original poster. This occurred yesterday after updating to VSCode 1.31.1. I disabled all extensions and re-enabled them one-by-one to find the culprit is code-settings-sync. 🌴 Visual Studio Code Version : [ 1.31.1 ] |
Having the same problem. Error log: [Extension Host] Sync : Connected with user : 'username' |
Me too. |
v3.2.4 released with the fix by @nekonenene Please update and let me know so i can close this ticket ? |
Error is gone for me with the 3.2.5 update. Thanks all involved! Visual Studio Code Version : [ 1.31.1 ] |
Thanks for reporting!!! |
Working again. Thank you! |
Okay, the problem had been solved. |
Found a better one 'Syncing'. Save my day. |
🐛 Describe the bug
A clear and concise description of what the bug is.
🌴 Visual Studio Code Version : [ 1.31 ]
🌴 Code Settings Sync Version : [ 2.3.4 ]
🌴 Standard or Insiders : [ Standard ]
🌴 OSS or Portable : [ OSS ]
🌴 Operating System : [ Mac OS High Sierra ]
🌴 Occurs On: [Upload / Download / Help Configuring ]
🌴 Proxy Enabled: [ Yes / No ]
📰 To Reproduce
Steps to reproduce the behavior:
💪 Expected behavior
Working like it does all time.
📺 Console Error Log
dyld: lazy symbol binding failed: Symbol not found: __ZN2v816FunctionTemplate3NewEPNS_7IsolateEPFvRKNS_20FunctionCallbackInfoINS_5ValueEEEENS_5LocalIS4_EENSA_INS_9SignatureEEEiNS_19ConstructorBehaviorENS_14SideEffectTypeE
Referenced from: /Users/yannheeser/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64/fse.node
Expected in: flat namespace
dyld: Symbol not found: __ZN2v816FunctionTemplate3NewEPNS_7IsolateEPFvRKNS_20FunctionCallbackInfoINS_5ValueEEEENS_5LocalIS4_EENSA_INS_9SignatureEEEiNS_19ConstructorBehaviorENS_14SideEffectTypeE
Referenced from: /Users/yannheeser/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64/fse.node
Expected in: flat namespace
📺 Additional context
"Extension host terminated unexpectedly"
The text was updated successfully, but these errors were encountered: