guard not working with Growl 1.3 #60

Closed
jgyllen opened this Issue Oct 5, 2011 · 14 comments

Comments

Projects
None yet
4 participants

jgyllen commented Oct 5, 2011

I just installed Growl 1.3 from the Mac App Store. When i run guard start, I get the following error:

```/Users/baron/.rvm/gems/ruby-1.9.2-p290@global/gems/rb-appscript-0.6.1/lib/_aem/findapp.rb:30:inrescue in _find_app': Application "[\"GrowlHelperApp.app\"]" not found. (FindApp::ApplicationNotFoundError) from /Users/baron/.rvm/gems/ruby-1.9.2-p290@global/gems/rb-appscript-0.6.1/lib/_aem/findapp.rb:25:in_find_app'
from /Users/baron/.rvm/gems/ruby-1.9.2-p290@global/gems/rb-appscript-0.6.1/lib/_aem/findapp.rb:55:in`rescue in by_name'
from /Users/baron/.rvm/gems/ruby-1.9.2-p290@global/gems/rb-appscript-0.6.1/lib/_aem/findapp.rb:49:in `by_name'
from /Users/baron/.rvm/gems/ruby-1.9.2-p290@global/gems/rb-appscript-0.6.1/lib/appscript.rb:855:in`by_name'
from /Users/baron/.rvm/gems/ruby-1.9.2-p290@global/gems/rb-appscript-0.6.1/lib/appscript.rb:932:in `by_name'
from /Users/baron/.rvm/gems/ruby-1.9.2-p290@global/gems/rb-appscript-0.6.1/lib/appscript.rb:994:in`app'
from /Users/baron/.rvm/gems/ruby-1.9.2-p290@my-secondlife/gems/growl_notify-0.0.1/lib/growl_notify.rb:26:in `register'
from /Users/baron/.rvm/gems/ruby-1.9.2-p290@my-secondlife/gems/growl_notify-0.0.1/lib/growl_notify.rb:16:in`config'
from /Users/baron/.rvm/gems/ruby-1.9.2-p290@my-secondlife/gems/guard-0.8.2/lib/guard/notifier.rb:177:in `require_growl'
from /Users/baron/.rvm/gems/ruby-1.9.2-p290@my-secondlife/gems/guard-0.8.2/lib/guard/notifier.rb:33:in`turn_on'
from /Users/baron/.rvm/gems/ruby-1.9.2-p290@my-secondlife/gems/guard-0.8.2/lib/guard.rb:36:in `setup'
from /Users/baron/.rvm/gems/ruby-1.9.2-p290@my-secondlife/gems/guard-0.8.2/lib/guard.rb:104:in`start'
from /Users/baron/.rvm/gems/ruby-1.9.2-p290@my-secondlife/gems/guard-0.8.2/lib/guard/cli.rb:61:in `start'
from /Users/baron/.rvm/gems/ruby-1.9.2-p290@my-secondlife/gems/thor-0.14.6/lib/thor/task.rb:22:in`run'
from /Users/baron/.rvm/gems/ruby-1.9.2-p290@my-secondlife/gems/thor-0.14.6/lib/thor/invocation.rb:118:in `invoke_task'
from /Users/baron/.rvm/gems/ruby-1.9.2-p290@my-secondlife/gems/thor-0.14.6/lib/thor.rb:263:in`dispatch'
from /Users/baron/.rvm/gems/ruby-1.9.2-p290@my-secondlife/gems/thor-0.14.6/lib/thor/base.rb:389:in `start'
from /Users/baron/.rvm/gems/ruby-1.9.2-p290@my-secondlife/gems/guard-0.8.2/bin/guard:6:in`<top (required)>'
from /Users/baron/.rvm/gems/ruby-1.9.2-p290@my-secondlife/bin/guard:19:in `load'
from /Users/baron/.rvm/gems/ruby-1.9.2-p290@my-secondlife/bin/guard:19:in`

'




Not sure if this is caused by guard-rspec or one of the dependencies. I am using the following gems: guard-rspec 0.4.5, growl 1.0.3, rb-fsevent 0.4.3.1

jgyllen commented Oct 5, 2011

Btw, when I set :notification => false in Guardfile it still complains.

Owner

thibaudgg commented Oct 5, 2011

Please try with growl_notify gem instead of growl gem, it has been updated to support Growl 1.3

jgyllen commented Oct 5, 2011

That worked. Thanks!

jgyllen closed this Oct 5, 2011

jgyllen commented Oct 5, 2011

Well, it did work when starting up Spork. It displays something like "Spork started successfully" in Growl, but then when the tests are done I get:

"The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC() to debug."

..followed by lots of low-level OS info.

I got this earlier when using Growl 1.2.2. Found a GitHub issue about it somewhere. That's why I changed to the growl gem. What to do?

Owner

thibaudgg commented Oct 6, 2011

You can do two things, and you should do both :)

  • open an issue on growl gem to have Growl 1.3 support (cc @visionmedia)
  • open an issue on growl_notify gem about this CoreFoundation error (cc @scottdavis)

This has todo with core foundation and shared memory I don't think I can do much also with the removal of the growl_notify command from growl I don't think the growl gem can work with 1.3

Sent from my iPhone

On Oct 6, 2011, at 3:10 AM, Thibaud Guillaume-Gentilreply@reply.github.com wrote:

You can do two things, and you should do both :)

  • open an issue on growl gem to have Growl 1.3 support (cc @visionmedia)
  • open an issue on growl_notify gem about this CoreFoundation error (cc @scottdavis)

Reply to this email directly or view it on GitHub:
#60 (comment)

jgyllen commented Oct 7, 2011

What are you saying @scottdavis? None of the gems could work with Growl 1.3?

Growl 1.3 removed all but the AppleScript API and the network XML API. The growl gem was using the growl_notify (not my gem) command that was an optional install with growl pre 1.3 so I don't think that the growl gem will ever work without a total rewrite

Sent from my iPhone

On Oct 6, 2011, at 8:34 PM, Jacob Gyllenstiernareply@reply.github.com wrote:

What are you saying @scottdavis? None of the gems could work with Growl 1.3?

Reply to this email directly or view it on GitHub:
#60 (comment)

jgyllen commented Oct 7, 2011

Ok, thanks for the info. I'm following about the growl gem, but what about the growl_notify gem?

Can I resolve the issue I described after closing the issue? Or does that have to do with the things they removed in 1.3?

Cheers.

So your original issue was that i hadn't upgraded the growl_notify gem to support 1.3 i have since done that. The core foundation issue with spork I can do nothing about its at a much lower level then my gem currently goes. It seems like the rb-appscript gem i use doesn't want corefoundation using shared memory.

jgyllen commented Oct 7, 2011

Ok. Thanks for the clarification!

Member

dnagir commented Oct 10, 2011

I've submitted the issue to growl_notify: scottdavis/growl_notify#6

Hope it will be fixed soon.

As I said in another bug report this is out of my control

Sent from my iPhone

On Oct 10, 2011, at 7:30 PM, Dmytrii Nagirniakreply@reply.github.com wrote:

I've submitted the issue to growl_notify: scottdavis/growl_notify#6

Hope it will be fixed soon.

Reply to this email directly or view it on GitHub:
#60 (comment)

Member

dnagir commented Oct 11, 2011

Guys,

I've copied the appscript repo from sourceforge to GitHub.

If somebody knows how to fix, please feel free to fork it.
https://github.com/dnagir/appscript

I hope I made it a little bit easier.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment