Skip to content
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

Migration failure during reaction migration from gitea (#13344) #13346

Merged

Conversation

techknowlogick
Copy link
Member

  • Migrating reactions is just not that important

A failure during migrating reactions should not cause failure of
migration.

Signed-off-by: Andrew Thornton art27@cantab.net

  • When checking issue reactions check the correct permission

Signed-off-by: Andrew Thornton art27@cantab.net
Credit @zeripath

* Migrating reactions is just not that important

A failure during migrating reactions should not cause failure of
migration.

Signed-off-by: Andrew Thornton <art27@cantab.net>

* When checking issue reactions check the correct permission

Signed-off-by: Andrew Thornton <art27@cantab.net>

Co-authored-by: techknowlogick <techknowlogick@gitea.io>
@techknowlogick techknowlogick added this to the 1.12.6 milestone Oct 29, 2020
@techknowlogick techknowlogick added type/bug topic/repo-migration Migrate repos from other platforms to Gitea, or from Gitea to them labels Oct 29, 2020
@techknowlogick
Copy link
Member Author

Closing this as Gitea migration isn't in 1.12

@GiteaBot GiteaBot added the lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. label Oct 29, 2020
@zeripath
Copy link
Contributor

No but the reactions API is and it is those fixes which needs to be backported

@techknowlogick
Copy link
Member Author

Ah yes.

Copy link
Contributor

@zeripath zeripath left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is missing the issue comment reactions changes

@techknowlogick
Copy link
Member Author

@zeripath those aren't included because modules/migrations/gitea_downloader.go doesn't exist in release/v1.12.

@techknowlogick techknowlogick added the status/blocked This PR cannot be merged yet, i.e. because it depends on another unmerged PR label Oct 29, 2020
@techknowlogick
Copy link
Member Author

Adding blocked label

@zeripath
Copy link
Contributor

Nope it's not that - unfortunately both the original and the 1.13 backport were missing one final change that I thought I had pushed up.

Line 60 of the issue_reaction.go has the same bug and also needs to be fixed.

Unfortunately my final push to go-gitea#13344 didn't register - or I failed to push it properly. GetIssueCommentReactions in routers/api/v1/repo/issue_reaction.go also makes the same mistake.
@GiteaBot GiteaBot added lgtm/need 1 This PR needs approval from one additional maintainer to be merged. and removed lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. labels Oct 29, 2020
@zeripath zeripath removed the status/blocked This PR cannot be merged yet, i.e. because it depends on another unmerged PR label Oct 29, 2020
@GiteaBot GiteaBot added lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. and removed lgtm/need 1 This PR needs approval from one additional maintainer to be merged. labels Oct 29, 2020
@techknowlogick techknowlogick merged commit 2123195 into go-gitea:release/v1.12 Oct 29, 2020
@techknowlogick techknowlogick deleted the backport-13344-12 branch October 29, 2020 18:43
@go-gitea go-gitea locked and limited conversation to collaborators Dec 14, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. topic/repo-migration Migrate repos from other platforms to Gitea, or from Gitea to them type/bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants