itowlson
itowlson
Apologies for the pedantry but... the specific Spin output lines you quote are _not_ logs - they are written directly as actionable information for the user. They should not receive...
FWIW Spin logs appear like this, at least on Linux:  The top stanza is logs (only errors by default). Then the startup message, and then the application log. I...
I'm not in favour of decorating normal user interaction this way. If we're going to decorate stuff, it should be the stuff you only use for diagnostics when something's gone...
What version of Spin are you on, please? Platform may require an older version of Spin but either way there is clearly something wrong with that user interface!
`spin login` in Spin 1.3 hands off to the `spin cloud` plugin, which doesn't include support for Platform. I believe you'll need to use Spin 1.2 or earlier to deploy...
@karthik2804 on that I was guided by https://github.com/fermyon/spin/issues/2146#issuecomment-2000217985 but for sure I do not know enough either way
Given #2471 and #2473, is it okay to close this as addressed via the port 0 workaround?
@dicej Is this something @dlozina could access by wit-bindgen-ing the wasi-http outgoing-handler interface directly into their project, or is it something the Spin host would need to (invisibly) do?
Client supports v5 via a module (https://docs.rs/rumqttc/latest/rumqttc/v5/index.html) so in theory this should be reasonably easy. @calebschoepp Would we need to support v3 and v5 alongside each other, or would v5...