Skip to content

Conversation

@HiroakiMikami
Copy link

The description of --num-tasks seems to be wrong, and this PR fixes the description.

--num-tasks description says that "if the value is 0, worker will process infinite number of tasks".
But when I set --num-tasks to 0, the worker exits soon after initialization.

related code:

for i := w.config.NumTasks; i != 0; i-- {

@everpeace
Copy link
Contributor

hmm... should we fix in the case of 0 so as to process tasks infinitely??

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants