Improve error message for missing upgrade tag #608

Open
opened 2024-04-11 06:53:30 +00:00 by decentral1se · 1 comment
Owner

WARN[0011] no published versions in catalogue, trying local recipe repository
FATA[0011] '' is not supported (^$)

> WARN[0011] no published versions in catalogue, trying local recipe repository > FATA[0011] '' is not supported (^$)
decentral1se added the
bug
abra
labels 2024-04-11 06:53:30 +00:00
Member

Hehe, I was meaning to file a more ambitious issue but you beat me to it... 👍

To relatively inexperienced Operators, such as yours truly, these can be a bit vague and unclear (as most technical error msgs are 🤣).
I can think of a two ways to better handle this:

🧠 1. Add to Docs site Abra -> Error Messages

We can have longer explanations in the CLI. I feel like the best place for these msgs is on the Abra -> Trouble or perhaps a new page called Error Messages

🤯 2. Provide links to docs in Terminal after Error Message

user@dev:~$ abra app upgrade sextant.eotl.supply
WARN[0007] no published versions in catalogue, trying local recipe repository 
FATA[0007] '' is not supported (^$)

To solve this read this help page: 

https://docs.coopcloud.tech/abra/trouble/#ERR-0007

It's probably not feasible for every real bug / stack trace... but known cases seems possible to me?!

Hehe, I was meaning to file a more ambitious issue but you beat me to it... 👍 To relatively inexperienced *Operators*, such as yours truly, these can be a bit vague and unclear (as most technical error msgs are 🤣). I can think of a two ways to better handle this: 🧠 **1. Add to Docs site `Abra -> Error Messages`** We can have longer explanations in the CLI. I feel like the best place for these msgs is on the [Abra -> Trouble](https://docs.coopcloud.tech/abra/trouble) or perhaps a new page called `Error Messages` 🤯 **2. Provide links to docs in Terminal after Error Message** ``` user@dev:~$ abra app upgrade sextant.eotl.supply WARN[0007] no published versions in catalogue, trying local recipe repository FATA[0007] '' is not supported (^$) To solve this read this help page: https://docs.coopcloud.tech/abra/trouble/#ERR-0007 ``` It's probably not feasible for every real bug / stack trace... but known cases seems possible to me?!
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: coop-cloud/organising#608
No description provided.