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
Observe that the path is not excluded and causes a file watcher error
I am connecting to a large workspace with a lot of files that are causing [error] [File Watcher (parcel)] Inotify limit reached (ENOSPC) (path: /home/ec2-user)
In an attempt to fix the problem I added the large directories (e.g. conda) to the files.watcherExclude setting in the remote settings.json, but the error continued. I then added both ** and **/** as a test to exclude everything, but the error continues to occur. I also tried adding the same settings to my local user and the workspace settings.json but this also did nothing.
[12:43:18.306] Log Level: 2
[12:43:18.307] remote-ssh@0.76.1
[12:43:18.307] win32 x64
[12:43:18.366] SSH Resolver called for "ssh-remote+ec2-1-2-3.ap-southeast-2.compute.amazonaws.com", attempt 1
[12:43:18.367] "remote.SSH.useLocalServer": false
[12:43:18.368] "remote.SSH.showLoginTerminal": false
[12:43:18.368] "remote.SSH.remotePlatform": {"ec2-1-2-3.ap-southeast-2.compute.amazonaws.com":"linux","ec2-1-2-3.ap-southeast-2.compute.amazonaws.com":"linux"}
[12:43:18.368] "remote.SSH.path": undefined
[12:43:18.368] "remote.SSH.configFile": C:\Users\User\.ssh\config
[12:43:18.368] "remote.SSH.useFlock": true
[12:43:18.368] "remote.SSH.lockfilesInTmp": false
[12:43:18.369] "remote.SSH.localServerDownload": auto
[12:43:18.369] "remote.SSH.remoteServerListenOnSocket": false
[12:43:18.369] "remote.SSH.showLoginTerminal": false
[12:43:18.369] "remote.SSH.defaultExtensions": []
[12:43:18.370] "remote.SSH.loglevel": 2
[12:43:18.370] "remote.SSH.enableDynamicForwarding": true
[12:43:18.370] "remote.SSH.enableRemoteCommand": false
[12:43:18.370] "remote.SSH.serverPickPortsFromRange": {}
[12:43:18.372] "remote.SSH.serverInstallPath": {"ec2-1-2-3.ap-southeast-2.compute.amazonaws.com":"/home/ec2-user/workspace"}
[12:43:18.375] SSH Resolver called for host: ec2-1-2-3.ap-southeast-2.compute.amazonaws.com
[12:43:18.376] Setting up SSH remote "ec2-1-2-3.ap-southeast-2.compute.amazonaws.com"
[12:43:18.383] Using commit id "b5205cc8eb4fbaa726835538cd82372cc0222d43" and quality "stable" for server
[12:43:18.386] Install and start server if needed
[12:43:18.388] Checking ssh with "ssh -V"
[12:43:18.434] > OpenSSH_for_Window
[12:43:18.434] > s_8.1p1, LibreSSL 3.0.2
[12:43:18.440] Using SSH config file "C:\Users\User\.ssh\config"
[12:43:18.441] Running script with connection command: ssh -T -D 57947 -F "C:\Users\User\.ssh\config" "ec2-3-105-143-71.ap-southeast-2.compute.amazonaws.com" bash
[12:43:18.443] Terminal shell path: C:\WINDOWS\System32\cmd.exe
[12:43:18.766] > �]0;C:\WINDOWS\System32\cmd.exe�
[12:43:18.766] Got some output, clearing connection timeout
[12:43:20.714] > {
> "RequestId": "f879cad6-3070-4ec1-91d9-c2b3e7bd734e",
> "Success": true
> }
[12:43:22.248] > c86f99b5e7f4: running
[12:43:22.282] > Acquiring lock on /home/ec2-user/workspace/.vscode-server/bin/b5205cc8eb4fbaa726
> 835538cd82372cc0222d43/vscode-remote-lock.ec2-user.b5205cc8eb4fbaa726835538cd823
> 72cc0222d43
[12:43:22.326] > Found existing installation at /home/ec2-user/workspace/.vscode-server/bin/b5205
> cc8eb4fbaa726835538cd82372cc0222d43...
> Checking /home/ec2-user/workspace/.vscode-server/.b5205cc8eb4fbaa726835538cd8237
> 2cc0222d43.log and /home/ec2-user/workspace/.vscode-server/.b5205cc8eb4fbaa72683
> 5538cd82372cc0222d43.pid for a running server
> Looking for server with pid: 19829
> Starting server with command... /home/ec2-user/workspace/.vscode-server/bin/b520
> 5cc8eb4fbaa726835538cd82372cc0222d43/bin/code-server --start-server --host=127.0
> .0.1 --accept-server-license-terms --enable-remote-auto-shutdown --port=0 --tele
> metry-level all &> "/home/ec2-user/workspace/.vscode-server/.b5205cc8eb4fbaa72
> 6835538cd82372cc0222d43.log" < /dev/null
> printenv:
> MANPATH=/opt/aws/neuron/share/man:
> XDG_SESSION_ID=43
> SHELL=/bin/bash
> SSH_CLIENT=1.2.3.4 57951 22
> CONDA_SHLVL=0
> USER=ec2-user
> LD_LIBRARY_PATH=/opt/amazon/efa/lib64:/opt/amazon/openmpi/lib64:/usr/local/l
> ib:/usr/lib:/lib:
> CONDA_EXE=/home/ec2-user/anaconda3/bin/conda
> VSCODE_AGENT_FOLDER=/home/ec2-user/workspace/.vscode-server
> _CE_CONDA=
> PATH=/home/ec2-user/anaconda3/condabin:/opt/amazon/openmpi/bin/:/opt/amazon/
> efa/bin/:/home/ec2-user/anaconda3/condabin:/home/ec2-user/.dl_binaries/bin:/opt/
> aws/neuron/bin:/usr/libexec/gcc/x86_64-redhat-linux/7:/opt/aws/bin:/usr/local/bi
> n:/usr/bin
[12:43:22.330] >
> MAIL=/var/mail/ec2-user
> PWD=/home/ec2-user
> LANG=en_US.UTF-8
> MODULEPATH=/usr/share/Modules/modulefiles:/etc/modulefiles
> LOADEDMODULES=
> _CE_M=
> HOME=/home/ec2-user
> SHLVL=2
> LOGNAME=ec2-user
> CONDA_PYTHON_EXE=/home/ec2-user/anaconda3/bin/python
> SSH_CONNECTION=101.113.92.197 57951 172.31.0.49 22
> MODULESHOME=/usr/share/Modules
> PKG_CONFIG_PATH=/usr/local/lib/pkgconfig:
> LESSOPEN=||/usr/bin/lesspipe.sh %s
> XDG_RUNTIME_DIR=/run/user/1000
> BASH_FUNC_module()=() { eval `/usr/bin/modulecmd bash $*`
> }
> _=/usr/bin/printenv
[12:43:22.347] > Removing old logfile at /home/ec2-user/workspace/.vscode-server/.b5205cc8eb4fbaa
> 726835538cd82372cc0222d43.log
[12:43:22.365] > Spawned remote server: 1923
> Waiting for server log...
[12:43:22.380] >
[12:43:22.403] > Waiting for server log...
[12:43:22.440] >
> *
> * Reminder: You may only use this software with Visual Studio family products,
> * as described in the license (https://go.microsoft.com/fwlink/?linkid=2077057)
> *
>
[12:43:22.447] >
> c86f99b5e7f4: start
> SSH_AUTH_SOCK====
> DISPLAY====
> webUiAccessToken====
> listeningOn==45373==
> osReleaseId==amzn==
[12:43:22.457] >
[12:43:22.467] > arch==x86_64==
> tmpDir==/run/user/1000==
> platform==linux==
> unpackResult====
> didLocalDownload==0==
> downloadTime====
> installTime====
> extInstallTime====
> serverStartTime==119==
> connectionToken==11aa1111-11aa-1111-111a-111aa1aa1a1a==
> c86f99b5e7f4: end
[12:43:22.468] Received install output:
SSH_AUTH_SOCK====
DISPLAY====
webUiAccessToken====
listeningOn==45373==
osReleaseId==amzn==
arch==x86_64==
tmpDir==/run/user/1000==
platform==linux==
unpackResult====
didLocalDownload==0==
downloadTime====
installTime====
extInstallTime====
serverStartTime==119==
connectionToken==11aa1111-11aa-1111-111a-111aa1aa1a1a==
[12:43:22.469] Remote server is listening on 45373
[12:43:22.469] Parsed server configuration: {"serverConfiguration":{"remoteListeningOn":{"port":45373},"osReleaseId":"amzn","arch":"x86_64","webUiAccessToken":"","sshAuthSock":"","display":"","tmpDir":"/run/user/1000","platform":"linux","connectionToken":"11aa1111-11aa-1111-111a-111aa1aa1a1a"},"serverStartTime":119,"installUnpackCode":""}
[12:43:22.473] Starting forwarding server. localPort 57952 -> socksPort 57947 -> remotePort 45373
[12:43:22.474] Forwarding server listening on 57952
[12:43:22.474] Waiting for ssh tunnel to be ready
[12:43:22.475] Tunneled 45373 to local port 57952
[12:43:22.475] Resolved "ssh-remote+ec2-1-2-3.ap-southeast-2.compute.amazonaws.com" to "127.0.0.1:57952"
[12:43:22.476] [Forwarding server 57952] Got connection 0
[12:43:22.490] ------
[12:43:22.515] [Forwarding server 57952] Got connection 1
[12:43:22.838] [Forwarding server 57952] Got connection 2
The text was updated successfully, but these errors were encountered:
A limitation on Linux that we still have is that more complex glob patterns for excludes are not supported on the native layer. Please spell out the paths if possibe.
Steps to Reproduce:
I am connecting to a large workspace with a lot of files that are causing
[error] [File Watcher (parcel)] Inotify limit reached (ENOSPC) (path: /home/ec2-user)
In an attempt to fix the problem I added the large directories (e.g. conda) to the
files.watcherExclude
setting in the remote settings.json, but the error continued. I then added both**
and**/**
as a test to exclude everything, but the error continues to occur. I also tried adding the same settings to my local user and the workspace settings.json but this also did nothing.The text was updated successfully, but these errors were encountered: