We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spottet twice in prod (here and here) after today's deployment:
panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x1c21260] goroutine 1 [running]: github.com/gitpod-io/gitpod/ws-daemon/pkg/dispatch.(*Dispatch).Close(0xc0002d8310, 0x0, 0x0) github.com/gitpod-io/gitpod/ws-daemon/pkg/dispatch/dispatch.go:152 +0x100 github.com/gitpod-io/gitpod/ws-daemon/pkg/daemon.(*Daemon).Stop(0xc000532840, 0x0, 0xc0008f8eb8) github.com/gitpod-io/gitpod/ws-daemon/pkg/daemon/daemon.go:178 +0x39
The call stack looks like the one from #5229 Container-version of ws-daemon: commit-2e90d32ba9ece42b8f56d1bb298c3ba53b4d2f99.
ws-daemon
The text was updated successfully, but these errors were encountered:
Line numbers are not matching anything sensible in this commit. To me it looks like the log is from a state before that the commit fixed.
Sorry, something went wrong.
Closing. Fixed in #5229
aledbf
No branches or pull requests
Spottet twice in prod (here and here) after today's deployment:
The call stack looks like the one from #5229
Container-version of
ws-daemon
: commit-2e90d32ba9ece42b8f56d1bb298c3ba53b4d2f99.The text was updated successfully, but these errors were encountered: