Verify `caffeinate` is being ignored via assertions
BigMacAdmin opened this issue · comments
User reported on Slack that caffeinate was not being ignored for assertions:
https://macadmins.slack.com/archives/C04FXLJB8GG/p1710965891604149?thread_ts=1710962743.534069&cid=C04FXLJB8GG
I had a quick update on this as I was able to reproduce it.
if caffeinate is being run twice for whatever reason it only removes one instance from the blocking assertions list and causes renew to not display.
Steps to reproduce:
Run two instances of caffeinate -d and trigger Renew.