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
Create a new scenario, in the modal that appears, specify the topology from step 1
Navigate back to project details
Attempt to delete your topology
Expected
A warning that it cannot be deleted because it's referenced in a portfolio/scenario, and that either the scenario must be deleted first. (Or the entire portfolio the scenario is in.)
In the network tab I should something more like a 400 (bad request) or 403 (forbidden).
Actual
Nothing happens in the UI, but in Network tab I can see a 500, internal server error.
The text was updated successfully, but these errors were encountered:
SethFalco
changed the title
Internal server error when attempting to delete topology references in portfolio
Internal server error when attempting to delete topology referenced in scenario
Mar 10, 2023
This change fixes#135 which showed that trying to delete a topology
used by a scenario would result in nothing happening in the UI and a 500
error being returned by the server. We check whether a scenario still
references the topology and show an error to the user if that happens.
Fixes#135
This pull request addresses several issues that have been reported for the OpenDC web UI.
## Implementation Notes ⚒️
* Update dependencies for web UI
* Inform user when deleted topology is still used
* Do not offset hover layer after dragging
* Fix access to machines on lower shelves
* Do not allow selection of empty unit
* Fix rack deletion
Fixes#135, #136, #137, #138, #139
Steps to reproduce
Expected
A warning that it cannot be deleted because it's referenced in a portfolio/scenario, and that either the scenario must be deleted first. (Or the entire portfolio the scenario is in.)
In the network tab I should something more like a 400 (bad request) or 403 (forbidden).
Actual
Nothing happens in the UI, but in Network tab I can see a 500, internal server error.
The text was updated successfully, but these errors were encountered: