Reproduction Steps:
npm installws://.../connectThis is not 100% reproduction.
OS and version:
Diagnostics:
I suspect the root cause is this NPE.

@monaka I can't reliably reproduce this, my npm exits fine and there was no 504 reported in my end. Probably connection issues?
I don't think the root cause is connection issue.
Traefik report like this.
time="2017-09-10T06:40:22Z" level=warning msg="Error dialing `172.18.0.2:4412`: dial tcp 172.18.0.2:4412: getsockopt: connection timed out"
Looks the terminal service on dev-machine is down.
I created PR #6205 to show my expectations. Frankly I've not tested that yet. Anyway this will be issue by execution timing.
@monaka thanks for the issue and associated PR - it looks like you've found a bug here and we really appreciate the PR. One of the maintainers has already commented on the PR asking you for some feedback - can't wait to see this merged!
@monaka I was able to reproduce the NPE after some trials, so I can confirm this.
We've also seen this issue quite a lot, but in our case when we copy a massive amount of files/directories from within a docker image into the workspace
Is this still an issue?
Not for us, resolved with the tree fixes last year
Closing as fixed - @monaka if this is still an issue please reopen with details.