req.socket.destroy() is not a function #31
Comments
|
I'm gonna close this... I've tried to reproduce it by doing weird things in express apps and I cannot. I could just add a line to prevent it, but I'd rather do that after finding a legit reproduction case. |
ErisDS
added a commit
to TryGhost/framework
that referenced
this issue
Mar 31, 2022
refs: antongolub/reqresnext#31 - Whilst building the test framework I kept hitting this weird error req.socket.destroy() is not a function - I added a workaround of declaring it as a function, and that made me get more sensible errors, showing that there was some other issue at play - I can no longer remember the causes nor reproduce the issue with the framework, so I'm removing this line - It is untested and untestable... as I can't find the case! - If anyone gets this error again, we'll create a repro case and fix the issue in reqresnext with tests
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Regularly when I cock things up slightly whilst working with reqresnext I get an error
req.socket.destroy()is not a function coming from finalhandler here: https://github.com/pillarjs/finalhandler/blob/master/index.js#L128I have moved past it many times as each time I see this, it's just masking another error in my code and don't have a proper recorded error + trace or a reproduction case right now.
The text was updated successfully, but these errors were encountered: