Opened 6 years ago

Last modified 6 years ago

#9242 reopened defect

ejabberd:Users added to a shared roster don't see pubsub presence of existing users immediately.

Reported by: martin.langhoff Owned by: martin.langhoff
Priority: normal Milestone: xs-0.7
Component: school server Version: not specified
Keywords: Cc:
Blocked By: Blocking:
Deployments affected: Action Needed: never set
Verified: no

Description

Upstream bug report: https://support.process-one.net/browse/EJAB-865

This affects Moodle & user/course management, has a simple workaround: as soon as the client reconnects, the problem is fixed.

Change History (4)

comment:1 Changed 6 years ago by martin.langhoff

This bug and various related issues are fixed in 2.0.3 -

comment:2 Changed 6 years ago by martin.langhoff

  • Resolution set to fixed
  • Status changed from new to closed

This is fixed for on the eabberd 2.0.3 in XS-0.5.2 and XS-0.6

comment:3 Changed 6 years ago by martin.langhoff

  • Resolution fixed deleted
  • Status changed from closed to reopened

Actually, on further testing, I have to qualify the fix. With 2.0.3 + my patches.

  • @online@ - from my patches - works like a charm
  • conventional SRGs do not work work correctly

In other words, https://support.process-one.net/browse/EJAB-767 does not appear to be fixed for me.

Downgrading the mod_shared_roster.beam file to a fresh one, compiled from src did not make things better -- so 2.0.3 seems broken. This needs investigation.

The current recommended workaround: trigger a reconnection to the AP / AA.

comment:4 Changed 6 years ago by martin.langhoff

  • Milestone changed from xs-0.6 to xs-0.7

This bug is confirmed as present on 0.6 but we'll target a fix for 0.7.

For XS-0.6 users:

the "mainstream" use case of 0.6 is not affected. Only if you are using "presence-by-course" mode, where the ejabberd is controlled by Moodle you will see this problem. It manifests itself in that when you add a user to an new course, that user does not see the new 'peers' in the neighbourhood view immediately. When the user restarts the Sugar session or reconnects to the AP, all the peers are visible.

This only affects users when students are being enrolled in new courses -- not a frequent occurrence in a school.

The workaround to see the new peers immediately is to reconnect to the AP.

Note: See TracTickets for help on using tickets.