-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
GetRestApis failed PROTOCOL_ERROR #1022
Comments
Hello @smugcloud, thank you for reaching out to us. This was a bug that has been addressed in later version of the SDK. Can you try updating to latest and see if this resolves the issue? |
I'm also getting the same error today. This was, very, recently working for me. Something changed in the last day or so. I just updated to the latest package here, but it didn't seem to fix the issue. |
@tmaiaroto, interesting, we haven't changed anything regarding requests in the last week or so. I wonder if this is a service issue. I'll reach out to them and see if anything looks suspicious. Are you also using the |
Yes, I am (for reference: https://github.com/tmaiaroto/aegis/blob/master/cmd/up.go#L510). I'm thinking service issue as well given how frequently it was just working. It has been a few hours, but I'll also check again tomorrow. |
Thanks @xibz. I mistakenly left off the After properly upgrading, it is working again. |
Also working for me now. |
Awesome @smugcloud @tmaiaroto, great to hear! If you guys have any additional questions, please let us know. |
We are running the issue since ~2 weeks ago, on our calls to lambda - we
definitely cannot create/read functions or triggers.
Note that we're using Terraform 0.7, and that includes aws-sdk-go 1.14.15
…On 30 November 2017 at 18:44, xibz ***@***.***> wrote:
@rabbbit <https://github.com/rabbbit> - Are you still running into the
issue? From what I remember this was on the service's side and was not
related to #874 <#874>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1022 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AARt0qoZT1A78F21KTVpwhm1GG2mIJh-ks5s7umTgaJpZM4LUf4K>
.
|
@rabbbit - Could please enable HTTP2 debugging? This can be enabled by using |
Woooahh, http2? I did see HTTP 1.1 in our logs, didn't expect 2 to make a difference. So, without the debugging enabled, we were seeing a lot of:
and
With debugging enabled, it's:
|
@rabbbit - Looks like the |
Sure, although it might take a while before we get to upgrade terraform,
it's not trivial.
What did you mean by the original comment in this task though? You were
suggesting an issue that was fixed on your end, right?
…On 30 Nov 2017 21:37, "xibz" ***@***.***> wrote:
@rabbbit <https://github.com/rabbbit> - Looks like the RST_STREAM is
being set which is canceling that stream. I am curious if this would be
resolved by updating Golang. I know the language made several changes to
the HTTP2 library since then. Please let us know if this resolves the issue.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1022 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AARt0s_7toSLePOL7icZ08xUn_A_lzqQks5s7xIBgaJpZM4LUf4K>
.
|
@rabbbit - There was a bug regarding HTTP2 in an earlier version of the SDK. I noticed you were using a very early version of the SDK. So, updating that would be a good idea as well. |
Hello,
Below is the DEBUG output from a simple GET to the
GetRestApis
ApiGateway operation. It appears the response code is zero. Is this a bug?GET
Debug
The text was updated successfully, but these errors were encountered: