Skip to content

Conversation

@PeterFarber
Copy link
Collaborator

Summary

  • Fix SNP verify to check M1 first (pipeline result), then fall back to M2 (direct call)
  • Add fallback to raw message when report key not found in committed message
  • Return proper error instead of crashing when report key is missing

Context

When using SNP verification in a pipeline flow like:

/~relay@1.0/call&relay-path=".../~snp@1.0/generate"/verify~snp@1.0

The relay result (containing the SNP report) is passed as M1, not M2. Previously, verify/3 only looked in M2, causing verification to fail with a function_clause error when json:decode received not_found.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants