Closed millenc closed 2 years ago
Hi @millenc , thanks for report this, looks like a bug in the Safety report only with Tensorflow, we are going to verify and inspect the possible cause and we will apply a fix as soon as possible.
@millenc I closed this issue because it was fixed in our backend side, no update is needed, so you should be able to see the fix with no action from your side. Let me know if it's ok for you, don't hesitate to reach us if there is another issue.
@millenc I closed this issue because it was fixed in our backend side, no update is needed, so you should be able to see the fix with no action from your side. Let me know if it's ok for you, don't hesitate to reach us if there is another issue.
@yeisonvargasf I can confirm that the issue appears to be fixed. I've tried using safety on a fresh project with tensorflow==2.5.0
(one of the affected versions) and the report looks good now.
Thank you very much for your support!
1.10.3
3.7.10
Description
The safety report (either
--full-report
or--short-report
) is huge and contains lots of duplicated lines when tensorflow2.4.0
is installed and an API key is used.What I Did
virtualenv -p /usr/bin/python3.7 ~/.envs/tensorflow
pip3 install tensorflow==2.4.0 safety
safety check
export SAFETY_API_KEY="<MY API KEY HERE>"
Running safety with no API key (step 4.) the report looks like this:
If I export the API key (step 5.) and run the analysis again (step 6.) the result is the log included on the attached file:
safety-check-tensorflow-2.4.0-with-apikey.log
As you can see, there are more than 16k lines in there. Such a report is not useful at all and causes issues on CI/CD pipelines that impose limits on the size of logs. Using the
--full-report
option is even worse since the log turns out to have more than 160k lines (~14MB). The same thing happens with the JSON report.