Prebuild failed "fatal: 'origin/main' is not a commit and a branch 'main' cannot be created from it

[david-bakin]

Bug description

Prebuild failed as follows:

SYSTEM ERROR
Prebuild failed for system reasons. Please contact support. cannot initialize workspace: cannot initialize workspace: git initializer clone: git checkout -B main origin/main failed (exit status 128): fatal: 'origin/main` is not a commit and a branch 'main' cannot be created from it

Main repo: https://gitlab.com/bakins-bits/gitpod-setup-for-bitcoin-core-dev/ (default branch is main, commit c800c2e3)

Additional repos:

• https://github.com/david-bakin/bitcoin (default branch is master, commit 695ca641a)
• https://github.com/david-bakin/btcdeb (default branch is master, commit 3ba1ec7f4)

Prebuild url: https://gitpod.io/projects/gitpod-setup-for-bitcoin-core-dev/7cfe11d0-5d28-47fd-963d-7d47c18859ec

Incremental prebuilds not enabled.

Note that this used to work. Nothing has changed recently in any of these repos (especially no change of default branch). Also only minor (unrelated) changes to .gitpod.yml and the custom docker image. (Though you can check that.)

Steps to reproduce

Just try to open / prebuild this workspace. Same thing also happens when opening new workspace off this repo w/o prebuild.

Workspace affected

https://bakinsbits-gitpodsetupf-gpparx4s13d.ws-us60.gitpod.io/

Expected behavior

Prebuild should work! Main repository and additional repositories should be fetched from their appropriate default branch (main for the main repo, master for the additional repos.)

Example repository

https://gitlab.com/bakins-bits/gitpod-setup-for-bitcoin-core-dev/-/tree/main

Anything else?

Commit hashes given above so I can advance gitpod.yml to try to get unwedged.

Front conversations

[david-bakin]

Also the error messages shown are inadequate for a multi-repo workspace: which repository is causing the trouble, eh?

[david-bakin]

Dup of #11854 ?

[axonasif]

Possibly.

[geropl]

Dup of #11854 ?

@david-bakin Yes, that seems to be the case. Moving over to workspace, but assume we can close it once rolled out.

[jenting]

This is duplicated of #11854, and it's deployed already.
Closing this issue now. Feel free to reopen it once you still encounter it.
Thank you.