growlnotify --wait seems to time out after about 10 seconds

[TJ Luoma]

The man page for growlnotify describes '--wait' as

>     -w, --wait  Causes growlnotify to wait until the notification is dismissed (either by clicking or timing out) before it returns.

I assumed that meant that if used with

> --sticky        Causes the notification to stick around until clicked.

then I could use something like "growlnotify --wait --sticky -m test message" in shell scripts as a simple method of waiting for user action before continuing.

Unfortunately, it seems to time out after about 10 seconds.

The message is still displayed, but the script continues:

For example:

$ date;growlnotify --wait --sticky -m test message;date

Tue Mar  6 10:43:07 EST 2012

2012-03-06 10:43:18.352 growlnotify[35574:707] Got disconnected: Error Domain=GCDAsyncSocketErrorDomain Code=4 "Read operation timed out" UserInfo=0x7fc431c0ad20 {NSLocalizedDescription=Read operation timed out}

Tue Mar  6 10:43:18 EST 2012

I re-ran it several times and saw a similar error each time:

2012-03-06 10:43:38.438 growlnotify[35577:707] Got disconnected: Error Domain=GCDAsyncSocketErrorDomain Code=4 "Read operation timed out" UserInfo=0x7ff7abc197f0 {NSLocalizedDescription=Read operation timed out}

2012-03-06 10:43:51.639 growlnotify[35580:707] Got disconnected: Error Domain=GCDAsyncSocketErrorDomain Code=4 "Read operation timed out" UserInfo=0x102119fc0 {NSLocalizedDescription=Read operation timed out}

1. Is --wait plus --sticky supposed to be able to do what I am trying to do?

2. Is this just a bug in growl/growlnotify or is there another way to accomplish it?

Thanks

TjL

[Daniel Siemer]

GrowlNotify 1.3 has an internal timeout of 10 seconds with --wait. I
believe this has been changed in what will be GrowlNotify 1.4 to allow
--wait --sticky to work as expected, and not timeout. I do not have
information on when growlnotify 1.4 will be available, probably about
the same time Growl.app 1.4 is available, as there is at least one
GrowlNotify feature in 1.4 that will require Growl.app 1.4 to work
right (Click feedback via opening a URL)

[TJ Luoma]

FYI - this still does not work with Growl 1.4 

% date ; /usr/local/bin/growlnotify -s -w -m "Test" Title ; date

Fri Jun 15 02:07:40 EDT 2012

2012-06-15 02:07:51.262 growlnotify[31681:707] Got disconnected: Error Domain=GCDAsyncSocketErrorDomain Code=4 "Read operation timed out" UserInfo=0x7fac0341a680 {NSLocalizedDescription=Read operation timed out}

Fri Jun 15 02:07:51 EDT 2012

as you can see from the date stamps it gives up after about 10 seconds, same as before.

This is with growlnotify (CLI tool) version 1.3 as that still appears to be the latest version available.

[Daniel Siemer]

I said it would require GrowlNotify 1.4, which has not been built and
shipped yet, and Im not sure its been tested lately, so we need to do
some testing on it still. We have been very busy with getting ready
for, and being at WWDC.