-
Notifications
You must be signed in to change notification settings - Fork 987
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix #15899 : failed to reset password #15914
Conversation
Jenkins BuildsClick to see older builds (4)
|
88% of end-end tests have passed
Failed tests (4)Click to expandClass TestOneToOneChatMultipleSharedDevicesNewUi:
Class TestGroupChatMultipleDeviceMergedNewUI:
Class TestCommunityMultipleDeviceMerged:
Passed tests (28)Click to expandClass TestOneToOneChatMultipleSharedDevicesNewUi:
Class TestCommunityOneDeviceMerged:
Class TestGroupChatMultipleDeviceMergedNewUI:
Class TestCommunityMultipleDeviceMerged:
Class TestActivityCenterContactRequestMultipleDevicePR:
Class TestActivityMultipleDevicePR:
|
@qfrank I am blocked from testing this for now until we will find out and fix status-go issue with slow login. Andrea is looking on that. |
Failed to reload keystore contents" err="open /data/user/0/im.status.ethereum.pr/no_backup/keystore/0x6f56979602c2f951397ec87170664cc870e39774338b290653af9dfa98343233: no such file or directory" I had this error on this build by
|
interesting, let me check |
@qfrank it's the geth keystore, not sure is related to your pr though |
it's just hanging here, what i did:
|
I have faced such issue in this PR. |
this issue should also exist on branch |
right. I have just re-checked and can confirm. Reproduced both login issue and stuck Generation keys screen. But regarding login case, in develop after waiting for some time I am facing "cannot retrieve valid key for given multiaccount.." error and not redirected into account. I believe this particular error has been fixed by current PR as I have not faced it here. So, slow login and stucked Generation keys screen issues are not related to this PR. We just used builds from current PR to reproduce those issues. |
found the cause that causing stuck |
after resolving the stuck issue , i'm unable to reproduce this issue 🙂 @cammellos |
56facd4
to
e9775a5
Compare
can you retry again after last rebase , the stuck issue should not exist anymore, also pls re-check issue @cammellos reported (i'm unable to reproduce), thank you @pavloburykh |
thanx, I will re-check today. |
@qfrank thank you for the fix. PR is tested and ready to be merged. |
e9775a5
to
150ac01
Compare
fixes #15899
Platforms
status: ready