Skip to content
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

REUSE status incompliant without error #622

Closed
SebastianWolf-SAP opened this issue Nov 4, 2022 · 4 comments
Closed

REUSE status incompliant without error #622

SebastianWolf-SAP opened this issue Nov 4, 2022 · 4 comments

Comments

@SebastianWolf-SAP
Copy link

It seems that we have again a situation like the one described in #424 - https://api.reuse.software/info/github.com/SAP/cloud-sdk-js shows non-compliant, but without any error. The project-specific CI/CD pipeline also didn't find any issue, see also SAP/cloud-sdk-js#3027

Could you please have a look?

@linozen
Copy link
Member

linozen commented Nov 23, 2022

It shows up as "compliant" to me. Feel free to reopen if this reemerges.

@linozen linozen closed this as completed Nov 23, 2022
@mxmehl
Copy link
Member

mxmehl commented Nov 23, 2022

I cannot completely understand how the SAP bot checks for compliance. Is it the lint in your CI pipeline or the API?

For the latter, because of a high increase in usage. This should have already improved. More performance improvements will follow soon with a more radical approach.

@SebastianWolf-SAP
Copy link
Author

Thanks for the improvements. We actually poll the API for each project once a day. If the API returns "incompliant", our bot creates an issue in the affected repository (see the referenced ones).

@mxmehl
Copy link
Member

mxmehl commented Nov 24, 2022

Ah, I see, that explains it. Do I see correctly that the number of reports decreased during the last week? This is when @linozen made some database performance improvements.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants