Add more PPU Hashes (#947) #289
Annotations
7 warnings
|
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-dotnet@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
dotnet build Release:
CompatBot/Utils/ColorGetter.cs#L58
This call site is reachable on: 'Windows' all versions. 'Bitmap' is only supported on: 'windows' 6.1 and later. (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1416)
|
|
dotnet build Release:
CompatBot/Database/DbImporter.cs#L78
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
dotnet build Release:
CompatBot/Database/DbImporter.cs#L79
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
dotnet build Release:
CompatBot/Utils/ColorGetter.cs#L58
This call site is reachable on: 'Windows' all versions. 'Bitmap' is only supported on: 'windows' 6.1 and later. (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1416)
|
|
dotnet build Release:
CompatBot/Database/DbImporter.cs#L78
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
dotnet build Release:
CompatBot/Database/DbImporter.cs#L79
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
The logs for this run have expired and are no longer available.
Loading