search

schneidmaster / gitreports.com

Git Reports is a free service that lets you set up a stable URL for anonymous users to submit bugs and other Issues to your GitHub repositories.
MIT License
134 stars 27 forks source link

Cant delete so cant update to fix #107

Closed schneidmaster closed 7 years ago

schneidmaster commented 7 years ago

Hi there was a 404 issue where when you created a new report you would get a 404 how ever i noticed the issues have been closed and tried now to use git reports and still get a 404 however im also unable to delete the report to get it to use patch

so either the 404 issue isnt resolved or a delete is needed so people can use the patch

moe-bugs commented 7 years ago

Hello, I think i'm running into the same issue. I keep getting 404's when trying to submit a bug report. It looks like the issue might be caused due to having so many duplicate users for some reason as seen here:

I'm not sure the exact steps i did to have so many duplicate users.

I think maybe a delete repository link would be good to have in general.

The git reports repository link is https://gitreports.com/repositories/13890

NYPD commented 7 years ago

It seems like if I change the form-action to moe-bugs rather than NYPD:

I still get a 404 when submitting, but the issue does make it to the actual repo.

I'm still not sure exactly what is going on. If there is any chance you can delete the moe-sounds repo from gitreports that would be great.

I'll have to keep poking around to see what is causing this.

schneidmaster commented 7 years ago

Hi. Your repositories are re-synced whenever you log out & log back in (which is why there's no delete button -- though perhaps there should be a manual re-sync button). Can you try that and see if it fixes your repository URL?

NYPD commented 7 years ago

I logged out and logged back in with my "issue reporter" account and my main account and that didn't seem to work. It seems every time I do that I re-add users to the git reports:

I'm afraid i'm still getting the 404s

MathijsBesten commented 7 years ago

I got the same issue, but only with one repo. I hope it can be fixed. I logged in and out, but it did not help

CheweyZ commented 7 years ago

Just found an anomalies so I've got 2 accounts one was for opening issues and one is the repo owner and when logged in as repo owner and disabled the reactivated repo it now works?

schneidmaster commented 7 years ago

I think I've finally cleared up this issue. GitHub used to always return 1 stable access token for each user, but they changed it to return a new access token on each login, so duplicate users were getting created. I changed the auth code to key off of username instead of access token and ran a migration to clean up duplicate users. Let me know if this clears things up for y'all.

NYPD commented 7 years ago

Works for me! thanks m8

CheweyZ commented 7 years ago

Works for me to THANKS!

schneidmaster commented 7 years ago

Thanks all. Closing this issue, feel free to open a new one if something else related comes up.