Build: #854 was successful Manual run by daryl herzmann

Build result summary

Details

Completed
Queue duration
1 second
Duration
1 minute
Labels
None
Agent
Default Agent
Revision
5b23edcf5a8716fdd4b8ec5a09b6711b4c934468
Total tests
437
Successful since
#749 ()

Tests

Code commits

Author Commit Message Commit date
daryl herzmann <akrherz@iastate.edu> daryl herzmann <akrherz@iastate.edu> 5b23edcf5a8716fdd4b8ec5a09b6711b4c934468 Merge pull request #1731 from guusdk/OF-2092_PEP-memory-leak
PEP notification rewrite
Guus der Kinderen Guus der Kinderen e6d5e282e3441938d89ba61c5860b048e49cc8ee m OF-2105: Don't depend on PEP service to be cached for removal.
The existing implementation of removal of a PEP service (which gets triggered if the owning user gets deleted) only operates on PEP services if they're currently in a cache.

Even if the PEP service is not currently cached, it should be deleted.
Guus der Kinderen Guus der Kinderen d9bc156ae986898730b4dc7584f0ff747ef76d0a m Pubsub: add logging around lifecycle events.
Guus der Kinderen Guus der Kinderen aa68522a78dabfb7d818258675f2d0f482ab9697 m OF-2039: When processing CAPS changes, consider subscribed-to PEP nodes
Apply changes to notification filtering not only to PEP nodes that belong to the service owned by the sender, but also to those that the sender subscribes to.
Guus der Kinderen Guus der Kinderen 97b6994eb248690242225daa34690c0179a62c2d m OF-2102: Prevent incorrect shutdown of pubsub persistence provider
Do not shut down the persistence infrastructure when just one (of potentially many) pubsub services shuts down.

This commit depends on the previous commit, in that that commit now ensures that the persistence infrastructure is shut down when appropriate.

Jira issues

IssueDescriptionStatus
Unknown Issue TypeOF-1988Could not obtain issue details from Jira
Unknown Issue TypeOF-2039Could not obtain issue details from Jira
Unknown Issue TypeOF-2092Could not obtain issue details from Jira
Unknown Issue TypeOF-2102Could not obtain issue details from Jira
Unknown Issue TypeOF-2105Could not obtain issue details from Jira