WorkerPool warnings after upgrade from 1.13 to 1.16-rc1 #8504

New Issue

GiteaMirror · 2025-11-02T08:09:06-06:00

GiteaMirror commented

2025-11-02 08:09:06 -06:00

Originally created by @pboguslawski on GitHub (Feb 5, 2022).

Gitea Version

1.16-rc1

Git Version

No response

Operating System

No response

How are you running Gitea?

Compiled from source.

Database

No response

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Description

After upgrade from 1.13 to 1.16-rc1 gitea send to its stderr messages like

2022/02/05 04:56:21 .../queue/workerpool.go:93:zeroBoost() [W] WorkerPool: 17 (for mirror-channel) has zero workers - adding 1 temporary workers for 5m0s
2022/02/05 04:56:28 .../queue/workerpool.go:93:zeroBoost() [W] WorkerPool: 14 (for repo_stats_update-channel) has zero workers - adding 1 temporary workers for 5m0s
2022/02/05 11:23:46 .../queue/workerpool.go:93:zeroBoost() [W] WorkerPool: 13 (for issue_indexer) has zero workers - adding 1 temporary workers for 5m0s

No such messages in gitea 1.13 on same data so looks like a bug in new gitea version.

Screenshots

No response

Originally created by @pboguslawski on GitHub (Feb 5, 2022). ### Gitea Version 1.16-rc1 ### Git Version _No response_ ### Operating System _No response_ ### How are you running Gitea? Compiled from source. ### Database _No response_ ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Description After upgrade from 1.13 to 1.16-rc1 gitea send to its stderr messages like ``` 2022/02/05 04:56:21 .../queue/workerpool.go:93:zeroBoost() [W] WorkerPool: 17 (for mirror-channel) has zero workers - adding 1 temporary workers for 5m0s 2022/02/05 04:56:28 .../queue/workerpool.go:93:zeroBoost() [W] WorkerPool: 14 (for repo_stats_update-channel) has zero workers - adding 1 temporary workers for 5m0s 2022/02/05 11:23:46 .../queue/workerpool.go:93:zeroBoost() [W] WorkerPool: 13 (for issue_indexer) has zero workers - adding 1 temporary workers for 5m0s ``` No such messages in gitea 1.13 on same data so looks like a bug in new gitea version. ### Screenshots _No response_

GiteaMirror closed this issue

2025-11-02 08:09:06 -06:00

GiteaMirror commented

2025-11-02 08:09:07 -06:00

@lunny commented on GitHub (Feb 5, 2022):

It's just a warn and it should have no effect for usage.

But I think maybe it could be a trace or a info. @zeripath

@lunny commented on GitHub (Feb 5, 2022): It's just a warn and it should have no effect for usage. But I think maybe it could be a `trace` or a `info`. @zeripath

GiteaMirror commented

2025-11-02 08:09:07 -06:00

@pboguslawski commented on GitHub (Feb 5, 2022):

It's just a warn and it should have no effect for usage.

Errors/warnings should not be ignored by admins. Gitea should not log errors/warnings for irrelevant stuff.

@pboguslawski commented on GitHub (Feb 5, 2022): > It's just a warn and it should have no effect for usage. Errors/warnings should not be ignored by admins. Gitea should not log errors/warnings for irrelevant stuff.

GiteaMirror commented

2025-11-02 08:09:07 -06:00

@zeripath commented on GitHub (Feb 5, 2022):

These are all already debug on 1.17. I'll add it to #18620

@zeripath commented on GitHub (Feb 5, 2022): These are all already debug on 1.17. I'll add it to #18620

GiteaMirror commented

2025-11-02 08:09:07 -06:00

@zeripath commented on GitHub (Feb 5, 2022):

I would note that this has been there since 1.15 when we moved to the zero initial worker mode and was there to ensure things were working correctly.

@zeripath commented on GitHub (Feb 5, 2022): I would note that this has been there since 1.15 when we moved to the zero initial worker mode and was there to ensure things were working correctly.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#8504