-
Notifications
You must be signed in to change notification settings - Fork 262
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
Retrying to send fail messages (enh) #7180
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very nice work! :) Design feedback:
- The "Retry" icon button on the right might be better as just a text-only tertiary button with text "Retry".
- The loading spinner doesn’t seem to be the standard one from the Vue components?
- For long subject or error subline, the text needs to be ellipsized a bit earlier to not overlap with the icon
f463551
to
b2b90c9
Compare
Signed-off-by: Mikhail Sazanov <m@sazanof.ru>
@jancborchardt done. Please take a look. |
Signed-off-by: Mikhail Sazanov <m@sazanof.ru>
Signed-off-by: Mikhail Sazanov <m@sazanof.ru>
Signed-off-by: Mikhail Sazanov <m@sazanof.ru>
Signed-off-by: Mikhail Sazanov <m@sazanof.ru>
Signed-off-by: Mikhail Sazanov <m@sazanof.ru>
Signed-off-by: Mikhail Sazanov <m@sazanof.ru>
Signed-off-by: Mikhail Sazanov <m@sazanof.ru>
c6e4520
to
2e97866
Compare
} | ||
}, | ||
}, | ||
created() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this means with every page load we retry sending those messages. I'm not sure if this is how we want it.
shouldn't each message have some kind of retry counter so it's only retried a few times? with the first iteration of the outbox feature we continuously retried sending failed messages. but that caused more trouble than expected. so this was deliberately disabled via #6602.
also see #6540. there are some side effects with blindly resending ever pending message in the outbox.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ChristophWurst thank you! As you said, we can retry X-times to send messages only if message failed when it sent first time. In other cases, do not retry sending. What di you think?
In addition, if automatic sending is still not needed, can I leave the updated functionality for resending messages manually =)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's try with a counter 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello everyone!
Is it better to turn on the counter when the page loads, or to attract something like a permanent storage (localstorage, database)? Although probably the latter has more chances for bugs?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd say the counter should be in the backend
also friendly ping here |
#9364 and related handle this on the backend. The frontend trigger is obsolete |
Hello everyone!
I will be glad if you consider this improvement and give your comments. =)
Maybe it refers to #6401
Basically there are 2.5 improvements:
And here are the screenshots:
Perhaps another processing logic is needed here, so I would like to discuss this.
Thanks!