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
{{ message }}
Repository navigation
[Bug]: "Visual Studio Code is unable to watch for file changes in this large workspace" (error ENOSPC) #4782
Hmm...I guess this is specific to Linux. I couldn't reproduce locally on macOS.
I'm seeing the "permission denied" errors in your logs. Sounds like that solution isn't working.
To me, this seems like an issue specific to your environment and not a bug in code-server. Do you agree? (Still willing to help but want to clarify and see if we're on the same page)
Hmm I do agree
Synology have lots of stupid issues and their docker version is ancient…
What is interesting is, before when I was in older version, this error didnt pop up..
Hmm...well things definitely changed in code-server between versions so not ruling that out, but at least we agree. Let's move this to a Q and A then and continue there.
Activity
jsjoeio commentedon Jan 24, 2022
Oops. Looks like our new template is missing reproduction steps. How do I reproduce this?
YueMiyuki commentedon Jan 24, 2022
Hi
Just create an new code-server and if you have big files like
node_modulesand the project is running somewhere else,It will return this
mauri-sfdc commentedon Jan 25, 2022
@ItzMiracleOwO is the output of
df -iin the terminal? are you running code-server in docker in Synology DSM?YueMiyuki commentedon Jan 25, 2022
yes im on DSM
jsjoeio commentedon Jan 25, 2022
Hmm...I guess this is specific to Linux. I couldn't reproduce locally on macOS.
I'm seeing the "permission denied" errors in your logs. Sounds like that solution isn't working.
To me, this seems like an issue specific to your environment and not a bug in code-server. Do you agree? (Still willing to help but want to clarify and see if we're on the same page)
YueMiyuki commentedon Jan 26, 2022
Hmm I do agree
Synology have lots of stupid issues and their docker version is ancient…
What is interesting is, before when I was in older version, this error didnt pop up..
jsjoeio commentedon Jan 26, 2022
Hmm...well things definitely changed in code-server between versions so not ruling that out, but at least we agree. Let's move this to a Q and A then and continue there.