Fix these coverity issues:
Some of these are false positives that are worked around in the PR to quiet covscans
1.4.0.9
https://pagure.io/389-ds-base/pull-request/49676
Metadata Update from @mreynolds: - Custom field component adjusted to None - Custom field origin adjusted to None - Custom field reviewstatus adjusted to review - Custom field type adjusted to None - Custom field version adjusted to None
commit 7a8b5ac master
Metadata Update from @mreynolds: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
<img alt="0001-fix-coverity-issue-ensure-that-be-is-in-the-range-of.patch" src="/389-ds-base/issue/raw/files/3769a6398e3063f05748d6200b1027821d6f015f80a498212c56791baedf4e7b-0001-fix-coverity-issue-ensure-that-be-is-in-the-range-of.patch" />
alternative for the backend issue
Thanks Ludwig, Covscan does not show any issues with this patch. So its ready for review again...
https://pagure.io/389-ds-base/pull-request/49729
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/2734
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.