You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Version: v12.13.1
Platform: Darwin Kernel Version 18.7.0: Sun Dec 1 18:59:03 PST 2019; root:xnu-4903.278.19~1/RELEASE_X86_64 x86_64
we are seeing the same issue that is reported on the issue #21063 on NodeJS V12
Also verified the same in:
V10.18.0 - its working
V12.13.0 - its not working
v13.6.0 - its not working
The text was updated successfully, but these errors were encountered:
Assuming "it's not working" actually means that 'close' is always being emitted, then that is expected. That behavior was only reverted for node v10.x.
Yes, the 'close' is always being emitted.
with the 'close' always being emitted, when my project is upgraded to NodeJs v12.X, i see some BOSH http-bind requests are getting closed abruptly and seeing a weird behavior, where this project is successfully working on NodeJs V8.x and V10.x
Version: v12.13.1
Platform: Darwin Kernel Version 18.7.0: Sun Dec 1 18:59:03 PST 2019; root:xnu-4903.278.19~1/RELEASE_X86_64 x86_64
we are seeing the same issue that is reported on the issue #21063 on NodeJS V12
Also verified the same in:
V10.18.0 - its working
V12.13.0 - its not working
v13.6.0 - its not working
The text was updated successfully, but these errors were encountered: