Vaughn Dice

Doesn't look like this will make Spin 3.0 so untethering...

The foundation of this feature has been added in https://github.com/fermyon/spin/pull/2524. Wanted to cross-reference here as further work continues (eg around the `A component in Spin is a Wasm module together...

Re: https://github.com/fermyon/spin/issues/2552#issuecomment-2383994519, the grain and zig templates run fine w/ Spin 3 for me (well, Spin from `main` as of writing). However, the [php template](https://github.com/fermyon/spin/tree/main/templates/http-php) does not. Can we update?...

Doesn't appear to include any more information, alas: ``` $ spin up -e WASMTIME_BACKTRACE_DETAILS=1 Logging component stdio to ".spin/logs/" Serving http://127.0.0.1:3000 Available Routes: php-template: http://127.0.0.1:3000 (wildcard) 2024-10-30T21:25:35.791411Z ERROR spin_trigger_http::server: Error...

No luck :( ``` $ WASMTIME_BACKTRACE_DETAILS=1 spin up Logging component stdio to ".spin/logs/" Serving http://127.0.0.1:3000 Available Routes: php-template: http://127.0.0.1:3000 (wildcard) 2024-10-30T21:40:21.868509Z ERROR spin_trigger_http::server: Error processing request: error while executing at...

Was preparing to remove the php template when I noticed that we have [test coverage for this one](https://github.com/fermyon/spin/blob/c02196882a336d46c3dd5fcfafeed45ef0a4490e/tests/integration.rs#L652-L665) -- and it appears to be passing: `test integration_tests::http_php_template_smoke_test ... ok` from...

D'oh! Thanks @lann. What's our plan with this issue? Keep open for tracking? Close out now that the implementation work is in?

@lann now that the [grain template](https://github.com/fermyon/spin/blob/d83330147584f87618dcbbb75d6422b660f3c39d/templates/http-grain/content/spin.toml#L16) and [language page](https://developer.fermyon.com/wasm-languages/grain) have been updated to use `--release`, do we still want to keep this open? Untether from Spin 3.0 if so?

> Could someone from @fermyon/spin-core-maintainers enable CI and merge this? CI didn't run as the base branch is still `factors`. Perhaps rebase this on `main`? Then CI should run.

@calebschoepp is there any overlap with this request and current/forecasted telemetry work?