-
Notifications
You must be signed in to change notification settings - Fork 94
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
Failed to POST issue status code 404 #88
Comments
Aha, so I tried with my main user account (jaraco) and that worked. Probably the issue is that |
I'm confused, were you not an admin on github or BB side? Hinting would be fine, but I wonder if there's an API we can hit that checks the permissions level of the user to actually know if that's the underlying issue or not? |
Github side. Yes, better would be to detect the necessary conditions directly. |
Also hit this as well -- fixed it by adding the |
I have the same problem, and Nikratio is an admin on the s3ql/s3ql repo - any idea?
|
@Nikratio can you open a new issue? I have a hunch this is a different issue (tbh, most likely user-error, but maybe not) than what this ticket is about |
I had the same issue with 404 response and it tuned out that copy & paste did not properly paste the auth token on windows so I had to type it in manually. |
I had this problem and needed to generate an auth token instead of password. |
Attempting to migrate a repo, I get the same error reported in later in #63:
I read the README, as suggested, but I don't see any relevant hint there. I double-checked that the import API docs linked from the README are don't indicate anything about the API having gone away.
404 means Not Found, and the URL that's not found is
https://api.github.com/repos/yougov/fuzzy/import/issues
.I'll be deleting that repo shortly, but I just confirmed that I'm able to create issues with the bb-migration user in that repo, so it's not an access issue. That account is not enabled for 2FA, so that shouldn't be an issue either.
The text was updated successfully, but these errors were encountered: