Pipeline error: "could not load config from forge: %!w()" #279

AlexanderAmelkin commented 2025年10月23日 12:03:38 +02:00

For some reason, the pipelines for my frugen project stopped running some time ago.

All I see in the Woodpecker UI when I push "Show errors" is "could not load config from forge: %!w()".
This happens for all the branches.

Please see the project status here: https://ci.codeberg.org/repos/13632

How can I fix that?

I suspect that may have started when I added a branch pages for my static pages, where I apparently do not have any woodpecker configuration (why would I? if .woodpecker.yml is required, then what should I put there to prevent any pipeline from running on that specific branch?)

For some reason, the pipelines for my frugen project stopped running some time ago. All I see in the Woodpecker UI when I push "Show errors" is "could not load config from forge: %!w()". This happens for all the branches. Please see the project status here: https://ci.codeberg.org/repos/13632 How can I fix that? I suspect that may have started when I added a branch pages for my static pages, where I apparently do not have any woodpecker configuration (why would I? if .woodpecker.yml is required, then what should I put there to prevent any pipeline from running on that specific branch?)

Gusted commented 2025年10月23日 13:45:16 +02:00

Could you try to logout of https://ci.codeberg.org/ and login again? then restart a pipeline.

Could you try to logout of https://ci.codeberg.org/ and login again? then restart a pipeline.

6543 commented 2025年10月23日 14:51:40 +02:00

I think the repair repo option in repo settings -> actions
could help

I think the `repair repo` option in repo settings -> actions could help

6543 commented 2025年10月23日 14:53:56 +02:00

also your config looks strange ...

 commands: >
 # Run the build.
 mkdir build
 cd build
 cmake ..
 make

it would be more common to do:

 commands:
 - mkdir build
 - cd build
 - cmake ..
 - make

also your config looks strange ... ``` commands: > # Run the build. mkdir build cd build cmake .. make ``` it would be more common to do: ``` commands: - mkdir build - cd build - cmake .. - make ```

AlexanderAmelkin commented 2025年10月23日 16:34:24 +02:00

The commands format is fine and has always been like this.
It's to allow for wrapping lines of long commands, it's called "folded style block scalar" and is described here:
https://yaml.org/spec/1.2.2/#813-folded-style
and here in more human-readable form: https://stackoverflow.com/a/21699210/1286717

There are no long lines now, but there were some in the past. Anyway, the same format is used in my other project and works just fine there: https://ci.codeberg.org/repos/13633/pipeline/50/config
However, for frugen, the same page is just empty: https://ci.codeberg.org/repos/13632/pipeline/168/config

The .woodpecker.yml file is essentially the same for both projects:
https://codeberg.org/IPMITool/frugen/src/branch/bugfix/refactor-area-sorting/.woodpecker.yml -- broken (for master branch too)
https://codeberg.org/IPMITool/ipmitool/src/branch/master/.woodpecker.yml -- works

I tried pushing repair repo button, and the only change I see sis that now it says pipeline definition not found on the errors page.
It's totally unclear why the definition is 'not found'. If I download the metadata, both the workflow and step fields are empty:

{"repo": {"id": 13632,"name": "frugen","owner": "IPMITool","remote_id": "111660","forge_url": "https://codeberg.org/IPMITool/frugen","clone_url": "https://codeberg.org/IPMITool/frugen.git","clone_url_ssh": "ssh://git@codeberg.org/IPMITool/frugen.git","default_branch": "master","trusted": {}},..."workflow": {},"step": {},"sys": {"name": "woodpecker","host": "ci.codeberg.org","url": "https://ci.codeberg.org","version": "3.10.0"},"forge": {"type": "forgejo","url": "https://codeberg.org"}}

I can't understand why it's so and how to fix that. Not much debug info is available regarding the step where Woodpecker pulls the configuration from the repo.

The commands format is fine and has always been like this. It's to allow for wrapping lines of long commands, it's called "folded style block scalar" and is described here: https://yaml.org/spec/1.2.2/#813-folded-style and here in more human-readable form: https://stackoverflow.com/a/21699210/1286717 There are no long lines now, but there were some in the past. Anyway, the same format is used in my other project and works just fine there: https://ci.codeberg.org/repos/13633/pipeline/50/config However, for `frugen`, the same page is just empty: https://ci.codeberg.org/repos/13632/pipeline/168/config The `.woodpecker.yml` file is essentially the same for both projects: https://codeberg.org/IPMITool/frugen/src/branch/bugfix/refactor-area-sorting/.woodpecker.yml -- broken (for `master` branch too) https://codeberg.org/IPMITool/ipmitool/src/branch/master/.woodpecker.yml -- works I tried pushing `repair repo` button, and the only change I see sis that now it says `pipeline definition not found` on the errors page. It's totally unclear why the definition is 'not found'. If I download the metadata, both the `workflow` and `step` fields are empty: ```yaml { "repo": { "id": 13632, "name": "frugen", "owner": "IPMITool", "remote_id": "111660", "forge_url": "https://codeberg.org/IPMITool/frugen", "clone_url": "https://codeberg.org/IPMITool/frugen.git", "clone_url_ssh": "ssh://git@codeberg.org/IPMITool/frugen.git", "default_branch": "master", "trusted": {} }, ... "workflow": {}, "step": {}, "sys": { "name": "woodpecker", "host": "ci.codeberg.org", "url": "https://ci.codeberg.org", "version": "3.10.0" }, "forge": { "type": "forgejo", "url": "https://codeberg.org" } } ``` I can't understand why it's so and how to fix that. Not much debug info is available regarding the step where Woodpecker pulls the configuration from the repo.

AlexanderAmelkin commented 2025年10月23日 16:36:12 +02:00

Loggin out and back in also didn't help (I wouldn't expect otherwise because it's clearly a backend, not a UI problem)

Loggin out and back in also didn't help (I wouldn't expect otherwise because it's clearly a backend, not a UI problem)

Gusted commented 2025年10月23日 20:41:39 +02:00

@AlexanderAmelkin wrote in #279 (comment):

I tried pushing repair repo button, and the only change I see sis that now it says pipeline definition not found on the errors page.

Hm that's a different error, that's promising. It might help if you push a commit to the master branch, it's possible it will find the pipeline when doing a clean "run".

@AlexanderAmelkin wrote in https://codeberg.org/Codeberg-CI/feedback/issues/279#issuecomment-7869638: > I tried pushing `repair repo` button, and the only change I see sis that now it says `pipeline definition not found` on the errors page. Hm that's a different error, that's promising. It might help if you push a commit to the `master` branch, it's possible it will find the pipeline when doing a clean "run".

AlexanderAmelkin commented 2025年10月24日 15:19:50 +02:00

You're right! After a new commit to master, it picked up the configuration and ran the build successfully.
I'm now wondering whether or not it will break again when I push to pages branch that doesn't contain .woodpecker.yml

You're right! After a new commit to `master`, it picked up the configuration and ran the build successfully. I'm now wondering whether or not it will break again when I push to `pages` branch that doesn't contain `.woodpecker.yml`

Gusted commented 2025年10月24日 16:27:48 +02:00

@AlexanderAmelkin wrote in #279 (comment):

I'm now wondering whether or not it will break again when I push to pages branch that doesn't contain .woodpecker.yml

It will not break. It checks the default branch for the woodpecker pipeline.

@AlexanderAmelkin wrote in https://codeberg.org/Codeberg-CI/feedback/issues/279#issuecomment-7882763: > I'm now wondering whether or not it will break again when I push to `pages` branch that doesn't contain `.woodpecker.yml` It will not break. It checks the default branch for the woodpecker pipeline.