Learn more about these different git repos.
Other Git URLs
Create unit test for be_refresh located at src/providers/dp_refresh.c.
Fields changed
milestone: NEEDS_TRIAGE => SSSD 1.11 beta type: defect => task
rhbz: => 0
Moving open tickets from 1.11 beta to 1.11 beta2
milestone: SSSD 1.11 beta => SSSD 1.11 beta 2
changelog: => milestone: SSSD 1.11 beta 2 => Interim Bucket
milestone: Interim Bucket => SSSD 1.12 beta
blocking: 1923 => #1923
milestone: SSSD 1.12 beta => SSSD 1.12.1
Mass-moving all tickets that didn't make 1.12.1 into 1.12.2
milestone: SSSD 1.12.1 => SSSD 1.12.2
We need to do a release as requested by downstream. Moving tickets that are not fixed already or very close to acking to 1.12.3
milestone: SSSD 1.12.2 => SSSD 1.12.3
mark: => 0 owner: somebody => mzidek
It makes sense to write the unit tests now instead of moving them to a later release again, but the tickets in 1.12.3 should be more focused at this point. Moving to 1.12.4
milestone: SSSD 1.12.3 => SSSD 1.12.4
milestone: SSSD 1.12.4 => SSSD Deferred
Metadata Update from @pbrezina: - Issue assigned to mzidek - Issue marked as blocked by: #1923 - Issue set to the milestone: SSSD Patches welcome
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/2982
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.