Closed dfntlynotjorn closed 8 months ago
Thanks for filing. I can repro this on at least one of my apps as well. Definitely appears to be domain-related (looking at cloud_plugin::commands::apps::domains_current_and_in_progress::hd4e7090418a2a8cb
from the stack trace). In fact, it has been awhile since I last deployed/configured this app, but I believe I did at one point configure a custom domain, or had attempted configuration of one.
Well, I appear to have hit it with a freshly-deployed app, so scratch my impression that it only affects apps w/ custom domain configuration:
$ spin cloud apps info new-rust
Warning: You're using a pre-release version of Spin (2.4.0-pre0). This plugin might not be compatible (supported: >=1.3). Continuing anyway.
thread 'main' panicked at src/commands/apps.rs:107:35:
index out of bounds: the len is 0 but the index is 0
stack backtrace:
0: rust_begin_unwind
at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/panicking.rs:645:5
1: core::panicking::panic_fmt
at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/core/src/panicking.rs:72:14
2: core::panicking::panic_bounds_check
at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/core/src/panicking.rs:208:5
3: cloud_plugin::commands::apps::domains_current_and_in_progress
4: cloud_plugin::main::{{closure}}
5: tokio::runtime::park::CachedParkThread::block_on
6: tokio::runtime::context::runtime::enter_runtime
7: tokio::runtime::runtime::Runtime::block_on
8: cloud_plugin::main
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
Stemming from the following line in apps.rs
That implies there are no channels for the app - I thought there was always exactly one channel. @bacongobbler any idea why that might be?
I thought there was always exactly one channel
This used to be the case. Nowadays apps are created without a channel.
Looks like spin cloud apps info
relies on the app having at least one channel to fetch the "app subdomain". This can now be fetched through the subdomain
field. #185 addresses this.
I'll go check and see if there are other locations in the cloud plugin that are still relying on one channel being required.
I checked and this appears to be the only location requiring the use of channels.
Thanks for identifying this issue, @dfntlynotjorn!
We've pushed a fix and released it under v0.7.1. You can fetch the latest release by calling spin plugins update && spin plugins upgrade
.
Thanks again for the report!