You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When sending an event as a reply to a thread using the default "chronological"pendingEventOrdering, I'd expect the reply to appear in the thread's timeline as soon as sendMessage is called. In actuality, with [email protected], the event only shows up in the thread's timeline about half a second after the sendMessage promise resolves.
(I'd also be fine with the local echo appearing in the thread's containing Room, but no dice there either.)
Here is a branch of a repo that I think has a minimal reproducing example, although it's a little noisy due to many Thread.updates called – I believe related to #3463. (I don't think this is caused by the same bug as #3463 though, as this happens for me in threads with fewer than 11 events.)
Here are logs of me running this code:
The text was updated successfully, but these errors were encountered:
When sending an event as a reply to a thread using the default
"chronological"
pendingEventOrdering
, I'd expect the reply to appear in the thread'stimeline
as soon assendMessage
is called. In actuality, with[email protected]
, the event only shows up in the thread's timeline about half a second after thesendMessage
promise resolves.(I'd also be fine with the local echo appearing in the thread's containing
Room
, but no dice there either.)Here is a branch of a repo that I think has a minimal reproducing example, although it's a little noisy due to many
Thread.update
s called – I believe related to #3463. (I don't think this is caused by the same bug as #3463 though, as this happens for me in threads with fewer than 11 events.)Here are logs of me running this code:
![Screen Shot 2023-06-11 at 7 19 31 PM](https://private-user-images.githubusercontent.com/1924620/244992190-94f9fccf-cadc-4b62-8840-2dc691e2fb95.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkwODEyNDcsIm5iZiI6MTczOTA4MDk0NywicGF0aCI6Ii8xOTI0NjIwLzI0NDk5MjE5MC05NGY5ZmNjZi1jYWRjLTRiNjItODg0MC0yZGM2OTFlMmZiOTUucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI1MDIwOSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNTAyMDlUMDYwMjI3WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9ZDI3MjQ0YzBiYWU2ZjczNTBkZmEzMGU5NTIyZmY2NzQ2ZDk3OGVkZWE0ZTkxZjAyMTdmZmJkODM5NjJlYzYyYSZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.TMwSHb_MVkhiKeUWcwi88gRfymqp5_Q3M9NVlHlrkOg)
The text was updated successfully, but these errors were encountered: