There are 4 resource leaks being reported that need to be fixed
<img alt="0001-Ticket-49531-coverity-issues-fix-memory-leaks.patch" src="/389-ds-base/issue/raw/files/2d6562461cb0532229373dcbc06c31994286b46f647a767111fdd9551f5e76a4-0001-Ticket-49531-coverity-issues-fix-memory-leaks.patch" />
Metadata Update from @mreynolds: - Custom field component adjusted to None - Custom field origin adjusted to QE - Custom field reviewstatus adjusted to review - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1519406 - Custom field type adjusted to None - Custom field version adjusted to None
Metadata Update from @lkrispen: - Custom field reviewstatus adjusted to ack (was: review)
8448369..700d742 master -> master
f807b9b..a2df295 389-ds-base-1.3.7 -> 389-ds-base-1.3.7
Metadata Update from @mreynolds: - 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/2590
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.