You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I believe this is primarily a backend issue. When running AppInst/ClusterInst updates on the UI, it immediately triggers a popup showing "Creating" or "Updating" followed by a stream of messages as the work progresses. Such a thing does not happen with Cloudlet Update - it sits there with no response until the work is actually done, then it pops up the popup showing the "success" message. It really should create the popup immediately to show that work is happening. This should be triggered by the backend sending an acknowledgment of the state UPDATE_REQUESTED transitioning to UPDATING. But controller-data.go does not do so for cloudletChanged. This may need some work in the controller to pick off state changes from CloudletInfo to push to the callback/stream.
The text was updated successfully, but these errors were encountered:
I believe this is primarily a backend issue. When running AppInst/ClusterInst updates on the UI, it immediately triggers a popup showing "Creating" or "Updating" followed by a stream of messages as the work progresses. Such a thing does not happen with Cloudlet Update - it sits there with no response until the work is actually done, then it pops up the popup showing the "success" message. It really should create the popup immediately to show that work is happening. This should be triggered by the backend sending an acknowledgment of the state UPDATE_REQUESTED transitioning to UPDATING. But controller-data.go does not do so for cloudletChanged. This may need some work in the controller to pick off state changes from CloudletInfo to push to the callback/stream.
The text was updated successfully, but these errors were encountered: