Offline support needs more work #471
Loading…
x
Reference in New Issue
Block a user
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?
Finally got to the core of coop-cloud/organising#432 and it's related to the changes around trying to make
abra
more resilient to git.coopcloud.tech downtime. I'm reverting parts of the original implementation now to get backabra
ops to their original state.Reviewing the code, there are actually very few cases when offline is possible considering our reliance on collective operations from several co-operatives. Sometimes you only want to fallback to offline when the network is not up and try to salvage something if possible. The code tries to make that decision for us currently but it needs to be refined.
I think perhaps a
--offline
flag would be a better approach, to trigger it. Then it is more explicit. For the clear cut cases where git.coopcloud.tech is not needed, i.e. streaming logs, those can do "offline" by default still.Previous discussion: coop-cloud/organising#292
We're still resilient to the catalogue going offline, that is unrelated to these changes.