#1549 mod_scansion_record handles generated unavaille presence weirdly

Reporter Zash
Owner Nobody
Created
Updated
Stars ★ (1)
Tags
  • Type-Defect
  • Status-Accepted
  • Priority-Medium
  1. Zash on

    What steps will reproduce the problem? 1. start prosody with mod_scansion_record 2. connect one client 3. have it send presence 4. disconnect What is the expected output? # mod_scansion_record on host 'localhost' recording started 2020-05-08T22:08:57Z [Client] Romeo password: password jid: romeo@localhost/Jor0tYiv ----- Romeo connects Romeo sends: <presence xml:lang='sv'/> Romeo receives: <presence xml:lang='sv' from='romeo@localhost/Jor0tYiv'> <x xmlns='vcard-temp:x:update'> <photo/> </x> </presence> Romeo disconnects # recording ended on 2020-05-08T22:09:07Z What do you see instead? # mod_scansion_record on host 'localhost' recording started 2020-05-08T22:08:57Z [Client] Romeo password: password jid: romeo@localhost/Jor0tYiv ----- Romeo connects Romeo sends: <presence xml:lang='sv'/> Romeo receives: <presence xml:lang='sv' from='romeo@localhost/Jor0tYiv'> <x xmlns='vcard-temp:x:update'> <photo/> </x> </presence> Romeo disconnects Romeo sends: <presence type='unavailable'/> # recording ended on 2020-05-08T22:09:07Z What version of the product are you using? trunk 866003968e2e Please provide any additional information below. This technically reflects the order of events in Prosody, as the final unavailable presence is generated by Prosody after the client disconnects. This should probably not go in the recording like this tho. Other actors subscribed to the presence should of course see it.

  2. Zash on

    Also, scansion should probably consider such a script not well formed and raise an error.

New comment

Not published. Used for spam prevention and optional update notifications.