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: Migration message not shown in 1:1 conversations (WPB-11194) #3042

Merged
merged 2 commits into from
Sep 27, 2024

Conversation

ohassine
Copy link
Member

@ohassine ohassine commented Sep 26, 2024

BugWPB-11194 [Android] Migration message not shown in 1:1 conversations


PR Submission Checklist for internal contributors

  • The PR Title

    • conforms to the style of semantic commits messages¹ supported in Wire's Github Workflow²
    • contains a reference JIRA issue number like SQPIT-764
    • answers the question: If merged, this PR will: ... ³
  • The PR Description

    • is free of optional paragraphs and you have filled the relevant parts to the best of your ability

What's new in this PR?

Issues

We don't show any system messages after dowing the migration from Proteus to MLS in 1:1 conversations

Causes (Optional)

Not implemented

Solutions

Call insertProtocolChangedSystemMessage after finishing the migration for 1:1 conversations

Needs releases with:

  • GitHub link to other pull request

Testing

Test Coverage (Optional)

  • I have added automated test to this contribution

How to Test

Briefly describe how this change was tested and if applicable the exact steps taken to verify that it works as expected.

Notes (Optional)

Specify here any other facts that you think are important for this issue.

Attachments (Optional)

Attachments like images, videos, etc. (drag and drop in the text box)


PR Post Submission Checklist for internal contributors (Optional)

  • Wire's Github Workflow has automatically linked the PR to a JIRA issue

PR Post Merge Checklist for internal contributors

  • If any soft of configuration variable was introduced by this PR, it has been added to the relevant documents and the CI jobs have been updated.

References
  1. https://sparkbox.com/foundry/semantic_commit_messages
  2. https://github.com/wireapp/.github#usage
  3. E.g. feat(conversation-list): Sort conversations by most emojis in the title #SQPIT-764.

@echoes-hq echoes-hq bot added the echoes: unplanned Any work item that isn’t part of the product or technical roadmap. label Sep 26, 2024
@ohassine ohassine requested review from a team, typfel, alexandreferris, mchenani, Garzas and saleniuk and removed request for a team September 26, 2024 15:03
Copy link

Copy link
Contributor

github-actions bot commented Sep 26, 2024

Test Results

3 208 tests  ±0   3 101 ✅ ±0   3m 48s ⏱️ -5s
  551 suites ±0     107 💤 ±0 
  551 files   ±0       0 ❌ ±0 

Results for commit 81f77b5. ± Comparison against base commit 752c124.

♻️ This comment has been updated with latest results.

Copy link
Contributor

🐰 Bencher Report

BranchMigration-message-not-shown-in-11-conversations
Testbedubuntu-latest

⚠️ WARNING: The following Measure does not have a Threshold. Without a Threshold, no Alerts will ever be generated!

Click here to create a new Threshold
For more information, see the Threshold documentation.
To only post results if a Threshold exists, set the --ci-only-thresholds CLI flag.

Click to view all benchmark results
BenchmarkLatencynanoseconds (ns)
com.wire.kalium.benchmarks.logic.CoreLogicBenchmark.createObjectInFiles📈 view plot
⚠️ NO THRESHOLD
715,802.76
com.wire.kalium.benchmarks.logic.CoreLogicBenchmark.createObjectInMemory📈 view plot
⚠️ NO THRESHOLD
698,185,794.77
com.wire.kalium.benchmarks.persistence.MessagesNoPragmaTuneBenchmark.messageInsertionBenchmark📈 view plot
⚠️ NO THRESHOLD
951,522,296.39
com.wire.kalium.benchmarks.persistence.MessagesNoPragmaTuneBenchmark.queryMessagesBenchmark📈 view plot
⚠️ NO THRESHOLD
21,699,622.70
🐰 View full continuous benchmarking report in Bencher

@datadog-wireapp
Copy link

Datadog Report

Branch report: Migration-message-not-shown-in-11-conversations
Commit report: 4b26be8
Test service: kalium-jvm

✅ 0 Failed, 3101 Passed, 107 Skipped, 12.02s Total Time

@vitorhugods
Copy link
Member

Should we backport this to 4.6?

@ohassine ohassine added this pull request to the merge queue Sep 27, 2024
Merged via the queue into develop with commit 025b3f7 Sep 27, 2024
22 checks passed
@ohassine ohassine deleted the Migration-message-not-shown-in-11-conversations branch September 27, 2024 08:12
yamilmedina added a commit that referenced this pull request Jan 9, 2025
…WPB-11194) (#3221)

* fix: fallback to proteus if conversation already present but MLS is default (WPB-15191) (#3200)

* fix: fallback to proteus if conversation already present and no common protocol

* fix: test coverage

* fix: test coverage

* fix: Migration message not shown in 1:1 conversations (#3042)

* fix: update common protocol resolution (#3208)

* feat: detekt

---------

Co-authored-by: Oussama Hassine <[email protected]>
Garzas added a commit that referenced this pull request Jan 10, 2025
* fix: fallback to proteus if conversation already present but MLS is default (WPB-15191) (#3200)

* fix: fallback to proteus if conversation already present and no common protocol

* fix: test coverage

* fix: test coverage

* fix: Migration message not shown in 1:1 conversations (#3042)

* fix: update common protocol resolution (#3208)

* fix: mls client init [WPB-15022] (#3178)

* fix: secure mls client creation with is mls enabled

* fix: dont persist mls conversations when mls is disabled

* review improvements

* fix: persist mls conversation when mls disabled (#3205)

---------

Co-authored-by: Yamil Medina <[email protected]>
Co-authored-by: Oussama Hassine <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
echoes: unplanned Any work item that isn’t part of the product or technical roadmap. 🚨 Potential breaking changes 👕 size: S type: bug / fix 🐞
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants