ineednewpajamas

Issue persists in chef-server-core-15.0.9 but with updated versions ``` /opt/opscode/embedded/lib/ruby/gems/2.7.0/gems/chef-vault-4.1.10/lib/chef-vault/version.rb:18: warning: already initialized constant ChefVault::VERSION /opt/opscode/embedded/lib/ruby/gems/2.7.0/gems/chef-vault-4.1.5/lib/chef-vault/version.rb:18: warning: previous definition of VERSION was here /opt/opscode/embedded/lib/ruby/gems/2.7.0/gems/chef-vault-4.1.10/lib/chef-vault/version.rb:19: warning: already initialized constant ChefVault::MAJOR /opt/opscode/embedded/lib/ruby/gems/2.7.0/gems/chef-vault-4.1.5/lib/chef-vault/version.rb:19:...

The current behavior seems at odds with this line in the docs "Once turned on, the Compliance Phase always outputs its results in the CLI on manual runs. The output...

Looks good using develop5. Thank you.

Note that this cookbook also relies on hostsfile and that also has the issue and doesn't seem to be maintained: https://github.com/customink-webops/hostsfile/issues/102

Also tested on 4.1.7-develop6 just in case, still an issue. I tried to look through the code but I'm stumped.

I wonder if the issue is here: https://github.com/StuffAnThings/qbit_manage/blob/adb58ddd1486207cab087647e577a07028a37103/modules/core/share_limits.py#L545 Since max_seeding_time defaults to -1, wouldn't it never really be `None` and there is no check for -1 so it would hit...

I'm working to rewrite this to support more config options since the original was really specific to my setup

I fizzled out with life. I might be able to pick it back up in November.