Sarah Oslund
Sarah Oslund
You're seeing the above error only with spdx 3.0? @pragnya17 is currently working on SPDX 3.0 and is not yet finished so I expect this issue will be addressed by...
It looks like that error is still showing up in our CI runs on this PR: https://dev.azure.com/mseng/1ES/_build/results?buildId=29671974&view=results
> Last I checked (in April), this was just waiting on approval. I don't think that's accurate, some of my previous comments have not been resolved (like reverting changes to...
Hi @m-bachner I would suggestion pointing the buildDropPath and buildComponent path parameters to project specific directories, instead of solution specific directories. The exact parameters you provide will depend on the...
As discussed in https://github.com/microsoft/sbom-tool/issues/78 and https://github.com/microsoft/sbom-tool/issues/592, we will not be accepting this feature request right now.
I suspect that the cancellation issue here will be fixed by part of https://github.com/microsoft/sbom-tool/pull/933#discussion_r1967007677
@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...
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...
We have discussed this and have the following takeaways: - This code is calling out to the clearly defined APIs which we do not own/ control, and tend to be...