Open erri120 opened 4 months ago
I'm facing the same issue in what I'd consider a small project (102 components in total, 27 explicitly referenced).
Maybe using a lower batchSize
would help preventing timeouts:
https://github.com/microsoft/sbom-tool/blob/0b4db48ca4f235cb75d9deaff2e094f710d55b2d/src/Microsoft.Sbom.Api/Executors/LicenseInformationService.cs#L34
But it would also increase the risk of hitting the documented rate limits, so all things considered, I think a configurable timeout would be the best solution.
EDIT: I tried to make a PR about this, but can't build the solution, see #687.
Same here. But I don't know the root cause for the timeout. Very large project.
The timeout of 30 seconds is a bit too short for larger projects:
Would it be possible to increase the timeout or have a configuration option?
https://github.com/microsoft/sbom-tool/blob/0b4db48ca4f235cb75d9deaff2e094f710d55b2d/src/Microsoft.Sbom.Api/Executors/LicenseInformationService.cs#L23
https://github.com/microsoft/sbom-tool/blob/0b4db48ca4f235cb75d9deaff2e094f710d55b2d/src/Microsoft.Sbom.Api/Executors/LicenseInformationService.cs#L41