Build: #1230 was successful Scheduled with changes by Guus der Kinderen and Emiel van der Herberg <emiel.van.der.herberg@marviq.com>

Build result summary

Details

Completed
Queue duration
10 minutes
Duration
1 minute
Labels
None
Agent
Default Agent
Revision
44497c3cb9070be22fa665b83b311f74661c4409
Total tests
466
Successful since
#749 ()

Tests

Code commits

Author Commit Message Commit date
Guus der Kinderen Guus der Kinderen 44497c3cb9070be22fa665b83b311f74661c4409 OF-2308: Prevent MUC nickname change to reserved nickname
When another user reserved a nickname in a MUC, another user should not be able to change its nickname to that reserved value after joining the room.
Guus der Kinderen Guus der Kinderen 2f111994af3ef1d64699b65166a05123448fc348 OF-2305: Do not treat nickname change as a join
Openfire tries to accomodate clients that think that they're no longer in the room, while they are. Sadly, this code does not distinguish between that scenario, and a scenario in which a client triest to change a nickname in the room. This commit adds that differentation.
Guus der Kinderen Guus der Kinderen 1d34cd66adf9b787ae175d1348bbdc425c4ce33b OF-2307: Allow nickname change to existing nickname of same user
When a user is joined a room with two different nicknames, it should be allowed to rename one of its nicknames into the other, without a conflict being raised.
Guus der Kinderen Guus der Kinderen acbc50f338ed3e21139f412271bd88517eb9f3c1 OF-2304: Non-MUC-occupants should not be able to change nicknames
The code that detects if the requestor of a nickname change is an occupant in the room needs fixing.

Many thanks to @MightyMop for identifying this problem and suggesting a fix.
Guus der Kinderen Guus der Kinderen 46ae93c22be1eb576c4e92c7fca1669cbf99c7de OF-2293: Prevent duplicate MUC occupants from existing
This commit prevents an occupant to be added to a room that already has that same occupant. This has been observed in the wild (while testing new MUC/Clustering code).

The changes in this commit do not take away the cause of the duplicated addition, which are unknown at this time. The change does take away the direct event (preventing the duplicate from being added), and logs an error message that contains a stack trace. Hopefully that can be used in the future to find the cause of the issue.

Jira issues

IssueDescriptionStatus
Unknown Issue TypeOF-2293Could not obtain issue details from Jira
Unknown Issue TypeOF-2304Could not obtain issue details from Jira
Unknown Issue TypeOF-2305Could not obtain issue details from Jira
Unknown Issue TypeOF-2307Could not obtain issue details from Jira
Unknown Issue TypeOF-2308Could not obtain issue details from Jira