Skip to content
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

fix: handle NoCommonProtocol error while starting conversation cherry-pick #3138

Conversation

borichellow
Copy link
Contributor

For some reason auto-cherry-pick didn't work, so i raised it by myself
cherry-pick of #3120

What's new in this PR?

Issues

When user is trying to start 1o1 conversation with user that has no common protocol with, the error is no displayed anyhow.

Causes (Optional)

Error handling in creating conversation was implemented only for NoKeypackages error.

Solutions

Add handling for all errors (specific texts for NoKeypackages and NoCommonProtocol errors and some default text for other errors.)

Attachments (Optional)

Screenshot 2024-06-24 at 12 20 43

Copy link

Copy link
Contributor

Test Results

932 tests   932 ✅  8m 55s ⏱️
124 suites    0 💤
124 files      0 ❌

Results for commit b9344f5.

@vitorhugods
Copy link
Member

I see it failed with MissingTranslation. Maybe we should disable this check in the linter. We don't want to hardcode translations in English or something like that. It's preferable to keep it empty.

@borichellow borichellow merged commit 91bb89e into release/candidate Jun 28, 2024
14 of 15 checks passed
@borichellow borichellow deleted the fix/handle-no-common-protocol-error-while-starting-conversation-cherry-pick branch June 28, 2024 07:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants