Python taking 100% of my processor #23
Comments
|
Hi, First and foremost, I am huge fan of this workflow and use it daily! However, I am experiencing the same issue as @arturbenchimol and I've turned it off also :-( I'm also not an expert programmer but there is a process called "Python" that is consuming ~98% of my CPU. Here are the "Open files and ports" (found via Activity Monitor -> Inspect): Finally, my system specs are below:
Please let me know what else I can do to help debug from here. Justin |
|
thanks, @justinjm I'll give it a try and report back here. Thanks! |
|
I have the same issue. Alfred Fixum didn't solve the issue unfortunately. Only resolution would be if the workflow get's updated. @azai91 any plans for solving this bug? |
|
I'm facing the same problem. Hope this could be fixed soon. |
|
I added the Fixum workflow and it stopped bothering me.
… On Jun 22, 2017, at 16:55, Carlos Yaconi H. ***@***.***> wrote:
I'm facing the same problem. Hope this could be fixed soon.
Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#23 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AIkjqMeB98Hd76Ll0dGZqkj__OW9bNXhks5sGtTfgaJpZM4M6P9L>.
|
|
@jgarber is just swapping the file for the new version enough? |
|
Sorry I have to ask, but do I run "make" after cloning this to get the workflow updated? I tried it but getting some errors. I just want to get this updated because I'm having the same issue as mentioned above. Thanks! edit: screenshot http://d3fy.xyz/GCS9r5 |
|
Sorry for the noob question here, but I can't find anything online to help me with this... How do I get this repo "packaged" into an alfred workflow so I can install it? I'm trying to get the latest version. Thanks |
|
@azai91 - please create a release with the most recent version. Thank you. |
|
It is the Though currently it is still using a version of the alfred-workflow module which is incompatible with Alfred 3.4 but I have submitted a PR for updating it. I added the new version as a git submodule so use |
|
Thank you @sorbits - I appreciate it! |
I realize that it is not popular to change the implementation to another language, but I felt a major refactoring was called for to continue adding desired features, and as I work a lot faster in ruby, I decided to do it in ruby. Some of the improvements that this rewrite brings: - When we have cached data, we immediately return a response to Alfred based on the cache. If the cace is older than 10 minutes, we refresh the cache _in a background process_ and instruct Alfred to reload the list again after 0.8 seconds. - Removed `d > Clear Cache` and `d > Set Cache [seconds]` because of the improved caching behavior. - The create actions accept an optional document name and are no longer under `d >`, for example `d ns Budget` should now create a spreadsheet named “Budget”. Closes azai91#11. - Removed `d > Login` as we automatically open the Google Sign In page when refresh token is missing/invalid. - Changed `d > Logout` to `d Sign out of Google Drive` and made it perform an account sign out (instead of just deleting the access tokens). - Refresh access token when expiration time is less than 10 seconds into the future. This avoids an extra (failing) server request/response, which is mainly for the document creation actions, as Google’s servers are on the slow side. - The OAuth2 HTTP callback server is running in our main process, this means that we can perform actions that require authentication _after_ we receive the callback from Google, for example `d new document` without a valid token will now first ask the user to sign in and _then_ create the new document. It also improves robustness slightly because error handling is in the same process. - Cache is refreshed (in the background) after creating a new document. - Add verbose (timestamped) logging which should make troubleshooting easier. - The OAuth2 HTTP callback server will run until we see the expected `GET /` request (so not fooled by a `favicon.ico` request or similar) and it uses a URL parser to obtain the `code` query parameter from the callback URL. The above should fix azai91#5, azai91#16, azai91#23, and azai91#25. You can also close azai91#28 (but I already did that in 6006836).
I realize that it is not popular to change the implementation to another language, but I felt a major refactoring was called for to continue adding desired features, and as I work a lot faster in ruby, I decided to do it in ruby. Some of the improvements that this rewrite brings: - When we have cached data, we immediately return a response to Alfred based on the cache. If the cace is older than 10 minutes, we refresh the cache _in a background process_ and instruct Alfred to reload the list again after 0.8 seconds. - Removed `d > Clear Cache` and `d > Set Cache [seconds]` because of the improved caching behavior. - The create actions accept an optional document name and are no longer under `d >`, for example `d ns Budget` should now create a spreadsheet named “Budget”. Closes #11. - Removed `d > Login` as we automatically open the Google Sign In page when refresh token is missing/invalid. - Changed `d > Logout` to `d Sign out of Google Drive` and made it perform an account sign out (instead of just deleting the access tokens). - Refresh access token when expiration time is less than 10 seconds into the future. This avoids an extra (failing) server request/response, which is mainly for the document creation actions, as Google’s servers are on the slow side. - The OAuth2 HTTP callback server is running in our main process, this means that we can perform actions that require authentication _after_ we receive the callback from Google, for example `d new document` without a valid token will now first ask the user to sign in and _then_ create the new document. It also improves robustness slightly because error handling is in the same process. - Cache is refreshed (in the background) after creating a new document. - Add verbose (timestamped) logging which should make troubleshooting easier. - The OAuth2 HTTP callback server will run until we see the expected `GET /` request (so not fooled by a `favicon.ico` request or similar) and it uses a URL parser to obtain the `code` query parameter from the callback URL. The above should fix #5, #16, #23, and #25. You can also close #28 (but I already did that in 6006836).
|
There is now a version 2.0 which is a complete rewrite and no longer relies on the python library that caused this issue. |
Hi there, I've been using this workflow and I absolutely love it. I realized it was taking almost 100% of my processor capacity and I had to turn it off to bring it back to normal. The process that was taking all the CPU power was Python.
It also elevated Alfred's energy impact to 151.95
I am not really a programer so I wouldn't be able to point out exactly what was happening. Is there any fix I should do?
thanks!
The text was updated successfully, but these errors were encountered: