Codeberg/Community

Fork 12

Error 500 when removing repo #632

New issue

Closed

opened 2022-06-03 12:12:15 +02:00 by fnetX · 7 comments

fnetX commented

2022-06-03 12:12:15 +02:00

Owner

We sometimes see error 500 screens when removing repos. Log:

2022/06/03 12:06:05 .../web/repo/setting.go:722:SettingsPost() [E] DeleteRepository: repository does not exist [id: 37385, uid: 39959, owner_name: , name: ]
2022/06/03 12:06:05 .../web/repo/setting.go:722:SettingsPost() [E] DeleteRepository: repository does not exist [id: 37385, uid: 39959, owner_name: , name: ]

...

We sometimes see error 500 screens when removing repos. Log: ~~~ 2022/06/03 12:06:05 .../web/repo/setting.go:722:SettingsPost() [E] DeleteRepository: repository does not exist [id: 37385, uid: 39959, owner_name: , name: ] 2022/06/03 12:06:05 .../web/repo/setting.go:722:SettingsPost() [E] DeleteRepository: repository does not exist [id: 37385, uid: 39959, owner_name: , name: ] ~~~ ...

fnetX added the

bug

s/Forgejo

labels

2022-06-03 12:12:15 +02:00

Gusted commented

2022-06-04 20:33:08 +02:00

Owner

when removing repos

How? Via the API? Via the moderation tool? Via the Web UI?

> when removing repos How? Via the API? Via the moderation tool? Via the Web UI?

fnetX commented

2022-06-04 22:09:26 +02:00

Author

Owner

web ui

Gusted commented

2022-06-04 23:33:37 +02:00

Owner

The code itself looks good(no codeberg-specific code 😄) is there anything special with these repositories?

The code itself looks good(no codeberg-specific code :smile:) is there anything special with these repositories?

ashimokawa commented

2022-06-04 23:57:15 +02:00

Owner

No, I had error 500 with (IIRC) empty repos also. also with some of mine.

All are gone afterwards though.
Seems random.

I am not sure if @fnetX pasted the "correct" log - there might have been a 404 afterwards.

No, I had error 500 with (IIRC) empty repos also. also with some of mine. All are gone afterwards though. Seems random. I am not sure if @fnetX pasted the "correct" log - there might have been a 404 afterwards.

Gusted commented

2022-06-05 00:00:18 +02:00

Owner

Maybe the request is made twice? There are some issues with Gitea of that happening.

ashimokawa commented

2022-06-05 00:07:53 +02:00

Owner

@Gusted

When I double click I get 404 at least ;)

But good point about a maybe even almost simultanious request.

We had a race condition and random 500 when adding muliple labels to issues before. So maybe something similar.

@Gusted When I double click I get 404 at least ;) But good point about a maybe even almost simultanious request. We had a race condition and random 500 when adding muliple labels to issues before. So maybe something similar.

👍 1