|
|
|
|
|
|
8/4/2017 8:35:12 PM
See af7214c939, a7e04cd295
|
8/4/2017 8:07:26 PM
See af7214c939
|
|
|
|
|
7/31/2017 12:24:18 PM
fix to 4c35c066e8e4e7d928f2709b491a749d63815d0d, but for
subscriptions having gone through a CHANGE.
Signed-off-by: Pierre-Alexandre Meyer <pierre@mouraf.org>
|
8/3/2017 9:56:38 AM
Pierre-Alexandre Meyer <pierre@mouraf.org>
|
8/3/2017 8:37:17 AM
doesn't find the right plan when processing a PHASE
event when the entry was retired at the time of the PHASE event.
The issue was that the wrong catalog version was pulled: instead of using the
version at the time of the subscription creation, the version at the time of
the phase event was used.
For symmetry, this behavior has been fixed for uncancel operations too (this is
a behavior change as previously uncancel operations would be prevented from the API
when the original plan was retired at the time of the uncancellation).
Additional tests have been written to verify and illustrate these scenarii.
Signed-off-by: Pierre-Alexandre Meyer <pierre@mouraf.org>
|
