-
Notifications
You must be signed in to change notification settings - Fork 44
Error: could not handle the request #31
Comments
There are no known issues that would cause this. Are you sure that it isn't a bug in your app? |
I never get the error when testing with ( My handler encodes a png image and writes it to Here is more error information from the logs:
|
Can you try removing the use of the nodego logger and see if that fixes the problem? By the way, when you add the logging back, you should add the nodego.WithLoggerFunc middleware. That way your logs will get associated with the request that triggered them. See examples/logging.go. |
Removing the nodego logger does seem to fix the issue. The problem remains even when using the |
Nevermind the problem remains even without the logs, just took over a hundred requests before it happened. https://gist.github.com/montanaflynn/bb002f8212e9cc7f75af5cc03e7a5fd8
|
I removed any third party packages and can reproduce with standard library: This code returns the error / 500 response every so often. The difference in the code that doesn't return an error is I removed all the nodego logger code including init |
It seems that the problem could still be logging as you include |
By the way, you can use |
Hi all, I am getting the same error. |
Cloud Functions now has official Go support: As a result, this repository is no longer under active development. Pull requests are still welcome though. |
Getting this plain text response every 30 or so requests:
Checking the server logs I found this:
The text was updated successfully, but these errors were encountered: