Skip to content

Conversation

@SimonThormeyer
Copy link
Member

@SimonThormeyer SimonThormeyer commented Jul 3, 2025


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

Briefly describe the issue you have solved or implemented with this pull request. If the PR contains multiple issues, use a bullet list.

Causes (Optional)

Briefly describe the causes behind the issues. This could be helpful to understand the adopted solutions behind some nasty bugs or complex issues.

Solutions

Briefly describe the solutions you have implemented for the issues explained above.

Dependencies (Optional)

If there are some other pull requests related to this one (e.g. new releases of frameworks), specify them here.

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.

@github-actions github-actions bot added the size/s label Jul 3, 2025
This allows creating a commit from proposals without sending the
proposals over the wire first.
Previously, the tree shrink function would be called eagerly after each
remove proposal. If the shrink threshold was reached, the blanked out
nodes were removed from the diff tree.

If there were additional add proposals in a commit that triggered the
tree to grow again, this resulted in incorrect state if there were FEWER
add proposals than remove proposals. That's because the blanked out nodes
removed during shrinking were not re-added during growing.

To fix this, we don't shrink/trim the tree eagerly after each remove
proposal, but after remove and add proposals have been processed.
@SimonThormeyer SimonThormeyer force-pushed the simon/feat/build-commit-with-inline-proposals branch from 412eee6 to 8d44e38 Compare July 3, 2025 15:44
@SimonThormeyer SimonThormeyer marked this pull request as ready for review July 3, 2025 15:45
@SimonThormeyer SimonThormeyer merged commit c9cde17 into wire/stable Jul 4, 2025
44 of 48 checks passed
@SimonThormeyer SimonThormeyer deleted the simon/feat/build-commit-with-inline-proposals branch July 4, 2025 09:33
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.

3 participants