proposed fix at
http://github.com/alikins/func-alikins-devel/tree/func_transmit_errors
This changes the func-transmit api a bit (well, it implements handling
something it
didnt before anyway) so wanted to float this by folks using
func-transmit first.
Is this something the language bindings could make use of?
Adrian
I'm trying to fix a bug I'm seeing with func-transmit in the case of
attempting
to talk to non existing minions.
Currently, if you do this, the Overlord() api class will raise a
Func_Client_Exception.
At the moment, func-transmit doesn't know how to handle this and just
throws
a traceback.
Ideally, we would have a way to handle this in a way that would work for
JSON or yaml or other methods, but since at least JSON doesnt have a
standard Error/Exception type, I'm not sure how to do this.
Some options:
1) Catch it and return an object that could be detected as an error.
Maybe a dictionary with "type":"error" or something?
2) exit non-zero. This means apps using func-transmit would need
to check the exit status of course
3) both of the above
Any other ideas?
Adrian
_______________________________________________
Func-list mailing list
Func-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/func-list
_______________________________________________
Func-list mailing list
Func-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/func-list
