-
-
Notifications
You must be signed in to change notification settings - Fork 263
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
TypeError: Cannot read property 'statusCode' of undefined #31
Comments
Were you using version 1.3.1 when you got this? The code in your stack trace, on line 78, is no longer on line 78 but line 80 so I'm going to assume not? The change in your pull request assumes there's a case where both I was assuming one or the other would always be defined. I attempted to fix the error you mentioned here 06573af, as it was reported yesterday #26. |
Ah, I didn't see that this was fixed yesterday. This might have been under
1.3.0, which gekko might install (see here:
https://github.com/askmike/gekko/blob/develop/package.json ). I will update
my dependencies and report back if your fix turned out not sufficiant.
Regards,
Mike
On 24 Jan 2018 21:07, "Aaron Garvey" <notifications@github.com> wrote:
Were you using version 1.3.1 when you got this? The code in your stack
trace, on line 78, is no longer on line 78 but line 80 so I'm going to
assume not? The change in your pull request assumes there's a case where
both err and response are undefined. Has that been your experience?
I was assuming one or the other would always be defined. I attempted to fix
the error you mentioned here 06573af
<06573af>,
as it was reported yesterday #26
<#26>.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#31 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA7MD1cf6NtXeLJH_VdGHldKg_uuFp8Oks5tN42ZgaJpZM4Rrxkq>
.
|
No worries. Sorry to create the extra work for you. The issue actually got introduced attempting fix the clock drift issue for gekko. Hopefully 1.3.1 clears everything up. |
Closing this under assumption this is fixed in 1.3.1. |
Here is the full error:
cross post from askmike/gekko#1781.
The text was updated successfully, but these errors were encountered: