-
Notifications
You must be signed in to change notification settings - Fork 161
License information may not be fully recorded #944
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@schuhbsi I'm not sure I'm understanding the issues here- it sounds like the timeout is working as expected and terminating license discovery after the default of 30 seconds. We fetch license data from clearly defined which can sometimes be a long running operation or run into throttling, so it is expected that there will occasionally be cases in which license data gathering can take longer than the default of 30 seconds. Can you please clarify what this issue is/ what kinds of changes you would like to be made here? |
@sfoslund Sorry that I did not express myself clearly. I would simply like to have the necessary licenses, i.e. license types, for my components that are integrated in the projects. But I have the following problem that I sometimes get a timeout or another error like here ( License information may not be fully recorded), although I would have increased the timeout with the parameter from the default value 30 seconds as here in the example to 90 seconds. However, I have to say that my project also includes a large number of components, sometimes over 1000, where a license should be found. Would the solution then be to set the timeout even higher or would there be other parameters besides -lto and -li that would be important for the sbom generation with licenses? |
No, there are no other parameters besides the ones you mentioned which should effect license gathering. If you have a large number of components then sometimes this can take some time as it requires external requests which can be long running or throttled. I would suggest trying to increase your timeout and see if that helps. |
@sfoslund I have now set the timeout to 300 seconds but unfortunately this error still occurs sometimes:
|
sbom-tool version: 3.1.0
I execute the following command in an Azure Devops pipeline:
sbom-tool generate -b {{ parameters.workingDirectory }} -pn $(Build.DefinitionName) -pv 1.0.0 -ps sbom -nsb https://sbom.com -li true -V Verbose -D true -lto 90
The following result is returned
If I leave out the -lto parameter I get the timeout error
sbom-tool generate -b {{ parameters.workingDirectory }} -pn $(Build.DefinitionName) -pv 1.0.0 -ps sbom -nsb https://sbom.com -li true -V Verbose -D true
But strangely enough, sometimes the licence generation works even if the timeout is not specified
The text was updated successfully, but these errors were encountered: