\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]",[2896,2899],{"name":2897,"color":2898},"bug","d73a4a",{"name":2900,"color":2901},"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.7593114,{"description":2908,"labels":2909,"number":2912,"owner":2875,"repository":2876,"state":2877,"title":2913,"updated_at":2914,"url":2915,"score":2916},"### Clear and concise description of the problem\n\nOn the \"Settings > Queue\" page, tasks with dependencies list which task they're waiting for with a `waiting for ####` label. Tasks with dependencies that haven't finished yet are marked before the task ID with a red circle with a square punched out of the middle. Tasks with completed dependencies still display the `waiting for` label, but the task ID marker is just an empty circle. It can be confusing to see a task list a dependency with an ID number that is no longer visible in the queue, because it has finished.\n\n### Suggested solution\n\nI propose that the `waiting for` label is removed once that dependent task is finished and removed from the queue display.\n\n### Alternative\n\nAlternatively, don't remove dependent tasks from the queue until all related tasks are complete. Mark completed tasks with a checkmark in a green circle.\r\n\r\nRemoving the `waiting for` label is probably the preferred option.\n\n### Additional context\n\n_No response_\n\n### Validations\n\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]\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 request the same feature to avoid creating a duplicate.",[2910,2911],{"name":2900,"color":2901},{"name":2869,"color":2870},2574,"Queued tasks should drop \"waiting for\" after the dependent task completes","2023-10-12T15:59:46Z","https://github.com/woodpecker-ci/woodpecker/issues/2574",0.76703376,{"description":2918,"labels":2919,"number":2925,"owner":2875,"repository":2876,"state":2926,"title":2927,"updated_at":2928,"url":2929,"score":2930},"like the agent:\r\nhttps://github.com/woodpecker-ci/woodpecker/blob/205f8ecc1649ab48a9d5fb52b0ecd7b8c24abf4f/docker/Dockerfile.agent.multiarch#L21\r\n\r\nref https://docs.docker.com/engine/reference/builder/#healthcheck\r\n\r\nTODO:\r\n- [ ] add subcommand to server that can test against https://github.com/woodpecker-ci/woodpecker/blob/205f8ecc1649ab48a9d5fb52b0ecd7b8c24abf4f/server/router/router.go#L69\r\n- [ ] use subcommand in container",[2920,2923,2924],{"name":2921,"color":2922},"server","5D7A92",{"name":2886,"color":2887},{"name":2872,"color":2873},1943,"closed","Add an healthcheck to server container","2023-07-25T13:55:31Z","https://github.com/woodpecker-ci/woodpecker/issues/1943",0.72737384,{"description":2932,"labels":2933,"number":2938,"owner":2875,"repository":2876,"state":2926,"title":2939,"updated_at":2940,"url":2941,"score":2942},"### Clear and concise description of the problem\r\n\r\nI'm trying to run a container image build step in my pipeline that uses [buildah](https://quay.io/repository/buildah/stable?tab=info). I'm running into a lot of permission errors like this:\r\n\r\n```\r\ntime=\"2023-10-07T19:59:26Z\" level=error msg=\"writing \\\"0 0 4294967295\\\\n\\\" to /proc/17/uid_map: write /proc/17/uid_map: operation not permitted\"\r\ntime=\"2023-10-07T19:59:26Z\" level=error msg=\"(Unable to determine exit status)\"\r\n```\r\n\r\nAfter some experimentation with podman and buildah containers on my cluster, I have determined that I need to configure a few different settings at the Pod level for this to work:\r\n\r\n- `metadata.annotations`: I need to be able to set `container.apparmor.security.beta.kubernetes.io/\u003Ccontainer_name>` to use a custom apparmor profile for my buildah container. I would like to use the `WOODPECKER_BACKEND_K8S_POD_ANNOTATIONS` env variable, but since the container names are randomly generated I'm not sure how to make this work.\r\n- `spec.securityContext`: The only way I have found to make buildah work is to run it as non-root. This means that I need to set `runAsUser`, `runAsGroup`, and `fsGroup` on the Pod level `securityContext` (not the container level).\r\n\r\n### Suggested solution\r\n\r\nAdding support for `securityContext` seems like it should be fairly straightforward. We could just follow that same approach that is currently used for `resources`, `nodeSelector`, etc. [documented here](https://woodpecker-ci.org/docs/next/administration/backends/kubernetes#resources).\r\n\r\nThe AppArmor profile is trickier since the container name needs to be included in the annotation key. I'm imagining a configuration like `backend_options.kubernetes.appArmorProfile` that could take all of the possible values for the annotation [documented here](https://kubernetes.io/docs/tutorials/security/apparmor/). Then, the pod generation logic would just look for this configuration and add the appropriate annotation if it's found.\r\n\r\n### Alternative\r\n\r\nI could disable AppArmor entirely, but that's not really advisable for a production environment. I could also try to find a way to get the buildah container running as root (it should be possible), but again, that's not ideal from a security perspective.\r\n\r\n### Additional context\r\n\r\nThis is somewhat of a follow up from #2510. I'm trying to get Woodpecker to run on my kubeadm/CRI-O based cluster running on Debian which I believe makes me some kind of leprechaun/unicorn/lochness monster. There definitely aren't many of us out there.\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 [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 request the same feature to avoid creating a duplicate.",[2934,2935],{"name":2869,"color":2870},{"name":2936,"color":2937},"backend/kubernetes","bfdadc",2545,"Support AppArmor annotations and securityContext in kubernetes backend","2024-01-12T22:32:26Z","https://github.com/woodpecker-ci/woodpecker/issues/2545",0.7298216,{"description":2944,"labels":2945,"number":2947,"owner":2875,"repository":2876,"state":2926,"title":2948,"updated_at":2949,"url":2950,"score":2951},"### Component\n\nagent\n\n### Describe the bug\n\nThe docs say: https://woodpecker-ci.org/docs/usage/pipeline-syntax#tag\r\n\r\nbut the filter in a condition is not working for tags:\r\n\r\n```\r\n when:\r\n event: tag\r\n tag: v*\r\n```\r\nThe step with this condition is executed, even when the tag name is something different e.g. 'x' or 'pre1.2.3'\r\n\r\nHow to use this feature? \r\n\r\n\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"0.15.1\"}\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/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] Check that this is a concrete bug. For Q&A join our [Discord Chat Server](https://discord.gg/fcMQqSMXJy).",[2946],{"name":2897,"color":2898},945,"Tag filter in when is not working","2022-12-23T21:05:55Z","https://github.com/woodpecker-ci/woodpecker/issues/945",0.7438954,{"description":2953,"labels":2954,"number":2959,"owner":2875,"repository":2876,"state":2926,"title":2960,"updated_at":2961,"url":2962,"score":2963},"### Component\n\ncli\n\n### Describe the bug\n\nSince updating to 2.4.x woodpecker-cli runs into a runtime error:\r\n\r\n```\r\npanic: runtime error: invalid memory address or nil pointer dereference\r\n[signal SIGSEGV: segmentation violation code=0x2 addr=0x20 pc=0x1004c71a8]\r\n\r\ngoroutine 1 [running]:\r\ngo.woodpecker-ci.org/woodpecker/v2/cli/internal/config.Load(0x14000591580)\r\n go.woodpecker-ci.org/woodpecker/v2/cli/internal/config/config.go:53 +0x268\r\ngo.woodpecker-ci.org/woodpecker/v2/cli/common.Before(0x14000591580)\r\n go.woodpecker-ci.org/woodpecker/v2/cli/common/hooks.go:53 +0x70\r\ngithub.com/urfave/cli/v2.(*Command).Run(0x14000597760, 0x14000591580, {0x1400014c000, 0xc, 0xc})\r\n github.com/urfave/cli/v2@v2.27.1/command.go:219 +0x3d0\r\ngithub.com/urfave/cli/v2.(*App).RunContext(0x140001d6e00, {0x101e2cca0, 0x102d70660}, {0x1400014c000, 0xc, 0xc})\r\n github.com/urfave/cli/v2@v2.27.1/app.go:337 +0x514\r\ngithub.com/urfave/cli/v2.(*App).Run(...)\r\n github.com/urfave/cli/v2@v2.27.1/app.go:311\r\nmain.main()\r\n go.woodpecker-ci.org/woodpecker/v2/cmd/cli/main.go:26 +0x48\r\n```\r\n\r\nHere is an example. I export the variables first\r\n\r\n```\r\nexport WOODPECKER_PROJECT=\"test/project\"\r\nexport WOODPECKER_SERVER=\"https://our.server\"\r\nexport WOODPECKER_TOKEN=\"asdf\"\r\n```\r\n\r\nThen i run any command, like `woodpecker-cli pipeline ls` and the error occurs.\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"2.4.1\"}\r\n\r\n➜ ~ woodpecker-cli --version\r\nwoodpecker-cli version 2.4.1\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]",[2955,2956],{"name":2897,"color":2898},{"name":2957,"color":2958},"cli","1d76db",3553,"woodpecker-cli - runtime error: invalid memory address or nil pointer dereference with 2.4.x","2024-04-15T19:18:03Z","https://github.com/woodpecker-ci/woodpecker/issues/3553",0.7590692,{"description":2965,"labels":2966,"number":2971,"owner":2875,"repository":2876,"state":2926,"title":2972,"updated_at":2973,"url":2974,"score":2975},"### Component\n\nserver\n\n### Describe the bug\n\ngitea/forgejo organisations are getting imported as users.\r\n\r\n```\r\nsqlite> select * from orgs;\r\nid|name|is_user|private\r\n1|org1|1|1\r\n2|org2|1|0\r\n3|user|1|0\r\n```\r\n\r\n@qwerty287 suggested it's a bug in the gitea/forgejo driver in the ensuing [discord conversation](https://discord.com/channels/838698813463724034/838698813463724037/1192166176223141889)\r\n\r\n\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"2.1.1\"}\n```\n\n\n### Additional context\n\nForgejo Version\r\n 1.20.4+1 built with GNU Make 4.4.1, go1.20.8 : bindata, timetzdata, sqlite, sqlite_unlock_notify\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).",[2967,2968],{"name":2897,"color":2898},{"name":2969,"color":2970},"forge/gitea","E96280",3117,"gitea/forgejo organisations are being imported as users, not orgs","2024-01-08T08:05:40Z","https://github.com/woodpecker-ci/woodpecker/issues/3117",0.76013714,{"description":2977,"labels":2978,"number":2979,"owner":2875,"repository":2876,"state":2926,"title":2980,"updated_at":2981,"url":2982,"score":2983},"### Clear and concise description of the problem\n\nPeople miss this feature Drone CI has: https://docs.drone.io/runner/exec/overview/\r\n\r\nIt allows you to execute a build on a systems default shell, without isolation.\n\n### Suggested solution\n\nA user should be able to add and choose agents for a repo.\n\n### Alternative\n\nPeople keep using Drone CI.\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/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 request the same feature to avoid creating a duplicate.",[],847,"Support \"Exec runner\"","2022-03-23T16:56:18Z","https://github.com/woodpecker-ci/woodpecker/issues/847",0.7603073,["Reactive",2985],{},["Set"],["ShallowReactive",2988],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fB1hTG3ow8tliFuwbf-rZGZPss_vYAhaY3HNy_jXuaFE":-1},"/woodpecker-ci/woodpecker/4747"]