Cannot comment on issue #224

New issue

Closed

opened 2025-07-13 11:24:48 +02:00 by catfood · 2 comments

catfood commented

2025-07-13 11:24:48 +02:00

I have tried to comment on an issue with berg issue comment, but that command always returns a 404 error.

Steps to reproduce

Clone the repo from https://codeberg.org/catfood/Musicsystem
Try to comment on issue #1 via berg issue comment and selecting issue #1
Submit your comment

Observed behavior
Got a message with content 404 Not Found: IsErrIssueNotExist and the comment is not sent to the server

Expected behavior
The message is transferred to the server -> I can see it in my issue via the Codeberg web interface

I have tried to comment on an issue with `berg issue comment`, but that command always returns a 404 error. **Steps to reproduce** 1. Clone the repo from `https://codeberg.org/catfood/Musicsystem` 2. Try to comment on issue `#1` via `berg issue comment` and selecting issue `#1` 3. Submit your comment **Observed behavior** Got a message with content ` 404 Not Found: IsErrIssueNotExist` and the comment is not sent to the server **Expected behavior** The message is transferred to the server -> I can see it in my issue via the Codeberg web interface

timstoop referenced this issue from a pull request that will close it,

2025-10-11 19:04:48 +02:00

fix: use issue.number instead of issue.id in comment command #256

Aviac commented

2025-10-13 19:00:12 +02:00

Owner

This is pretty weird. I can reproduce it with codeberg, but in the integration tests reproducing it is a bit harder. I'm on it now though!

Aviac referenced this issue from a commit

2025-10-13 19:23:09 +02:00

fix: add regression tests and fix issue #224

Aviac referenced this issue

2025-10-13 19:23:15 +02:00

fix: add regression tests and fix issue #224 #258

Aviac referenced this issue from a commit

2025-10-13 19:23:22 +02:00

fix: add regression tests and fix issue #224 (#258)

Aviac closed this issue

2025-10-13 19:23:22 +02:00

Aviac commented

2025-10-13 19:28:02 +02:00

Owner

The issue should be fixed now. Also props for @timstoop for working on this and helping a lot! 💚

Short analysis of what was happening: Internally we used the .id of an issue which is global over the whole forgejo instance instead of the .number which is local to a repository and which is the number actually displayed before the # symbol. This is fixed now!

Thanks for reporting the issue and sorry it took so long to fix it. If you encounter anything else, please let me know. I'm more active again now!

The issue should be fixed now. Also props for @timstoop for working on this and helping a lot! 💚 --- Short analysis of what was happening: Internally we used the `.id` of an issue which is global over the whole forgejo instance instead of the `.number` which is local to a repository and which is the number actually displayed before the `#` symbol. This is fixed now! Thanks for reporting the issue and sorry it took so long to fix it. If you encounter anything else, please let me know. I'm more active again now!