\r\n\n\n### Steps to reproduce\n\n.\n\n### Expected behavior\n\n_No response_\n\n### System Info\n\n```shell\n\"next-d126cf9e35\"\n```\n\n\n### Additional context\n\n_No response_\n\n### Validations\n\n- [X] Read the [docs](https://woodpecker-ci.org/docs/intro).\n- [X] Check that there isn't [already an issue](https://github.com/woodpecker-ci/woodpecker/issues) that reports the same bug to avoid creating a duplicate.\n- [X] Checked that the bug isn't fixed in the `next` version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]",[3170,3171],{"name":3154,"color":3155},{"name":3172,"color":3173},"ui","46DEA2",4677,"`tag` pipelines are missing avatar and commit title","2025-01-12T06:19:42Z","https://github.com/woodpecker-ci/woodpecker/issues/4677",0.74527043,{"description":3180,"labels":3181,"number":3183,"owner":3160,"repository":3161,"state":3162,"title":3184,"updated_at":3185,"url":3186,"score":3187},"### Component\n\nserver\n\n### Describe the bug\n\nHello,\r\nI've recently updated my Woodpecker agent and server to the latest `next` version. When I pushed to my repository, I noticed the pipeline didn't start, so I triggered it manually and got an error. By following the container's logs I noticed some errors very close to the ones on https://github.com/woodpecker-ci/woodpecker/issues/1609, which I thought was weird because I have a newer version and I don't think my pipeline is wrong. I also got the same thing described in that issue of having eternally stuck pipelines which can't be stopped. My error log from back then is here: https://pasty.nikko.cf/yrmUGk.txt\r\n\r\nIn order to avoid all possibilities of user error, I deleted the containers, the databse, and installed Woodpecker from scratch. I added again the repository and ran the pipeline. These are the logs as shown by `docker compose logs -f` from the moment of starting Woodpecker at first install to right after I had triggered the pipeline: https://pasty.nikko.cf/4m3bum.txt\r\n\r\nI noticed that running pipelines on other repositories worked - sort of: it ran the first step fine but hanged at the second one. I saw another couple of errors in the logs:\r\n```\r\nwoodpecker-woodpecker-server-1 | {\"level\":\"warn\",\"error\":\"sql: no rows in result set\",\"time\":\"2023-06-30T16:20:19Z\"}\r\nwoodpecker-woodpecker-server-1 | {\"level\":\"error\",\"error\":\"database is locked\",\"now\":1688142054,\"time\":\"2023-06-30T16:20:59Z\",\"message\":\"obtain cron list\"}\r\n```\r\nbut I think the first is caused by the database being locked, and the database being locked is caused by the program crashing earlier. As the pipeine was stuck, Woodpecker also took a worrying amount of CPU and I had to kill it to free it because it wouldn't stop normally.\r\n\r\nI hope this report can be helpful. Feel free to ask if you need more information.\r\n\n\n### System Info\n\n```shell\nVersion: `{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"next-44b54db4\"}`\r\nOS (`uname -a`): `Linux p4 5.10.0-23-amd64 #1 SMP Debian 5.10.179-1 (2023-05-12) x86_64 GNU/Linux` \r\nDocker version: `Docker version 24.0.2, build cb74dfc` \r\nCompose:\r\n\r\n# docker-compose.yml\r\nversion: '3'\r\n\r\nservices:\r\n woodpecker-server:\r\n image: woodpeckerci/woodpecker-server:next\r\n restart: always\r\n ports:\r\n - 8085:8000\r\n volumes:\r\n - ./data:/var/lib/woodpecker/\r\n environment:\r\n - WOODPECKER_OPEN=true\r\n - WOODPECKER_HOST=https://woodpecker.massivebox.net\r\n - WOODPECKER_GITEA=true\r\n - WOODPECKER_GITEA_URL=https://git.massivebox.net\r\n - WOODPECKER_GITEA_CLIENT=REDACTED\r\n - WOODPECKER_GITEA_SECRET=REDACTED\r\n - WOODPECKER_AGENT_SECRET=REDACTED\r\n networks:\r\n - internal\r\n - caddy\r\n labels:\r\n caddy: woodpecker.massivebox.net\r\n caddy.reverse_proxy: \"{{upstreams 8000}}\"\r\n\r\n woodpecker-agent:\r\n image: woodpeckerci/woodpecker-agent:next\r\n command: agent\r\n restart: always\r\n depends_on:\r\n - woodpecker-server\r\n volumes:\r\n - /var/run/docker.sock:/var/run/docker.sock\r\n environment:\r\n - WOODPECKER_SERVER=woodpecker-server:9000\r\n - WOODPECKER_AGENT_SECRET=REDACTED\r\n networks:\r\n - internal\r\n\r\nnetworks:\r\n caddy:\r\n name: caddy\r\n external: true\r\n internal:\r\n internal: true\r\n\r\n```\n```\n\n\n### Additional context\n\nConfiguration file: https://git.massivebox.net/ecodash/ecodash/src/branch/master/.woodpecker/.woodpecker.yml\n\n### Validations\n\n- [X] Read the [Contributing Guidelines](https://github.com/woodpecker-ci/woodpecker/blob/master/CONTRIBUTING.md).\n- [X] Read the [docs](https://woodpecker-ci.org/docs/intro).\n- [X] Check that there isn't [already an issue](https://github.com/woodpecker-ci/woodpecker/issues) that reports the same bug to avoid creating a duplicate.\n- [X] Checked that the bug isn't fixed in the `next` version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]\n- [X] Check that this is a concrete bug. For Q&A join our [Discord Chat Server](https://discord.gg/fcMQqSMXJy) or the [Matrix room](https://matrix.to/#/#woodpecker:matrix.org).",[3182],{"name":3154,"color":3155},1905,"Runtime error on manual pipeline execution","2024-03-20T23:43:12Z","https://github.com/woodpecker-ci/woodpecker/issues/1905",0.7518466,{"description":3189,"labels":3190,"number":3197,"owner":3160,"repository":3161,"state":3162,"title":3198,"updated_at":3199,"url":3200,"score":3201},"e.g. like https://github.com/woodpecker-ci/woodpecker/pull/3086 create pull tags.\r\n\r\njust clean them up if the pull gets closed",[3191,3194],{"name":3192,"color":3193},"enhancement","7E1FE4",{"name":3195,"color":3196},"build","6AB8BA",3087,"build: delete pr images on pull close","2023-12-31T07:28:26Z","https://github.com/woodpecker-ci/woodpecker/issues/3087",0.7531695,{"description":3203,"labels":3204,"number":3207,"owner":3160,"repository":3161,"state":3208,"title":3209,"updated_at":3210,"url":3211,"score":3212},"### Component\n\nagent\n\n### Describe the bug\n\nAgent image builds with `next-*` version instead of tag/release. Server version is OK.\n\n### System Info\n\n```shell\n{\"level\":\"info\",\"time\":\"2023-08-17T11:47:41Z\",\"message\":\"Starting Woodpecker server with version '1.0.2'\"}\r\n{\"level\":\"info\",\"time\":\"2023-08-17T12:01:26Z\",\"message\":\"Starting Woodpecker agent with version 'next-d9e06696' and backend 'kubernetes' using platform 'linux/amd64' running up to 1 pipelines in parallel\"}\n```\n\n\n### Additional context\n\n_No response_\n\n### Validations\n\n- [X] Read the [Contributing Guidelines](https://github.com/woodpecker-ci/woodpecker/blob/main/CONTRIBUTING.md).\n- [X] Read the [docs](https://woodpecker-ci.org/docs/intro).\n- [X] Check that there isn't [already an issue](https://github.com/woodpecker-ci/woodpecker/issues) that reports the same bug to avoid creating a duplicate.\n- [X] Checked that the bug isn't fixed in the `next` version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]\n- [X] Check that this is a concrete bug. For Q&A join our [Discord Chat Server](https://discord.gg/fcMQqSMXJy) or the [Matrix room](https://matrix.to/#/#woodpecker:matrix.org).",[3205,3206],{"name":3154,"color":3155},{"name":3195,"color":3196},2236,"closed","Incorrect version of agent","2023-08-18T14:39:20Z","https://github.com/woodpecker-ci/woodpecker/issues/2236",0.7037262,{"description":3214,"labels":3215,"number":3217,"owner":3160,"repository":3161,"state":3208,"title":3218,"updated_at":3219,"url":3220,"score":3221},"### Component\n\nserver, web-ui\n\n### Describe the bug\n\nHi, \r\n\r\nIf I try to create a secret from the webUI, a global or a user secret, it fails with \"unkown error\"\r\n\r\nI tried next and 2.0.0-rc0, with and without WOODPECKER_ENCRYPTION_KEY set. \r\nI tried sqlite and postgres backend, deleting the whole DB between tests. Same result each time. \r\n\r\nI switched to 1.0.3, works like a charm !\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"1.0.3\"}\r\n\r\nPostgres image : ghcr.io/cloudnative-pg/postgresql:16.0 ( 3 nodes cluster in k8s )\n```\n\n\n### Additional context\n\n_No response_\n\n### Validations\n\n- [X] Read the [Contributing Guidelines](https://github.com/woodpecker-ci/woodpecker/blob/main/CONTRIBUTING.md).\n- [X] Read the [docs](https://woodpecker-ci.org/docs/intro).\n- [X] Check that there isn't [already an issue](https://github.com/woodpecker-ci/woodpecker/issues) that reports the same bug to avoid creating a duplicate.\n- [X] Checked that the bug isn't fixed in the `next` version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]\n- [X] Check that this is a concrete bug. For Q&A join our [Discord Chat Server](https://discord.gg/fcMQqSMXJy) or the [Matrix room](https://matrix.to/#/#woodpecker:matrix.org).",[3216],{"name":3154,"color":3155},2821,"Can NOT create secret from the webUI","2023-11-23T06:46:03Z","https://github.com/woodpecker-ci/woodpecker/issues/2821",0.7039398,{"description":3223,"labels":3224,"number":3226,"owner":3160,"repository":3161,"state":3208,"title":3227,"updated_at":3228,"url":3229,"score":3230},"### Component\n\nagent\n\n### Describe the bug\n\nOn an arm64 agent (Raspberry Pi 4b+), the clone step fails when the container is running in podman:\r\n\r\n```\r\n+ git init -b main\r\nInitialized empty Git repository in /woodpecker/src/git.vdx.hu/voidcontext/nix-config/.git/\r\n+ git config --global --replace-all safe.directory /woodpecker/src/git.vdx.hu/voidcontext/nix-config\r\n+ git remote add origin https://git.vdx.hu/voidcontext/nix-config.git\r\n+ git fetch --no-tags --depth=1 --filter=tree:0 origin +a4b83a869d6366bf24921b8f4f3f5836f806f57e:fatal: unable to access 'https://git.vdx.hu/voidcontext/nix-config.git/': Could not resolve host: git.vdx.hu\r\nexit status 128\r\n```\r\n\r\nThe server is on a different server (on amd64).\r\n\r\nExample: https://woodpecker.ci.vdx.hu/repos/109/pipeline/119/5\r\n\r\nThe same pipeline is successful on an amd64 agent (Kubernetes on a 3rd machine).\r\n\r\nThe issue seems to be similar to https://github.com/woodpecker-ci/woodpecker/issues/1407 which has been closed bacause of inactivity.\n\n### Steps to reproduce\n\n1) install server on amd64 machine (A)\r\n2) install agent on arm64 machine (B) using Docker backend that points to a docker compatible podman socket.\r\n3) Run pipeline\n\n### Expected behavior\n\nGit is able to resolve the host as it has a public DNS record.\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"2.6.0\"}\r\n```\n```\n\n\n### Additional context\n\nUnfortunately I wasn't able to test this on `next`.\n\n### Validations\n\n- [X] Read the [docs](https://woodpecker-ci.org/docs/intro).\n- [X] Check that there isn't [already an issue](https://github.com/woodpecker-ci/woodpecker/issues) that reports the same bug to avoid creating a duplicate.\n- [X] Checked that the bug isn't fixed in the `next` version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]",[3225],{"name":3154,"color":3155},3892,"Git clone step fails with \"Could not resolve host\" error when running fetch","2024-07-18T22:49:20Z","https://github.com/woodpecker-ci/woodpecker/issues/3892",0.7271569,{"description":3232,"labels":3233,"number":3240,"owner":3160,"repository":3161,"state":3208,"title":3241,"updated_at":3242,"url":3243,"score":3244},"### Clear and concise description of the problem\r\n\r\nFor example, automatic detection doesn't work for Podman. This causes strange errors like `git executable doesn't exist` in the `clone` step.\r\nThis issue was posted on Matrix, but there was something like that before, as I remember.\r\n\r\n### Suggested solution\r\n\r\nDisable automatic fallback to the `local` backend.\r\n\r\n### Alternative\r\n\r\n_No response_\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Validations\r\n\r\n- [X] Checked that the feature isn't part of the `next` version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]\r\n- [X] Read the [docs](https://woodpecker-ci.org/docs/intro).\r\n- [X] Check that there isn't already an [issue](https://github.com/woodpecker-ci/woodpecker/issues) that request the same feature to avoid creating a duplicate.",[3234,3237],{"name":3235,"color":3236},"agent","ECBCDF",{"name":3238,"color":3239},"breaking","A1B83C",3996,"Disable auto-fallback to Local backend","2024-08-07T10:04:12Z","https://github.com/woodpecker-ci/woodpecker/issues/3996",0.73316735,{"description":3246,"labels":3247,"number":3255,"owner":3160,"repository":3161,"state":3208,"title":3256,"updated_at":3257,"url":3258,"score":3259},"### Component\r\n\r\nother\r\n\r\n### Describe the bug\r\n\r\nPlease take a look at this [issue on Codeberg](https://codeberg.org/Codeberg-CI/feedback/issues/136). I found out what causes this problem. See [this comment](https://codeberg.org/Codeberg-CI/feedback/issues/136#issuecomment-1318012) for details. #2126 added a Org for each user. But it looks like there was a mistake in the Migration, so the Users don't have access to their Org. `https://ci.codeberg.org/api/user `say my Org ID is 592, but `https://ci.codeberg.org/api/orgs/592 `gives me a 403.\r\n\r\n### System Info\r\n\r\n```shell\r\n{\r\n \"source\":\"https://github.com/woodpecker-ci/woodpecker\",\r\n \"version\":\"next-62e1081b24\"\r\n}\r\n```\r\n\r\n\r\n### Additional context\r\n\r\nI'm just a User and not the Admin of this instance, so I can't give you detailed technical information, but I want to share my findings.\r\n\r\n### Validations\r\n\r\n- [X] Read the [Contributing Guidelines](https://github.com/woodpecker-ci/woodpecker/blob/main/CONTRIBUTING.md).\r\n- [X] Read the [docs](https://woodpecker-ci.org/docs/intro).\r\n- [X] Check that there isn't [already an issue](https://github.com/woodpecker-ci/woodpecker/issues) that reports the same bug to avoid creating a duplicate.\r\n- [X] Checked that the bug isn't fixed in the `next` version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]\r\n- [X] Check that this is a concrete bug. For Q&A join our [Discord Chat Server](https://discord.gg/fcMQqSMXJy) or the [Matrix room](https://matrix.to/#/#woodpecker:matrix.org).",[3248,3249,3252],{"name":3154,"color":3155},{"name":3250,"color":3251},"forge/gitea","E96280",{"name":3253,"color":3254},"regression","7E192B",2714,"User don't have permission for own Org","2023-12-19T08:13:41Z","https://github.com/woodpecker-ci/woodpecker/issues/2714",0.7351513,{"description":3261,"labels":3262,"number":3266,"owner":3160,"repository":3161,"state":3208,"title":3267,"updated_at":3268,"url":3269,"score":3270},"Currently there are three different versions of a build-model being used: \r\n- \"normal\" build model\r\n- build-feed (build model with repo-name, repo-owner and repo-fullname)\r\n- build with procs and file-changes\r\n\r\nUsing the same data-model in three different versions brings some complexity with data-storing in the frontend as data has to be merged / stored twice.\r\n\r\nA suggestion to fix this problem would be:\r\n- create a new separate data-model called build-details\r\n - contains: build-id, procs and changed-files\r\n - could have its own endpoint similar to `/api/build`\r\n- add repo-id / repo-owner and repo-name to every build, so the corresponding repo information can simply be gathered from the data-store or by requesting the repo-endpoint. This way build-feed model can be easily replaced by normal build-model ",[3263],{"name":3264,"color":3265},"refactor","4f8cc9",259,"Unify build models","2022-09-29T16:17:44Z","https://github.com/woodpecker-ci/woodpecker/issues/259",0.73980236,["Reactive",3272],{},["Set"],["ShallowReactive",3275],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fGOtQkzRQlOGqoftK3HyXaVT4OupnDp2oX9LDf44jsKs":-1},"/woodpecker-ci/woodpecker/924"]