#2674 reduce the code duplication of timeout setting with child processes
Closed: wontfix 8 months ago by pbrezina. Opened 5 years ago by jhrozek.

this came up recently on sssd-devel during code review of one-way trust patches.

Each place that uses the child process framework duplicates the timeout setting and management. We should move the timeout code to some common area and reduce the code duplication.


Fields changed

type: defect => task

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.13 backlog

This would also be a nice way to get familiar with our unit tests.

owner: somebody => pcech

Fields changed

rhbz: => 0

Fields changed

status: new => assigned

Fields changed

status: assigned => new

We have much more important tasks on our plate at the moment..

milestone: SSSD 1.13 backlog => SSSD 1.14 backlog

Fields changed

keywords: => easyfix

Since the 1.14 branch is transitioning into maintenance mode and new functionality is being developed in master which will become 1.15 eventually, I'm mass-moving tickets from the 1.14 backlog milestone to the "Future releases" milestone.

milestone: SSSD 1.14 backlog => SSSD Future releases (no date set yet)

Metadata Update from @jhrozek:
- Issue assigned to pcech
- Issue set to the milestone: SSSD Future releases (no date set yet)

3 years ago

Metadata Update from @jhrozek:
- Assignee reset
- 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 sensitive reset (from 0)
- Custom field testsupdated reset (from 0)
- Issue close_status updated to: None
- Issue tagged with: easyfix

3 years ago

Metadata Update from @thalman:
- Custom field design_review reset (from false)
- Custom field mark reset (from false)
- Custom field patch reset (from false)
- Custom field review reset (from false)
- Custom field sensitive reset (from false)
- Custom field testsupdated reset (from false)
- Issue tagged with: Canditate to close

8 months ago

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)

8 months ago

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

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.

Login to comment on this ticket.

Metadata