Skip to content

Conversation

@link2xt
Copy link
Collaborator

@link2xt link2xt commented Nov 27, 2025

This is a preparation for #7485, I have split easier to review changes here so it can be merged quickly.

@link2xt link2xt force-pushed the link2xt/transport-sync-prepare branch from 759f4ba to e6a2d94 Compare November 27, 2025 22:59
Currently there is a race between transports
to upload sync messages and delete them from `imap_send` table.
Sometimes mulitple transports upload the same message
and sometimes only some of them "win".
With this change only the primary transport
will upload the sync message.
@link2xt link2xt force-pushed the link2xt/transport-sync-prepare branch from e6a2d94 to 4fa2153 Compare November 28, 2025 02:15
.get_config(Config::ConfiguredAddr)
.await?
.unwrap_or_default()
== connection.addr
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just a side question: should this better be something like has_transport_address(connection.addr) in the multi-transport feature? "ConfiguredAddr" does not feel like a valid thing to work with anymore.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

configured_addr is the address of the primary transport. Unlike all other configured_* settings it is not deprecated and is used to set the primary transport and tell which transport is currently the primary one.

@link2xt link2xt merged commit 343dca8 into main Nov 29, 2025
29 checks passed
@link2xt link2xt deleted the link2xt/transport-sync-prepare branch November 29, 2025 00:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants