\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]",[2867,2870],{"name":2868,"color":2869},"bug","d73a4a",{"name":2871,"color":2872},"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.6954981,{"description":2882,"labels":2883,"number":2888,"owner":2874,"repository":2875,"state":2876,"title":2889,"updated_at":2890,"url":2891,"score":2892},"### 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.",[2884,2885],{"name":2871,"color":2872},{"name":2886,"color":2887},"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.71739554,{"description":2894,"labels":2895,"number":2900,"owner":2874,"repository":2875,"state":2876,"title":2901,"updated_at":2902,"url":2903,"score":2904},"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.",[2896,2897],{"name":2886,"color":2887},{"name":2898,"color":2899},"backend/local","bfdadc",3095,"Implement services for local backend","2025-02-10T13:40:24Z","https://github.com/woodpecker-ci/woodpecker/issues/3095",0.72162944,{"description":2906,"labels":2907,"number":2912,"owner":2874,"repository":2875,"state":2876,"title":2913,"updated_at":2914,"url":2915,"score":2916},"https://ci.woodpecker-ci.org/repos/8987/pipeline/94/errors\r\n\r\nversion: current main",[2908,2909],{"name":2868,"color":2869},{"name":2910,"color":2911},"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.7589242,{"description":2918,"labels":2919,"number":2926,"owner":2874,"repository":2875,"state":2876,"title":2927,"updated_at":2928,"url":2929,"score":2930},"and address\r\n- https://github.com/woodpecker-ci/woodpecker/issues/3503 -> #3820\r\n- https://github.com/woodpecker-ci/woodpecker/pull/3733#issuecomment-2180578290\r\n- ...\r\n\r\nTests to run:\r\n- [ ] Run workflow with steps that should only run if the step before [failed,succeded] (could help with questions like: https://github.com/woodpecker-ci/woodpecker/pull/3846#discussion_r1686246455)\r\n- [ ] Services and check if it is started before the steps who need it ...\r\n- [ ] Make sure the Queue respect **labels** and dependencies correctly\r\n- [ ] ...",[2920,2923],{"name":2921,"color":2922},"tests","ACEA1E",{"name":2924,"color":2925},"summary","C3DC73",3819,"Create \"backend integration test\" framework","2024-11-05T23:18:48Z","https://github.com/woodpecker-ci/woodpecker/issues/3819",0.7701829,{"description":2932,"labels":2933,"number":2939,"owner":2874,"repository":2875,"state":2876,"title":2940,"updated_at":2941,"url":2942,"score":2943},"We could have a workspace preparation docker image that would be run as root and do necessary tasks to prepare everything so that the skip clone would work and also clone steps could be run as non-root images?\n\nMaybe even a woodpecker server could act as docker registry to serve container image for this so that it would work in instances that have no internet connection\n\n_Originally posted by @lafriks in https://github.com/woodpecker-ci/woodpecker/pull/5056#issuecomment-2784618118_",[2934,2935,2937],{"name":2910,"color":2911},{"name":2936,"color":2899},"backend/docker",{"name":2938,"color":2899},"backend/kubernetes",5082,"Add workspace preparation hidden step before clone steps","2025-04-07T21:24:54Z","https://github.com/woodpecker-ci/woodpecker/issues/5082",0.7705294,{"description":2945,"labels":2946,"number":2952,"owner":2874,"repository":2875,"state":2876,"title":2953,"updated_at":2954,"url":2955,"score":2956},"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",[2947,2948,2949],{"name":2910,"color":2911},{"name":2886,"color":2887},{"name":2950,"color":2951},"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.7723185,{"description":2958,"labels":2959,"number":2961,"owner":2874,"repository":2875,"state":2962,"title":2963,"updated_at":2964,"url":2965,"score":2966},"### 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]",[2960],{"name":2868,"color":2869},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.725965,{"description":2968,"labels":2969,"number":2972,"owner":2874,"repository":2875,"state":2962,"title":2973,"updated_at":2974,"url":2975,"score":2976},"### 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).",[2970,2971],{"name":2868,"color":2869},{"name":2871,"color":2872},718,"The spaces in task output should be kept.","2022-06-16T17:24:27Z","https://github.com/woodpecker-ci/woodpecker/issues/718",0.7318797,{"description":2978,"labels":2979,"number":2984,"owner":2874,"repository":2875,"state":2962,"title":2985,"updated_at":2986,"url":2987,"score":2988},"### Component\r\n\r\nagent\r\n\r\n### Describe the bug\r\n\r\nIt sometimes happens that Woodpecker doesnt build the actual commit that was pushed, but different code. Usually it is an earlier commit from the same branch. This problem seems to happen completely randomly. When it happens, restarting the build from Woodpecker website doesnt help, it keeps rebuilding the same wrong code.\r\n\r\nAs far as I noticed this only happens in the [lemmy](https://github.com/LemmyNet/lemmy) repo, so maybe there is a problem with the `.woodpecker.yml` config.\r\n\r\nIm sure I opened an issue about this before, but cant find it anymore.\r\n\r\n### System Info\r\n\r\n```shell\r\nnext-556607b5 (also happened with previous \"next\" versions that we used)\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).",[2980,2981],{"name":2868,"color":2869},{"name":2982,"color":2983},"feedback","4B7070",1866,"Woodpecker sometimes builds wrong version of code","2024-12-23T00:00:58Z","https://github.com/woodpecker-ci/woodpecker/issues/1866",0.74535906,["Reactive",2990],{},["Set"],["ShallowReactive",2993],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f6AaJxH_TPrFm1qi81_BWQZltvs2_N0CufBzRhJ-hk0s":-1},"/woodpecker-ci/woodpecker/3924"]