-
Notifications
You must be signed in to change notification settings - Fork 24.5k
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
[IMP] mail: prevent message loss during connection issue #32422
Closed
jgi-odoo
wants to merge
1
commit into
odoo:master
from
odoo-dev:master-post-message-during-connectivity-loss-jgi
Closed
[IMP] mail: prevent message loss during connection issue #32422
jgi-odoo
wants to merge
1
commit into
odoo:master
from
odoo-dev:master-post-message-during-connectivity-loss-jgi
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
alexkuhn
reviewed
Apr 16, 2019
alexkuhn
reviewed
Apr 16, 2019
jgi-odoo
force-pushed
the
master-post-message-during-connectivity-loss-jgi
branch
from
April 16, 2019 09:31
11abe92
to
66eab5b
Compare
alexkuhn
approved these changes
Apr 16, 2019
Before the changes, when a message was posted (on Discuss or in the chat window), the composer was cleared directly as it didn't wait for the rpc response. If there was latency or a connection loss, the message disappeared from the composer but took time to appear in the content window or didn't appear at all and was lost. Now, the composer waits for the rpc response and then is cleared. Task #1957856
jgi-odoo
force-pushed
the
master-post-message-during-connectivity-loss-jgi
branch
from
April 23, 2019 12:06
66eab5b
to
05a1f82
Compare
robodoo
added
CI 🤖
Robodoo has seen passing statuses
and removed
CI 🤖
Robodoo has seen passing statuses
labels
Apr 23, 2019
@robodoo r+ |
robodoo
pushed a commit
that referenced
this pull request
Apr 24, 2019
Before the changes, when a message was posted (on Discuss or in the chat window), the composer was cleared directly as it didn't wait for the rpc response. If there was latency or a connection loss, the message disappeared from the composer but took time to appear in the content window or didn't appear at all and was lost. Now, the composer waits for the rpc response and then is cleared. Task #1957856 closes #32422 Signed-off-by: Alexandre Kühn (aku) <aku@odoo.com>
Merged, thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Before the changes, when a message was posted (on Discuss or in
the chat window), the composer was cleared directly as it didn't
wait for the rpc response. If there was latency or a connection
loss, the message disappeared from the composer but took time to
appear in the content window or didn't appear at all and was lost.
Now, the composer waits for the rpc response and then is cleared.
Task #1957856