Node / Js / es6 step 0 about mal HOT 1 CLOSED

The node readline module has a bit of an issue properly detecting and responding to non-interactive use. In order to get it to pass the tests, you need to call createInterface using the terminal: false option. Note that you may want to add a command line option for this because for interactive use you will want the readline features (history, line editing, etc).

There are actually a few other implementations that have the same issue: C#, F#, VB.net, and Tcl. The way this is handled in the toplevel Makefile is by setting the RAW environment variable to 1 when calling the implementation run script during testing:

$ grep RAW Makefile
get_runtest_cmd = $(call get_run_prefix,$(1),$(2),$(if $(filter cs fsharp tcl vb,$(1)),RAW=1,)) ...

You can see how the --raw option is added in the run script:

$ grep "raw" */run
cs/run:exec mono $(dirname $0)/${STEP:-stepA_mal}.exe ${RAW:+--raw} "${@}"
fsharp/run:exec mono $(dirname $0)/${STEP:-stepA_mal}.exe ${RAW:+--raw} "${@}"
tcl/run:exec tclsh $(dirname $0)/${STEP:-stepA_mal}.tcl ${RAW:+--raw} "${@}"
vb/run:exec mono $(dirname $0)/${STEP:-stepA_mal}.exe ${RAW:+--raw} "${@}"

In case you are curious (and for others who may stumble onto this issue), here is what is happening. The runtest.py script launches the implementation using an interactive pty. Most readline/lineedit implementation detect this properly and will print readline prompt so that the test driver can determine when the implementation is ready for the next test line. However, the implementations I listed above and the readline module in node, do some non-standard way of detecting interactive and come to the conclusion that they are being used in non-interactive mode and so the readline prompt is never actually display and the runtest.py script times out waiting for it.

Hope that helps.

from mal.