Skip to content
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

v8.12.0 ParserIncomingMessage is not a constructor #22823

Closed
tone81 opened this issue Sep 12, 2018 · 1 comment
Closed

v8.12.0 ParserIncomingMessage is not a constructor #22823

tone81 opened this issue Sep 12, 2018 · 1 comment

Comments

@tone81
Copy link

tone81 commented Sep 12, 2018

Version: v8.12.0
Platform: Linux
Subsystem: http
Works in v8.11.4

The same code run in v8.11.4 has been tested without issue

Broken in v8.12.0

This is the error message I get when starting my app with v8.12.0.

TypeError: ParserIncomingMessage is not a constructor
    at HTTPParser.parserOnHeadersComplete (_http_common.js:81:21)
    at socketOnData (_http_server.js:472:20)
    at Socket.emit (events.js:180:13)
    at addChunk (_stream_readable.js:274:12)
    at readableAddChunk (_stream_readable.js:249:11)
    at Socket.Readable.unshift (_stream_readable.js:223:10)
    at /root/tunnel-server.js/wstunneld.js:502:14
    at process._tickCallback (internal/process/next_tick.js:176:11)

This may or may not be similar to #20241.

@lpinca
Copy link
Member

lpinca commented Sep 16, 2018

#22857 is a duplicate of this but is more active. I think this can be closed.

@tone81 tone81 closed this as completed Sep 16, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants