When using Lobster with Bazel, it clears the PATH variable (to make sure all inputs are exactly known),
But lobster-html-report calls graphviz by looking up the location of the graphviz executible in PATH. Hence it is not possible to generate an image of the tracing policy in the HTML report.
Request:
Add a feature to specify the path to the graphviz executable.
Problem:
When using Lobster with Bazel, it clears the
PATHvariable (to make sure all inputs are exactly known), Butlobster-html-reportcalls graphviz by looking up the location of the graphviz executible inPATH. Hence it is not possible to generate an image of the tracing policy in the HTML report.Request:
Add a feature to specify the path to the graphviz executable.