-
Notifications
You must be signed in to change notification settings - Fork 5
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
[wasip2] incoming http handler #8
base: wasip2
Are you sure you want to change the base?
Conversation
Signed-off-by: Rajat Jindal <[email protected]>
I'll update this branch to use wasm-tools-go from bytecodealliance org as that repo has been moved. |
2bc1963
to
6af96c4
Compare
I believe this PR is ready for review. 🎉 thank you |
Adding an extra line to the response output gives me this error
|
Signed-off-by: Rajat Jindal <[email protected]>
Signed-off-by: Rajat Jindal <[email protected]>
Signed-off-by: Rajat Jindal <[email protected]>
6af96c4
to
cb3739a
Compare
Hi Adam, thanks for pointing this out. I have pushed a fix for it and it seems to be working now. |
Signed-off-by: Rajat Jindal <[email protected]>
cb3739a
to
9132e8b
Compare
Signed-off-by: Rajat Jindal <[email protected]>
3ca0f15
to
67b4c95
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.
@rajatjindal This is a great start and I'm excited to have something to iterate on. To keep it consistent with the other Spin repos I feel like we should stick to GitHub Actions rather than introducing Dagger at this time. Could we break out Dagger to a separate conversation from this PR?
w.Header().Set("Content-Type", "text/plain") | ||
w.Header().Set("foo", "bar") | ||
|
||
//TODO(rajatjindal): calling WriteHeader is required right now, need to fix before merging |
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 think this TODO can be removed?
yes absolutely. I will push updated PR. |
This PR is first of many to support wasip2 in spin go sdk.