David Edler

Thanks for confirming it is not a code bug. The reason for the bug yesterday might be, that microcloud is changing network configuration after setting it up. I think this...

We recently merged a way to [retry for this exact error](https://github.com/canonical/lxd-ui/pull/927). So if the network is unstable, the UI will try to reload instead of crashing right away.

Thank you for the request, adding special device support was not yet on our roadmap. It sounds quite straightforward, we'll consider adding it. You can already configure Nvidia GPUs in...

GPU support landed recently and is available now on the latest/edge channel of the LXD-UI. Though we opted to not support the MIG configuration in the UI as it is...

The used by concept from storage does not directly apply to networks. Because networks can be referenced from two different types: instances and profiles. There might be a way to...

> These components are now available in react-components: https://canonical.github.io/react-components/?path=/docs/components-applicationlayout--docs. > > There are some small changes since this PR was created, but if someone would like to take over this...

Thank you for reaching out. Is this a UI problem, or do you use the command line? In the later case, please report to [LXD directly](https://github.com/canonical/lxd-ui/issues/new), as this is the...

Linked the wrong PR initially, this is the right one: https://github.com/canonical/lxd-ui/pull/512 It seems to me some behaviour of LXD on the network change is triggering chrome to cancel running requests....

> @edlerd what OS version are you using with Chrome btw? OS: Ubuntu 22.04.3 LTS Chrome: Version 118.0.5993.117 (Official Build) (64-bit)

I can still reproduce it today:  Though priority is not so high, as we have a workaround in the UI. We check if the request was successful with a...