API configuration defaults to value 0 for limitThreads if it is not specified at all in the configuration file. This can happen when the user upgrades to the latest version while still using the old config file that does not contain the new parameter.
This causes an exception down the line when the value is about to be used, as 0 threads is just wrong.
Mitigation:
Add line
limitThreads: -1
(or any other valid number > 0) to config.yml to make things work.
Jusas
commented
1 year ago
Noticed by a user:
API configuration defaults to value
0forlimitThreadsif it is not specified at all in the configuration file. This can happen when the user upgrades to the latest version while still using the old config file that does not contain the new parameter. This causes an exception down the line when the value is about to be used, as 0 threads is just wrong.Mitigation:
Add line
(or any other valid number > 0) to
config.ymlto make things work.