Closed nariox closed 4 years ago
Thanks @nariox, I'll push a fix for this in the next version
Hi @amanusk, It's really a low priority bug, it only fails when the user does something that doesn't really make sense, but I thought it'd be right to report it anyway. Thank you for the quick and courteous response.
Fixed in version 1.0, setting workers to 0 does not activate stress at all. Please validate if you can.
Great, no more crashes :) Thanks a lot!
Step 1: Describe your environment
Step 2: Describe the problem:
Observed Results:
If I set the stress options to 0 worker for all stress options and switch to stress mode, nothing happens (nothing wrong here), but when I switch back to monitor mode, the program crashes.
Expected behavior:
The program either realizes that stress needs at least one worker and prevents stress mode being activated without workers or program realizes no workers were called, so it doesn't try to close workers when none are present
Traceback output:
traceback.txt