-
Notifications
You must be signed in to change notification settings - Fork 9
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
Fails to upload SARIF when a scanning report is too large #375
Comments
GitHub limits the size of the SARIF file to 10MB, but based on your number of lines, it seems like 0.2MB. Am I correct?
Could you please provide the workflow in which you are running Differential ShellCheck? |
I checked the output.sarif size and it happens to be 10784 KB which just exceeds the limit that I did not know about. The workflow yaml is as follows.
|
I tried minimizing the output.sarif file by removing white spaces (as curl should do with the data) and now it is 2.6 MB. |
Checked the gzipped output sarif and it is 0.3 MB. The gzipped minimized sarif is 0.1 MB.
I apologise for the distraction with the file sizes. |
Thank you for the report and the fix. I'll try to release a new version today. The workflow looks ok. But I think |
Thanks. I will try removing |
Type of issue
Bug Report
Description
When is triggered on default branch push the following error occurs.
Assumed cause:
Curl could not process a large SARIF report passed as a cli argument. In my case the report was saved and it is 226194 lines long.
Describe the solution you'd like
The report is uploaded successfully. Potentially getting the data from a file.
The text was updated successfully, but these errors were encountered: