#49123 str2entry_dupcheck not all errors are logged
Closed: wontfix 3 years ago by spichugi. Opened 7 years ago by firstyear.

A number of error cases in str2entry_dupcheck are only logged at LOG_TRACE, when they should be logged at an error level (WARNING, ERR). This can cause silent failures of imports.


Metadata Update from @firstyear:
- Issue set to the milestone: 0.0 NEEDS_TRIAGE

7 years ago

Metadata Update from @mreynolds:
- Issue close_status updated to: None
- Issue set to the milestone: 1.3.7 backlog (was: 0.0 NEEDS_TRIAGE)

7 years ago

Metadata Update from @mreynolds:
- Custom field reviewstatus adjusted to None
- Issue set to the milestone: FUTURE (was: 1.3.7 backlog)

4 years ago

Metadata Update from @mreynolds:
- Issue set to the milestone: 1.4.4 (was: FUTURE)
- Issue tagged with: Easyfix

3 years ago

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/2182

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata