microsoft / microsoft/component-detection
Detection is getting hung up on macOS
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 553
- Forks
- 135
- Avg merge
- 20h 58m
- Merged PRs (30d)
- 6
Description
I've discussed this with @pauld-msft but wanted to open an issue for tracking purposes. When the internal version of our sbom tool calls into component-detection on macOS systems, one or more detection threads stops responding, leading to the process timing out and failing. We've added a workaround on our side to try to handle the timeout more gracefully, but we still need to identify and fix the root cause. According to reports, this is occurring about 15% of the time. Reach out to me if you need more information, internal links, etc.
The problem first occurred when we moved from Microsoft.ComponentDetection.* 4.8.9 to Microsoft.ComponentDetection.* 4.9.6.
There have been sporadic reports that this may also be happening on x64, but not approaching the 15% failure rate reported on macOS.
Contributor guide
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 reproducing the intermittent timeout on macOS with the internal SBOM tool and compare component-detection versions 4.8.9 and 4.9.6. Investigate which detection thread stops responding, including reports on x64, and consider the issue done when detection completes reliably without timing out on macOS.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100