Software /
code /
prosody
File
spec/scansion/tombstones.scs @ 12479:4d36fbcdd210 0.12
core.moduleapi: Fix 'global' property via :context() - #1748
The 'global' property should reflect whether the module API instance
represents the global context or a VirtualHost or Component context.
However the module:context() method did not override this, leading the
property of the previous module shining trough, leading to bugs in code
relying on the 'global' property.
See also #1736
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Wed, 27 Apr 2022 17:18:46 +0200 |
parent | 12116:efcf25ad5406 |
line wrap: on
line source
# Tombstones [Client] Romeo jid: romeo@localhost password: password [Client] Juliet jid: juliet-tombstones@localhost password: password --------- Romeo connects Juliet connects Juliet sends: <iq type="set" id="bye"> <query xmlns="jabber:iq:register"> <remove/> </query> </iq> # Scansion gets disconnected right after this with a stream error makes # scansion itself abort, so we preemptively disconnect to avoid that # Juliet receives: # <iq type="result" id="bye"/> Juliet disconnects Romeo sends: <presence type="probe" to="${Juliet's JID}"/> Romeo receives: <presence type="error" from="${Juliet's JID}"/> Romeo receives: <presence type="unsubscribed" from="${Juliet's JID}"/>