wxiaoguang e159297443 Fix queue worker incorrectly stopped when there are still more items in the queue (#29532) ... Without `case <-t.C`, the workers would stop incorrectly, the test won't pass. For the worse case, there might be only one running worker processing the queue items for long time because other workers are stopped. The root cause is related to the logic of doDispatchBatchToWorker. It isn't a serious problem at the moment, so keep it as-is. (cherry picked from commit 6465f94a2d26cdacc232fddc20f98d98df61ddac)		2024-03-06 12:10:46 +08:00
..
lqinternal
backoff.go
base.go
base_channel.go
base_channel_test.go
base_dummy.go
base_levelqueue.go
base_levelqueue_common.go
base_levelqueue_test.go
base_levelqueue_unique.go
base_redis.go
base_redis_test.go	[CI] disable redis test, no redis server yet in CI	2024-02-05 13:33:58 +01:00
base_test.go
config.go
manager.go
manager_test.go	Increase queue length (#27555)	2023-10-10 18:47:49 +08:00
queue.go
testhelper.go
workergroup.go	Fix queue worker incorrectly stopped when there are still more items in the queue (#29532)	2024-03-06 12:10:46 +08:00
workerqueue.go	Fix queue worker incorrectly stopped when there are still more items in the queue (#29532)	2024-03-06 12:10:46 +08:00
workerqueue_test.go	Fix queue worker incorrectly stopped when there are still more items in the queue (#29532)	2024-03-06 12:10:46 +08:00