-
Notifications
You must be signed in to change notification settings - Fork 992
Handle confirmations from mailservers #12824
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
Conversation
Jenkins BuildsClick to see older builds (12)
|
6fcd9f5
to
14bf3c5
Compare
@cammellos can we do e2e build with default |
@churik yes, I think so, I'll push a commit |
14bf3c5
to
b5e3bac
Compare
6a2675a
to
388aed6
Compare
Tested confirmations (flows New > Sent > Delivered, New (not sent), New > Sent, Sent > Delivered) on group chats + 1-1 chats (with offline resending) and on public chat (no resending) after offline 1min, 5mins, 30mins, 48h +. I noticed that 'stuck' messages in public chats couldn't be resent but I suppose it is not the part of this PR, right @cammellos ? e2e test results: here and here Devices:
|
388aed6
to
61910d2
Compare
Signed-off-by: Andrea Maria Piana <andrea.maria.piana@gmail.com>
61910d2
to
fdadee6
Compare
Makes confirmations a bit more robust.
It should fix an issue with being offline and having your messages confirmed.
On develop currently the behavior is:
Expected:
Message not confirmed
Actual:
Message is confirmed
After this change it will not mark the message as confirmed.
Testing
This PR will work just as in develop against prod & staging fleet (so it will result in the
Actual
behavior from above).The
Expected
behavior needs to be tested against the test fleet.It should though not have any issue (other than the above) when testing with prod/staging.
Develop though won't work with the test fleet, messages won't get confirmed, that's know, as it's a breaking change.
status: ready