Changelog trimming does not trim the anchor csns. But if an anchor csn is found there are two calls to getNext entry and the change folloing an anchor csn is skipped and not trimmed
Per triage meeting...
Metadata Update from @nhosoi: - Issue set to the milestone: 1.3.6 backlog
Metadata Update from @mreynolds: - Custom field component reset (from Replication - General) - Issue close_status updated to: None - Issue set to the milestone: 1.3.7.0 (was: 1.3.6 backlog)
@lkrispen - was this already fixed via a different ticket?
Metadata Update from @mreynolds: - Custom field reviewstatus adjusted to None
Metadata Update from @mreynolds: - Issue set to the milestone: 1.4.2 (was: 1.3.7.0)
don't think so, the impact is not so big, so we could either close it or give me some time to reproduce and fix - or someone else wanting to dive into replication code
Metadata Update from @vashirov: - Issue priority set to: minor (was: normal) - Issue set to the milestone: 1.4 backlog (was: 1.4.2)
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/1723
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.