\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]",[2865,2868],{"name":2866,"color":2867},"bug","d73a4a",{"name":2869,"color":2870},"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.7287953,{"description":2880,"labels":2881,"number":2886,"owner":2872,"repository":2873,"state":2874,"title":2887,"updated_at":2888,"url":2889,"score":2890},"https://ci.woodpecker-ci.org/repos/8987/pipeline/94/errors\r\n\r\nversion: current main",[2882,2883],{"name":2866,"color":2867},{"name":2884,"color":2885},"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.7293367,{"description":2892,"labels":2893,"number":2897,"owner":2872,"repository":2873,"state":2874,"title":2898,"updated_at":2899,"url":2900,"score":2901},"see https://github.com/woodpecker-ci/woodpecker/issues/558#issuecomment-987456959\r\n\r\nIt could happen that the original user who activated a repo reject there oauth2 access or left the project, dont have the rights anymore ...\r\nOr you want to set it to a \"bot\" account ...\r\n\r\nin all cases you at the moment have to change that in the database manually :/ - change that!\r\n\r\nNOTE: the repair now set it to the current user: #4128",[2894],{"name":2895,"color":2896},"enhancement","7E1FE4",571,"let repo admin change the user account who do the api to send back the status","2024-09-20T21:24:09Z","https://github.com/woodpecker-ci/woodpecker/issues/571",0.7295991,{"description":2903,"labels":2904,"number":2907,"owner":2872,"repository":2873,"state":2874,"title":2908,"updated_at":2909,"url":2910,"score":2911},"### 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.",[2905,2906],{"name":2869,"color":2870},{"name":2895,"color":2896},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.73027027,{"description":2913,"labels":2914,"number":2915,"owner":2872,"repository":2873,"state":2916,"title":2917,"updated_at":2918,"url":2919,"score":2920},"### 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,"closed","Support \"Exec runner\"","2022-03-23T16:56:18Z","https://github.com/woodpecker-ci/woodpecker/issues/847",0.7051258,{"description":2922,"labels":2923,"number":2928,"owner":2872,"repository":2873,"state":2916,"title":2929,"updated_at":2930,"url":2931,"score":2932},"on agent start, it trys to connect to the server and if it cant it stops.\r\n\r\nthere should be retry atempts, as the server could be restarting/starting in just the same moment",[2924,2927],{"name":2925,"color":2926},"agent","ECBCDF",{"name":2895,"color":2896},1721,"Agent Start should have connection retrys","2023-05-03T11:31:31Z","https://github.com/woodpecker-ci/woodpecker/issues/1721",0.7190498,{"description":2934,"labels":2935,"number":2937,"owner":2872,"repository":2873,"state":2916,"title":2938,"updated_at":2939,"url":2940,"score":2941},"### Component\n\nserver\n\n### Describe the bug\n\nFrequently seeing this error:\r\n```\r\n{\"level\":\"error\",\"error\":\"pq: value too long for type character varying(255)\",\"time\":\"2022-08-16T21:03:05Z\",\"caller\":\"/woodpecker/src/github.com/woodpecker-ci/woodpecker/server/pipeline/create.go:107\",\"message\":\"failure to save build for stintel/openthread-ci\"}\r\n```\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"next-e6d0b403\"}\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) or the [Matrix room](https://matrix.to/#/#woodpecker:matrix.org).",[2936],{"name":2866,"color":2867},1115,"pq: value too long for type character varying(255)","2022-10-12T22:47:13Z","https://github.com/woodpecker-ci/woodpecker/issues/1115",0.72401834,{"description":2943,"labels":2944,"number":2947,"owner":2872,"repository":2873,"state":2916,"title":2948,"updated_at":2949,"url":2950,"score":2951},"### 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).",[2945,2946],{"name":2866,"color":2867},{"name":2869,"color":2870},718,"The spaces in task output should be kept.","2022-06-16T17:24:27Z","https://github.com/woodpecker-ci/woodpecker/issues/718",0.7247629,{"description":2953,"labels":2954,"number":2962,"owner":2872,"repository":2873,"state":2916,"title":2963,"updated_at":2964,"url":2965,"score":2966},"### 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).",[2955,2956,2959],{"name":2866,"color":2867},{"name":2957,"color":2958},"forge/gitea","E96280",{"name":2960,"color":2961},"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.7255498,{"description":2968,"labels":2969,"number":2971,"owner":2872,"repository":2873,"state":2916,"title":2972,"updated_at":2973,"url":2974,"score":2975},"### 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]",[2970],{"name":2866,"color":2867},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.73067456,["Reactive",2977],{},["Set"],["ShallowReactive",2980],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fUgTn22XKxCbh5enIbM-tgoPbvzs0xo_BaF1NLBUESAo":-1},"/woodpecker-ci/woodpecker/1866"]