You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a periodic clockify-cli command running (clockify-cli report --duration-formatted) and keep seeing MacOS notifying me that it blocked incoming connections for 'clockify-cli' (see attached screenshot).
I'm not sure what is going on, as the notification is pretty scarce in information (nothing about a port or a pid or anything like that) but I'm a little puzzled anyway as to why clockify-cli would want to expose a listener. I couldn't find any obvious clues from the src either; there doesn't appear to be any code that creates a listener as far as I can tell.
Does clockify-cli indeed need to listen for incoming network connections, and if so why?
I'm running version Version: 0.45.0, Commit: ae519735a6e0448de46329c9c215007da365279e, Build At: 2023-08-05T23:20:01Z installed using homebrew, on MacOS Ventura 13.6
The text was updated successfully, but these errors were encountered:
Hello there,
Thanks for the great tool.
I have a periodic clockify-cli command running (
clockify-cli report --duration-formatted
) and keep seeing MacOS notifying me that it blocked incoming connections for 'clockify-cli' (see attached screenshot).I'm not sure what is going on, as the notification is pretty scarce in information (nothing about a port or a pid or anything like that) but I'm a little puzzled anyway as to why clockify-cli would want to expose a listener. I couldn't find any obvious clues from the src either; there doesn't appear to be any code that creates a listener as far as I can tell.
Does clockify-cli indeed need to listen for incoming network connections, and if so why?
I'm running version
Version: 0.45.0, Commit: ae519735a6e0448de46329c9c215007da365279e, Build At: 2023-08-05T23:20:01Z
installed using homebrew, on MacOS Ventura 13.6The text was updated successfully, but these errors were encountered: