We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
> Which is expected. Should we now expose an UnsafeSignEOTS in which we would retain the old logic or mock EOTS for this e2e?
Good point. For this PR, we can add a case where the error is expected to make CI pass. A subsequent PR can implement UnsafeSignEOTS for old logic
UnsafeSignEOTS
Originally posted by @gitferry in #184 (comment)
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Originally posted by @gitferry in #184 (comment)
The text was updated successfully, but these errors were encountered: