If I send:
<iq type="set" to="barejid" id="4lrho9u7oi" xmlns="jabber:client">
<query xmlns="urn:xmpp:mam:2" queryid="U1ocivjINMG2">
<x xmlns="jabber:x:data" type="submit">
<field var="FORM_TYPE" type="hidden"><value>urn:xmpp:mam:2</value></field>
<field var="start"><value>2023-09-12T20:17:31+05:00</value></field>
</x></query></iq>
then I get results from earlier on 2023-09-12
Zash
on
Unable to reproduce, start=2023-09-12T20:17:31+05:00 (timestamp equivalent to 2023-09-12T15:17:31Z) return results in prosody@ starting at 2023-09-12T15:18:49Z which is after 15:17 / 20:17+05:00
Where are you seeing this and what exactly does it look like?
Changes
tags Status-NeedInfo
Stephen Paul Weber
on
I can't reproduce this again now. If I see it again I'll capture more logs.
If I send: <iq type="set" to="barejid" id="4lrho9u7oi" xmlns="jabber:client"> <query xmlns="urn:xmpp:mam:2" queryid="U1ocivjINMG2"> <x xmlns="jabber:x:data" type="submit"> <field var="FORM_TYPE" type="hidden"><value>urn:xmpp:mam:2</value></field> <field var="start"><value>2023-09-12T20:17:31+05:00</value></field> </x></query></iq> then I get results from earlier on 2023-09-12
Unable to reproduce, start=2023-09-12T20:17:31+05:00 (timestamp equivalent to 2023-09-12T15:17:31Z) return results in prosody@ starting at 2023-09-12T15:18:49Z which is after 15:17 / 20:17+05:00 Where are you seeing this and what exactly does it look like?
ChangesI can't reproduce this again now. If I see it again I'll capture more logs.
Assuming this can be closed then.
Changes