Pavel Tumik

One possible cause of this is this: https://github.com/gitpod-io/gitpod/issues/12357

This is not an error any more. This is simply a by product of how gRPC logs its errors in tracing. When we call `/wsdaemon.WorkspaceContentService/WaitForInit` we need to return a...

We already have log entry for this: https://github.com/gitpod-io/gitpod/blob/6390f2064394ebccf788f4ff5b57fd66e0313ce1/components/content-service/pkg/initializer/git.go#L75 Also looking at logs, it looks like workspace failed, and then 5 minutes later ws-daemon tried to run initializer for it (???):...

This is related to this: https://github.com/gitpod-io/gitpod/issues/12282 If StopWorkspace was called while workspace was still doing content init, then it may fail with this exact error, as ws-daemon does not know...

Could be that our housekeeping job in ws-daemon does that? :thinking:

I would love to see this merged as well, as we currently dealing with the exact same problem, of having to modify containerd config so that it can actually read...

Just to confirm, I am running this version in our environment. Going to wait 48 hours to see if it will trigger or not.

@jacksontj nope, got it again. :( `unexpected error: runtime error: invalid memory address or nil pointer dereference`

@jacksontj I was getting it on 0.0.72, but right now going to switch to 0.0.73 and will let you now if I will get it on that version or not...

Yeah, no errors on 0.0.73 I will try no_recover build today and will keep you posted!