\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]",[1984,1987],{"name":1985,"color":1986},"bug","d73a4a",{"name":1988,"color":1989},"ui","46DEA2",4677,"woodpecker-ci","woodpecker","open","`tag` pipelines are missing avatar and commit title","2025-01-12T06:19:42Z","https://github.com/woodpecker-ci/woodpecker/issues/4677",0.7092312,{"description":1999,"labels":2000,"number":2005,"owner":1991,"repository":1992,"state":1993,"title":2006,"updated_at":2007,"url":2008,"score":2009},"### 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.",[2001,2002],{"name":1988,"color":1989},{"name":2003,"color":2004},"enhancement","7E1FE4",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.71801376,{"description":2011,"labels":2012,"number":2017,"owner":1991,"repository":1992,"state":1993,"title":2018,"updated_at":2019,"url":2020,"score":2021},"we currently don't have a concept how to translate/interpreter the services into \"local backend\" and just ignore them.\r\n\r\nwe should have it that way so it works very similar to what the user know with docker or kube backend.",[2013,2014],{"name":2003,"color":2004},{"name":2015,"color":2016},"backend/local","bfdadc",3095,"Implement services for local backend","2025-02-10T13:40:24Z","https://github.com/woodpecker-ci/woodpecker/issues/3095",0.72311884,{"description":2023,"labels":2024,"number":2029,"owner":1991,"repository":1992,"state":1993,"title":2030,"updated_at":2031,"url":2032,"score":2033},"https://ci.woodpecker-ci.org/repos/8987/pipeline/94/errors\r\n\r\nversion: current main",[2025,2026],{"name":1985,"color":1986},{"name":2027,"color":2028},"server","5D7A92",4249,"[Bug] MultiForge: second forge can not be used","2024-10-25T17:33:00Z","https://github.com/woodpecker-ci/woodpecker/issues/4249",0.766343,{"description":2035,"labels":2036,"number":2039,"owner":1991,"repository":1992,"state":1993,"title":2040,"updated_at":2041,"url":2042,"score":2043},"### Component\n\nserver\n\n### Describe the bug\n\nError when enabling Gitea repository in Woodpecker CI:\n\n`could not create/update repo in store. error=\"pq: duplicate key value violates unique constraint \\\"UQE_repos_name\\\"\"`\n\nThere are no records with forge_id 0 in orgs table where we had similar problems\n\n### Steps to reproduce\n\n1. Press \"Enable\" in repository list\n2. Webhook is created\n3. Record in database can not be updated (possible tries to insert new one instead of updating?)\n\n### Expected behavior\n\n_No response_\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"3.3.0\"}\n```\n\n### Additional context\n\nPostgreSQL database, Gitea forge integration\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/versions]",[2037,2038],{"name":1985,"color":1986},{"name":2027,"color":2028},4935,"Activating repository error that failed to activate becauce of UQE_repos_name constraint","2025-03-11T14:11:01Z","https://github.com/woodpecker-ci/woodpecker/issues/4935",0.7675202,{"description":2045,"labels":2046,"number":2052,"owner":1991,"repository":1992,"state":1993,"title":2053,"updated_at":2054,"url":2055,"score":2056},"limit the add repo endpoint, to only return one page (in terms of pagination)\r\n\r\nand add a note (explizite hint) that if you can not find your desired repo to specify it in the searchbox to get it",[2047,2048,2049],{"name":2027,"color":2028},{"name":2003,"color":2004},{"name":2050,"color":2051},"ux","fef2c0",1774,"[UX] Add Repository, limit repos and add search hint","2024-04-02T08:05:24Z","https://github.com/woodpecker-ci/woodpecker/issues/1774",0.7697395,{"description":2058,"labels":2059,"number":2061,"owner":1991,"repository":1992,"state":2062,"title":2063,"updated_at":2064,"url":2065,"score":2066},"### 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]",[2060],{"name":1985,"color":1986},3892,"closed","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.7284623,{"description":2068,"labels":2069,"number":2071,"owner":1991,"repository":1992,"state":2062,"title":2072,"updated_at":2073,"url":2074,"score":2075},"### 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).",[2070],{"name":1985,"color":1986},945,"Tag filter in when is not working","2022-12-23T21:05:55Z","https://github.com/woodpecker-ci/woodpecker/issues/945",0.728657,{"description":2077,"labels":2078,"number":2080,"owner":1991,"repository":1992,"state":2062,"title":2081,"updated_at":2082,"url":2083,"score":2084},"### Component\r\n\r\nserver, agent\r\n\r\n### Describe the bug\r\n\r\nAfter renaming on matrix variable and forgetting to change on the `image` property,\r\nI noticed that woodpecker will fail (of cause), but with no meaningful error and without showing the error.\r\n\r\nThe webui only shows \"Unknown error\" and show `exit code 0` within that step (also the step is marked as \"succeeded\").\r\n\r\n\r\n\r\n\r\n### System Info\r\n\r\n```shell\r\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"next-c2b0c1d7\"}\r\n```\r\n\r\n\r\n### Additional context\r\nLog from server:\r\n```shell\r\n{\"level\":\"warn\",\"error\":\"sql: no rows in result set\",\"time\":\"2021-12-14T14:34:17Z\"}\r\n{\"level\":\"warn\",\"error\":\"sql: no rows in result set\",\"time\":\"2021-12-14T14:46:27Z\"}\r\n{\"level\":\"error\",\"time\":\"2021-12-14T14:47:52Z\",\"message\":\"failure to parse yaml from hook for Flaschengeist/flaschengeist-frontend. yaml: line 5: found character that cannot start any token\"}\r\n{\"level\":\"error\",\"error\":\"Error #01: yaml: line 5: found character that cannot start any token\\n\",\"ip\":\"172.22.0.1\",\"latency\":554.057332,\"method\":\"POST\",\"path\":\"/hook\",\"status\":200,\"time\":\"2021-12-14T14:47:52Z\",\"user-agent\":\"Go-http-client/1.1\",\"time\":\"2021-12-14T14:47:52Z\"}\r\n{\"level\":\"warn\",\"error\":\"sql: no rows in result set\",\"time\":\"2021-12-14T14:57:07Z\"}\r\n```\r\nLog from agent: [error.log](https://github.com/woodpecker-ci/woodpecker/files/7758788/error.log)\r\n\r\n### Validations\r\n\r\n- [X] Read the [Contributing Guidelines](https://github.com/woodpecker-ci/woodpecker/blob/master/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] Check that this is a concrete bug. For Q&A join our [Discord Chat Server](https://discord.gg/fcMQqSMXJy).",[2079],{"name":2003,"color":2004},637,"Unknown error and invalid state when pipeline contains invalid matrix tags","2024-02-11T23:24:04Z","https://github.com/woodpecker-ci/woodpecker/issues/637",0.74340093,{"description":2086,"labels":2087,"number":2090,"owner":1991,"repository":1992,"state":2062,"title":2091,"updated_at":2092,"url":2093,"score":2094},"### Component\n\nweb-ui\n\n### Describe the bug\n\nThe spaces in task output should be kept.\r\n\r\n\r\n\n\n### System Info\n\n```shell\n\"source\": \"https://github.com/woodpecker-ci/woodpecker\",\r\n\"version\": \"next-9feb6be9\"\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).",[2088,2089],{"name":1985,"color":1986},{"name":1988,"color":1989},718,"The spaces in task output should be kept.","2022-06-16T17:24:27Z","https://github.com/woodpecker-ci/woodpecker/issues/718",0.7469744,["Reactive",2096],{},["Set"],["ShallowReactive",2099],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"6AaJxH_TPrFm1qi81_BWQZltvs2_N0CufBzRhJ-hk0s":-1},"/woodpecker-ci/woodpecker/3924"]