-
Notifications
You must be signed in to change notification settings - Fork 984
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
Use new login endpoint #16013
Use new login endpoint #16013
Conversation
Jenkins BuildsClick to see older builds (42)
|
1c46a4c
to
aebaa7d
Compare
aebaa7d
to
3497fc1
Compare
61% of end-end tests have passed
Failed tests (13)Click to expandClass TestActivityCenterContactRequestMultipleDevicePR:
Class TestOneToOneChatMultipleSharedDevicesNewUi:
Class TestActivityMultipleDevicePR:
Class TestCommunityMultipleDeviceMerged:
Class TestGroupChatMultipleDeviceMergedNewUI:
Passed tests (20)Click to expandClass TestActivityCenterContactRequestMultipleDevicePR:
Class TestCommunityOneDeviceMerged:
Class TestOneToOneChatMultipleSharedDevicesNewUi:
Class TestActivityMultipleDevicePR:
Class TestCommunityMultipleDeviceMerged:
Class TestGroupChatMultipleDeviceMergedNewUI:
|
@cammellos hello! Thank you for the PR. Could you please rebase the PR? Sorry for pinging you, I could do it myself but there are conflicts that need to be resolved during rebasing. |
546236d
to
ea3b8fe
Compare
@pavloburykh thanks for the ping, rebased! |
82% of end-end tests have passed
Failed tests (6)Click to expandClass TestGroupChatMultipleDeviceMergedNewUI:
Class TestCommunityMultipleDeviceMerged:
Class TestOneToOneChatMultipleSharedDevicesNewUi:
Passed tests (27)Click to expandClass TestGroupChatMultipleDeviceMergedNewUI:
Class TestActivityCenterContactRequestMultipleDevicePR:
Class TestOneToOneChatMultipleSharedDevicesNewUi:
Class TestCommunityMultipleDeviceMerged:
Class TestCommunityOneDeviceMerged:
Class TestActivityMultipleDevicePR:
|
@cammellos PR overall PR looks LGTM. Though while testing I have faced messages delivery issues. Could you please check the logs and see if it could be PR related? Yet I was not able to reproduce problem on nightly build. On video below you can observe that messages sent from User A to User B (and vica-verse) are not delivered until app re-login. messages_not_delivered1.mp4If the issue is not PR related - then PR is ready for merge. Meanwhile I will try to reproduce issue on nightly. |
ea3b8fe
to
45a4a2d
Compare
@cammellos I think this is not a PR issues. We are facing delivery issues in nightly in our e2e tests. So it should be logged and addressed separately. I believe this PR can be merged if you have not found anything suspicious in attached logs that might show relation of delivery issues to current PR changes. |
status-im/status-go@47711c4...47711c4 This commit changes the login endpoint so that it uses LoginAccount. The main difference is that is consistent with the two others we use for creation/importing, and this will override the networks and use the secrets provided.
45a4a2d
to
66cd3ed
Compare
Use new login endpoint
status-im/status-go@7586452...3559636
This commit changes the login endpoint so that it uses LoginAccount.
The main difference is that is consistent with the two others we use for
creation/importing, and this will override the networks and use the
secrets provided.
This should allow us in theory to remove a fair amount of code (anything to do with node config, but that would be a separate PR)