question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Node 12.8.0 and --h2 option leads to crash

See original GitHub issue

Expected Behavior

ui5 serve --h2 works without error with Node 12.8.0.

Current Behavior

When running ui5 serve --h2 with Node 12.8.0 the Node application immediately crashes when trying to access resources from the server. The error is a RangeError in some internals - not directly related to the UI5 tooling.

Steps to reproduce the issue

  1. Use Node 12.8.0
  2. Run ui5 serve --h2 on any UI5 project with any UI5 tooling version supporting h2

Context

  • UI5 Module Version (output of ui5 --version when using the CLI): 1.4.3 but also happens with 1.7.0
  • Node.js Version: 12.8.0
  • npm Version: 6.10.3
  • OS/Platform: MacOS

Affected components (if known)

Log Output / Stack Trace

URL: https://localhost:8443
internal/buffer.js:940
class FastBuffer extends Uint8Array {}
^

RangeError: Invalid typed array length: -4095
    at new Uint8Array (<anonymous>)
    at new FastBuffer (internal/buffer.js:940:1)
    at Handle.onStreamRead [as onread] (internal/stream_base_commons.js:165:17)
    at Stream.<anonymous> (/Users/d039071/Downloads/aoffline/node_modules/@ui5/cli/node_modules/handle-thing/lib/handle.js:120:12)
    at Stream.emit (events.js:208:15)
    at endReadableNT (/Users/d039071/Downloads/aoffline/node_modules/@ui5/cli/node_modules/readable-stream/lib/_stream_readable.js:1010:12)
    at processTicksAndRejections (internal/process/task_queues.js:77:11)

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:9 (6 by maintainers)

github_iconTop GitHub Comments

3reactions
RandomBytecommented, Mar 26, 2020

The upstream spdy/handle-thing issue has been fixed: https://github.com/spdy-http2/handle-thing/pull/13

Now the current master supports HTTP/2 with all current Node.js releases. For the UI5 CLI, this dependency update will be released with v2.0.0 next week.

This only requires an in-range dependency update of handle-thing. @kristian your project should only need to update any package-lock.json to resolve this issue.

0reactions
petermuessigcommented, Apr 3, 2020

👍 Works, thanks!

Read more comments on GitHub >

github_iconTop Results From Across the Web

The Difference Between Node.js 10 LTS and Node.js 12 LTS
Fixed an issue related to stdio that could lead to a crash of the process in some circumstances #28490. stream:.
Read more >
Let It Crash: Best Practices for Handling Node.js Errors on ...
This blog post is adapted from a talk given by Julián Duque at NodeConf EU 2019 titled "Let it crash!." Before coming to...
Read more >
Node.js heap out of memory - Stack Overflow
Today I ran my script for filesystem indexing to refresh RAID files index and after 4h it crashed with following error:
Read more >
node - Official Image | Docker Hub
Node.js is a JavaScript-based platform for server-side and networking applications.
Read more >
6 reasons your Node.js apps are failing - IBM Developer
If a Node.js application crashes or aborts in native code, the symptoms are minimal. The application stops immediately, but usually produces at least...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found