Error: no such file or directory, '/src/packages/server/build/web/favicon.ico'

• code-server version:
• OS Version: Ubuntu Server 16

Description

When I run code server, everything works and I can connect, but after about 2 minutes (I haven’t done anything in this time) I get this error:

Error: ENOENT: no such file or directory, open '/src/packages/server/build/web/favicon.ico'
INFO  WebSocket opened / {"client":1,"ip":"172.17.0.1"}
internal/child_process.js:366
    throw errnoException(err, 'spawn');
    ^

Error: spawn ENOMEM
    at ChildProcess.spawn (internal/child_process.js:366:11)
    at Object.spawn [as _spawn] (child_process.js:538:9)
    at t.async (/src/packages/server/out/cli.js:504:34598)
    at e.exports (/src/packages/server/out/cli.js:504:34099)
    at e (/src/packages/server/out/cli.js:504:32722)
    at Timeout.u [as _onTimeout] (/src/packages/server/out/cli.js:504:33015)
    at ontimeout (timers.js:436:11)
    at tryOnTimeout (timers.js:300:5)
    at listOnTimeout (timers.js:263:5)
    at Timer.processTimers (timers.js:223:10)

Steps to Reproduce

1. Start code server using docker command
2. Wait
3. After about 2 minutes, the following error appears

[EnKrypt]

I’m running the release binaries directly and not via AUR so I guess these remain relevant.

I guess I should add that it’s still very usable in its current state. The bugs I’m facing are more of an inconvenience than a deal breaker, but I would like to help solve them. If I can get more closure on some of these, I’d like to chip in and write up PRs myself.

The folder opening issue is rather strange. I thought I saw an issue earlier about it, but I was wrong and those were different. I hope you don’t mind if I open another issue documenting that bug.

The crashes are rather strange, setting to verbose and inspecting will help. If it’s not something that I can fix in my env, I’ll open an issue for that too.

The terminal glitching is rather rare, but it does happen. I don’t think it’s a bandwidth issue since I’m running off my local network. As you say however, this is an upstream issue not relating to code-server.

In all honestly, I’ve never quite heard of Arch in the context of a best-practice distro. It’s part of Linux mainstream and if some of these bugs are indeed Arch specific, then I think it’s in our interest to address them as well.

Anyway, I apologize for completely derailing this. I will open new issues as I investigate and help figure out how we can solve them.

[sr229]

Closing as fixed. Favicon works as intended now.