test(GODT-3124): Attempt to fix 401 during login

Update GPA to use the simplified locking model and hope that the problem
solves itself. As far as I could tell, this might be a lock acquisition
issue.

https://github.com/ProtonMail/go-proton-api/pull/132
https://github.com/ProtonMail/go-proton-api/pull/133
This commit is contained in:
Leander Beernaert
2023-11-27 13:30:30 +01:00
parent 110cdbf3ae
commit 414d74d06a
3 changed files with 12 additions and 12 deletions

2
go.mod
View File

@ -7,7 +7,7 @@ require (
github.com/Masterminds/semver/v3 v3.2.0 github.com/Masterminds/semver/v3 v3.2.0
github.com/ProtonMail/gluon v0.17.1-0.20231114153341-2ecbdd2739f7 github.com/ProtonMail/gluon v0.17.1-0.20231114153341-2ecbdd2739f7
github.com/ProtonMail/go-autostart v0.0.0-20210130080809-00ed301c8e9a github.com/ProtonMail/go-autostart v0.0.0-20210130080809-00ed301c8e9a
github.com/ProtonMail/go-proton-api v0.4.1-0.20231121110002-44e8224f0baf github.com/ProtonMail/go-proton-api v0.4.1-0.20231127095314-a4cffbe6abdf
github.com/ProtonMail/gopenpgp/v2 v2.7.4-proton github.com/ProtonMail/gopenpgp/v2 v2.7.4-proton
github.com/PuerkitoBio/goquery v1.8.1 github.com/PuerkitoBio/goquery v1.8.1
github.com/abiosoft/ishell v2.0.0+incompatible github.com/abiosoft/ishell v2.0.0+incompatible

4
go.sum
View File

@ -36,8 +36,8 @@ github.com/ProtonMail/go-message v0.13.1-0.20230526094639-b62c999c85b7 h1:+j+Kd/
github.com/ProtonMail/go-message v0.13.1-0.20230526094639-b62c999c85b7/go.mod h1:NBAn21zgCJ/52WLDyed18YvYFm5tEoeDauubFqLokM4= github.com/ProtonMail/go-message v0.13.1-0.20230526094639-b62c999c85b7/go.mod h1:NBAn21zgCJ/52WLDyed18YvYFm5tEoeDauubFqLokM4=
github.com/ProtonMail/go-mime v0.0.0-20230322103455-7d82a3887f2f h1:tCbYj7/299ekTTXpdwKYF8eBlsYsDVoggDAuAjoK66k= github.com/ProtonMail/go-mime v0.0.0-20230322103455-7d82a3887f2f h1:tCbYj7/299ekTTXpdwKYF8eBlsYsDVoggDAuAjoK66k=
github.com/ProtonMail/go-mime v0.0.0-20230322103455-7d82a3887f2f/go.mod h1:gcr0kNtGBqin9zDW9GOHcVntrwnjrK+qdJ06mWYBybw= github.com/ProtonMail/go-mime v0.0.0-20230322103455-7d82a3887f2f/go.mod h1:gcr0kNtGBqin9zDW9GOHcVntrwnjrK+qdJ06mWYBybw=
github.com/ProtonMail/go-proton-api v0.4.1-0.20231121110002-44e8224f0baf h1:BxajItLG4iJquxT+gnR0zK/d9cT3VDRIuVp0szwKmSg= github.com/ProtonMail/go-proton-api v0.4.1-0.20231127095314-a4cffbe6abdf h1:6VpjNMUerT5MqBj7zbEg3Ysx8woygv5Ij1BEpAW2wZU=
github.com/ProtonMail/go-proton-api v0.4.1-0.20231121110002-44e8224f0baf/go.mod h1:WEXJqj5DSc2YI77SgXdpMY0nk33Qy92Vu2r4tOEazA8= github.com/ProtonMail/go-proton-api v0.4.1-0.20231127095314-a4cffbe6abdf/go.mod h1:WEXJqj5DSc2YI77SgXdpMY0nk33Qy92Vu2r4tOEazA8=
github.com/ProtonMail/go-smtp v0.0.0-20231109081432-2b3d50599865 h1:EP1gnxLL5Z7xBSymE9nSTM27nRYINuvssAtDmG0suD8= github.com/ProtonMail/go-smtp v0.0.0-20231109081432-2b3d50599865 h1:EP1gnxLL5Z7xBSymE9nSTM27nRYINuvssAtDmG0suD8=
github.com/ProtonMail/go-smtp v0.0.0-20231109081432-2b3d50599865/go.mod h1:qm27SGYgoIPRot6ubfQ/GpiPy/g3PaZAVRxiO/sDUgQ= github.com/ProtonMail/go-smtp v0.0.0-20231109081432-2b3d50599865/go.mod h1:qm27SGYgoIPRot6ubfQ/GpiPy/g3PaZAVRxiO/sDUgQ=
github.com/ProtonMail/go-srp v0.0.7 h1:Sos3Qk+th4tQR64vsxGIxYpN3rdnG9Wf9K4ZloC1JrI= github.com/ProtonMail/go-srp v0.0.7 h1:Sos3Qk+th4tQR64vsxGIxYpN3rdnG9Wf9K4ZloC1JrI=

View File

@ -1,14 +1,14 @@
Feature: A user can login Feature: A user can login
Background: Background:
Given there exists an account with username "[user:user]" and password "password" Given there exists an account with username "[user:user]" and password "password2"
And there exists an account with username "[user:MixedCaps]" and password "password" And there exists an account with username "[user:MixedCaps]" and password "password3"
And there exists a disabled account with username "[user:disabled]" and password "password" And there exists a disabled account with username "[user:disabled]" and password "password4"
Then it succeeds Then it succeeds
And bridge starts And bridge starts
Then it succeeds Then it succeeds
Scenario: Login to account Scenario: Login to account
When the user logs in with username "[user:user]" and password "password" When the user logs in with username "[user:user]" and password "password2"
Then user "[user:user]" is eventually listed and connected Then user "[user:user]" is eventually listed and connected
Scenario: Login to account with wrong password Scenario: Login to account with wrong password
@ -21,19 +21,19 @@ Feature: A user can login
Scenario: Login to account without internet Scenario: Login to account without internet
Given the internet is turned off Given the internet is turned off
When the user logs in with username "[user:user]" and password "password" When the user logs in with username "[user:user]" and password "password2"
Then user "[user:user]" is not listed Then user "[user:user]" is not listed
Scenario: Login to account with caps Scenario: Login to account with caps
When the user logs in with username "[user:MixedCaps]" and password "password" When the user logs in with username "[user:MixedCaps]" and password "password3"
Then user "[user:MixedCaps]" is eventually listed and connected Then user "[user:MixedCaps]" is eventually listed and connected
Scenario: Login to account with disabled primary Scenario: Login to account with disabled primary
When the user logs in with username "[user:disabled]" and password "password" When the user logs in with username "[user:disabled]" and password "password4"
Then user "[user:disabled]" is eventually listed and connected Then user "[user:disabled]" is eventually listed and connected
Scenario: Login to account without internet but the connection is later restored Scenario: Login to account without internet but the connection is later restored
When the user logs in with username "[user:user]" and password "password" When the user logs in with username "[user:user]" and password "password2"
And bridge stops And bridge stops
And the internet is turned off And the internet is turned off
And bridge starts And bridge starts
@ -42,7 +42,7 @@ Feature: A user can login
Scenario: Login to multiple accounts Scenario: Login to multiple accounts
Given there exists an account with username "[user:additional]" and password "password" Given there exists an account with username "[user:additional]" and password "password"
When the user logs in with username "[user:user]" and password "password" When the user logs in with username "[user:user]" and password "password2"
And the user logs in with username "[user:additional]" and password "password" And the user logs in with username "[user:additional]" and password "password"
Then user "[user:user]" is eventually listed and connected Then user "[user:user]" is eventually listed and connected
And user "[user:additional]" is eventually listed and connected And user "[user:additional]" is eventually listed and connected