The change for 49316 (clock unsafety) is breaking the loop of the eventq that continuously sleeps without calling the recorded events
Recorded periodic event (likely also fixed time event) are not called
Call the recorded event
<img alt="0001-Ticket-49332-Event-queue-is-not-working.patch" src="/389-ds-base/issue/raw/files/9aa72873aa6ad8e0947ee8465514a6cb2157b4c9ac789cedaa2d592d5bcbb604-0001-Ticket-49332-Event-queue-is-not-working.patch" />
Metadata Update from @tbordaz: - Custom field component adjusted to None - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Custom field type adjusted to None - Custom field version adjusted to None
Metadata Update from @tbordaz: - Custom field reviewstatus adjusted to review (was: None)
Metadata Update from @tbordaz: - Issue assigned to tbordaz
Metadata Update from @tbordaz: - Issue set to the milestone: 1.3.7.0
Metadata Update from @firstyear: - Custom field reviewstatus adjusted to ack (was: review)
git push origin master
Counting objects: 6, done. Delta compression using up to 8 threads. Compressing objects: 100% (6/6), done. Writing objects: 100% (6/6), 877 bytes | 0 bytes/s, done. Total 6 (delta 4), reused 0 (delta 0) remote: Sending to redis to log activity and send commit notification emails remote: Emitting a message to the fedmsg bus. remote: * Publishing information for 1 commits remote: Sending notification emails to: 389-commits@lists.fedoraproject.org To ssh://git@pagure.io/389-ds-base.git 28ad77e..af536ea master -> master
Metadata Update from @tbordaz: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
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/2391
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)
Log in to comment on this ticket.