fix: stability and perf fixes

[isekovanic]

CLA

• I have signed the Stream CLA (required).
• Code changes are tested

Description of the changes, What, Why and How?

Linear ticket: https://linear.app/stream/issue/REACT-1226/stability-and-performance-fixes

Fixes pagination, channel list ordering and offline cold start issues in the v10 state layer, each reproduced against the release candidate and confirmed on device.

• 1be4ec66: Fixes an issue where jumping to a message could leave the message list loading forever. Jumps that commit their own state (the first-unread query, a failed jumpToMessage, jumpToTheLatestMessage from an older window) never cleared isLoading, so the list never paginated again. Also fixes jumps inside a thread: they were sent without a limit, and the replies endpoint ignores id_around without one and returns the newest replies, so tapping a quoted reply did nothing and the thread stopped paginating. Jumps now always send a limit, and their head/tail flags are measured against that limit.
• bb9bd6ed: Fixes an issue where, after a jump, the list could decide there were no more messages above or below the target and stop paginating. The flags were guessed from the target's position in the page, which only matches how the server splits the page for odd limits (the default thread page size of 50 broke both directions). They are now derived from how many messages came back on each side.
• bdd5acac: Fixes an issue where an empty page (asking for newer messages when the newest are already loaded) cleared the cursor for the other direction, so the list could no longer load older messages.
• 3ca29362: Fixes an issue where a channel that was added while empty and then received its first message was stored twice in its list, and removing it (for example when the user is removed from the channel) cleaned up only one entry. The next list query threw on the stale entry, the list stayed loading and stopped updating, and connection recovery skipped it. Locating an item now checks whether the list already holds it before using sort bounds, without scanning for new or unmoved items.
• 65d34077: Fixes an issue where truncating a channel kept its last message preview and its position in the list. The server clears last_message_at on truncation; the paginator now recomputes the last message from what remains, drops a seeded last-message time older than the truncation, and channel.truncated applies the event's channel data.
• 0373a2d6: Fixes an issue where a hidden channel did not come back to the list on a new message. The server unhides a channel on any new message without sending channel.visible; message.new and notification.message_new now clear hidden before the lists route the event.
• 9878b23e: Fixes an issue where lists sorted by last_updated moved a channel to the top when its data was updated. The server's last_updated is the last message time, else the creation time; it does not use updated_at.
• a87bba04: Fixes an issue where the channel preview's last message did not update for changes that do not go through ingestion: soft deletes, reactions and other writes to the stored message by other holders, and an author rename. The message paginator now refreshes its last message from the store when it changes.
• 5794effe: Fixes an issue where hard-deleting a channel's newest message updated the preview but kept the channel at its old position until the next query. The server moves last_message_at back to the previous message; the paginator now does the same with the previous loaded message, and keeps the server value when no earlier message is loaded.
• c58a6090: Fixes an issue where a channel list published a new items array on every channel event (a new message to the top channel, presence, typing) even when the order and membership were unchanged, re-rendering every consumer of the list. The list keeps its current array when the next one holds the same channels in the same order.
• b34b69f1: Fixes an issue where an error thrown by an event handler was logged without the error itself, only the handler id and index.
• c4295b29: Fixes an issue where, on an offline cold start, a channel list read its cached first page from the offline database once for every request made before the sync finished (UIs make several on mount), re-hydrating the same channels and re-rendering every row each time. The query waiting for the sync is now remembered, so a repeat request for the same query does nothing: the cache is read once and the network query runs once. A request for a different query still reads the cache for itself and replaces the waiting one.

Changelog

• Fix message list pagination stopping after jumping to a message, including quoted replies in threads.
• Fix a channel list getting stuck after the user is removed from a channel that was added while empty.
• Fix channel list order and previews after truncating a channel, hiding it, hard-deleting its newest message, or updating its data under a last_updated sort.
• Fix channel previews not reflecting soft deletes, reactions and author renames of the last message.
• Avoid re-rendering a channel list when an event leaves its order unchanged.
• Read the offline cache and query the channel list once on an offline cold start.
• Log the error when an event handler throws.

[stream-ci-bot]

🎉 This PR is included in version 10.0.0-rc.22 🎉

The release is available on:

• GitHub release
• npm package (@rc dist-tag)

Your semantic-release bot 📦🚀