worknenjoy/gitpay

Cannot import issue "Error to update issue"

Closed this issue · 6 comments

Hi there,

I want to fund some issues: mono/mono#14412 and keepassxreboot/keepassxc#2281.

When I click on "import issue" and input any of these two issues url, it shows "Error to update issue".

https://github.com/worknenjoy/gitpay/issues/1083 also fails

@Zahrun, we have solved it for now; some of the issues already exist, and we have better feedback now. I think there's a case when the Github API limit is exceeded, and now we have a specific notification for it. We will work to better handle Github API calls or even not depend on them if they're not available in the near future.

Can you test again?

FireShot Capture 001 - Gitpay - Bounties for git issues solved - gitpay me

I found under my profile the 3 issues were already created. I deleted the one related to #1083 and then created it again. Tried that on mobile the other day and it failed with "actions.task.issues.error.notfound". Maybe deleting and recreating is not supported. Now from laptop I tried again and got "Error to update issue" then refreshed the my profile and it was in the list, created "a few seconds ago".
I cleared cookies and site data, reloaded the page, added a different issue https://github.com/pacstall/chaotic-PPR/issues/5, and got again "Error to update issue". Refreshed the profile, and the issue is listed there as actually created.

I found under my profile the 3 issues were already created. I deleted the one related to #1083 and then created it again. Tried that on mobile the other day and it failed with "actions.task.issues.error.notfound". Maybe deleting and recreating is not supported. Now from laptop I tried again and got "Error to update issue" then refreshed the my profile and it was in the list, created "a few seconds ago". I cleared cookies and site data, reloaded the page, added a different issue https://github.com/pacstall/chaotic-PPR/issues/5, and got again "Error to update issue". Refreshed the profile, and the issue is listed there as actually created.

Thanks for reporting, @zahru, I will work to fix those bugs.

Hey @Zahrun, thanks again for catching all bugs and reporting to us; now I believe these bugs are solved on my last commits: eb1ed4c 05fb7a2

Now we verify that the API limit was explicitly exceeded, and the error scenarios with the import process you described were mostly fixed, as the not found and error on update cases.

Let me know if there's any issue; otherwise, we can close this one 🤞

Issue created successfully on Gitpay
This issue was imported already

It seems to work, very nice, thank you