\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).",[2012,2015],{"name":2013,"color":2014},"bug","d73a4a",{"name":2016,"color":2017},"server","5D7A92",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.77584225,{"description":2024,"labels":2025,"number":2033,"owner":1991,"repository":1992,"state":2034,"title":2035,"updated_at":2036,"url":2037,"score":2038},"### Component\r\n\r\nserver\r\n\r\n### Describe the bug\r\n\r\nFrom 2.7.0 if I add a service container that had `WORKDIR` set in Dockerfile the service won't be able to find files via relative paths (or it expects to find files in it's current folder).\r\n\r\nWorkaround: Set `directory` manually on the service\r\n\r\n### Steps to reproduce\r\n\r\n1. Create a container that has `WORKDIR` set to something you know the contents of and set `CMD` and `ENTRYPOINT` to `ls`\r\n2. Add said container to a pipeline as a service (with no commands ofc)\r\n3. Observe the output, it should be different from `WORKDIR`'s contents.\r\n\r\n### Expected behavior\r\n\r\nWorking directory inside the container should be left alone and be the same set in the container.\r\n\r\n### System Info\r\n\r\n```shell\r\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"2.7.0\"}\r\n```\r\n\r\ndocker-compose config:\r\n\r\n```\r\nversion: '3'\r\n\r\nservices:\r\n woodpecker-server:\r\n image: woodpeckerci/woodpecker-server:v2.7.0\r\n ports:\r\n - 5000:8000\r\n - 10000:9000\r\n volumes:\r\n - ./data:/var/lib/woodpecker/\r\n - /etc/ssl/certs:/etc/ssl/certs:ro\r\n - /etc/timezone:/etc/timezone\r\n - /etc/docker/certs.d:/etc/docker/certs.d:ro\r\n environment:\r\n - WOODPECKER_OPEN=true\r\n - WOODPECKER_HOST=REDACTED\r\n - WOODPECKER_GITEA=true\r\n - WOODPECKER_GITEA_URL=REDACTED\r\n - WOODPECKER_GITEA_CLIENT=a3439c88-9061-4ce7-b3dc-64500fd5257f\r\n - WOODPECKER_GITEA_SECRET=REDACTED\r\n - WOODPECKER_GITEA_SKIP_VERIFY=true\r\n - WOODPECKER_AGENT_SECRET=REDACTED\r\n - WOODPECKER_ADMIN=Gr3qi\r\n # - WOODPECKER_LOG_LEVEL=debug\r\n - WOODPECKER_AUTHENTICATE_PUBLIC_REPOS=true\r\n #- WOODPECKER_MIGRATIONS_ALLOW_LONG=true\r\n - WOODPECKER_BACKEND_DOCKER_VOLUMES=/etc/ssl/certs:/etc/ssl/certs:ro,/etc/timezone:/etc/timezone,/etc/docker/certs.d:/etc/docker/certs.d:ro\r\n # woodpecker-agent:\r\n # image: woodpeckerci/woodpecker-agent:v2.6.0\r\n # command: agent\r\n # restart: always\r\n # depends_on:\r\n # - woodpecker-server\r\n # volumes:\r\n # - /var/run/docker.sock:/var/run/docker.sock\r\n # - /etc/ssl/certs:/etc/ssl/certs:ro\r\n # - /etc/timezone:/etc/timezone\r\n # - /etc/docker/certs.d:/etc/docker/certs.d:ro\r\n # environment:\r\n # - WOODPECKER_SERVER=woodpecker-server:9000\r\n # - WOODPECKER_AGENT_SECRET=REDACTED\r\n # - WOODPECKER_BACKEND_DOCKER_VOLUMES=/etc/ssl/certs:/etc/ssl/certs:ro,/etc/timezone:/etc/timezone,/etc/docker/certs.d:/etc/docker/certs.d:ro\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]",[2026,2029,2030],{"name":2027,"color":2028},"documentation","7D625D",{"name":2002,"color":2003},{"name":2031,"color":2032},"engine","5319e7",3993,"closed","Service containers have their working directory changed when launched","2024-11-25T19:13:33Z","https://github.com/woodpecker-ci/woodpecker/issues/3993",0.75609255,{"description":2040,"labels":2041,"number":2046,"owner":1991,"repository":1992,"state":2034,"title":2047,"updated_at":2048,"url":2049,"score":2050},"To prevent connections to external servers and to improve usability if a server is unreachable, download the plugin icons when docs are built and store and serve them from the docs server.",[2042,2045],{"name":2043,"color":2044},"plugin","887B27",{"name":2027,"color":2028},1771,"Docs: Serve plugin icons locally","2024-06-06T13:28:09Z","https://github.com/woodpecker-ci/woodpecker/issues/1771",0.7574425,{"description":2052,"labels":2053,"number":2056,"owner":1991,"repository":1992,"state":2034,"title":2057,"updated_at":2058,"url":2059,"score":2060},"### Component\n\nserver\n\n### Describe the bug\n\nAfter migration form 0.15.11 After migration from 0.15.11 during start of server, we get this error:\r\n\r\n```\r\nwodpecker-server_1 | {\"time\":\"2023-08-01T07:07:19Z\",\"message\":\"LogLevel = info\"}\r\nwoodpecker-server_1 | {\"level\":\"error\",\"error\":\"Migrating logs to log_entries is skipped, as we have 49180 entries to convert. Set 'WOODPECKER_MIGRATIONS_ALLOW_LONG' to 'true' to migrate anyway\",\"time\":\"2023-08-01T07:07:19Z\",\"message\":\"migration task 'migrate-logs-to-log_entries' failed but is not required\"}\r\nwoodpecker-server_1 | {\"level\":\"info\",\"time\":\"2023-08-01T07:07:19Z\",\"message\":\"Starting Woodpecker server with version '1.0.0'\"}\r\n\r\n```\r\nSetting WOODPECKER_MIGRATIONS_ALLOW_LONG to true does nothing. \r\n\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"1.0.0\"}\r\n\r\n\r\nversion: '3'\r\n\r\nservices:\r\n woodpeckerdb:\r\n image: postgres:14.5-alpine\r\n restart: always\r\n environment:\r\n POSTGRES_DB: xxxxx\r\n POSTGRES_USER: xxx\r\n POSTGRES_PASSWORD: xxx\r\n TZ: Europe/Zagreb\r\n volumes:\r\n - ./_data/db/postgres:/var/lib/postgresql/data\r\n \r\n woodpecker-server:\r\n #image: woodpeckerci/woodpecker-server:v0.15.11-alpine\r\n image: woodpeckerci/woodpecker-server:v1.0.0-alpine\r\n restart: always\r\n depends_on:\r\n - woodpeckerdb\r\n volumes:\r\n - ./_data/woodpecker:/var/lib/woodpecker\r\n environment:\r\n - WOODPECKER_OPEN=true\r\n - WOODPECKER_OPEN=true\r\n - WOODPECKER_HOST=https://ci.domain.local\r\n - WOODPECKER_AGENT_SECRET=xxxx\r\n - WOODPECKER_GITEA=true\r\n - WOODPECKER_GITEA_URL=https://gitea.domain.local\r\n - WOODPECKER_GITEA_CLIENT=085e34c6-a362-42d2-9344-d4ab5f556bb4\r\n - WOODPECKER_GITEA_SECRET=gto_53npywpjlwwp4planwetxa2ixqbjloh4rq37sl6dfwqqzlej547q\r\n - WOODPECKER_AUTHENTICATE_PUBLIC_REPOS=true\r\n - WOODPECKER_BACKEND_DOCKER_NETWORK=fronted_network\r\n - WOODPECKER_DATABASE_DRIVER=postgres\r\n - WOODPECKER_DATABASE_DATASOURCE=postgres://woodpecker:woodpecker@woodpeckerdb:5432/woodpeckerdb?sslmode=disable\r\n - WOODPECKER_MIGRATIONS_ALLOW_LONG=true\r\n```\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).",[2054,2055],{"name":2013,"color":2014},{"name":2016,"color":2017},2079,"After migration from 0.15.11 getting error \"error\":\"Migrating logs to log_entries is skipped, as we have 49180 entries to convert on app start","2023-08-21T07:29:47Z","https://github.com/woodpecker-ci/woodpecker/issues/2079",0.7635529,{"description":2062,"labels":2063,"number":2068,"owner":1991,"repository":1992,"state":2034,"title":2069,"updated_at":2070,"url":2071,"score":2072},"### Component\n\nserver\n\n### Describe the bug\n\nI don't know yet why and how, but there's a bug in the repo syncing with Gitea (or maybe in general but the following report is from Gitea).\r\n\r\nI've seen this in the past in different characteristics but now I am facing it again. And I am a bit out of ideas after 2 hours.\r\n\r\nScenario:\r\n\r\n1. Create new Gitea org\r\n2. Create two repos\r\n3. Go to WP and click \"add repos\"\r\n4. Only one repo shows up\r\n\r\nEven after logout/login, same issue. Same issue also when directly checking via the API (which is expected as there's nothing but an API call in the background when syncing repos).\r\n\r\nSame user as the one which provides the WP - Gitea connection (and yes, the Gitea PAT is from an Gitea admin user and is in fact the same user as the one facing the issue).\r\n\r\nSet the server log level to \"DEBUG\" but no relatable entries.\r\n\r\nRelates to https://github.com/woodpecker-ci/woodpecker/discussions/2491\n\n### System Info\n\n```shell\nnext-7b3eeec65c (Oct 17th)\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).",[2064,2065],{"name":2013,"color":2014},{"name":2066,"color":2067},"forge/gitea","E96280",2613,"Some (Gitea) repositories are not synced","2023-11-05T18:33:32Z","https://github.com/woodpecker-ci/woodpecker/issues/2613",0.7647539,{"description":2074,"labels":2075,"number":2083,"owner":1991,"repository":1992,"state":2034,"title":2084,"updated_at":2085,"url":2086,"score":2087},"### Component\r\n\r\nweb-ui\r\n\r\n### Describe the bug\r\n\r\n@anbraten \r\n\r\n- [x] This does not work on light theme (fix: #2765):\r\n \r\n Looks like the SVG has a hardcoded backend color which if `fff`\r\n- [x] And if you're on next if there's an update it links to a not existing release page. (see https://ci.woodpecker-ci.org/admin#info), e.g. https://github.com/woodpecker-ci/woodpecker/releases/tag/next-fe48928 #2871 \r\n- [ ] if our CI does not update the docs because of `path` filters the version.json file is not updated.\r\n- [ ] if only `docs` wf runs the version.json is updated even though there's no new docker image\r\n- [x] RC versions are never respected #2871 \r\n \r\n\r\n\r\n### System Info\r\n\r\n```shell\r\nafter #2722\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/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).",[2076,2077,2080],{"name":2013,"color":2014},{"name":2078,"color":2079},"build","6AB8BA",{"name":2081,"color":2082},"summary","C3DC73",2748,"Fix version check","2024-01-03T09:31:50Z","https://github.com/woodpecker-ci/woodpecker/issues/2748",0.7661264,{"description":2089,"labels":2090,"number":2093,"owner":1991,"repository":1992,"state":2034,"title":2094,"updated_at":2095,"url":2096,"score":2097},"### Component\n\nweb-ui\n\n### Describe the bug\n\nCreate a secret (I guess the name is important for this bug).\r\n\r\nThen try to remove it with the trash button.\r\n\r\n\r\n\r\nNote : I managed to remove another secret. I think that there is a problem with the name of the secret I cannot remove.\r\n\r\n\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"next-94f2331a\"}\r\n\r\nBackend Kubernetes\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] 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).",[2091,2092],{"name":2013,"color":2014},{"name":2016,"color":2017},1937,"Cannot remove/delete/trash a secret","2023-07-08T20:17:41Z","https://github.com/woodpecker-ci/woodpecker/issues/1937",0.76691294,{"description":2099,"labels":2100,"number":2102,"owner":1991,"repository":1992,"state":2034,"title":2103,"updated_at":2104,"url":2105,"score":2106},"You ask in the readme:\r\n\r\n>Who uses Woodpecker?\r\n\r\nA topic (repository tag) can help answer the question.\r\n\r\nA good example is: https://github.com/topics/github-actions\r\n\r\nSo, please decide on a tag that should be used and promote it in the readme.\r\n\r\n[woodpecker](https://github.com/topics/woodpecker) is already used for unrelated purposes, so [woodpecker-ci](https://github.com/topics/woodpecker-ci) seem to be the best choice.\r\n\r\nI have used it here: https://codeberg.org/explore/repos?q=woodpecker-ci&topic=1",[2101],{"name":2027,"color":2028},320,"Promote topic","2022-01-11T15:47:59Z","https://github.com/woodpecker-ci/woodpecker/issues/320",0.7690327,["Reactive",2108],{},["Set"],["ShallowReactive",2111],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"l7m6AO9P438t6OqZR2khxTaeOtGadGDvRCtpqxfM4fA":-1},"/woodpecker-ci/woodpecker/1040"]