commit f639711 added the following clean up call to windows_search_entry_ext, which set NULL before the stashed raw_entry is refered in the winsync callbacks. + / clear it here in case the search fails and + we are left with a bogus old entry / + windows_private_set_raw_entry(conn->agmt, NULL);
git patch file (master) 0001-Ticket-47989-Windows-Sync-accidentally-cleared-raw_e.patch
Looks good to me
Reviewed by Mark (Thank you!!)
Pushed to master: 3182d2e..3305a6b master -> master commit 3305a6b
Pushed to 389-ds-base-1.3.3: 391539a..f6d8b2e 389-ds-base-1.3.3 -> 389-ds-base-1.3.3 commit f6d8b2e
Pushed to 389-ds-base-1.3.2: a379565..19af1af 389-ds-base-1.3.2 -> 389-ds-base-1.3.2 commit 19af1af
Pushed to 389-ds-base-1.3.1: 86b728f..bf55d5a 389-ds-base-1.3.1 -> 389-ds-base-1.3.1 commit bf55d5ac6547028ebabdcf19df28cfdd4017872f
Pushed to 389-ds-base-1.2.11: 295cf31..a605e94 389-ds-base-1.2.11 -> 389-ds-base-1.2.11 commit a605e94
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1183820
Metadata Update from @nhosoi: - Issue assigned to nhosoi - Issue set to the milestone: 1.2.11.33
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/1320
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.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Fixed)
Login to comment on this ticket.