Closed Thiritin closed 5 years ago
same problem for me today, how to use v0.3.5?
i have the same problem i dont know why i have the ftp-sync.json file OK
Got the same issue.
Got the same issue.
[2018-12-05 11:34:47.682] [exthost] [error] Error: ENOENT: no such file or directory, mkdir 'C:\d:\xxxxxx\xxxxxxxx\.vscode' at fs.mkdirSync (fs.js:885:18) at Object.fs.mkdirSync (ELECTRON_ASAR.js:702:16) at module.exports (C:\Users\xxxxxxx\.vscode\extensions\lukasz-wronski.ftp-sync-0.3.6\modules\init-command.js:13:6) at e._executeContributedCommand (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:460:160) at e.$executeContributedCommand (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:460:648) at t._doInvokeHandler (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:609:757) at t._invokeHandler (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:609:423) at t._receiveRequest (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:608:15) at t._receiveOneMessage (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:606:957) at c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:604:773 at c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:103:886 at e.fire (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:105:344) at a (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:156:881) at Socket._socketDataListener (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:157:95) at emitOne (events.js:116:13) at Socket.emit (events.js:211:7) at addChunk (_stream_readable.js:263:12) at readableAddChunk (_stream_readable.js:250:11) at Socket.Readable.push (_stream_readable.js:208:10) at Pipe.onread (net.js:594:20) extension.ftpsyncinit
i fix this problem by replace all rootPath().path
to rootPath().fsPath
at C:\Users\[USERNAME]\.vscode\extensions\lukasz-wronski.ftp-sync-0.3.6\modules
directory in win10, about 8 files changed.
i fix this problem by replace all
rootPath().path
torootPath().fsPath
atC:\Users\[USERNAME]\.vscode\extensions\lukasz-wronski.ftp-sync-0.3.6\modules
directory in win10, about 8 files changed.
Problem solved. but uploadOnSave function still not work 😛
I have the same problem
I have the same problem
Temporary solution: replace all ftpconfig.rootPath().path to vscode.workspace.rootPath replace all this.rootPath().path to vscode.workspace.rootPath at C:\Users[USERNAME].vscode\extensions\lukasz-wronski.ftp-sync-0.3.6\modules
我今天也遇到这个问题,怎么操作来解决这个问题?
我今天也遇到这个问题,怎么操作来解决这个问题?
上面的方法可以临时先解决
我用你的方法,把ftpconfig.rootPath()全部换成vscode.workspace.rootPath(然后还是不行,方便加一下微信吗
我用你的方法,把ftpconfig.rootPath()全部换成vscode.workspace.rootPath(然后还是不行,方便加一下微信吗
rogeren
Broken path is fixed now. Thanks for feedback and sorry for trouble.
@black-jk Can you tell me more about your problem with uploadOnSave? It seems to be working fine for me. The last fix was mostly for uploadOnSave not adding directories or adding them as blank files. There's a problem where uploadOnSave isn't working when size of the file wasn't changed. I'll fix this asap.
@NajSurf I have a problem with "uploadOnSave". It does not work after updating to 0.3.5.
Can you provide me some more information? When is it happening? How does your config look like? Are there any errors? I tried to reproduce the bug and I found out that when I run init inside a new workspace, the uploadOnSave wont work until I restart vscode, then it's working fine.
My config:
{ "remotePath": "project_folder", "host": "ip", "username": "project", "password": "project", "port": 22, "secure": false, "protocol": "sftp", "uploadOnSave": true, "passive": false, "debug": false, "privateKeyPath": null, "passphrase": null, "agent": null, "allow": [], "ignore": [ "\\.vscode", "\\.git", "\\.DS_Store" ], "generatedFiles": { "uploadOnSave": true, "extensionsToInclude": [], "path": "project_folder" } }
The error appeared only 1 time. After the first restarting vscode. What was in it - I do not remember. I tried to completely reinstall vscode (maybe it's in him?). Did not help.
@NajSurf I tried to open an old project where everything worked before and a similar config. "uploadOnSave" does not work
Solved the problem by installing the previous version
https://github.com/lukasz-wronski/vscode-ftp-sync/issues/267#issuecomment-444599981
Please check the latest version for a fix #269 It should be working fine now.
I've just downloaded the latest version from store but again I have this problem too.
Again same problem: Command 'Ftp-sync: Init' resulted in an error (Running the contributed command: 'extension.ftpsyncinit' failed.)
It's after fresh extension install. VSC version is 1.46.0
I had the same problem on vscode 1.53 and ftp-sync 0.3.9. downgrade ftp-sync to 0.3.5 and solved problem.
had the same problem, downgrade to 0.3.5 also fixed it
Hi,
Similar: #108
after some time Working with the Addon i suddenly run into an issue with the addon. I could not upload as it was asking for a config file. Then i tried to make a blank project and i received the following error.
Steps to Reproduce
Not known
Tried Solutions