Notifying to Growl for Linux fails about gntp HOT 3 CLOSED

Can you run it with logging to see what message is returned from Growl for Linux ?

import logging
logging.basicConfig(level=logging.DEBUG)

from gntp.

On 03/03/2013 03:10 PM, Paul Traylor wrote:

Can you run it with logging to see what message is returned from Growl for Linux ?

import logging
logging.basicConfig(level=logging.DEBUG)

---

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

Hi, I did that. A extract of the log is attached. It's rather confusing...

You'll see there is no answer from the Growl for Linux application. In
that application appears a log line also, with the right title but
"(NULL)" text.

I have 3 threads simultaneously sending growl notifications with your
library each time an event is fired. Two of the send notifications to
Windows boxes (Growl for Windows) and never fail. The third one is a
Linux box that has the problems I reported.

When an event is fired I first call register() is fired and then notify().

Once I enabled the logging the three threads started to log debug
informartion to a log file (one file for each thread).

Amusingly the 3 log files are identical: every notification sent to any
of the remote boxes is logged in all the log files (but each
notification is sent only once, by the corresponding thread!). Also, the
logs corresponding to the same events appear somewhat intermixed as if
the threads tried to write simultaneously to the log files.

Finally, at some point each time before calling register() and notify()
I started to append a separator to the log (the '--- --- ---' you'll see
in the attachment). Once I did that I had to wait much longer for the
problem to appear (two o three days instead of two or three hours). That
suggests some kind of race condition, may be?

Thanks,
MRC

THREADS SRL
[email protected]
www.threads-srl.com.ar

from gntp.

I don't believe the log got attached to the github issue. You can try pasting it in a gist. https://gist.github.com/

from gntp.