-
Notifications
You must be signed in to change notification settings - Fork 147
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
TypeError when executing with --full-report #141
Comments
I'm seeing the same error. I've got scheduled daily builds - the last successful was July 17, and then they started failing July 18. That doesn't seem to be tied to the release of 1.8.2 on July 11. I tried the same run using safety 1.8.1 and the build ran fine. I'm guessing it's tied to this commit. I'd love to supply more details, but what's weird is I can't re-create this error locally or manually on the CI server - it only fails during the automated run. ¯_(ツ)_/¯ My versions:
|
Hi @richleland @JochenABC thanks for the details, we're looking into this. In the mean time if you come across any more details please let me know. |
I have opened a PR potential fix: #142 We will be testing this before deploying. @JochenABC can you confirm that if you change back to safety 1.8.1 it works for you? |
@Jwomers Confirmed:
|
@JochenABC @richleland looks like PR #142 works for all, I will be merging and pushing to PyPi later today. |
This is merged and being pushed to PyPi. Closing this issue. Thanks all for the help. |
Description
Whenever safety is run with
--full-report
and tries to report an issue it will abort withTypeError: unsupported format string passed to bytes.__format__
What I Did
The text was updated successfully, but these errors were encountered: