Better error messages #448

Cyborus commented 2026年05月01日 22:32:28 +02:00

Issue

A lot of the error messages in fj are unhelpful, or even misleading. This issue is to track the improvement of them all in one place. Error messages that need work can be brought up in a comment on this issue, and they'll be added to the list in the issue body.

Note that this is different from #112. That is about the appearance of errors, while this is about the content of them.

---

1. no repo info specified
   1. when no host information is found. It should say that it could not find the Forgejo instance and how to supply that.
   2. when the repository name cannot be found, but the host can.
   3. when in detached HEAD state. It should explain that it cannot find the remote without a branch.
2. unknown remote object format 'sha256';. git2 doesn't support SHA256 repos. It should explain that they aren't supported and to use git clone instead.

(more to be added as they come up)

Code of Conduct

• I agree to act in accordance with the CoC & AI Agreement.
• This issue was not generated by an LLM, even in part.

### Issue A lot of the error messages in `fj` are unhelpful, or even misleading. This issue is to track the improvement of them all in one place. Error messages that need work can be brought up in a comment on this issue, and they'll be added to the list in the issue body. Note that this is different from #112. That is about the appearance of errors, while this is about the content of them. --- 1. [ ] `no repo info specified` 1. [ ] when no *host* information is found. It should say that it could not find the Forgejo instance and how to supply that. 2. [ ] when the repository name cannot be found, but the host can. 3. [ ] when in detached HEAD state. It should explain that it cannot find the remote without a branch. 2. [ ] `unknown remote object format 'sha256';`. `git2` doesn't support SHA256 repos. It should explain that they aren't supported and to use `git clone` instead. (more to be added as they come up) ### Code of Conduct - [x] I agree to act in accordance with the CoC & AI Agreement. - [x] This issue was not generated by an LLM, even in part.

SLASHLogin commented 2026年05月17日 17:52:21 +02:00

When repo is cloned using SSH with custom port, the tool incorrectly converts it to HTTPS. (削除) SSH sends header, thus the following SSL error. Message could at least display the formatted URL (削除ここまで):

Edit: I've never noticed the error message. But at least maybe we should handle this case, or make a suggestion to set the alias, when the port is not standard.

$ fj actions tasks
Error: error sending request for url (https://forgejo.slashlogin.dev:30022/api/v1/repos/SLASHLogin/forgejo-cli/actions/tasks?page=1&limit=20)
Caused by:
 0: client error (Connect)
 1: error:0A00010B:SSL routines:tls_validate_record_header:wrong version number:ssl/record/methods/tlsany_meth.c:77:
 2: error:0A00010B:SSL routines:tls_validate_record_header:wrong version number:ssl/record/methods/tlsany_meth.c:77:
Location:
 src/actions.rs:162:15

The error is produced at: https://codeberg.org/forgejo-contrib/forgejo-cli/src/branch/main/src/actions.rs#L162-L170

Not sure if this fits into the message improvement task.

When repo is cloned using SSH with custom port, the tool incorrectly converts it to HTTPS. ~~SSH sends header, thus the following SSL error. Message could at least display the formatted URL~~: Edit: I've never noticed the error message. But at least maybe we should handle this case, or make a suggestion to set the alias, when the port is not standard. ``` $ fj actions tasks Error: error sending request for url (https://forgejo.slashlogin.dev:30022/api/v1/repos/SLASHLogin/forgejo-cli/actions/tasks?page=1&limit=20) Caused by: 0: client error (Connect) 1: error:0A00010B:SSL routines:tls_validate_record_header:wrong version number:ssl/record/methods/tlsany_meth.c:77: 2: error:0A00010B:SSL routines:tls_validate_record_header:wrong version number:ssl/record/methods/tlsany_meth.c:77: Location: src/actions.rs:162:15 ``` The error is produced at: https://codeberg.org/forgejo-contrib/forgejo-cli/src/branch/main/src/actions.rs#L162-L170 Not sure if this fits into the message improvement task.