ratson Posted March 3, 2016 Share Posted March 3, 2016 Hi, some workflows that used to work cannot be used since although their command is found but once they are selected I cannot proceed. I have issues with the following: - http://www.packal.org/workflow/movie-and-tv-show-search - http://www.packal.org/workflow/packal-workflow-search - http://www.packal.org/workflow/homebrew-and-cask-alfred the interesting part is that there are no messages shown in workflow debug and using their commands in terminal do work and return the needed data in xml format. Can you give me some troubleshooting hints? thanks! Link to comment
ratson Posted March 4, 2016 Author Share Posted March 4, 2016 it seems to me like Alfred couldn't connect to the internet??? at least I have tried a few additional workflows and when it does it's job locally it works but when it needs to connect to the internet it doesn't. although Alfred can check for updates. Could you help me please? Link to comment
Andrew Posted March 4, 2016 Share Posted March 4, 2016 it seems to me like Alfred couldn't connect to the internet??? at least I have tried a few additional workflows and when it does it's job locally it works but when it needs to connect to the internet it doesn't. although Alfred can check for updates. Could you help me please? Are you using a proxy to connect to the internet? If so, you may need to select to use the proxy settings in the bottom left of Alfred's "Advanced" preferences. Link to comment
deanishe Posted March 5, 2016 Share Posted March 5, 2016 Those are all Python workflows. I haven't figured out why, but sometimes Python stops working in applications (I've had the issue with Alfred and Sublime Text). If other, non-Python workflows continue to work, I'd suggest this may be the problem you're having. The only fix I've found so far is rebooting. Link to comment
ratson Posted March 7, 2016 Author Share Posted March 7, 2016 Thanks guys, no proxy. reboot fixed it, yes these are all python workflows.... is this a known bug? for the developers too? Link to comment
deanishe Posted March 7, 2016 Share Posted March 7, 2016 Dunno. This might be the first Andrew has heard of the issue, but it doesn't seem to be specific to Alfred. Whenever this has happened, I've also had other issues with the system, and restarting the affected applications has no effect. As a result, I figure it's a bug in some OS X subsystem. Link to comment
ratson Posted March 7, 2016 Author Share Posted March 7, 2016 Dunno. This might be the first Andrew has heard of the issue, but it doesn't seem to be specific to Alfred. Whenever this has happened, I've also had other issues with the system, and restarting the affected applications has no effect. As a result, I figure it's a bug in some OS X subsystem. perhaps. ok, any ways thanks for the quick help, everything is working properly now! Link to comment
deanishe Posted April 18, 2016 Share Posted April 18, 2016 It appears that this issue is caused by a full IO buffer, which is causing the workflow process to lock up. The root cause is Alfred's handling of output to STDERR. It predominantly affects workflows based on Alfred-Workflow, as I've encouraged AW users to log heavily. Link to comment
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now