crash when running commands on the "default" context for local operation #175
Labels
No Label
abra
abra-gandi
awaiting-feedback
backups
bug
build
ci/cd
community organising
contributing
coopcloud.tech
democracy
design
documentation
duplicate
enhancement
finance
funding
good first issue
help wanted
installer
kadabra
performance
proposal
question
recipes.coopcloud.tech
security
test
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/organising#175
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
Steps to reproduce
abra server add default
abra server init default
Describe the expected behavior
Step 3 does nothing because the default context already exists.
Step 4 creates
~/.abra/servers/default
Describe the current behavior
3-5 all crash with variations of:
Additional information
Think it's 0.14-alpha?
Hmmmm right yep. I think we have some code in places that just skips the
default
context but now I realise that yes, this does break theabra
on the server mode of use. We should fix that.As an aside, is
abra server add default
intuitive for "run things on this machine locallyabra
"? Perhaps we'd want to use another keyword like "local"? We don't have to use what Docker uses.I wasn't able to reproduce the stack trace on step 3, I got:
It does explode on step 4 indeed. On the bash impl. I see this:
And I can't remember being able to manage the local machine but I thought it did work?
abra server add
assumes a working DNS entry and SSH server for<domain>
(if you runabra server add -h
). So what kind of UI/UX do we expect here?abra server add --local mymachine
could be a thing? Then we can check Docker is installed locally, create all the~/.abra/...
machinery and mark it for local connections.abra server add --local mymachine
seems workable then!Discussed in Autonomic internal co-work.
Fixed in
3688ea9d69
.