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
{{ message }}
This repository has been archived by the owner on Feb 22, 2024. It is now read-only.
When subscribing to an EventStream for the emote_set.update event, I am able to receive events as intended for emotes that are pushed, updated, and pulled. However, specifically on pulled emotes, the value of old_value.timestamp is wildly incorrect. Examples are shown below.
Given that there's no documentation describing special behavior for pulled emote timestamps, I assume this is in error. Do you have any idea why this might be occurring, or a temporary workaround to obtain the proper timestamp?
Edit to add: I also would have expected there to be a timestamp value for the pulled update itself as well, but the endpoint doesn't appear to provide one. I think this is a separate—albeit related—issue, though.
When subscribing to an EventStream for the
emote_set.update
event, I am able to receive events as intended for emotes that are pushed, updated, and pulled. However, specifically on pulled emotes, the value ofold_value.timestamp
is wildly incorrect. Examples are shown below.Given that there's no documentation describing special behavior for pulled emote timestamps, I assume this is in error. Do you have any idea why this might be occurring, or a temporary workaround to obtain the proper timestamp?
Edit to add: I also would have expected there to be a
timestamp
value for the pulled update itself as well, but the endpoint doesn't appear to provide one. I think this is a separate—albeit related—issue, though.Sample
pushed
array:Sample
pulled
array, for an update executed moments later:The text was updated successfully, but these errors were encountered: