The CI pipeline we set up for dialab/dialibra stopped working some time in the past few months for no apparent reason—there have been no configuration changes between the time it was working and now.
When running a job, we see could not load config from forge: %!w() on the errors tab.
Screenshot 2025年08月10日 at 5.18.40 PM
This seems to indicate it can't read the configuration file, but its location at .woodpecker/hugo.yml has not changed since it was previously working fine.
Debugging locally with woodpecker-cli exec is not viable because it won't support secrets until 3.9.0 is released.
I am unsure if this is related, but when clicking on the Branches tab for the repo I get a toast error that states failed to load branches: user does not exist [uid: 0, name: ]
Screenshot 2025年08月10日 at 5.17.49 PM
We see the same failures whether it is triggered by PR, Merge, or manual.
I tried setting up a custom agent to see if this would make a difference, and it did not.
At this point I have exhausted any diagnostic steps I can think of and would welcome suggestions or assistance.
The CI pipeline we set up for [dialab/dialibra](https://codeberg.org/dialab/dialibra) stopped working some time in the past few months for no apparent reason—there have been no configuration changes between the time it was working and now.
When running a job, we see `could not load config from forge: %!w()` on the errors tab.
This seems to indicate it can't read the configuration file, but its location at `.woodpecker/hugo.yml` has not changed since it was previously working fine.
Debugging locally with `woodpecker-cli exec` is not viable because it won't support secrets until [3.9.0 is released](https://github.com/woodpecker-ci/woodpecker/pull/5304).
I am unsure if this is related, but when clicking on the Branches tab for the repo I get a toast error that states `failed to load branches: user does not exist [uid: 0, name: ]`
We see the same failures whether it is triggered by PR, Merge, or manual.
I tried setting up a custom agent to see if this would make a difference, and it did not.
At this point I have exhausted any diagnostic steps I can think of and would welcome suggestions or assistance.
