High CPU usage of workflow update script

[jezdez]

After installing and doing the initialization, the workflow would hang in the background and use a high level of CPU until I killed the Python process via the activity manager.

Checking the /Users/jezdez/Library/Caches/com.runningwithcrayons.Alfred-3/Workflow Data/org.jeef.emoji/org.jeef.emoji.log file it says at the end:

10:27:51 workflow.py:2433 INFO     Checking for update ...
10:27:51 background.py:180 INFO     Task `__workflow_update_check` is already running
10:27:51 workflow.py:2351 DEBUG    Set last run version : 0.9.49
10:27:51 workflow.py:2194 DEBUG    Workflow finished in 0.146 seconds.
14:51:38 background.py:243 ERROR    Command failed with [-9] : [u'/usr/bin/python', '/Users/jezdez/Library/Application Support/Alfred 3/Alfred.alfredpreferences/workflows/user.workflow.72CB48E1-6DF8-430D-B50D-79E2B4410F92/workflow/update.py', u'check', 'jeeftor/EmojiTaco', '0.9.49']
14:51:38 background.py:248 DEBUG    Task `__workflow_update_check` finished
14:51:38 workflow.py:1568 DEBUG    Reading settings from `/Users/jezdez/Library/Application Support/Alfred 3/Workflow Data/org.jeef.emoji/settings.json` ...
14:51:38 workflow.py:2351 DEBUG    Set last run version : 0.9.49
14:51:38 workflow.py:2194 DEBUG    Workflow finished in 16067.089 seconds.

14:51 was the time I killed the process. So it seems to have been running for at least 16067.089 seconds, which seems an awful long time for checking for updates ;)

[miharekar]

Same here

[jeeftor]

Hmmm. I actually noticed this myself recently but I thought it was a proxy issue on my end. I'll look into it

Sent from my iPhone

On Jun 14, 2017, at 4:37 AM, Miha Rekar notifications@github.com wrote:

Same here

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[garymh]

Looks like this was related to a certain version of Python. Alfred is now disabling the script in the recent (beta) update:

[jeeftor]

Sounds like I better do an update! Expect one by this weekend

Sent from my iPhone

On Jul 19, 2017, at 1:21 PM, Gary Holtz notifications@github.com wrote:

Looks like this was related to a certain version of Python. Alfred is now disabling the script in the recent (beta) update:

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[FrancesCoronel]

Just wanted to add that yes, the workflow does cause high CPU usage because of the Python script.

With the update, it should be ok though!

[jorgenbs]

Thanks for the update, had the same issue