\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]",[1984,1987],{"name":1985,"color":1986},"bug","d73a4a",{"name":1988,"color":1989},"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.7260538,{"description":1999,"labels":2000,"number":2004,"owner":1991,"repository":1992,"state":1993,"title":2005,"updated_at":2006,"url":2007,"score":2008},"### Clear and concise description of the problem\n\nIn a `Dockerfile` it is often necessary to connect to some resource (e.g. remote registry) and for that we need secrets.\r\n\r\nThere is no way to do this.\n\n### Suggested solution\n\nThe [official solution](https://docs.docker.com/engine/reference/builder/#run---mounttypesecret) is to use `RUN --mount=type=secret`. But that isn't supported by Woodpecker.\n\n### Alternative\n\n*There is no safe alternative.*\r\n\r\nUsing `ENV` is a terrible idea because they will be baked into the image. Unless they are passed into the docker build from the pipeline, but Woodpecker isn't able to do that currently.\r\n\r\nUsing `ARG` is also bad as they are [exposed](https://docs.docker.com/engine/reference/builder/#arg) in the docker history. So we can't use Woodpecker's `build_args` option.\n\n### Additional context\n\nI am sure some people will say that this is an easy problem to solve: \"just move that logic out of the Dockerfile and into the pipeline itself\".\r\n\r\nThat is not always possible. Some Dockerfiles are complex and must be used as-is. But they are managed by the pipeline, and the pipeline doesn't have any way to pass secrets (via environment variables or --mount=type=secret).\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.",[2001],{"name":2002,"color":2003},"feature","180DBE",2446,"Support --mount=type=secret when building a Dockerfile","2023-09-11T23:45:21Z","https://github.com/woodpecker-ci/woodpecker/issues/2446",0.7594053,{"description":2010,"labels":2011,"number":2016,"owner":1991,"repository":1992,"state":1993,"title":2017,"updated_at":2018,"url":2019,"score":2020},"### Component\n\nserver\n\n### Describe the bug\n\nError when enabling Gitea repository in Woodpecker CI:\n\n`could not create/update repo in store. error=\"pq: duplicate key value violates unique constraint \\\"UQE_repos_name\\\"\"`\n\nThere are no records with forge_id 0 in orgs table where we had similar problems\n\n### Steps to reproduce\n\n1. Press \"Enable\" in repository list\n2. Webhook is created\n3. Record in database can not be updated (possible tries to insert new one instead of updating?)\n\n### Expected behavior\n\n_No response_\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"3.3.0\"}\n```\n\n### Additional context\n\nPostgreSQL database, Gitea forge integration\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]",[2012,2013],{"name":1985,"color":1986},{"name":2014,"color":2015},"server","5D7A92",4935,"Activating repository error that failed to activate becauce of UQE_repos_name constraint","2025-03-11T14:11:01Z","https://github.com/woodpecker-ci/woodpecker/issues/4935",0.76087093,{"description":2022,"labels":2023,"number":2030,"owner":1991,"repository":1992,"state":1993,"title":2031,"updated_at":2032,"url":2033,"score":2034},"I think we should have a look at https://nextcloud.com/contribute/ and chery-pick some ideas from that",[2024,2027],{"name":2025,"color":2026},"documentation","7D625D",{"name":2028,"color":2029},"enhancement","7E1FE4",4113,"Improve docs about starting to contribute","2024-09-15T09:47:05Z","https://github.com/woodpecker-ci/woodpecker/issues/4113",0.7648509,{"description":2036,"labels":2037,"number":2041,"owner":1991,"repository":1992,"state":2042,"title":2043,"updated_at":2044,"url":2045,"score":2046},"https://ci.woodpecker-ci.org/repos/3780/pipeline/20983/15\r\n\r\nbuild-deb-rpo errors with:\r\n```\r\nVERSION_NUMBER=0.0.0 nfpm package --config ./nfpm/agent.yaml --target dist --packager deb\r\nmatching \"./woodpecker-agent.service\": file does not exist\r\nmake: *** [Makefile:319: bundle-agent] Error 1\r\n```",[2038],{"name":2039,"color":2040},"build","6AB8BA",4152,"closed","fix 'binary' workflow","2024-10-05T14:43:41Z","https://github.com/woodpecker-ci/woodpecker/issues/4152",0.73638624,{"description":2048,"labels":2049,"number":2052,"owner":1991,"repository":1992,"state":2042,"title":2053,"updated_at":2054,"url":2055,"score":2056},"### Clear and concise description of the problem\n\nWhen committing with a structured message (e.g. following Conventional Commits specification), Woodpecker cramps the whole message together into one large string when displaying it in the repo commit list and the pipeline run title. This is usually pretty ugly and decreases readability. \r\n\r\nExample:\r\n\r\n\n\n### Suggested solution\n\nA new environment variable CI_COMMIT_MESSAGE_HEADER could be added which would be used to populate the strings mentioned above. This would of course require parsing the commit message first.\n\n### Alternative\n\nAlternatively, a UI section for the body and footer of the commit message could be added below the pipeline run title to display those variables. \r\n\r\nAll of the steps described above would still be necessary, but in addition, at least CI_COMMIT_MESSAGE_BODY (if one wants to treat body and footer as one) would have to be parsed and added as well.\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.",[2050,2051],{"name":1988,"color":1989},{"name":2002,"color":2003},1489,"Beautify display of commit messages with bodies and/or footers","2023-08-20T16:52:56Z","https://github.com/woodpecker-ci/woodpecker/issues/1489",0.74105006,{"description":2058,"labels":2059,"number":2065,"owner":1991,"repository":1992,"state":2042,"title":2066,"updated_at":2067,"url":2068,"score":2069},"like the agent:\r\nhttps://github.com/woodpecker-ci/woodpecker/blob/205f8ecc1649ab48a9d5fb52b0ecd7b8c24abf4f/docker/Dockerfile.agent.multiarch#L21\r\n\r\nref https://docs.docker.com/engine/reference/builder/#healthcheck\r\n\r\nTODO:\r\n- [ ] add subcommand to server that can test against https://github.com/woodpecker-ci/woodpecker/blob/205f8ecc1649ab48a9d5fb52b0ecd7b8c24abf4f/server/router/router.go#L69\r\n- [ ] use subcommand in container",[2060,2061,2062],{"name":2014,"color":2015},{"name":2002,"color":2003},{"name":2063,"color":2064},"good first issue","76ea72",1943,"Add an healthcheck to server container","2023-07-25T13:55:31Z","https://github.com/woodpecker-ci/woodpecker/issues/1943",0.7444252,{"description":2071,"labels":2072,"number":2074,"owner":1991,"repository":1992,"state":2042,"title":2075,"updated_at":2076,"url":2077,"score":2078},"### Component\n\nserver\n\n### Describe the bug\n\nThere is unnecessary empty table `registry_v031` in database.\n\n### Steps to reproduce\n\n```sql\r\npostgres=# \\c woodpecker\r\nYou are now connected to database \"woodpecker\" as user \"postgres\".\r\nwoodpecker=# \\dt\r\n List of relations\r\n Schema | Name | Type | Owner\r\n--------+------------------+-------+------------\r\n public | agents | table | woodpecker\r\n public | configs | table | woodpecker\r\n public | crons | table | woodpecker\r\n public | files | table | woodpecker\r\n public | forges | table | woodpecker\r\n public | log_entries | table | woodpecker\r\n public | migration | table | woodpecker\r\n public | orgs | table | woodpecker\r\n public | perms | table | woodpecker\r\n public | pipeline_configs | table | woodpecker\r\n public | pipelines | table | woodpecker\r\n public | redirections | table | woodpecker\r\n public | registries | table | woodpecker\r\n public | registry_v031 | table | woodpecker\r\n public | repos | table | woodpecker\r\n public | secrets | table | woodpecker\r\n public | server_configs | table | woodpecker\r\n public | steps | table | woodpecker\r\n public | tasks | table | woodpecker\r\n public | users | table | woodpecker\r\n public | workflows | table | woodpecker\r\n(21 rows)\r\n\r\nwoodpecker=# select * from registry_v031;\r\n registry_id | registry_repo_id | registry_addr | registry_username | registry_password\r\n-------------+------------------+---------------+-------------------+-------------------\r\n(0 rows)\r\n``` \n\n### Expected behavior\n\nThere is no garbage table.\n\n### System Info\n\n```shell\nWoodpecker `2.7.0`, Postgres 16.\n```\n\n\n### Additional context\n\n#3806\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]",[2073],{"name":1985,"color":1986},4104,"Garbage table registry_v031","2024-09-14T11:41:15Z","https://github.com/woodpecker-ci/woodpecker/issues/4104",0.7500819,{"description":2080,"labels":2081,"number":2083,"owner":1991,"repository":1992,"state":2042,"title":2084,"updated_at":2085,"url":2086,"score":2087},"### Component\n\nserver\n\n### Describe the bug\n\nTrying out woodpecker, my docker-compose file:\n```\nservices:\n woodpecker-server:\n image: woodpeckerci/woodpecker-server:v3\n ports:\n - 8000:8000\n volumes:\n - woodpecker-server-data:/var/lib/woodpecker/\n environment:\n - WOODPECKER_OPEN=true\n - WOODPECKER_HOST=http://192.168.10.162:8000\n\nvolumes:\n woodpecker-server-data:\n```\n\nWhen running with `docker compose up`, I get the following:\n```\n~/projects/foss/woodpecker$ docker compose up\n[+] Running 1/1\n ✔ Container woodpecker-woodpecker-server-1 Created 0.1s \nAttaching to woodpecker-server-1\nwoodpecker-server-1 | {\"level\":\"info\",\"time\":\"2025-03-07T05:42:55Z\",\"message\":\"log level: info\"}\nwoodpecker-server-1 | {\"level\":\"warn\",\"time\":\"2025-03-07T05:42:55Z\",\"message\":\"no sqlite3 file found, will create one at '/var/lib/woodpecker/woodpecker.sqlite'\"}\nwoodpecker-server-1 | {\"level\":\"error\",\"error\":\"can't setup store: could not migrate datastore: unable to open database file: no such file or directory\",\"time\":\"2025-03-07T05:42:55Z\",\"message\":\"error running server\"}\nwoodpecker-server-1 exited with code 0\n~/projects/foss/woodpecker$ \n```\n\nAlso, I doubled checked the volume dir, and there is no files there:\n```\nroot@[REDACTED]:/var/lib/docker/volumes/woodpecker_woodpecker-server-data/_data# ls -la\ntotal 0\ndrwxr-xr-x. 1 root root 0 Mar 5 04:50 .\ndrwx-----x. 1 root root 10 Mar 7 18:37 ..\nroot@[REDACTED]:/var/lib/docker/volumes/woodpecker_woodpecker-server-data/_data# \n```\n\n\n### Steps to reproduce\n\n1. Woodperker with docker (configuration from docs) & agent entry removed. (only service)\n2. `docker compose up`\n3. Observe the error\n\n### Expected behavior\n\n_No response_\n\n### System Info\n\n```shell\nDocker version 28.0.1, build 068a01e\n```\n\n### Additional context\n\n**However**, when running with `woodpeckerci/woodpecker-server:v3-alpine` image - this issue goes away.\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]",[2082],{"name":1985,"color":1986},4939,"Fresh run with docker results in \"unable to open database file\"","2025-03-18T16:47:23Z","https://github.com/woodpecker-ci/woodpecker/issues/4939",0.75192475,{"description":2089,"labels":2090,"number":2095,"owner":1991,"repository":1992,"state":2042,"title":2096,"updated_at":2097,"url":2098,"score":2099},"### Component\n\ncli\n\n### Describe the bug\n\nSince updating to 2.4.x woodpecker-cli runs into a runtime error:\r\n\r\n```\r\npanic: runtime error: invalid memory address or nil pointer dereference\r\n[signal SIGSEGV: segmentation violation code=0x2 addr=0x20 pc=0x1004c71a8]\r\n\r\ngoroutine 1 [running]:\r\ngo.woodpecker-ci.org/woodpecker/v2/cli/internal/config.Load(0x14000591580)\r\n go.woodpecker-ci.org/woodpecker/v2/cli/internal/config/config.go:53 +0x268\r\ngo.woodpecker-ci.org/woodpecker/v2/cli/common.Before(0x14000591580)\r\n go.woodpecker-ci.org/woodpecker/v2/cli/common/hooks.go:53 +0x70\r\ngithub.com/urfave/cli/v2.(*Command).Run(0x14000597760, 0x14000591580, {0x1400014c000, 0xc, 0xc})\r\n github.com/urfave/cli/v2@v2.27.1/command.go:219 +0x3d0\r\ngithub.com/urfave/cli/v2.(*App).RunContext(0x140001d6e00, {0x101e2cca0, 0x102d70660}, {0x1400014c000, 0xc, 0xc})\r\n github.com/urfave/cli/v2@v2.27.1/app.go:337 +0x514\r\ngithub.com/urfave/cli/v2.(*App).Run(...)\r\n github.com/urfave/cli/v2@v2.27.1/app.go:311\r\nmain.main()\r\n go.woodpecker-ci.org/woodpecker/v2/cmd/cli/main.go:26 +0x48\r\n```\r\n\r\nHere is an example. I export the variables first\r\n\r\n```\r\nexport WOODPECKER_PROJECT=\"test/project\"\r\nexport WOODPECKER_SERVER=\"https://our.server\"\r\nexport WOODPECKER_TOKEN=\"asdf\"\r\n```\r\n\r\nThen i run any command, like `woodpecker-cli pipeline ls` and the error occurs.\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"2.4.1\"}\r\n\r\n➜ ~ woodpecker-cli --version\r\nwoodpecker-cli version 2.4.1\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]",[2091,2092],{"name":1985,"color":1986},{"name":2093,"color":2094},"cli","1d76db",3553,"woodpecker-cli - runtime error: invalid memory address or nil pointer dereference with 2.4.x","2024-04-15T19:18:03Z","https://github.com/woodpecker-ci/woodpecker/issues/3553",0.7528861,["Reactive",2101],{},["Set"],["ShallowReactive",2104],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"k3eqncepRIlupfFgBKq5_CuP0FXZyMyAeEqwZAAwiaI":-1},"/woodpecker-ci/woodpecker/4517"]