Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

syncrepl code fails to store cookie after REFRESH phase completes and it switches to PERSIST #563

Open
quanah opened this issue Apr 11, 2024 · 1 comment

Comments

@quanah
Copy link
Contributor

quanah commented Apr 11, 2024

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

@quanah
Copy link
Contributor Author

quanah commented Apr 11, 2024

Found that during the refreshDelete phase, no cookie ends up being stored.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant