Forcing hard limit to max-workers via cpus available is not strictly required and should not be enforced. Defaults are already tied to number of cores, and the value passed should be the explicit value used (this puts more responsibility on the caller of multi-cuke to know limits, but doesn't artificially restrict them to one browser per core).
This is in reference to issue https://github.com/midniteio/multi-cuke/issues/35
Forcing hard limit to max-workers via cpus available is not strictly required and should not be enforced. Defaults are already tied to number of cores, and the value passed should be the explicit value used (this puts more responsibility on the caller of multi-cuke to know limits, but doesn't artificially restrict them to one browser per core).
@jimusbobus for reference.