You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sobelow Version: v0.11.1 (Tried with both published hex package, and build from master branch on github)
Operating System: MacOS Catalina 10.15.7, error also occurs on a Debian based docker image.
Notes:
Digging in to the stack trace a little indicates that Sobelow.print_output/0 makes a call to Sobelow.FindingLog.json/1 which attempts to call Jason.encode!/1 but is unable to find Jason within the scope of the current module. When building the module or running the install command provided by the README, Jason is being installed as a dependency. However, Jason is not being aliased into the FindingLog module definition, which may be causing the issue.
The text was updated successfully, but these errors were encountered:
Hey! Thanks for opening this issue. It looks like I missed a README update - as of 11.0, you should install Sobelow with mix escript.install hex sobelow. The Changelog has some additional details. Let me know if that fixes your issue, and I will update the README now.
Description:
Running sobelow with the option to output a JSON report (
mix sobelow -f json
) produces an exception.Steps to reproduce:
$ mix archive.install hex sobelow
per README instructions$ mix sobelow -f json
in a project containing a mix.exs fileEnvironment Information:
v0.11.1
(Tried with both published hex package, and build from master branch on github)Notes:
Digging in to the stack trace a little indicates that
Sobelow.print_output/0
makes a call toSobelow.FindingLog.json/1
which attempts to callJason.encode!/1
but is unable to findJason
within the scope of the current module. When building the module or running the install command provided by the README,Jason
is being installed as a dependency. However,Jason
is not beingalias
ed into theFindingLog
module definition, which may be causing the issue.The text was updated successfully, but these errors were encountered: