![]() ġ2:25:36 workflow.py:2263 DEBUG Workflow finished in 0.625 seconds. ġ2:25:36 workflow.py:2221 DEBUG Workflow version : 2.1.0ġ2:25:36 background.py:187 DEBUG Executing task `_workflow_update_install` in background.ġ2:25:36 workflow.py:1384 DEBUG Downloading and installing update. ġ2:25:36 background.py:178 DEBUG Command arguments cached to `/Users/candstef/Library/Caches/-3/Workflow Data/-pwgen/_workflow_update_install.argcache`ġ2:25:36 background.py:182 DEBUG Calling. I'm using Alfred 3.3.2 on macOS 10.12.5. Pasting the last part of the debug report:ġ2:25:36 update.py:281 DEBUG Release `v1.0` : ġ2:25:36 update.py:352 INFO 11 releases for deanishe/alfred-pwgenġ2:25:36 update.py:363 DEBUG Latest : Version('2.1.1') Installed : Version('2.1.0')ġ2:25:36 workflow.py:1894 DEBUG Cached data saved at : /Users/candstef/Library/Caches/-3/Workflow Data/-pwgen/_workflow_update_status.cpickleġ2:25:36 workflow.py:2541 DEBUG Downloading update. However, when trying to update with the built-in workflow update option it seems to get stuck (the attached image is just showed indefinitely) and the update is not downloaded/installed. I noticed that there is an update to the workflow. The default strength of 3 is sufficient for most purposes (~6.5 years to guess the password on 2015 dedicated password-cracking hardware). ![]() Please see the GitHub README for detailed information on the strength of the generated passwords and which settings you should (or shouldn't) use.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |