\r\n \u003Clink rel=\"alternate icon\" type=\"image/png\" href=\"/favicons/favicon-light-default.png\" id=\"favicon-png\" />\r\n \u003Clink rel=\"icon\" type=\"image/svg+xml\" href=\"/favicons/favicon-light-default.svg\" id=\"favicon-svg\" />\r\n \u003Cmeta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\" />\r\n \u003Cmeta name=\"theme-color\" content=\"#65a30d\" />\r\n \u003Ctitle>Woodpecker\u003C/title>\r\n \u003Cscript type=\"\" src=\"/web-config.js\">\u003C/script>\r\n \u003Cscript type=\"module\" crossorigin src=\"/assets/index-4b7b57db.js\">\u003C/script>\r\n \u003Clink rel=\"stylesheet\" href=\"/assets/index-f123c06a.css\">\r\n \u003C/head>\r\n \u003Cbody>\r\n \u003Cdiv id=\"app\">\u003C/div>\r\n\r\n \u003C/body>\r\n\u003C/html>\r\n```\r\n\r\nThat is basically an \"empty\" page. Let's look at the response code:\r\n```\r\n$ curl -I http://localhost:8000/foo\r\nHTTP/1.1 200 OK\r\nX-Woodpecker-Version: next-45319b24\r\n# ...etc.\r\n```\r\n\r\nThat should have returned 404.\r\n\r\nNow let's request a non-existent API endpoint:\r\n```\r\n$ curl -I http://localhost:8000/api/bar\r\nHTTP/1.1 200 OK\r\nX-Woodpecker-Version: next-45319b24\r\n# ...etc.\r\n```\r\n\r\nSame thing.\r\n\r\nNow let's request a real API endpoint, for healthchecks:\r\n```\r\n$ curl http://localhost:8000/api/healthz\r\n\u003C!DOCTYPE html>\r\n\u003Chtml lang=\"en\">\r\n # ...\r\n\u003C/html>\r\n\r\n$ curl -I http://localhost:8000/api/healthz\r\nHTTP/1.1 200 OK\r\nX-Woodpecker-Version: next-45319b24\r\n# ...etc.\r\n```\r\n\r\nSame thing. Also, it should not return a page, only a REST response.\r\n\r\nClean up:\r\n```\r\n$ apk delete curl\r\n$ exit\r\n```\r\n\r\nSummary:\r\n- both existent and non-existent endpoints and pages respond with 200\r\n- that means the `/api/healthz` endpoint is not working: it's a \"proof of life\" rather than \"proof of health\"\r\n- and the health endpoint should only return a json REST response, not a page\r\n\r\n### System Info\r\n\r\n```shell\r\nversion next-45319b24-alpine\r\ndockerised\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).",[2901,2904],{"name":2902,"color":2903},"bug","d73a4a",{"name":2888,"color":2889},1947,"All pages and API endpoints (including non-existent ones) return 200","2025-03-16T13:50:31Z","https://github.com/woodpecker-ci/woodpecker/issues/1947",0.7239813,{"description":2911,"labels":2912,"number":2918,"owner":2877,"repository":2878,"state":2879,"title":2919,"updated_at":2920,"url":2921,"score":2922},"### Clear and concise description of the problem\n\nThe \"Run pipeline\" button in the UI, which is triggered for `\"event: manual\"`, currently executes all existing pipeline definitions under `.woodpecker/`.\n\n### Suggested solution\n\nThe button could allow invoking specific pipelines only instead of starting all existing ones.\n\n### Alternative\n\n_No response_\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.",[2913,2914,2915],{"name":2888,"color":2889},{"name":2871,"color":2872},{"name":2916,"color":2917},"ux","fef2c0",2763,"Run pipeline: allow executing a single/specific pipeline if more than one pipeline definitions exist","2023-12-20T12:51:01Z","https://github.com/woodpecker-ci/woodpecker/issues/2763",0.7474719,{"description":2924,"labels":2925,"number":2928,"owner":2877,"repository":2878,"state":2879,"title":2929,"updated_at":2930,"url":2931,"score":2932},"Related issues: https://github.com/woodpecker-ci/woodpecker/issues/178 https://github.com/woodpecker-ci/woodpecker/issues/33\r\n\r\nOur problem:\r\n- a build can take 10-15 minutes\r\n- agent run as kubernetes pods\r\n- if an agent dies immediately (no graceful termination, for instance the node instantly goes away) and the build is running, the build stays in a \"running\" state until the timeout kicks in (by default 60 minutes)\r\n- instead of finishing as a failure (timeout), the build is rescheduled on a different agent, and starts over; it has the same build number and build steps run again as the same \"original\" build\r\n\r\nThis breaks flows where we assume the build number to be unique (as Restarting from the UI normally generates a new build number).\r\n\r\nAny chance this can be configured?",[2926,2927],{"name":2888,"color":2889},{"name":2891,"color":2892},220,"Agent interrupted builds restarted - is this desired/configurable?","2024-09-16T09:38:36Z","https://github.com/woodpecker-ci/woodpecker/issues/220",0.7515899,{"description":2934,"labels":2935,"number":2939,"owner":2877,"repository":2878,"state":2940,"title":2941,"updated_at":2942,"url":2943,"score":2944},"always sort default branch to be ontop of the list\r\n\r\n\r\n",[2936,2937,2938],{"name":2868,"color":2869},{"name":2891,"color":2892},{"name":2874,"color":2875},2845,"closed","make default branch first item in branch view in repos","2023-12-26T06:37:15Z","https://github.com/woodpecker-ci/woodpecker/issues/2845",0.7010299,{"description":2946,"labels":2947,"number":2948,"owner":2877,"repository":2878,"state":2940,"title":2949,"updated_at":2950,"url":2951,"score":2952},"### Component\n\nserver, web-ui\n\n### Describe the bug\n\nDue to various technical limitations of my situation I want to run a woodpecker-ci server behind an apache reverse-proxy server, reachable by an url like `https://example.org/foo`.\r\nI.e. the web server does *NOT* simply forward all requests, but only requests for `https://example.com/foo/*` are forwarded to `localhost:8000/*`.\r\n\r\nThe issue is now, that even if I configure `WOODPECKER_HOST=https://example.org/foo`, the `index.html` that is served still references further assets by absolute paths like `/web-config.js`, which causes the browser to request `https://example.com/web-config.js` instead of `https://example.com/foo/web-config.js`.\r\n\r\nI can successfully run Gitea behind such a reverse-proxy, so the web server is not to blame here.\r\n\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"next-6d86ec7fe7\"}\n```\n\n\n### Additional context\n\nHere is an example (running on local host)\r\n\r\n\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).",[],2477,"Server not honoring url path component of WOODPECKER_HOST","2023-09-19T16:30:20Z","https://github.com/woodpecker-ci/woodpecker/issues/2477",0.7160386,{"description":2954,"labels":2955,"number":2957,"owner":2877,"repository":2878,"state":2940,"title":2958,"updated_at":2959,"url":2960,"score":2961},"Queue seems to be missing items. This could be either caused by a server restart or by adding / removing agents through the autoscaler.\r\n\r\nWe have just 1 queue entry, but at least 3 pipelines should be running somehow.\r\n\r\n\r\n\r\n\r\n",[2956],{"name":2902,"color":2903},1915,"Queue items not matching running pipelines","2024-02-09T14:07:38Z","https://github.com/woodpecker-ci/woodpecker/issues/1915",0.72065526,{"description":2963,"labels":2964,"number":2969,"owner":2877,"repository":2878,"state":2940,"title":2970,"updated_at":2971,"url":2972,"score":2973},"For storage intensive pipelines would be nice to have an option to put workspace in ram disk (i.e. tmpfs); will be huge relief for systems with plenty of RAM and slower storage; pipelines will probably be much faster too.\r\n\r\nSimilar drone issue:\r\nhttps://discourse.drone.io/t/make-drone-src-workspace-a-tmpfs/8040\r\n\r\nRegards,\r\nPaweł\r\n",[2965,2966],{"name":2871,"color":2872},{"name":2967,"color":2968},"pipeline-config","1BE540",186,"Option to place workspace and service storage in RAM","2023-08-20T20:35:11Z","https://github.com/woodpecker-ci/woodpecker/issues/186",0.7215964,{"description":2975,"labels":2976,"number":2981,"owner":2877,"repository":2878,"state":2940,"title":2982,"updated_at":2983,"url":2984,"score":2985},"### Component\n\nagent\n\n### Describe the bug\n\npipeline file like this\r\n```yml\r\n---\r\nlabels:\r\n platform: linux/amd64\r\n backend: local\r\n\r\nsteps:\r\n hello:\r\n image: bash\r\n commands:\r\n - uname -a\r\n - pwd\r\n - echo $${CI_WORKSPACE}\r\n - ls -AFlh\r\n - echo \"hello world 你好\"\r\n - touch hello.txt\r\n - echo $${PATH}\r\n\r\n 测试:\r\n image: bash\r\n commands:\r\n - uname -a\r\n - pwd\r\n - ls -AFlh\r\n - echo \"hello world 你好 测试\"\r\n```\r\n\r\nCI_WORKSPACE set wrong in local backends\r\n\r\n\r\n\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"1.0.3\"}\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).",[2977,2978],{"name":2902,"color":2903},{"name":2979,"color":2980},"backend/local","bfdadc",2610,"CI_WORKSPACE set wrong in local backends","2023-10-23T10:54:12Z","https://github.com/woodpecker-ci/woodpecker/issues/2610",0.7378592,["Reactive",2987],{},["Set"],["ShallowReactive",2990],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fqTkolJ8aHTx_yH4REXlOhaYAx_3bWVhENOwuVRBTbMs":-1},"/woodpecker-ci/woodpecker/3021"]