Runtime stderr is missing from ruby error message

Open
#142 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript, ruby
Domain
backend

Research direction

Start by inspecting ExternalRuntime and the referenced commit 5cce03a to understand where stderr capture was removed. Reproduce a JavaScript runtime error and verify that the resulting Ruby error message again includes the runtime's error and trace information.

Written by the indexing model from the issue text.

Description

5cce03a removed stderr capture from ExternalRuntime. In the event of a runtime error, this means that the error message no longer contains error/trace info from runtime.

Terrible, terrible workaround:

ExecJS.runtime.instance_variable_get(:@popen_options).merge!({ err: [:child, :out] })

:)

Dominant language
Ruby
Stars
578
Forks
286
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rails/execjs

All issues in rails/execjs

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.