Ruby workflows in Mavericks

[radioman]

Sorry if this has been posted (I could not find any references). Just wondering if there are definitive plans to support Mavericks. 

[Andrew]

Sorry if this has been posted (I could not find any references). Just wondering if there are definitive plans to support Mavericks. 

 

Alfred 2 already runs great on Mavericks

[PSiCKo]

I'm using it on mavericks. The only issue is de dictionary, It doesn't define in alfred's box. But alfred runs on mavericks

[leefur]

Righteous. I hope the dictionary thing gets ironed out too. I use that a couple times a day.

[lanej0]

I've run into a couple of issues with workflows that worked before going to Mavericks.  Not sure if the workflows need tweaking, or if there is a compatibility issue, but here's a couple that I'm having trouble with:

 

https://github.com/neilrenicker/alfred-harvest

 

Trying to run the setup on this, you type "hv" <space> "setup", and then Alfred flips over to doing a Google search.  It's supposed to accept some arguments in order to set up authentication -- but it doesn't do that.

 

I've run into a similar problem with arguments using the Github workflow here:

 

https://github.com/zenorocha/alfred-workflows

 

This one definitely worked on 10.8 but upgrading to 10.9 has made the arguments work in strange ways.

[jdfwarrior]

I've run into a couple of issues with workflows that worked before going to Mavericks.  Not sure if the workflows need tweaking, or if there is a compatibility issue, but here's a couple that I'm having trouble with:

 

https://github.com/neilrenicker/alfred-harvest

 

Trying to run the setup on this, you type "hv" <space> "setup", and then Alfred flips over to doing a Google search.  It's supposed to accept some arguments in order to set up authentication -- but it doesn't do that.

 

I've run into a similar problem with arguments using the Github workflow here:

 

https://github.com/zenorocha/alfred-workflows

 

This one definitely worked on 10.8 but upgrading to 10.9 has made the arguments work in strange ways.

 

Are you sure that this isn't an issue with proper use of the workflow or something on the script side? I can't confirm the Harvest workflow but the Github one seems to be working in Mavericks for me.

[atsgal]

nt

Edited October 16, 2013 by atsgal

[sayzlim]

Can anyone force the files/folders search to open in new tab instead of creating new window?

[surrealroad]

Edit: never mind.

Edited October 23, 2013 by Jack James

[neilmiddleton]

I'm seeing similar issues with Workflows.

 

My workflow (here) worked fine before mavericks, now does nothing, and doesn't yield anything in the logs.

[Andrew]

I'm seeing similar issues with Workflows.

 

My workflow (here) worked fine before mavericks, now does nothing, and doesn't yield anything in the logs.

 

Could you check the location of ruby in Terminal...

 

whereis ruby

 

Cheers,

Andrew

[austinjreilly]

I'm having this same issue.

 

This was working before Mavericks.

 

Let's use Recent Downloads (https://github.com/ddjfreedom/recent-downloads-alfred-v2) as an example.

 

I'll type "Rec", the Recent Downloads workflow displays below the Alfred prompt as before, I hit the down arrow, then enter, and at that point Alfred reverts to the default search.

 

In the terminal, the output of whereas ruby is /usr/bin/ruby

 

Thanks for looking into this!

[jdfwarrior]

I'm having this same issue.

 

This was working before Mavericks.

 

Let's use Recent Downloads (https://github.com/ddjfreedom/recent-downloads-alfred-v2) as an example.

 

I'll type "Rec", the Recent Downloads workflow displays below the Alfred prompt as before, I hit the down arrow, then enter, and at that point Alfred reverts to the default search.

 

In the terminal, the output of whereas ruby is /usr/bin/ruby

 

Thanks for looking into this!

 

Is your ruby install the default install with the OS or something custom built or installed from something like home-brew? The reason I ask is, I'm not a big ruby guy so I don't have any kind of special installation of it and the recent downloads workflow and a recent documents workflow I have both seem to work fine in Mavericks.

[ClintonStrong]

I'm having this same issue.

 

This was working before Mavericks.

 

Let's use Recent Downloads (https://github.com/ddjfreedom/recent-downloads-alfred-v2) as an example.

 

I'll type "Rec", the Recent Downloads workflow displays below the Alfred prompt as before, I hit the down arrow, then enter, and at that point Alfred reverts to the default search.

 

In the terminal, the output of whereas ruby is /usr/bin/ruby

 

Thanks for looking into this!

 

This is an issue with the workflows, not with Alfred. Mavericks comes with an updated version of Ruby (v2.0.0), which has some compatibility issues with code written for v1.8.7 (the version of Ruby included with prior releases of OS X).

 

It's likely there's an issue with encoding in those workflows, particularly if they're getting data from somewhere else (a file, an HTTP request, etc.). I made some hacky attempts to fix the Recent Downloads workflow (check the last few posts in the thread), but I still need to do some more testing there.

[austinjreilly]

Is your ruby install the default install with the OS or something custom built or installed from something like home-brew? The reason I ask is, I'm not a big ruby guy so I don't have any kind of special installation of it and the recent downloads workflow and a recent documents workflow I have both seem to work fine in Mavericks.

 

I'm pretty sure that /usr/bin/ruby is the OS X copy. If I had installed ruby via home-brew it would be in /usr/local/Cellar/. Please correct me if I'm mistaken.

 

Clinton is right to point out that this is an extension/ruby issue. Thanks for that, Clinton.

 

If I have any feedback for the Recent Downloads workflow, I'll put it in the other thread (http://www.alfredforum.com/topic/338-recent-downloads-with-feedback/page-3).

[jdfwarrior]

I'm pretty sure that /usr/bin/ruby is the OS X copy. If I had installed ruby via home-brew it would be in /usr/local/Cellar/. Please correct me if I'm mistaken.

 

Clinton is right to point out that this is an extension/ruby issue. Thanks for that, Clinton.

 

If I have any feedback for the Recent Downloads workflow, I'll put it in the other thread (http://www.alfredforum.com/topic/338-recent-downloads-with-feedback/page-3).

 

As mentioned above though, it shouldn't be an issue with the extension/workflow/alfred because it works perfectly fine for me in a fresh mavericks install. Both the Recent Downloads and Recent Documents (created by Clinton) are ruby based and work as expected.

[austinjreilly]

As mentioned above though, it shouldn't be an issue with the extension/workflow/alfred because it works perfectly fine for me in a fresh mavericks install. Both the Recent Downloads and Recent Documents (created by Clinton) are ruby based and work as expected.

 

In that case, would you care to speculate as to why certain workflows would stop working after upgrading? Clinton's Ruby solution seems to make sense to me, but I would be happy to consider other possibilities.

[jdfwarrior]

In that case, would you care to speculate as to why certain workflows would stop working after upgrading? Clinton's Ruby solution seems to make sense to me, but I would be happy to consider other possibilities.

 

Clinton's answer does indeed sounds nice and plausible but the fact that they work flawlessly on a fresh Mavericks install somewhat eliminates that. If it were a difference in the ruby versions between Mavericks and previous versions of OSX, it would seem that I would still be experiencing the same issue. I can't say with certainty what the issue is but would lean toward something getting changed, moved, etc during the Mavericks upgrade process. I'm just making the point that Alfred and/or the workflow isn't the actual issue here. Could it be the code IN the workflow? Maybe, but I'm doubtful.

 

[Admin note: Renamed "Mavericks" thread to "Ruby workflows in Mavericks" as the discussion topic has become more specific]

[neilmiddleton]

So, I suspect there is a couple of things at play here.

 

I was able to modify my workflow so that it worked successfully via the command line calling the script directly.  To do this I had to re-bundle so that the path for Ruby 2.0.0 was correct.

 

However, it still fails as described via Alfred, again putting nothing in the logs.

[neilmiddleton]

I'm becoming less convinced that this is a Ruby problem at all, but an Alfred / Mavericks problem.  

 

If I run my Ruby script directly using the same path/command as Alfred it works fine.  However, from Alfred it immediately fails silently as described earlier in this thread.

 

If I go one step further and modify the workflow itself, for instance flip it to try and run the Ruby script with Python, I see exactly the same behaviour, and still nothing in the logs.

 

It seems that Alfred is immediately failing the execution of the script and not logging anything to the Alfred-Workflow.log.

[Andrew]

I'm becoming less convinced that this is a Ruby problem at all, but an Alfred / Mavericks problem.  

 

If I run my Ruby script directly using the same path/command as Alfred it works fine.  However, from Alfred it immediately fails silently as described earlier in this thread.

 

If I go one step further and modify the workflow itself, for instance flip it to try and run the Ruby script with Python, I see exactly the same behaviour, and still nothing in the logs.

 

It seems that Alfred is immediately failing the execution of the script and not logging anything to the Alfred-Workflow.log.

 

I have a ticket to look into this a bit more deeply… but it's a bit strange that the reports of this aren't widespread, and that David is seeing the workflows run fine in their current state.

[neilmiddleton]

Yeah, that's odd, but at the moment it doesn't look like Alfred is even hitting the workflow script.  I wonder if usage of Ruby workflows is just low.

[austinjreilly]

Is it possible that this is a permissions issue? I finally got around to doing a permissions repair (which I usually do once every major OS update) and I noticed that the permissions for the OS version of Ruby were "Repaired". 

[jdfwarrior]

Is it possible that this is a permissions issue? I finally got around to doing a permissions repair (which I usually do once every major OS update) and I noticed that the permissions for the OS version of Ruby were "Repaired". 

 

How about trying an extremely basic script that just.. I don't know, echoes something back from ruby and shows a notification? That would allow you to verify that may help narrow things down a little. Also, check austin's suggestion and repair permissions. As mentioned before, I've seen multiple people talking about all kinds of oddities from their Mavericks upgrade. Who knows what all Apple did

[Andrew]

Is it possible that this is a permissions issue? I finally got around to doing a permissions repair (which I usually do once every major OS update) and I noticed that the permissions for the OS version of Ruby were "Repaired". 

 

I think that this sounds like a very good idea!