You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
We have merged https://github.com/microsoft/component-detection/pull/1255/files to resolve issues with arm64, which I have confirmed some of the impacted macOS systems are using. Lets update to that package version once it is released, and see how that impacts these builds
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 toMicrosoft.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.
The text was updated successfully, but these errors were encountered: