chore_: bump status-go with message hash query for outgoing messages #20387
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
For status-go: status-im/status-go#5217
For outgoing messages, only mark it as it sent after successfully found in store node, the messages that are sent 5s ago and not found in store node will be marked as expired and resend.
For DM, since ack marks the outgoing message as delivered, the delivered messages will skip the above query, but will still update the
sent
status inraw_message
table to 1.For UX changes, after input a message and click return, the message will be not marked as sent (1 tick) in status-mobile immediately, instead it takes 5s to 10s to do so for un-acked messages.
Please help verify the changes @churik
cc @cammellos
Important changes:
Find outgoing messages which were sent 5s ago, query the store node with the hashes of the messages
message found will trigger EventEnvelopeSent, messages missed will trigger EventEnvelopeExpired
Review notes
Testing notes
Platforms
Areas that maybe impacted
Functional
Non-functional
Steps to test
Before and after screenshots comparison
status: ready