\n\nAnd here is the outcome on BitBucket:\n\u003Cimg width=\"479\" height=\"182\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/11c2a65d-cbf2-4162-9805-3d035bdac04e\" />\n\n\n### Steps to reproduce\n\n1. Run Woodpecker with BitBucket Cloud forge\n2. Create a pipeline that uses a matrix\n3. Let the pipeline finish on Woodpecker\n4. Observe the build statuses on the commit in BitBucket\n\n### Expected behavior\n\nBoth pipelines should show completed.\n\n### System Info\n\n```shell\nWoodpecker version: v3.8.0\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/versions]",[3019],{"name":3020,"color":3021},"bug","d73a4a",5338,"woodpecker-ci","woodpecker","open","Build status not completing on matrix pipelines with BitBucket","2025-07-17T18:03:12Z","https://github.com/woodpecker-ci/woodpecker/issues/5338",0.70311946,{"description":3031,"labels":3032,"number":3034,"owner":3023,"repository":3024,"state":3025,"title":3035,"updated_at":3036,"url":3037,"score":3038},"### Component\n\nserver, agent\n\n### Describe the bug\n\nI have been using woodpecker-CI for multiple years now in our company, and we rarely had any issues.\r\n\r\nEver since two days ago, pipelines _sometimes_ fail with an error connecting to the gitea forge:\r\n\r\n```\r\n+ git init --object-format sha1 -b main\r\nInitialized empty Git repository in /woodpecker/src/GITEA_URL/ORGANIZATION/REPOSITORY/.git/\r\n+ git config --global --replace-all safe.directory /woodpecker/src/GITEA_URL/ORGANIZATION/REPOSITORY\r\n+ git remote add origin https://GITEA_URL/ORGANIZATION/REPOSITORY.git\r\n+ git fetch --no-tags --depth=1 --filter=tree:0 origin +caf9334a3d53b3[2](https://CI_URL/repos/73/pipeline/471#L2)f4c382044ca4ff5d5982d4e58:\r\nFrom https://GITEA_URL/ORGANIZATION/REPOSITORY\r\n * branch caf9[3](https://CI_URL/repos/73/pipeline/471#L3)34a3d53b32f4c382044ca4ff5d5982d4e58 -> FETCH_HEAD\r\n+ git reset --hard -q caf9334a3d53b32f4c382044ca4ff5d5982d4e58\r\nfatal: unable to access 'https://GITEA_URL/ORGANIZATION/REPOSITORY.git/': Failed to connect to GITEA_URL port [4](https://CI_URL/repos/73/pipeline/471#L4)43 after 2002 ms: Could not connect to server\r\nfatal: could not fetch 374dd4d87[5](https://CI_URL/repos/73/pipeline/471#L5)f23bb4a2e8b631762d933d12d78d27 from promisor remote\r\nexit status 128\r\n```\r\n\r\nRestarting the pipeline often fixes the issue.\r\n\r\nI am failing to find any reasons to why this is happening. It seems to connect to gitea normally before (it loads the pipeline, runs the first fetch, and it works on restart). I have updated to woodpecker-next and the issue stays the same. I have not updated neither woodpecker or gitea in the past few days (just a few weeks ago).\r\n\r\nI had a similiar issue half a year ago, when my renovate-bot would open many pull requests simultaneously and it would fail with a \"Cannot read username\" message.\r\n\r\nIs this a problem with woodpecker? Am I running into a gitea rate limit? I am not running fail2ban on my host.\n\n### Steps to reproduce\n\nHard to reproduce sadly :(\n\n### Expected behavior\n\n_No response_\n\n### System Info\n\n```shell\nwoodpeckerci/plugin-git: 2.6.0\r\nwoodpecker version: next-defe6c418f\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]",[3033],{"name":3020,"color":3021},4558,"git reset fails sometimes when connecting to gitea forge","2024-12-16T11:55:17Z","https://github.com/woodpecker-ci/woodpecker/issues/4558",0.7045226,{"description":3040,"labels":3041,"number":3043,"owner":3023,"repository":3024,"state":3025,"title":3044,"updated_at":3045,"url":3046,"score":3047},"### Component\n\nagent, web-ui\n\n### Describe the bug\n\nOn all my pipelines only the first few log lines appear in the webui. Then everything else is cut out. I can certainly see the log output when I kubectl logs wp-1234.... the step/pipeline, bit it doesn't seem to get sent to the server from the agent.\r\n\r\nI also see a lot of \r\n`{\"level\":\"error\",\"repo\":\"renovatebot/renovate\",\"pipeline\":\"2064\",\"workflow_id\":\"6848\",\"image\":\"docker.io/woodpeckerci/plugin-git:2.5.1\",\"workflow_id\":\"6848\",\"error\":\"io: read/write on closed pipe\",\"time\":\"2024-11-17T13:04:52Z\",\"message\":\"copy limited logStream part\"}`\r\n\r\non the agent and \r\n\r\n`{\"level\":\"error\",\"repo_id\":\"29\",\"pipeline_id\":\"4660\",\"workflow_id\":\"6871\",\"error\":\"stream: not found\",\"time\":\"2024-11-18T12:55:30Z\",\"message\":\"done: cannot close log stream for step 21827\"}` and `{\"level\":\"error\",\"repo_id\":\"29\",\"pipeline_id\":\"4660\",\"workflow_id\":\"6871\",\"error\":\"sql: no rows in result set\",\"time\":\"2024-11-18T12:55:30Z\",\"message\":\"queue.Done: cannot ack workflow\"}`\r\n\r\non the server.\r\n\r\nIt has to be mentioned, that before a month ago (I upgrade woodpecker almost immediately after release) the logs worked almost flawlessly for more than a year, since I switched from drone to woodpecker.\r\n\r\nCurrently I don't know where to start debugging, to get to the bottom of this. Do you have any pointers?\n\n### Steps to reproduce\n\ninstall woodpecker using the helm chart version 1.6.2 on a kubernetes cluster v1.31 only setting WOODPECKER_BACKEND_K8S_STORAGE_RWX: false beside the setup with a forge using https://woodpecker-ci.org/docs/next/administration/forges/forgejo\n\n### Expected behavior\n\nI expect to always get all the logs, when I click on a step/workflow. \n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"2.7.3\"}\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]",[3042],{"name":3020,"color":3021},4409,"Logs only showing the first few lines of each step","2024-11-19T10:25:07Z","https://github.com/woodpecker-ci/woodpecker/issues/4409",0.725534,{"labels":3049,"number":3051,"owner":3023,"repository":3024,"state":3025,"title":3052,"updated_at":3053,"url":3054,"score":3055},[3050],{"name":3020,"color":3021},4848,"Server crash when pipeline start","2025-02-14T15:03:25Z","https://github.com/woodpecker-ci/woodpecker/issues/4848",0.7288574,{"description":3057,"labels":3058,"number":3062,"owner":3023,"repository":3024,"state":3025,"title":3063,"updated_at":3064,"url":3065,"score":3066},"### Clear and concise description of the problem\n\nIt would be nice if we could define all our pipelines in a single .woodpecker.yaml file, instead of resorting to holding multiple pipelines in individual files in a dedicated folder. YAML syntax allows for multiple documents to be contained in a single stream by separating them with '---' (triple hyphens). Woodpecker currently doesn't utilized this feature when loading pipelines, since it's the file URI that is passed to - for example - 'genItemForWorkflow' that produces a single item from a single file, even if that file contains multiple documents.\n\n### Suggested solution\n\nAllow for including multiple YAML documents within a single file.\n\nThis would require a change in some interfaces that currently take a file URI and pass it down to be processed by specialized functions first and extracting a list of YAML documents.\n\n### Alternative\n\n_No response_\n\n### Additional context\n\nHere are two relevant links to YAML official specification\n[2.2 Structures](https://yaml.org/spec/1.0/#id2489959)\n[4.3.1 Document](https://yaml.org/spec/1.0/#id2561718)\n\n### Validations\n\n- [x] Checked that the feature isn't part of the `next` version already [https://woodpecker-ci.org/versions]\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.",[3059],{"name":3060,"color":3061},"feature","180DBE",4821,"Allow loading multiple yaml documents from a single file","2025-02-08T00:04:37Z","https://github.com/woodpecker-ci/woodpecker/issues/4821",0.7304686,{"description":3068,"labels":3069,"number":3071,"owner":3023,"repository":3024,"state":3072,"title":3073,"updated_at":3074,"url":3075,"score":3076},"### Component\n\nserver\n\n### Describe the bug\n\nWhen a pipeline with multiple workflows starts a correct status is sent at first BitBucket correctly displays that build is in progress. When the build finishes however, only one build is displayed as finished but the other one is still in progress marking the whole commit as in progress(this is internal BitBucket logic). \n\nHere is a pipeline that has two workflows:\n\n\n\nAnd here is the outcome on BitBucket:\n\n\n\nI asked @langecode if he can take a look and we realized that there is a problem in BitBucket forge implementation of `Status` function. It looks like that for each call of `Status` function we send a status of the whole pipeline when we should've sent a status of individual workflows. I.e. change status of https://github.com/woodpecker-ci/woodpecker/blob/main/server/forge/bitbucketdatacenter/bitbucketdatacenter.go#L314\n\nTo:\n```go\nState: convertStatus(workflow.State)\n```\n\n### Steps to reproduce\n\n1. Run woodpecker with BitBucket Datacenter forge\n2. Create a pipeline that has multiple workflows\n3. Let the pipeline finish on woodpecker\n4. Observe the build statuses on the commit in BitBucket\n\n### Expected behavior\n\n_No response_\n\n### System Info\n\n```shell\nWoodpecker version: v3.5.2\nBitBucket Datacenter version: v8.18.1\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/versions]",[3070],{"name":3020,"color":3021},5177,"closed","Statuses get incorrectly reported for multi workflow pipelines on BitBucket","2025-05-19T11:01:04Z","https://github.com/woodpecker-ci/woodpecker/issues/5177",0.66037995,{"description":3078,"labels":3079,"number":3081,"owner":3023,"repository":3024,"state":3072,"title":3082,"updated_at":3083,"url":3084,"score":3085},"### Component\r\n\r\nserver\r\n\r\n### Describe the bug\r\n\r\nJust configured a new instance against gitlab.com.\r\n\r\nFacing the following issues:\r\n\r\n- Unable to start builds due to `[generic]could not load config from forge: %!w(\u003Cnil>)`\r\n\r\nServer logs report:\r\n\r\n```\r\n/server/services/config/forge.go:150\",\"message\":\"could not get folder from forge\"}\r\n```\r\n\r\nThe repo exists in a subgroup and hast just been enabled.\r\n\r\n- Subgroups are sometimes visualized in the UI dashboard, sometimes not\r\n\t- Enabled two repos in two different subgroups: one was listed as `group/subgroup/repo`, the other one as `group/repo`\r\n\r\nMaybe related: #2311\r\n\r\n### Steps to reproduce\r\n\r\n.\r\n\r\n### Expected behavior\r\n\r\n_No response_\r\n\r\n### System Info\r\n\r\n```shell\r\nGitlab 17.6\r\nWoodpecker next `next-9dd796ad65` (Oct 13th 2024)\r\nWP 2.7.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]",[3080],{"name":3020,"color":3021},4247,"GitLab subgroups broken?","2024-10-26T21:20:17Z","https://github.com/woodpecker-ci/woodpecker/issues/4247",0.6721773,{"description":3087,"labels":3088,"number":3090,"owner":3023,"repository":3024,"state":3072,"title":3091,"updated_at":3092,"url":3093,"score":3094},"### Component\n\nweb-ui\n\n### Describe the bug\n\nThe pipeline status image (on Woodpecker - returned by API: /api/badges/25/status.svg ) shows ERROR, even that last build is OK:\r\n\r\n\n\n### System Info\n\n```shell\nversion 2.4.1 running on Docker\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]",[3089],{"name":3020,"color":3021},3561,"Pipeline status is error, but last job is OK","2024-04-15T10:15:05Z","https://github.com/woodpecker-ci/woodpecker/issues/3561",0.6750937,{"description":3096,"labels":3097,"number":3102,"owner":3023,"repository":3024,"state":3072,"title":3103,"updated_at":3104,"url":3105,"score":3106},"### Component\r\n\r\nserver, agent\r\n\r\n### Describe the bug\r\n\r\nUser-1 have pipeline in repository `wp-test`, he [runs](https://woodpecker.test.smthd.com/repos/1/pipeline/139) `gitea-integration-test` branch:\r\n```yaml\r\nskip_clone: true\r\nservices:\r\n postgres:\r\n image: digitalocean/doks-debug\r\n commands:\r\n - echo 'This is Gitea Postgres test server' | nc -l -6 5432\r\n ports:\r\n - 5432\r\nsteps:\r\n gitea:\r\n image: digitalocean/doks-debug\r\n commands:\r\n - nc -v -6 -w 10 postgres 5432\r\n```\r\n\r\nUser-2 have pipeline below in his `wp-test-2` repository and `woodpecker-integration-test` branch:\r\n```yaml\r\nskip_clone: true\r\nservices:\r\n postgres:\r\n image: digitalocean/doks-debug\r\n commands:\r\n - echo 'This is Woodpecker Postgres test server' | nc -l -6 5432\r\n ports:\r\n - 5432\r\nsteps:\r\n wp:\r\n image: digitalocean/doks-debug\r\n commands:\r\n - nc -v -6 -w 10 postgres 5432\r\n```\r\nWhen User-1's pipeline Service and service Pod were launched, User-2 [ran his own](https://woodpecker.test.smthd.com/repos/2/pipeline/13).\r\n\r\nBugs:\r\n1. User-2's pipeline was cancelled with `error\":\"services \"postgres\" already exists`.\r\n2. User-1's Service and service Pod were deleted because User-2's pipeline cleaned up resources and the names were the same - `postgres`.\r\n\r\n### System Info\r\n\r\n```shell\r\n`next-0b5eef7d1e`, 1 Server, 1 Agent, max workflows 2.\r\n```\r\n\r\n\r\n### Additional context\r\n\r\n[woodpecker-agent.log](https://github.com/woodpecker-ci/woodpecker/files/14075623/woodpecker-agent.log)\r\n\r\nhttps://github.com/woodpecker-ci/woodpecker/pull/3236#issuecomment-1902404296\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]",[3098,3099],{"name":3020,"color":3021},{"name":3100,"color":3101},"backend/kubernetes","bfdadc",3288,"Multiple flaws when running pipelines with the same service (K8s)","2024-02-17T18:45:23Z","https://github.com/woodpecker-ci/woodpecker/issues/3288",0.6830063,{"description":3108,"labels":3109,"number":3114,"owner":3023,"repository":3024,"state":3072,"title":3115,"updated_at":3116,"url":3117,"score":3118},"### Component\n\nserver\n\n### Describe the bug\n\nversion: v3.7.0\n\nThe api:\n`/repos/1/pull-requests`\nreturn \"Internal Server Error\" failed.\n\nBecause the server request gitlab server with:\n`/api/v4/projects/111/merge_requests?page=1&per_page=50&state=open`\n\nAnd the gitlab response with\n```\n{\n \"error\": \"state does not have a valid value\"\n}\n```\n\nBecause the the merge_requests in gitlab was `opened`, not `open`.\n\nSo the request url should be: \n`/api/v4/projects/111/merge_requests?page=1&per_page=50&state=opened`\n\n\n### Steps to reproduce\n\n```\nexport WOODPECKER_OPEN=true\nexport WOODPECKER_LOG_LEVEL=trace\nexport WOODPECKER_HOST=localhost:8000\nexport WOODPECKER_GITLAB=true\nexport WOODPECKER_GITLAB_URL=https://gitlab.example.com\nexport WOODPECKER_GITLAB_CLIENT=\nexport WOODPECKER_GITLAB_SECRET=\nexport WOODPECKER_AGENT_SECRET=\n\n/usr/local/bin/woodpecker-server\n```\n\n### Expected behavior\n\n_No response_\n\n### System Info\n\n```shell\n{\n\"source\": \"https://github.com/woodpecker-ci/woodpecker\",\n\"version\": \"3.7.0\"\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/versions]",[3110,3111],{"name":3020,"color":3021},{"name":3112,"color":3113},"forge/gitlab","E96280",5279,"failed pull request with gitlab","2025-06-29T11:38:00Z","https://github.com/woodpecker-ci/woodpecker/issues/5279",0.698733,["Reactive",3120],{},["Set"],["ShallowReactive",3123],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$ff4lRARMnzTnXnWD33KjQpR60kdStQtuBdZOGNX80FPg":-1},"/woodpecker-ci/woodpecker/618"]