You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you found a bug in python-ldap, or would request a new feature,
this is the place to let us know.
Please describe the issue and your environment here.
Issue description:
When using the syncrepl code in python-ldap, if you have an idle system after the REFRESH phase completes and it switches to persist mode, and then shut down the sync client with no changes having happened with the LDAP server, the sync cookie is never saved (syncrepl_set_cookie is not called). If the process is started on a system with active changes, syncrepl_set_cookie is correctly called after every new change once it has switched to PERSIST phase
Steps to reproduce:
Run a syncrepl client against an ldap environment using refreshAndPersist mode, where no changes occur after persist mode has occurred.
Operating system:
linux
Python version:
3.10.12
python-ldap version:
3.4.3
The text was updated successfully, but these errors were encountered:
If you found a bug in python-ldap, or would request a new feature,
this is the place to let us know.
Please describe the issue and your environment here.
Issue description:
When using the syncrepl code in python-ldap, if you have an idle system after the REFRESH phase completes and it switches to persist mode, and then shut down the sync client with no changes having happened with the LDAP server, the sync cookie is never saved (syncrepl_set_cookie is not called). If the process is started on a system with active changes, syncrepl_set_cookie is correctly called after every new change once it has switched to PERSIST phase
Steps to reproduce:
Run a syncrepl client against an ldap environment using refreshAndPersist mode, where no changes occur after persist mode has occurred.
Operating system:
linux
Python version:
3.10.12
python-ldap version:
3.4.3
The text was updated successfully, but these errors were encountered: