Lann

We do currently set `SPIN_BIN_PATH` with `std::env::current_exe` for external commands. It might be nice to support something similar for `spin build` via `shellexpand` or `envsubst`, though perhaps we should go...

This repository is [not actively maintained](https://github.com/bytecodealliance/registry/blob/main/README.md). In fact we just un-archived it temporarily to fix a downstream dependency bug and I will now re-archive it to prevent further wasted effort...

I don't think there is any problem with an ugly error when you rudely interrupt the process 🤷 I am a bit confused about where the error is coming from...

Ohh so the `ctrlc` handler is just suppressing the default sigint handler but still causes the input to interrupt.

> That said, I'm still wary of the Ctrl+C handler. How will it affect parts of the program that are not performing user interaction? Another option here would be to...

Quick update on behalf of @calebschoepp: this seems to be a bug in `tracing-opentelemetry`. I believe he is still working on it.

> This is not an issue on the old Go and JS SDKs. How old?

https://github.com/bytecodealliance/wasm-pkg-tools/issues/13

We could maybe reduce confusion by type-checking that the file implements a `spin up`-able component before pushing.

> @lann is that in the context of #2556? Sure!