Jason Tackaberry wrote:
>> On a side note: this check-in broke beacon and I guess a lot of other
>> parts using kaa.rpc.
>
> I will take a look at beacon.  The kaa.rpc API hasn't changed, nor have
> the semantics.  So it's just a matter of fixing the bugs in kaa.rpc.

The bug seems simple. 

| try:
|     # this should not be possible
|     kaa.beacon.connect()
|     print 'beacon-daemon is already running.'
|     sys.exit(1)
| except kaa.beacon.ConnectError:
|     pass

I do not get a ConnectError anymore.
in beacon:

|  try:
|      server = kaa.rpc.Client('beacon')
|  except kaa.rpc.ConnectError, e:
|      raise ConnectError(e)

So the bug seems to be that an rpc client does not raise a
ConnectError anymore.


Dischi

-- 
And now for something completely different.

Attachment: pgpfpg7YqSeMR.pgp
Description: PGP signature

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Freevo-devel mailing list
Freevo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freevo-devel

Reply via email to