-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
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
AB#2432: Check for unsupported eclient import #172
Conversation
da657d6
to
a3cf018
Compare
cb873c9
to
0b1bb9d
Compare
Moved it from unit tests to integration tests. I would expect to show this in the output: But it's dropped. Any idea how to do handle this properly in bash? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd guess that it cannot be done with our run function. But I'm not a bash expert either, so this is not a definite answer.
However, the test itself works and the output is meaningful enough for me.
a00a718
to
9a17f03
Compare
Okay, I'll just keep it this way then. I also had the idea that since we already have custom Open Enclave / Edgeless RT error handling for more user friendly error handling that we can also put everything in the same function Only thing I am not super happy is that the if err != nil {
return err
}
return nil block in sign.go is kinda pointless, but changing it to just return err is inconsistent with the other functions, even though it effectively also returns nil in case no error occurred. Not sure what is the cleaner way here. |
LGTM. I have a slight preference for |
I'll make it |
99c593c
to
f5a5024
Compare
Proposed changes
The unit test is a bit heavy since it needs a go.mod & go.sum to function. Not sure whether we want to keep it as is or if there is a sleeker way.
Related issue
ego sign
#138