Closed Strakeln closed 10 months ago
Hi @Strakeln 👋
So this is actually an issue that has been folded out, but it hasn't yet made its way out in the form of a release. You can see the fix here. If you'd like, you can also validate that the problem is gone by running go run . run ...
in the project directory if you have it cloned 😄.
Hopefull that answers your question, and if you want to know anything else please feel free to update this issue. Also pleae let me know if you are happy for me to close the issue (might be worth waiting if you want to run the main
branch code locally).
Excellent news, @ChaosInTheCRD - thanks for the update. I am good with you closing the issue. Thanks!
What steps did you take and what happened:
If a user specifies one of the always-run attestor types (
product
andmaterial
), the specified attestor type is run twice.Example:
witness run -a product -s test -k key.pem -o output.json --echo "hello" >test.txt
Note the duplicate "starting product attestor" statement. In the resulting attestation, there are two
product
attestors. Same behavior applies if you specify thematerial
attestor.What did you expect to happen:
(and the resulting output attestation to only have one product attestation)
Environment: