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
We regularly (multiple times per day) see random workspace init failures with an error message like:
cannot initialize workspace:
github.com/gitpod-io/gitpod/content-service/pkg/initializer.InitializeWorkspace
github.com/gitpod-io/gitpod/[email protected]/pkg/initializer/initializer.go:344
- git initializer:
github.com/gitpod-io/gitpod/content-service/pkg/initializer.(*GitInitializer).Run
github.com/gitpod-io/gitpod/[email protected]/pkg/initializer/git.go:69
- git clone https://github.com/midwayjs/midway.git . failed (exit status 128): Cloning into '.'...
fatal: Unable to create temporary file '/dst/midway/.git/objects/pack/tmp_idx_XXXXXX': No such file or directory
fatal: index-pack failed
Search for jsonPayload.message="content init failed"
A quick search didn't reveal any insights. The error seems to happen occasionally across the internet.
We might mitigate this with multiple attempts until we call it a failure.
The text was updated successfully, but these errors were encountered:
Something similar just bit me as well in #4167 (comment): in my io-dev environment, one specific incremental prebuild was apparently successful, but caused one specific commit context URL to always with:
Bug description
We regularly (multiple times per day) see random workspace init failures with an error message like:
Search for
jsonPayload.message="content init failed"
A quick search didn't reveal any insights. The error seems to happen occasionally across the internet.
We might mitigate this with multiple attempts until we call it a failure.
The text was updated successfully, but these errors were encountered: