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

Ensure that pending to-device events are sent over federation at startup #16925

Merged
merged 8 commits into from
Mar 22, 2024

Commits on Feb 15, 2024

  1. Include destinations we never sent to in catchup

    When picking destination servers that we need to wake up for a retry, we need
    to be mindful of destinations that we have *never* successfully sent to. This
    can manifest either as a null `last_successful_stream_ordering`, or even no row
    in `destinations` at all.
    
    Hence, we need to left-join on `destinations` rather than inner-joining, and we
    need to treat a null `last_successful_stream_ordering` the same as 0.
    richvdh committed Feb 15, 2024
    Configuration menu
    Copy the full SHA
    bd010d7 View commit details
    Browse the repository at this point in the history
  2. Include destinations with to-device messages in catchup

    When considering which destinations need waking up for a retry, also look for
    those that have outstanding to-device messages.
    richvdh committed Feb 15, 2024
    Configuration menu
    Copy the full SHA
    3e467d3 View commit details
    Browse the repository at this point in the history
  3. Kick off the destination wakeup job immediately at startup

    We don't really want people to have to wait 60 seconds for their to-device
    messages.
    richvdh committed Feb 15, 2024
    Configuration menu
    Copy the full SHA
    ce234c2 View commit details
    Browse the repository at this point in the history
  4. changelog

    richvdh committed Feb 15, 2024
    Configuration menu
    Copy the full SHA
    edc8155 View commit details
    Browse the repository at this point in the history

Commits on Mar 14, 2024

  1. Add now param to looping_call

    richvdh committed Mar 14, 2024
    Configuration menu
    Copy the full SHA
    b7908ac View commit details
    Browse the repository at this point in the history

Commits on Mar 20, 2024

  1. Configuration menu
    Copy the full SHA
    6c73ba2 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    a63ffc8 View commit details
    Browse the repository at this point in the history

Commits on Mar 21, 2024

  1. Configuration menu
    Copy the full SHA
    0bf54b7 View commit details
    Browse the repository at this point in the history