Non-existing recipe breaks app ls -S --chaos #796

New Issue

2026-03-05T10:57:25Z

iexos commented

2026-03-05 10:57:25 +00:00

As a follow-up to #795 I tried with --chaos but now another wild thing happens:

$ abra app ls -S -s <server> --debug --chaos
[...]
DEBU <git/clone.go:49> git clone: https://git.coopcloud.tech/coop-cloud/snipe-it.git
DEBU <git/clone.go:59> git clone: /home/user/.abra/recipes/snipe-it cloned successfully
DEBU <git/clone.go:68> git clone: main branch failed, attempting master branch
FATA <app/list.go:117> .env.sample for snipe-it couldn't be read: open /home/user/.abra/recipes/snipe-it/.env.sample: no such file or directory

That recipe does not seem to exist and thus cannot be successfully cloned. The recipe dir only contains a non-functional .git/ dir.

Curiously, adding --offline doesn't change anything about this, it still tries cloning and claims success.

As a follow-up to #795 I tried with `--chaos` but now another wild thing happens: ``` $ abra app ls -S -s <server> --debug --chaos [...] DEBU <git/clone.go:49> git clone: https://git.coopcloud.tech/coop-cloud/snipe-it.git DEBU <git/clone.go:59> git clone: /home/user/.abra/recipes/snipe-it cloned successfully DEBU <git/clone.go:68> git clone: main branch failed, attempting master branch FATA <app/list.go:117> .env.sample for snipe-it couldn't be read: open /home/user/.abra/recipes/snipe-it/.env.sample: no such file or directory ``` That recipe does not seem to exist and thus cannot be successfully cloned. The recipe dir only contains a non-functional `.git/` dir. Curiously, adding `--offline` doesn't change anything about this, it still tries cloning and claims success.

decentral1se added the bug label 2026-03-05 11:02:57 +00:00

decentral1se commented

2026-03-05 11:28:24 +00:00

I believe this is a result of passing -S and the work done in #737. If you want to query the real status of the deployment then abra has to investigate the recipe config to understand which services you are interested in.

Where is the snipe-it recipe? If you have a local copy of it in $ABRA_DIR/recipes then it will work ofc but I guess abra is assuming it is on the usual recipe listing. If you don't have it published then I would assume it's your responsibility to put it where abra expects it to be locally?

Curious what further details you can provide and how you'd improve this situation!

I believe this is a result of passing `-S` and the work done in https://git.coopcloud.tech/toolshed/abra/issues/737. If you want to query the real status of the deployment then `abra` has to investigate the recipe config to understand which services you are interested in. Where is the `snipe-it` recipe? If you have a local copy of it in `$ABRA_DIR/recipes` then it will work ofc but I guess `abra` is assuming it is on the usual recipe listing. If you don't have it published then I would assume it's your responsibility to put it where `abra` expects it to be locally? Curious what further details you can provide and how you'd improve this situation!

iexos commented

2026-03-05 11:40:41 +00:00

I don't have the recipe at all, someone else on this server has been hacking on it. I don't have anything to do with that.

So what I would like is for the app to appear as an error state within the list so I can still see the rest. And print a warning or error message that this recipe was not found/does not exist.

I don't have the recipe at all, someone else on this server has been hacking on it. I don't have anything to do with that. So what I would like is for the app to appear as an error state within the list so I can still see the rest. And print a warning or error message that this recipe was not found/does not exist.

👍 1

decentral1se added this to the Abra "next" project 2026-03-05 14:12:23 +00:00

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: toolshed/abra#796

Non-existing recipe breaks app ls -S --chaos #796

Non-existing recipe breaks `app ls -S --chaos` #796