Learn more about these different git repos.
Other Git URLs
The resolver interface is used through the SSSD on various places and sometimes the timeout handling might cause the resolver request being cancelled but the resolver would reply afterwards. To be on the safe side, I think the resolver should strdup/memdup its input parameters so that the request is self-contained.
Fields changed
priority: major => minor type: defect => task
milestone: NEEDS_TRIAGE => SSSD 1.11 beta rhbz: => todo
mark: => 0
changelog: => owner: somebody => preichl
Subtask of refactoring the resolver
milestone: SSSD 1.13 beta => SSSD 1.13 backlog
Mass-moving tickets not planned for the next two releases.
Please reply with a comment if you disagree about the move..
milestone: SSSD 1.13 backlog => SSSD 1.15 beta
Metadata Update from @jhrozek: - Issue assigned to preichl - Issue set to the milestone: SSSD Future releases (no date set yet)
Metadata Update from @thalman: - Custom field design_review reset (from 0) - Custom field mark reset (from 0) - Custom field patch reset (from 0) - Custom field review reset (from 0) - Custom field testsupdated reset (from 0) - Issue close_status updated to: None - Issue tagged with: Canditate to close
Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.
Given that we are unable to fulfill this request I am closing the issue as wontfix.
If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.
Thank you for understanding.
Metadata Update from @pbrezina: - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
SSSD is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here: - https://github.com/SSSD/sssd/issues/2917
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.
Login to comment on this ticket.