\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]",[3020,3023],{"name":3021,"color":3022},"bug","d73a4a",{"name":3024,"color":3025},"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.7085893,{"description":3035,"labels":3036,"number":3043,"owner":3027,"repository":3028,"state":3029,"title":3044,"updated_at":3045,"url":3046,"score":3047},"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.",[3037,3040],{"name":3038,"color":3039},"enhancement","7E1FE4",{"name":3041,"color":3042},"backend/local","bfdadc",3095,"Implement services for local backend","2025-02-10T13:40:24Z","https://github.com/woodpecker-ci/woodpecker/issues/3095",0.7161905,{"description":3049,"labels":3050,"number":3055,"owner":3027,"repository":3028,"state":3029,"title":3056,"updated_at":3057,"url":3058,"score":3059},"https://ci.woodpecker-ci.org/repos/8987/pipeline/94/errors\r\n\r\nversion: current main",[3051,3052],{"name":3021,"color":3022},{"name":3053,"color":3054},"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.7230027,{"description":3061,"labels":3062,"number":3067,"owner":3027,"repository":3028,"state":3029,"title":3068,"updated_at":3069,"url":3070,"score":3071},"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",[3063,3064],{"name":3038,"color":3039},{"name":3065,"color":3066},"build","6AB8BA",3087,"build: delete pr images on pull close","2023-12-31T07:28:26Z","https://github.com/woodpecker-ci/woodpecker/issues/3087",0.7314679,{"description":3073,"labels":3074,"number":3077,"owner":3027,"repository":3028,"state":3029,"title":3078,"updated_at":3079,"url":3080,"score":3081},"### 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.",[3075,3076],{"name":3024,"color":3025},{"name":3038,"color":3039},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.7342471,{"description":3083,"labels":3084,"number":3089,"owner":3027,"repository":3028,"state":3029,"title":3090,"updated_at":3091,"url":3092,"score":3093},"I think we should have a look at https://nextcloud.com/contribute/ and chery-pick some ideas from that",[3085,3088],{"name":3086,"color":3087},"documentation","7D625D",{"name":3038,"color":3039},4113,"Improve docs about starting to contribute","2024-09-15T09:47:05Z","https://github.com/woodpecker-ci/woodpecker/issues/4113",0.73877484,{"description":3095,"labels":3096,"number":3099,"owner":3027,"repository":3028,"state":3100,"title":3101,"updated_at":3102,"url":3103,"score":3104},"### 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).",[3097,3098],{"name":3021,"color":3022},{"name":3065,"color":3066},2236,"closed","Incorrect version of agent","2023-08-18T14:39:20Z","https://github.com/woodpecker-ci/woodpecker/issues/2236",0.67693126,{"description":3106,"labels":3107,"number":3109,"owner":3027,"repository":3028,"state":3100,"title":3110,"updated_at":3111,"url":3112,"score":3113},"### Component\r\n\r\nserver, web-ui\r\n\r\n### Describe the bug\r\n\r\nHi, I have problem with my woodpecker instance. I'm using Github to provide OAuth2 Authorization. But the problem I cannot log in to the app. When I clicking \"Log in\" button, it returns to the same screen. Sometimes when I do many clicks in small amount time I need reatuhorize it in Github.\r\n\r\nInstance is hidden with ngnix proxy manager. \r\n\r\nMy docker compose looks like this:\r\n```\r\nservices:\r\n woodpecker-server:\r\n image: woodpeckerci/woodpecker-server:latest\r\n expose:\r\n - 8000\r\n - 9000\r\n volumes:\r\n - ./woodpecker-server-data:/var/lib/woodpecker/\r\n environment:\r\n - WOODPECKER_OPEN=false\r\n - WOODPECKER_HOST=${WOODPECKER_HOST}\r\n - WOODPECKER_GITHUB=true\r\n - WOODPECKER_GITHUB_CLIENT=${WOODPECKER_GITHUB_CLIENT}\r\n - WOODPECKER_GITHUB_SECRET=${WOODPECKER_GITHUB_SECRET}\r\n - WOODPECKER_AGENT_SECRET=${WOODPECKER_AGENT_SECRET}\r\n - WOODPECKER_ADMIN=${WOODPECKER_ADMIN}\r\n - WOODPECKER_REPO_OWNERS=${WOODPECKER_REPO_OWNERS}\r\n networks:\r\n - ngnix-internal\r\n - composehook-internal\r\n woodpecker-agent:\r\n image: woodpeckerci/woodpecker-agent:latest\r\n command: agent\r\n restart: always\r\n depends_on:\r\n - woodpecker-server\r\n volumes:\r\n - ./woodpecker-agent-config:/etc/woodpecker\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=${WOODPECKER_AGENT_SECRET}\r\n - WOODPECKER_BACKEND_DOCKER_NETWORK=composehook-internal\r\n networks:\r\n - ngnix-internal\r\n - composehook-internal\r\nnetworks:\r\n ngnix-internal:\r\n external: true\r\n name: ngnix-internal\r\n composehook-internal:\r\n external: true\r\n name: composehook-internal\r\n```\r\n\r\nIn logs I haven't see something weird or wrong.\r\n\r\n\r\n### System Info\r\n\r\n```shell\r\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"2.4.1\"}\r\n```\r\n\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Validations\r\n\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]",[3108],{"name":3021,"color":3022},3689,"Stuck on login screen. ","2024-06-21T08:20:32Z","https://github.com/woodpecker-ci/woodpecker/issues/3689",0.6811485,{"description":3115,"labels":3116,"number":3118,"owner":3027,"repository":3028,"state":3100,"title":3119,"updated_at":3120,"url":3121,"score":3122},"### Component\r\n\r\nagent\r\n\r\n### Describe the bug\r\n\r\nWhen having a backend error in the config, i.e. a malformed env var, the step and build are marked as successful even though they should be marked as \"failed\". \r\n\r\n\r\n\r\n\r\nk8s backend\r\n\r\n\r\n### System Info\r\n\r\n```shell\r\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"next-6ab9f802\"}\r\n```\r\n\r\n\r\n### Additional context\r\n\r\n_No response_\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] 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).",[3117],{"name":3021,"color":3022},1871,"Build is marked as \"successful\" although a backend error occurred","2025-01-10T21:25:48Z","https://github.com/woodpecker-ci/woodpecker/issues/1871",0.7008296,{"description":3124,"labels":3125,"number":3133,"owner":3027,"repository":3028,"state":3100,"title":3134,"updated_at":3135,"url":3136,"score":3137},"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",[3126,3127,3130],{"name":3053,"color":3054},{"name":3128,"color":3129},"feature","180DBE",{"name":3131,"color":3132},"good first issue","76ea72",1943,"Add an healthcheck to server container","2023-07-25T13:55:31Z","https://github.com/woodpecker-ci/woodpecker/issues/1943",0.70811945,["Reactive",3139],{},["Set"],["ShallowReactive",3142],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fHjsBTRp7OY_KRh5_2jrl1ZnDfF2W1UjMydTHc_cUE6s":-1},"/woodpecker-ci/woodpecker/2545"]