-
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
refactor: extract storenode cycle to go-waku #21494
base: develop
Are you sure you want to change the base?
Conversation
Jenkins BuildsClick to see older builds (4)
|
ec008ca
to
598d5f2
Compare
75% of end-end tests have passed
Failed tests (1)Click to expandClass TestCommunityOneDeviceMerged:
Expected to fail tests (1)Click to expandClass TestCommunityMultipleDeviceMerged:
Passed tests (6)Click to expandClass TestOneToOneChatMultipleSharedDevicesNewUi:
Class TestCommunityOneDeviceMerged:
Class TestWalletOneDevice:
Class TestWalletMultipleDevice:
|
60% of end-end tests have passed
Failed tests (2)Click to expandClass TestCommunityOneDeviceMerged:
Expected to fail tests (20)Click to expandClass TestActivityMultipleDevicePRTwo:
Class TestCommunityMultipleDeviceMergedTwo:
Class TestActivityMultipleDevicePR:
Class TestDeepLinksOneDevice:
Class TestCommunityMultipleDeviceMerged:
Passed tests (33)Click to expandClass TestGroupChatMultipleDeviceMergedNewUI:
Class TestFallbackMultipleDevice:
Class TestWalletOneDevice:
Class TestCommunityOneDeviceMerged:
Class TestDeepLinksOneDevice:
Class TestOneToOneChatMultipleSharedDevicesNewUi:
Class TestOneToOneChatMultipleSharedDevicesNewUiTwo:
Class TestWalletMultipleDevice:
Class TestActivityCenterContactRequestMultipleDevicePR:
|
@richard-ramos thanks for the PR. Please take a look at the issue. ISSUE 1 Backed up data is not restoredSteps:
Expected result: data has been restored Actual result: data has not been restored |
ISSUE 2 Curated communities are not fetched in Discovery sectionSteps:
Expected result: curated communities are fetched Actual result: curated communities not fetched Status-debug-logs - 2024-11-07T172237.909.zip telegram-cloud-document-2-5289623460522255460.mp4 |
ISSUE 3 Communities are not fetchedSteps:
Expected result: community is fetched Actual result: community not fetched Status-debug-logs - 2024-11-07T182443.341.zip telegram-cloud-document-2-5289623460522255712.mp4 |
598d5f2
to
f49383d
Compare
@pavloburykh, I just pushed a new commit with fixes for the observed issues |
44% of end-end tests have passed
Failed tests (11)Click to expandClass TestFallbackMultipleDevice:
Class TestWalletMultipleDevice:
Class TestOneToOneChatMultipleSharedDevicesNewUi:
Class TestGroupChatMultipleDeviceMergedNewUI:
Class TestWalletOneDevice:
Class TestCommunityOneDeviceMerged:
Class TestDeepLinksOneDevice:
Class TestActivityCenterContactRequestMultipleDevicePR:
Expected to fail tests (20)Click to expandClass TestActivityMultipleDevicePRTwo:
Class TestActivityMultipleDevicePR:
Class TestDeepLinksOneDevice:
Class TestCommunityMultipleDeviceMerged:
Class TestCommunityMultipleDeviceMergedTwo:
Passed tests (24)Click to expandClass TestOneToOneChatMultipleSharedDevicesNewUiTwo:
Class TestFallbackMultipleDevice:
Class TestOneToOneChatMultipleSharedDevicesNewUi:
Class TestGroupChatMultipleDeviceMergedNewUI:
Class TestCommunityOneDeviceMerged:
Class TestActivityCenterContactRequestMultipleDevicePR:
|
Requires:
This PR is a refactor that extracts the storenode cycle logic from status-go to go-waku, since this logic shouldn't be part of the application layer but from the waku layer instead.
The areas affected by this change are the message history retrieval as well as automatically choosing a storenode
cc: @pavloburykh @churik