-
Notifications
You must be signed in to change notification settings - Fork 986
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
Data delivery issues #16873
Comments
Example with a contact request from e2e tests:
Actual result: |
Another example of CR not delivered. Currently it is causing the whole e2e group of tests to fail. CR_receiver_logcut.log Here is a video from saucelab Device 1 sends CR to Device 2 https://app.eu-central-1.saucelabs.com/tests/70c14d8c67c94b509409174a9d107f85?auth=5b7b8a386f5c29002365977c4ac0bb1f#52 Device 2 does not receive CR https://app.eu-central-1.saucelabs.com/tests/b71969cb18bd4787866cac6a1068d9b5?auth=ec1bb0869ff82b5b6049c79f280834b0#55 waiting time: 60 sec |
@pavloburykh do you have the geth.log for both sender/receiver please? |
hi @cammellos! Unfortunately all we have are the above attached logcat files. |
One more issue with data delivery which was found and investigated during PR testing - more context is here: #17091 (comment) |
Example of missing a message in a community channel after user unblock, which causes e2e test fail in about 10% runs:
SauceLabs session of user A: https://app.eu-central-1.saucelabs.com/tests/b263360bc45f418c9a108c656b5bb208?auth=1443824e95e223f47a2eac9dc6161cfc#553 |
In this scenario User A does not receive a message, and in their geth.log there's lots of
This happens when peer count dropped to zero and full resubscribe is in order. Also at the same time lots of
Message from UserB sent on
Also there are lots of re-subscriptions to the same peer:
|
Bug Report
There are three most obvious data delivery issues that don't have exact steps to reproduce but that we encounter quite often.
As discussed, describing them here for further investigation (cc @siphiuel )
Logs and other details will be added as any of these are encountered.
1. Data loss on a synced device
Most often this can be observed in group chats (as described in #16786 with more details) or in Status Community.
2. After background on iOS
Sometimes we face the situation when data (messages/contact or membership requests/etc) stops being sent/received on iOS device after some time in background.
To start receiving/sending data again, you need to reopen the app and/or relogin.
3. Significant delivery delays in the late afternoon (for European users)
Sometimes the delivery of messages/requests becomes especially long in the afternoon compared to the morning for time zones such as UTC+2, UTC +3.
4. Some particular kind of data stops being delivered for no apparent reason
For example, you still can receive messages and contact requests, but stop getting approved to join the community.
Or you can receive messages but can't receive contact requests.
Sometimes relogin works, sometimes it doesn't.
Note
Some of these scenarios may actually be the same thing. Unfortunately, it is not always possible to distinguish between a delay in delivery and a complete loss of data.
The text was updated successfully, but these errors were encountered: