You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use a normal install and the following simple config:
{
"name": "Servers",
"host": "",
"protocol": "sftp",
"port": ,
"secure": true,
"username": "",
"password": "",
"remotePath": "/web",
"uploadOnSave": true
}
So, when I change a file and save it (Mac-OS 14.6.1) I expected it to send to remote but get:
[08-21 11:28:21] [info] [file-save] <local_vs-code_source_location/filename.css>
[08-21 11:28:22] [info] local ➞ remote <local_vs-code_source_location/filename.css>
I have replaced all private data with descriptions in <...>
It all used to work fine and I'm not sure what changed to cause it to continually fail.
Sometimes an uninstall including removing all extension data from VS-Code and refreshing fixes it, then later it regresses.
It may be when I switch networks but I'm not sure. Anyway, it seems rather odd that it'd try to send back to the file's own location.
The text was updated successfully, but these errors were encountered:
I use a normal install and the following simple config:
{
"name": "Servers",
"host": "",
"protocol": "sftp",
"port": ,
"secure": true,
"username": "",
"password": "",
"remotePath": "/web",
"uploadOnSave": true
}
So, when I change a file and save it (Mac-OS 14.6.1) I expected it to send to remote but get:
[08-21 11:28:21] [info] [file-save] <local_vs-code_source_location/filename.css>
[08-21 11:28:22] [info] local ➞ remote <local_vs-code_source_location/filename.css>
I have replaced all private data with descriptions in <...>
It all used to work fine and I'm not sure what changed to cause it to continually fail.
Sometimes an uninstall including removing all extension data from VS-Code and refreshing fixes it, then later it regresses.
It may be when I switch networks but I'm not sure. Anyway, it seems rather odd that it'd try to send back to the file's own location.
The text was updated successfully, but these errors were encountered: