\n\nThis id number isn't helpful for viewing, as people don't have the IDs of all their CI runners memorized. It'd be much better to use the agent name (or alias / whatever you tagged it as) instead, and possibly default to the ID if no name is present.\n\n### Suggested solution\n\nUse the agent name / alias instead of an id number for the queue badge.\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/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.",[3171],{"name":3172,"color":3173},"feature","180DBE",5469,"In the queue list, use the agent name rather than the agent id for the badge.","2025-08-29T18:27:54Z","https://github.com/woodpecker-ci/woodpecker/issues/5469",0.7933293,{"description":3180,"labels":3181,"number":3185,"owner":3161,"repository":3162,"state":3163,"title":3186,"updated_at":3187,"url":3188,"score":3189},"### Clear and concise description of the problem\r\n\r\nFrom a non-admin user's view, when I create a workflow with `labels` that do not match to any agents' configuration, the workflow will remain in a \"pending\" state indefinitely.\r\n\r\nThis means that a non-admin user cannot distinguish between the case where all agents are currently running other workflows, and it is sufficient to just be patient, and the case where no agents will ever be able to execute the workflow, and no amount of patience will ever be enough. This is a suboptimal user experience.\r\n\r\nAs an admin user, I at least can view the `/admin#queue` page and see a task in the queue with the `labels` required for the workflow, which is better, but still doesn't explain *why* the workflow is stalled. Even on `admin#agents` I cannot see the labels that are configured for the agents, so I either have to know about, or have to look at all of the configurations of the agent processes to determine the root cause.\r\n\r\n### Suggested solution\r\n\r\nIn the web interface, I would like for non-admin users to have feedback on the `/repos/$x/pipeline/$y` page explaining that a workflow is unschedulable if no agents have the appropriate filter(s) configured.\r\n\r\nAdditionally, this could also be displayed for unschedulable tasks in the `/admin#queue` page for admin users.\r\n\r\n### Alternative\r\n\r\n_No response_\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Validations\r\n\r\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]\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 request the same feature to avoid creating a duplicate.",[3182,3183,3184],{"name":3152,"color":3153},{"name":3155,"color":3156},{"name":3158,"color":3159},4392,"Distinguish to users the difference between stalled and pending workflows","2024-11-18T08:28:33Z","https://github.com/woodpecker-ci/woodpecker/issues/4392",0.79366213,{"description":3191,"labels":3192,"number":3199,"owner":3161,"repository":3162,"state":3163,"title":3200,"updated_at":3201,"url":3202,"score":3203},"### Component\r\n\r\nagent\r\n\r\n### Describe the bug\r\n\r\nThe agent failed to pick up new jobs, reporting RPC error.\r\n\r\n```\r\n2:48AM INF src/shared/logger/logger.go:101 > log level: debug\r\n2:48AM WRN src/pipeline/backend/kubernetes/kubernetes.go:101 > WOODPECKER_BACKEND_K8S_PULL_SECRET_NAMES is set to the default ('regcred'). It will default to empty in Woodpecker 3.0. Set it explicitly before then.\r\n2:48AM DBG src/cmd/agent/core/agent.go:173 > loaded kubernetes backend engine\r\n2:48AM DBG src/cmd/agent/core/agent.go:201 > agent registered with ID 30003\r\n2:48AM INF src/cmd/agent/core/agent.go:243 > starting Woodpecker agent with version 'next-5527d9bf86' and backend 'kubernetes' using platform 'linux/amd64' running up to 1 pipelines in parallel\r\n2:48AM DBG src/cmd/agent/core/agent.go:226 > created new runner 0\r\n2:48AM DBG src/cmd/agent/core/agent.go:234 > polling new steps\r\n2:48AM DBG src/agent/runner.go:54 > request next execution\r\n2:49AM ERR src/agent/rpc/client_grpc.go:93 > grpc error: done(): code: Unavailable error=\"rpc error: code = Unavailable desc = keepalive ping failed to receive ACK within timeout\"\r\n```\r\n\r\n### System Info\r\n\r\n```shell\r\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"2.4.1\"}\r\n```\r\n\r\n### Additional context\r\n\r\nThe server and the agent are running in two Kubernetes clusters in different locations, connected by WireGuard + iptables.\r\n\r\nThe server still assigns the pipeline to the agent, and may falsely assign more pipelines than the capacity.\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]",[3193,3196],{"name":3194,"color":3195},"bug","d73a4a",{"name":3197,"color":3198},"agent","ECBCDF",3712,"Agent failed to retrieve new jobs due to RPC error \"keepalive ping failed to receive ACK within timeout\"","2024-05-23T14:23:26Z","https://github.com/woodpecker-ci/woodpecker/issues/3712",0.8057561,{"description":3205,"labels":3206,"number":3211,"owner":3161,"repository":3162,"state":3163,"title":3212,"updated_at":3213,"url":3214,"score":3215},"We currently query our forges quite often for some calls. Some of those calls could be cached:\r\n- organisations\r\n- permissions\r\n- branches",[3207,3210],{"name":3208,"color":3209},"server","5D7A92",{"name":3155,"color":3156},1039,"Cache forge api requests","2024-02-25T07:20:01Z","https://github.com/woodpecker-ci/woodpecker/issues/1039",0.80653805,{"description":3217,"labels":3218,"number":3223,"owner":3161,"repository":3162,"state":3163,"title":3224,"updated_at":3225,"url":3226,"score":3227},"add an Admin panel to:\n * [x] see all registered agents #252 \n * [x] see all registered users (add / remove admins) #1634\n * [x] https://github.com/drone/drone-ui/pull/334 -> #1632\n * [x] `/queue/info`\n * [x] pause / resume queue\n * [ ] clear / reset queue and kill all pipelines\n * [ ] `/pipelines`\n * [ ] see resource usage per ... user/repo/org\n * [ ] report pipeline status pushed that failed ... -> user permissions changed etc...\n * [x] orgs list #2307 \n * [x] see all activated repos #2347 \n * [ ] pipeline stats https://github.com/woodpecker-ci/woodpecker/issues/345#issuecomment-1400542018\n * [x] show updates https://github.com/woodpecker-ci/woodpecker/issues/616\n * [ ] search https://github.com/woodpecker-ci/woodpecker/issues/3015\n * [ ] #4807 ",[3219,3220],{"name":3172,"color":3173},{"name":3221,"color":3222},"summary","C3DC73",345,"[Feature] Admin Panel","2025-02-08T07:40:04Z","https://github.com/woodpecker-ci/woodpecker/issues/345",0.8110252,{"description":3229,"labels":3230,"number":3236,"owner":3161,"repository":3162,"state":3237,"title":3238,"updated_at":3239,"url":3240,"score":3241},"Add an autoscaler into the server (optional, disabled by default)\r\n\r\nTODOs:\r\n - API for agent to tell it should stop -> teardown before it pulls from next workflow\r\n - Server calc if it should spinn up or teardown agents (add some inactivity/wait perode before change something)\r\n - to start just a basic \"autoscaler\"\r\n\r\n---\r\nBounty: 200$",[3231,3232,3233],{"name":3208,"color":3209},{"name":3172,"color":3173},{"name":3234,"color":3235},"bounty","bfd4f2",1333,"closed","Add initial Autoscaler support","2023-05-14T20:24:35Z","https://github.com/woodpecker-ci/woodpecker/issues/1333",0.74252796,{"description":3243,"labels":3244,"number":3246,"owner":3161,"repository":3162,"state":3237,"title":3247,"updated_at":3248,"url":3249,"score":3250},"### Component\n\nserver, other\n\n### Describe the bug\n\nSince updating to 2.7 we've observed a massive spike on the database load. Most of it seems to come from updates to the `agents` table. More specifically, the `last_work` field of several agents is updated multiple times per second.\r\n\r\nThis is greatly impacting database performance (which seems to feed into https://github.com/woodpecker-ci/woodpecker/issues/3999)\r\n\r\nI haven't done a full profiling but if I had to guess this seems to come from this change https://github.com/woodpecker-ci/woodpecker/pull/3844/files#diff-0f4ca4733649eb6707a0dd7e0ca0083cdc587b5cdced5b3ac051fc32cc9353cbR361-R368. If I understand correctly at every time a log line is persisted to the database, the respective agent is updated. The frequency of these updates seem quite high.\r\n\r\nFor context we were running Woodpecker 2.3 with a PostgreSQL database on Amazon RDS db.t4g.small before just fine (2 vCPU and 2 GiB RAM). After 2.7 we had to update to a db.t4g.xlarge (4 vCPU and 8 GiB RAM) and it's still struggling on the CPU.\r\n\r\nWe're running on Kubernetes with 10 agents and up to 10 workflows for agent.\n\n### Steps to reproduce\n\n1. Install Woodpecker 2.7\r\n2. Run multiple Workflows\r\n3. Observe multiple updates on the `agents` table\n\n### Expected behavior\n\nFrom https://github.com/woodpecker-ci/woodpecker/pull/3844 this seems to be the intended behavior. However it's clearly coming at a cost.\r\n\r\nMaybe we could only update the agents every X minutes instead of every log line/every second (not sure how it's implemented right now, need to look deeper). Possibly the same could be said for log_entries update, their frequency might be just a tad too high. Of course surely there are risks here (i.e. losing logs).\r\n\r\nWe will test an internal version with the last work update on every log disabled and see how that goes.\n\n### System Info\n\n```shell\nWoodpecker 2.7\r\nKubernetes installation\n```\n\n\n### Additional context\n\nHere's our Amazon Performance Insights from the database. On Friday 9th evening we updated Woodpecker from 2.3 to 2.7 but we barely had any pipelines ran then nor during the weekend. Then on Monday you can see how load is many times higher than the previous week. \r\n\r\n\r\n\r\nMost of it is from INSERTs coming from `log_entries` and `agents` however a more detailed analysis shows that in query _volume_, `log_entries` updates have not increased much after the update. However `agents` have increased tremendously. \r\n\r\nOn Monday we increased the database from a t4g.small to t4g.xlarge which helped but did not solve the issue.\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]",[3245],{"name":3194,"color":3195},4030,"Massive load on agents table since 2.7","2024-08-14T19:53:37Z","https://github.com/woodpecker-ci/woodpecker/issues/4030",0.77002203,{"description":3252,"labels":3253,"number":3255,"owner":3161,"repository":3162,"state":3237,"title":3256,"updated_at":3257,"url":3258,"score":3259},"\r\n\r\n\r\nwoodpecker version: v2.2.2\r\n\r\nif the autoscaler just cancled an agent who just managed to mark an task as started ... we will wait without any chance of success.\r\n\r\nso i propose on agent removal, (and if agent heartbet do timeout) to \"reset\" all running tasks in queue, so healthy agents can pick them up again",[3254],{"name":3194,"color":3195},3248,"remove of agent does not reset task in queue","2024-04-15T18:22:01Z","https://github.com/woodpecker-ci/woodpecker/issues/3248",0.7726574,{"description":3261,"labels":3262,"number":3268,"owner":3161,"repository":3162,"state":3237,"title":3269,"updated_at":3270,"url":3271,"score":3272},"to make sure on agent restart to also have the newest default images, we should pull them.\r\n\r\nhttps://github.com/woodpecker-ci/woodpecker/blob/master/shared/constant/constant.go",[3263,3264,3265],{"name":3197,"color":3198},{"name":3155,"color":3156},{"name":3266,"color":3267},"good first issue","76ea72",947,"Pull default images on agent start","2022-08-14T19:22:36Z","https://github.com/woodpecker-ci/woodpecker/issues/947",0.77268106,["Reactive",3274],{},["Set"],["ShallowReactive",3277],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fwwmnhk0Als715XJpfEKIE-isDmsqVuNMGS__ThBuHug":-1},"/woodpecker-ci/woodpecker/3826"]