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
=== release test-repl-timeout-throw ===
Path: parallel/test-repl-timeout-throw
>
var throws = 0;process.on("exit",function(){console.log(throws)});function thrower(){console.log("THROW",throws++);XXX};setTimeout(thrower);""
node.js:135
throw err;
^
Error: Could not parse history data in /Users/indutny/.iojs/.repl_history.
at onread (internal/repl.js:103:13)
at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:382:3)
assert.js:88
throw new assert.AssertionError({
^
AssertionError: false == true
at ChildProcess.<anonymous> (/Users/indutny/Code/indutny/node/test/parallel/test-repl-timeout-throw.js:52:3)
at emitTwo (events.js:87:13)
at ChildProcess.emit (events.js:169:7)
at maybeClose (child_process.js:953:16)
at Process.ChildProcess._handle.onexit (child_process.js:1020:5)
The history file contains undefined for some reason.
When running in non-TTY mode - the `repl.history` is `undefined` and
is not actually populated. Saving it will result in a crashes of
subsequent repl runs.
Fix: nodejs#1574
When running in non-TTY mode - the `repl.history` is `undefined` and
is not actually populated. Saving it will result in a crashes of
subsequent repl runs.
Fix: #1574
PR-URL: #1575
Reviewed-By: Chris Dickinson <[email protected]>
The history file contains
undefined
for some reason.cc @chrisdickinson
The text was updated successfully, but these errors were encountered: