-
Notifications
You must be signed in to change notification settings - Fork 282
Ensure valid wasms when publishing app #3206
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
Conversation
e4c7bee
to
76e466c
Compare
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.
The actual code that does the actual thing looks fine, but I did have a good old moan about the tests I'm afraid. Not a blocker but would be nice to tighten them up if you have the bandwidth.
76e466c
to
9b0a669
Compare
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.
Thanks, looks good! Just a couple of extremely non-blocking suggestions, feel free to ignore
Signed-off-by: Brian Hardock <[email protected]>
9b0a669
to
2852d93
Compare
macro_rules! make_locked { | ||
($source:literal, $($dep_name:literal=$dep_path:literal),*) => { | ||
from_json!({ | ||
"id": "jiggs", |
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.
YES
This PR ensures that each
source
field and depenency source specified in a Spin component is a valid Wasm binary.