microsoft / microsoft/RecursiveExtractor
Timeout Should be Resiliant to Stalls in Extractor Libraries
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 220
- Forks
- 35
- Avg merge
- 20d 1h
- Merged PRs (30d)
- 1
Description
#127 revealed an a new issue that if there is a stall in an extractor dependency we use, the resource governor is never called. This may require some refactoring to perhaps a task based system with a timer based cancellation to improve the robustness of the timer restriction.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how the resource governor is invoked around extractor dependencies and how the timer restriction is enforced. Determine how a stalled extractor should trigger cancellation and define done as ensuring the governor is still called and the timeout remains effective during dependency stalls.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- cli, tooling
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100