René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"syncrepl code fails to store cookie after REFRESH phase completes and it switches to PERSIST","articleBody":"If you found a bug in python-ldap, or would request a new feature,\r\nthis is the place to let us know.\r\n\r\nPlease describe the issue and your environment here.\r\n\r\n---\r\n\r\nIssue description:\r\n\r\nWhen 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\r\n\r\n\r\n\r\n\r\nSteps to reproduce: \r\n\r\nRun a syncrepl client against an ldap environment using refreshAndPersist mode, where no changes occur after persist mode has occurred.\r\n\r\n\r\nOperating system: \r\n\r\nlinux\r\n\r\nPython version: \r\n\r\n3.10.12\r\n\r\npython-ldap version: \r\n\r\n3.4.3","author":{"url":"https://github.com/quanah","@type":"Person","name":"quanah"},"datePublished":"2024-04-11T20:08:14.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/563/python-ldap/issues/563"}