Codeberg/Community
54
325
Fork
You've already forked Community
12

Creating Issue with certain letter combinations in title yields Error 500 #241

Closed
opened 2020年08月27日 18:02:01 +02:00 by lhinderberger · 4 comments

So here's a rather odd one:

I created a repo titled "test-a" (lhinderberger/test-a) and now I try to create issues there. That works fine, unless the issue's title is three or less letters long and contains at least one letter. In that case it yields Error 500.

Creating issues in another repository called "test-b" works fine with all names.

Maybe someone with access to the error logs can give some insights on what went wrong. I'll leave the test repo online until we know what's going on.

I'd like to create an issue over at Gitea, but I'm afraid I can't provide all the technical information required by their issue template.

Even worse, that happened while researching another bug in the issue tracker that also yields Error 500 - yikes!

So here's a rather odd one: I created a repo titled "test-a" (lhinderberger/test-a) and now I try to create issues there. That works fine, unless the issue's title is three or less letters long and contains at least one letter. In that case it yields Error 500. Creating issues in another repository called "test-b" works fine with all names. Maybe someone with access to the error logs can give some insights on what went wrong. I'll leave the test repo online until we know what's going on. I'd like to create an issue over at Gitea, but I'm afraid I can't provide all the technical information required by their issue template. <sub>Even worse, that happened while researching another bug in the issue tracker that also yields Error 500 - yikes!</sub>
lhinderberger changed title from (削除) Creating Issue with three-or-less-letter titles yields Error 500 in a repo named "test-a" (削除ここまで) to Creating Issue with certain letter combinations in title yields Error 500 2020年08月27日 22:16:13 +02:00

I managed to create some issues with three-letter combinations. But not all work. ggg and iii yield an error, but hhh, zzz and jjj work...

After trying again, iii succeeded once. Retrying yielded errors again. I couldn't yet figure out a pattern.

I managed to create some issues with three-letter combinations. But not all work. `ggg` and `iii` yield an error, but `hhh`, `zzz` and `jjj` work... After trying again, `iii` succeeded once. Retrying yielded errors again. I couldn't yet figure out a pattern.

There is no pattern, you just created too many issues in too little time.

There is no pattern, you just created too many issues in too little time.

You're right, my apologies for behaving like a spam bot 🤖 😄

You're right, my apologies for behaving like a spam bot 🤖 😄
lhinderberger 2020年08月28日 07:16:57 +02:00

well this feature codeberg has should be implemented in gitea, and if it is it also will tell you a better error message ;)

throu I cant say when this is happen

well this feature codeberg has should be implemented in gitea, and if it is it also will tell you a better error message ;) throu I cant say when this is happen
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility

Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug

Something is not working the way it should. Does not concern outages.
bug
infrastructure

Errors evidently caused by infrastructure malfunctions or outages
Codeberg

This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome

Please join the discussion and consider contributing a PR!
docs

No bug, but an improvement to the docs or UI description will help
duplicate

This issue or pull request already exists
enhancement

New feature
infrastructure

Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal

An issue directly involving legal compliance
licence / ToS

involving questions about the ToS, especially licencing compliance
please chill
we are volunteers

Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
public relations

Things related to Codeberg's external communication
question

More information is needed
question
user support

This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
s/Forgejo

Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration

Migration related issues in Forgejo
s/Pages

Issues related to the Codeberg Pages feature
s/Weblate

Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker

Woodpecker CI related issue
security

involves improvements to the sites security
service

Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
upstream

An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
wontfix

Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 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
Codeberg/Community#241
Reference in a new issue
Codeberg/Community
No description provided.
Delete branch "%!s()"

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?