can no longer login in qubes after timeouts merge / securedrop-sdk 0.0.9

[redshiftzero]

Description

Login to external server no longer works on latest master (06df84c) after merge of #362

STR

1. Set up the dev env in Qubes on latest master
2. Run the client without passing --no-proxy

Expected behavior

I can log in to my staging server.

Actual behavior

AuthError

Comments

I have not debugged this yet, I inferred that the above was causing the problems by:

1. Reverting back to securedrop-sdk==0.0.8
2. Reverting back to bad39fa

It's unclear yet if the fix involves this repo or the corresponding change made in the SDK: freedomofpress/securedrop-sdk#80

I discovered this during test of my fix to #363 (will put a draft PR until the underlying issues here are resolved), which is another Qubes only issue. I'm going to file a PR to update our merge policies so that we are testing and catching these issues in Qubes prior to merge.

[sssoleileraaa]

This is a good reminder that we should be testing client changes in Qubes. Will remember to add that to PR test plans until it becomes the norm.

I got my qubes machine running and can help debug the timeouts issue.

[kushaldas]

I can login to my environment using Qubes Proxy + securedrop sdk 0.0.9 on the latest master of the client repository.

[redshiftzero]

OK thanks @kushaldas - this must have been a local error... will debug, closing this for now