Add better handling upon backend crashes #2
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
After a backend crashes, we need to have better error handling. Perhaps we could automatically restart all the auto-start proxies?
Due to the architecture of how the backend works, we can't just restore the state like nothing happened. The best option currently is doing the above.
Fixed in
7837334361
.