itowlson

@lann The "last build" is a heuristic effort to mitigate the "I built Profile A then ran Profile B and none of my changes are showing up" problem discussed on...

I just re-read my previous message and noticed "The point about failed builds is valid" which I realised could come across as "not like your other point," which was not...

@tschneidereit Comparison to the draft SIP (https://github.com/spinframework/spin/pull/3075): * No support for `SPIN_PROFILE` environment variable * No support for selecting the `debug` profile with `--debug` * No aliasing of `release` to...

> > * Allows pushing non-default profile > > By "allows" do you mean "will push whatever was built last", or "adds a --profile option to the CLI subcommand"? If...

I would dearly love to use `clap_complete`. Unfortunately: 1. `clap_complete` doesn't have the vocabulary to express things like "list of templates" or "list of plugins." It only allows the `ValueHint`...

In shock news, `completely` has also broken my heart. The trouble is that for parameter completion it relies on a first-last pattern, e.g. `spin up*--from`, which works great for the...

This seems like it would be trading space for time - reduce memory footprint but need to reload/recompile idle components. Did the user share any further info on the memory...

Thanks for the extra info! It seems like the first step would be to benchmark how much memory the components are occupying compared to how much memory an inactive Spin...

Given that wasi-keyvalue is only in Phase 2 at the moment, this feels to me too far away to be planning for right now.

@jandubois The request here seems to be the result of a chain of challenges unfolding from "since I can't use the cli to query if templates and plugins have been...