-
Notifications
You must be signed in to change notification settings - Fork 174
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
https://api.bitbucket.org/1.0/user/repositories endpoint stopped working #71
Comments
This seems that "fixes" the issue with Faraday gem raising "Faraday::ConnectionFailed: end of file reached". Remove this commit when this issue bitbucket-rest-api#71 gets resolved.
@jimmykarily Just as a matter of interest, have you tried this with OAuth2? |
@zedlang I'm afraid I don't remember exactly what else I tried. It's been a while since I last worked on this. |
@jimmykarily Ah, I just wondered. I couldn't reproduce what you were getting but I was using OAuth2 rather than OAuth and I wondered if it might be something to do with that |
Has anyone tried using the 2.0 version of Bitbucket's API? I am also getting this timeout error. https://bitbucket.org/site/master/issues/12051/request-timeout-when-getting-branches-api |
Something strange happens with this endpoint.
Net::HTTP throws EOFError which results in the following exception being raise from Faraday:
To reproduce simply run the following on latests master:
The strange thing is that if I replace the API url from "https://api.bitbucket.org" to "https://bitbucket.org/api" it works. I compared the two requests and they are the same (except for the different url). This must have happened today because yesterday I'm sure it was working.
To make it more complicated, both urls behave the same when I use Postman (they both work) so I can't open an issue on Bitbucket for this. I turned debugging on with
set_debug_output($stdout)
on Net::HTTP and the only difference is the error:Failing debug output:
Working debug output:
(and the rest is the repository results in JSON format)
It seems that the first case is retried once before exiting with error.
The text was updated successfully, but these errors were encountered: