I figured out my problem. I need to refresh the api after I post to get a
valid session.
# Bad way
rbt_api = rbclient.get_root()
post.Post().run_from_argv(args)
# Enter username/password
rr = rbt_api.get_review_request(...)
That didn't work. This does
# Works
post.Post().run_from_argv(args)
#
Thanks Barret,
I'm very confused about the cookie file behavior. I tried to simplify it
as much as possible and found this:
$ rbt post 814
will write a new cookie file with a session id, but calling rbt from a
python script in any of these ways:
subprocess.call("rbt post 814", shel=True)
s
Hey Steve,
The cookie file is written inside of the ReviewBoardServer class (in
rbtools.api.request) when it is instantiated.
Regards,
Barret Rennie
> On Jun 2, 2015, at 11:29 AM, Steve wrote:
>
> I have a wrapper to rbt that calls directly into Post.run_from_argv(). I'm
> seeing different b
I have a wrapper to rbt that calls directly into Post.run_from_argv(). I'm
seeing different behavior regarding the saving of credentials in the
.rbtools-cookies file and am hoping someone can tell me where to look in
the code to understand this. I've been stepping through the debugger, but
ge