\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]",[3018],{"name":3019,"color":3020},"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.6702619,{"description":3030,"labels":3031,"number":3035,"owner":3022,"repository":3023,"state":3024,"title":3036,"updated_at":3037,"url":3038,"score":3039},"### Component\n\nweb-ui\n\n### Describe the bug\n\nWhen there is an error in one of the workflows , the UI does not show which file is causing the error:\r\n\r\nIn this project I have `build.yml` and `release.yml` and the UI gives me that:\r\n\r\n\r\n\r\nThe error was in workflow `release.yml` (which was not triggerd), but not in build.yml.\r\n\r\n\n\n### Steps to reproduce\n\nSchould be obvious\n\n### Expected behavior\n\nIch would like to see, which file / workflow is causing the error.\n\n### System Info\n\n```shell\nWoodpecker 2.7.3 (docker image)\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]",[3032],{"name":3033,"color":3034},"enhancement","7E1FE4",4376,"error message in UI does not point to workflow / yaml file","2024-11-14T14:27:25Z","https://github.com/woodpecker-ci/woodpecker/issues/4376",0.67393243,{"description":3041,"labels":3042,"number":3044,"owner":3022,"repository":3023,"state":3024,"title":3045,"updated_at":3046,"url":3047,"score":3048},"### 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]",[3043],{"name":3019,"color":3020},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.67533976,{"description":3050,"labels":3051,"number":3053,"owner":3022,"repository":3023,"state":3024,"title":3054,"updated_at":3055,"url":3056,"score":3057},"### Component\n\nserver\n\n### Describe the bug\n\nThis issue appears quite often now. Example:\n\nhttps://ci.woodpecker-ci.org/repos/8975/pipeline/1367/5\n\n### Steps to reproduce\n\nNot sure tbh.\n\n### Expected behavior\n\n_No response_\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"next-72823b7ffd\"}\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]",[3052],{"name":3019,"color":3020},4784,"Error response from daemon: removal of container wp_* is already in progress","2025-01-27T10:04:15Z","https://github.com/woodpecker-ci/woodpecker/issues/4784",0.67749274,{"description":3059,"labels":3060,"number":3065,"owner":3022,"repository":3023,"state":3066,"title":3067,"updated_at":3068,"url":3069,"score":3070},"### Component\n\nserver\n\n### Describe the bug\n\nSometimes pipeline cancellations still result in errors that will flag the pipeline as failed instead of cancelled:\r\n\r\n\r\n\n\n### Steps to reproduce\n\nHave not found a reliable way to reproduce this specific case.\n\n### Expected behavior\n\nPipeline should be marked as cancelled instead of failed.\n\n### System Info\n\n```shell\nnext-bf5405b6cc\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]",[3061,3062],{"name":3019,"color":3020},{"name":3063,"color":3064},"ui","46DEA2",4349,"closed","Cancelled pipelines marked as failed","2024-11-12T06:48:56Z","https://github.com/woodpecker-ci/woodpecker/issues/4349",0.64529544,{"description":3072,"labels":3073,"number":3075,"owner":3022,"repository":3023,"state":3066,"title":3076,"updated_at":3077,"url":3078,"score":3079},"### Component\n\nserver\n\n### Describe the bug\n\n\r\n\r\nI'll try to downgrade my woodpecker version to fix this, because all PRs are now broken on `next`.\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"next-5bd12aa646\"}\n```\n\n\n### Additional context\n\nNA\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).",[3074],{"name":3019,"color":3020},2350,"All github PRs are reported as *Waiting for status to be reported*","2023-10-02T06:45:33Z","https://github.com/woodpecker-ci/woodpecker/issues/2350",0.65343845,{"description":3081,"labels":3082,"number":3084,"owner":3022,"repository":3023,"state":3066,"title":3085,"updated_at":3086,"url":3087,"score":3088},"### 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]",[3083],{"name":3019,"color":3020},5177,"Statuses get incorrectly reported for multi workflow pipelines on BitBucket","2025-05-19T11:01:04Z","https://github.com/woodpecker-ci/woodpecker/issues/5177",0.66619754,{"description":3090,"labels":3091,"number":3096,"owner":3022,"repository":3023,"state":3066,"title":3097,"updated_at":3098,"url":3099,"score":3100},"### Component\n\nserver\n\n### Describe the bug\n\nWhen I tried to trigger a pipeline via api with an incorrect ID, I got an error 500 instead of 404, because it doesn't check if there is a repo with the given ID\r\n\r\nThe following route:\r\nhttps://my-woodpecker/api/repos/{repo_id}/pipelines\r\n\r\n*Sorry in advance if this is a duplication of issues, in searching I found no issues with my keywords*\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"2.4.1\"}\n```\n\n\n### Additional context\n\n\r\n\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]",[3092,3093],{"name":3019,"color":3020},{"name":3094,"color":3095},"server","5D7A92",3686,"Nil pointer with invalid id on trigger pipeline api","2024-05-11T08:38:36Z","https://github.com/woodpecker-ci/woodpecker/issues/3686",0.6711288,{"description":3102,"labels":3103,"number":3106,"owner":3022,"repository":3023,"state":3066,"title":3107,"updated_at":3108,"url":3109,"score":3110},"### Component\n\nweb-ui\n\n### Describe the bug\n\nOn output with 5500 lines, clicking pipeline which is producing these lines in realtime browser gets frozen with message \"Woodpecker is not reposinding [WAIT]\". After build is done and we reopen woodpecker in different tab we able to see an output.\n\n### System Info\n\n```shell\n0.15.32\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).",[3104,3105],{"name":3019,"color":3020},{"name":3063,"color":3064},768,"Browser tab crashes when long output printed and we attempt to monitor it in real time","2022-06-16T17:24:28Z","https://github.com/woodpecker-ci/woodpecker/issues/768",0.6757272,{"description":3112,"labels":3113,"number":3115,"owner":3022,"repository":3023,"state":3066,"title":3116,"updated_at":3117,"url":3118,"score":3119},"### Component\n\nweb-ui\n\n### Describe the bug\n\nIn case you try to trigger a manual pipeline that does not start an actual pipeline as all workflows have been filtered and returns 204 we want the UI to show this as a toast and return to the manual pipeline prompt.\n\n### Steps to reproduce\n\n1. create an empty repo\n2. trigger a manual pipeline\n3. receive 204 and see loading spinner forever\n\n### Expected behavior\n\n_No response_\n\n### System Info\n\n```shell\ncommit: 6161a7413d831dc98c47aff4f7f4a6d175c2ec2f (3.4.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]",[3114],{"name":3019,"color":3020},4978,"Show pipeline was filtered for manual pipelines","2025-03-18T13:43:52Z","https://github.com/woodpecker-ci/woodpecker/issues/4978",0.67738795,["Reactive",3121],{},["Set"],["ShallowReactive",3124],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f2VVu1Bh_XjcZAKK7Q2PfxC3nAbTpVNSG1YcyEkExNMw":-1},"/woodpecker-ci/woodpecker/3561"]