© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
Hmmm... I just tried to reproduce, but cannot. I modified the demo scope-A .ini file to point at a script:
ScopeRunner = /tmp/tryit
I've tried with the script immediately exiting with status 1, with status 0, and with the script hanging (by sleeping). Trace in the script verifies that the registry calls it correctly.
If the script exits, the client, receives a MiddlewareException from search() saying that the scope failed to start correctly after four seconds.
If the script hangs, the client gets the same exception from search, but after 8 seconds (because we do the locate() behind the scenes).
All this is as expected. Pawel, what did you do to make the demo client hang?
At any rate, I don't think there is any obvious problem with scopes-api. The behavior is as expected. Maybe the shell or the client you used do not handle the exception from search() correctly? Note that it is not possible to trigger the finished() callback if the scope never gets off the ground in the first place...