Message Update called twice #30

Closed
opened 2026-02-15 23:16:18 -05:00 by yindo · 1 comment
Owner

Originally created by @mcbabo on GitHub (Aug 19, 2023).

Describe the bug
If both message update listeners are written. on_raw_message_update gets also called when on_message_update "could" handle it

To Reproduce

async def on_message_update(self, message: revolt.Message):

async def on_raw_message_update(self, payload: MessageUpdateEventPayload):

Expected behavior
Only on_message_update should be called

Library version
0.1.11

Originally created by @mcbabo on GitHub (Aug 19, 2023). **Describe the bug** If both message update listeners are written. `on_raw_message_update` gets also called when `on_message_update` "could" handle it **To Reproduce** ```py async def on_message_update(self, message: revolt.Message): async def on_raw_message_update(self, payload: MessageUpdateEventPayload): ``` **Expected behavior** Only on_message_update should be called **Library version** 0.1.11
yindo added the wontfix label 2026-02-15 23:16:18 -05:00
yindo closed this issue 2026-02-15 23:16:18 -05:00
Author
Owner

@Zomatree commented on GitHub (Aug 19, 2023):

The raw event equivalents always get dispatched regardless of whether the non-raw event could handle it.

If you want to make it exclusive check the cache yourself to see if the message is cached.

@Zomatree commented on GitHub (Aug 19, 2023): The raw event equivalents always get dispatched regardless of whether the non-raw event could handle it. If you want to make it exclusive check the cache yourself to see if the message is cached.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: stoatchat/python-client-sdk#30