-
Notifications
You must be signed in to change notification settings - Fork 6
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
Spin Apps trap at runtime when build with TinyGo 0.35.0
#10
Comments
There is an updated template with an 0.35-friendly build command in the Spin repo. See fermyon/spin#2977 for the changes. |
That's strange, I updated all templates earlier today and was still getting this error. I'll check again tomorrow, however I'm pretty confident that I've updated templates from fermyon/spin as well. Thanks @itowlson |
You might be on a released build of Spin? In that case it picks up the "stable templates known to work with that version" snapshot; pass |
Will try and report back! |
I hit the same error and upgrading the templates fixed it for me. The build command you want is
|
Also, I just made the changes in CI for a working example #12 |
Updating the build command in templates fixed this for me as well. |
I've installed
tinygo
using Homebrew on my Apple Silicon Mac.As the tap is not versioned, I recently updated all my installed formulas (including
tinygo
) which results in me having0.35.0
right now.Although I could compile different Spin apps without any error, every app traps at runtime - when receiving incoming HTTP requests - and I receive the following error:
Steps to repro
0.35.0
spin new -t http-go -a hello-spin
) or take an existing Spin app created using thehttp-go
template (haven't tested other triggersspin b
)spin up
)curl localhost:3000/
)curl
won't receive anything and thespin
process should display an error similar to the one shown aboveWorkaround
I uninstalled
tinygo
from my machine and installed tinygo0.34.0
manually. After recompiling the Spin app with0.34.0
, I was able to successfully invoke the Spin app.The text was updated successfully, but these errors were encountered: