-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix panic in teams API when requesting members #19360
Conversation
CI is dead, that's the reason why the build fails. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If this code also exist in the release/1.16 branch it should be backported.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, you can't do both. I think you can just change only line 390.
I mean, what's the benefit? |
Co-authored-by: Lunny Xiao <[email protected]>
Both should work, but you should only chose one. You can't chose both, otherwise the slice will have 2 times elements and the first part are empty elements. |
* giteaoffical/main: Document 409 error returned by repos/migrate api (go-gitea#19376) Fix middleware function's placements for some `/user/...` (go-gitea#19377) Fix panic in teams API when requesting members (go-gitea#19360)
As title.
Should fix #19359
Do we backport API errors?Unnecessary in this case, error does not exist yet on v1.16 branch.
If I had to guess, one of the many
move xxx from models/ to models/xxx/
refactorings were the cause of this bug.