On Tue, Dec 12, 2017 at 7:37 PM, Michael McLean <mikem(a)redhat.com> wrote:
Note that an authenticated koji session will probably not play nice with
async use because of the callnum data.
Thanks, I see the callnum code in Koji now. What is the purpose of the
callnum? Is it a security feature, or just a way to maintain write
I've never used twisted. I presume its xmlrpc lib handles the nil
(otherwise you would almost certainly have seen lots of errors). I wonder if
it can handle an i8 tag, which kojihub will now emit for large integers in
Koji's faults can have many different fault codes, though yes 1000 is the
most likely. The full list in near the beginning of koji/__init__.py.
Thanks Mike for all these pointers. I checked Twisted and it uses
xmlrpclib.loads() to parse the responses. I tested <nil/> and it
translates fine to None, and the Koji git log indicates Python's
xmlrpclib will read <i8> too. I can't find a live Koji instance where
we've overflowed the 32-bit int yet to verify, though!