lukechilds
/
node
mirror of https://github.com/lukechilds/node.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
17134 Commits
131 Branches
446 Tags
325 MiB
Tree: 9433434461
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '9433434461'
${ noResults }
node/test/message/eval_messages.out

75 lines
2.0 KiB
Raw Normal View History

Report errors properly from --eval and stdin
13 years ago
[eval]
[eval]:1
with(this){__filename}
^^^^
SyntaxError: Strict mode code may not include a with statement
lib: fix event race condition with -e Commit c5b07d4 ("lib: fix beforeExit not working with -e") runs the to-be-evaluated code at a later time than before because it switches from `process.nextTick()` to `setImmediate()`. It affects `-e 'process.on("message", ...)'` because there is now a larger time gap between startup and attaching the event listener, increasing the chances of missing early messages. I'm reasonably sure `process.nextTick()` was also susceptible to that, only less pronounced. Avoid the problem altogether by evaluating the code synchronously. Harmonizes the logic with `Module.runMain()` from lib/module.js which also calls `process._tickCallback()` afterwards. PR-URL: https://github.com/nodejs/node/pull/11958 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com> Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com> Reviewed-By: Daijiro Wachi <daijiro.wachi@gmail.com>
8 years ago
at createScript (vm.js:*:*)
at Object.runInThisContext (vm.js:*:*)
test-message: fix message output 1. The net changes add a stack frame to stdin errors. 2. The error line numbers were overly strict in many places.
13 years ago
at Object.<anonymous> ([eval]-wrapper:*:*)
at Module._compile (module.js:*:*)
lib: fix event race condition with -e Commit c5b07d4 (&#34;lib: fix beforeExit not working with -e&#34;) runs the to-be-evaluated code at a later time than before because it switches from `process.nextTick()` to `setImmediate()`. It affects `-e &#39;process.on(&#34;message&#34;, ...)&#39;` because there is now a larger time gap between startup and attaching the event listener, increasing the chances of missing early messages. I&#39;m reasonably sure `process.nextTick()` was also susceptible to that, only less pronounced. Avoid the problem altogether by evaluating the code synchronously. Harmonizes the logic with `Module.runMain()` from lib/module.js which also calls `process._tickCallback()` afterwards. PR-URL: https://github.com/nodejs/node/pull/11958 Reviewed-By: Colin Ihrig &lt;cjihrig@gmail.com&gt; Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt; Reviewed-By: Jeremiah Senkpiel &lt;fishrock123@rocketmail.com&gt; Reviewed-By: Michael Dawson &lt;michael_dawson@ca.ibm.com&gt; Reviewed-By: Daijiro Wachi &lt;daijiro.wachi@gmail.com&gt;
8 years ago
at evalScript (bootstrap_node.js:*:*)
at run (bootstrap_node.js:*:*)
at run (bootstrap_node.js:*:*)
at startup (bootstrap_node.js:*:*)
at bootstrap_node.js:*:*
Report errors properly from --eval and stdin
13 years ago
42
42
[eval]:1
throw new Error("hello")
deps: update v8 to 4.4.63.9 Upgrade the bundled V8 and update code in src/ and lib/ to the new API. Notable backwards incompatible changes are the removal of the smalloc module and dropped support for CESU-8 decoding. CESU-8 support can be brought back if necessary by doing UTF-8 decoding ourselves. This commit includes https://codereview.chromium.org/1192973004 to fix a build error on python 2.6 systems. The original commit log follows: Use optparse in js2c.py for python compatibility Without this change, V8 won&#39;t build on RHEL/CentOS 6 because the distro python is too old to know about the argparse module. PR-URL: https://github.com/nodejs/io.js/pull/2022 Reviewed-By: Rod Vagg &lt;rod@vagg.org&gt; Reviewed-By: Trevor Norris &lt;trev.norris@gmail.com&gt;
10 years ago
^
vm: refactor vm module Switch to the more efficient module.exports = {} pattern. PR-URL: https://github.com/nodejs/node/pull/11392 Reviewed-By: Michaël Zasso &lt;targos@protonmail.com&gt; Reviewed-By: Colin Ihrig &lt;cjihrig@gmail.com&gt;
8 years ago
Report errors properly from --eval and stdin
13 years ago
Error: hello
at [eval]:1:7
lib: fix event race condition with -e Commit c5b07d4 (&#34;lib: fix beforeExit not working with -e&#34;) runs the to-be-evaluated code at a later time than before because it switches from `process.nextTick()` to `setImmediate()`. It affects `-e &#39;process.on(&#34;message&#34;, ...)&#39;` because there is now a larger time gap between startup and attaching the event listener, increasing the chances of missing early messages. I&#39;m reasonably sure `process.nextTick()` was also susceptible to that, only less pronounced. Avoid the problem altogether by evaluating the code synchronously. Harmonizes the logic with `Module.runMain()` from lib/module.js which also calls `process._tickCallback()` afterwards. PR-URL: https://github.com/nodejs/node/pull/11958 Reviewed-By: Colin Ihrig &lt;cjihrig@gmail.com&gt; Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt; Reviewed-By: Jeremiah Senkpiel &lt;fishrock123@rocketmail.com&gt; Reviewed-By: Michael Dawson &lt;michael_dawson@ca.ibm.com&gt; Reviewed-By: Daijiro Wachi &lt;daijiro.wachi@gmail.com&gt;
8 years ago
at ContextifyScript.Script.runInThisContext (vm.js:*:*)
at Object.runInThisContext (vm.js:*:*)
test-message: fix message output 1. The net changes add a stack frame to stdin errors. 2. The error line numbers were overly strict in many places.
13 years ago
at Object.<anonymous> ([eval]-wrapper:*:*)
at Module._compile (module.js:*:*)
lib: fix event race condition with -e Commit c5b07d4 (&#34;lib: fix beforeExit not working with -e&#34;) runs the to-be-evaluated code at a later time than before because it switches from `process.nextTick()` to `setImmediate()`. It affects `-e &#39;process.on(&#34;message&#34;, ...)&#39;` because there is now a larger time gap between startup and attaching the event listener, increasing the chances of missing early messages. I&#39;m reasonably sure `process.nextTick()` was also susceptible to that, only less pronounced. Avoid the problem altogether by evaluating the code synchronously. Harmonizes the logic with `Module.runMain()` from lib/module.js which also calls `process._tickCallback()` afterwards. PR-URL: https://github.com/nodejs/node/pull/11958 Reviewed-By: Colin Ihrig &lt;cjihrig@gmail.com&gt; Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt; Reviewed-By: Jeremiah Senkpiel &lt;fishrock123@rocketmail.com&gt; Reviewed-By: Michael Dawson &lt;michael_dawson@ca.ibm.com&gt; Reviewed-By: Daijiro Wachi &lt;daijiro.wachi@gmail.com&gt;
8 years ago
at evalScript (bootstrap_node.js:*:*)
at run (bootstrap_node.js:*:*)
at run (bootstrap_node.js:*:*)
at startup (bootstrap_node.js:*:*)
at bootstrap_node.js:*:*
Report errors properly from --eval and stdin
13 years ago
[eval]:1
throw new Error("hello")
deps: update v8 to 4.4.63.9 Upgrade the bundled V8 and update code in src/ and lib/ to the new API. Notable backwards incompatible changes are the removal of the smalloc module and dropped support for CESU-8 decoding. CESU-8 support can be brought back if necessary by doing UTF-8 decoding ourselves. This commit includes https://codereview.chromium.org/1192973004 to fix a build error on python 2.6 systems. The original commit log follows: Use optparse in js2c.py for python compatibility Without this change, V8 won&#39;t build on RHEL/CentOS 6 because the distro python is too old to know about the argparse module. PR-URL: https://github.com/nodejs/io.js/pull/2022 Reviewed-By: Rod Vagg &lt;rod@vagg.org&gt; Reviewed-By: Trevor Norris &lt;trev.norris@gmail.com&gt;
10 years ago
^
vm: refactor vm module Switch to the more efficient module.exports = {} pattern. PR-URL: https://github.com/nodejs/node/pull/11392 Reviewed-By: Michaël Zasso &lt;targos@protonmail.com&gt; Reviewed-By: Colin Ihrig &lt;cjihrig@gmail.com&gt;
8 years ago
Report errors properly from --eval and stdin
13 years ago
Error: hello
at [eval]:1:7
lib: fix event race condition with -e Commit c5b07d4 (&#34;lib: fix beforeExit not working with -e&#34;) runs the to-be-evaluated code at a later time than before because it switches from `process.nextTick()` to `setImmediate()`. It affects `-e &#39;process.on(&#34;message&#34;, ...)&#39;` because there is now a larger time gap between startup and attaching the event listener, increasing the chances of missing early messages. I&#39;m reasonably sure `process.nextTick()` was also susceptible to that, only less pronounced. Avoid the problem altogether by evaluating the code synchronously. Harmonizes the logic with `Module.runMain()` from lib/module.js which also calls `process._tickCallback()` afterwards. PR-URL: https://github.com/nodejs/node/pull/11958 Reviewed-By: Colin Ihrig &lt;cjihrig@gmail.com&gt; Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt; Reviewed-By: Jeremiah Senkpiel &lt;fishrock123@rocketmail.com&gt; Reviewed-By: Michael Dawson &lt;michael_dawson@ca.ibm.com&gt; Reviewed-By: Daijiro Wachi &lt;daijiro.wachi@gmail.com&gt;
8 years ago
at ContextifyScript.Script.runInThisContext (vm.js:*:*)
at Object.runInThisContext (vm.js:*:*)
test-message: fix message output 1. The net changes add a stack frame to stdin errors. 2. The error line numbers were overly strict in many places.
13 years ago
at Object.<anonymous> ([eval]-wrapper:*:*)
at Module._compile (module.js:*:*)
lib: fix event race condition with -e Commit c5b07d4 (&#34;lib: fix beforeExit not working with -e&#34;) runs the to-be-evaluated code at a later time than before because it switches from `process.nextTick()` to `setImmediate()`. It affects `-e &#39;process.on(&#34;message&#34;, ...)&#39;` because there is now a larger time gap between startup and attaching the event listener, increasing the chances of missing early messages. I&#39;m reasonably sure `process.nextTick()` was also susceptible to that, only less pronounced. Avoid the problem altogether by evaluating the code synchronously. Harmonizes the logic with `Module.runMain()` from lib/module.js which also calls `process._tickCallback()` afterwards. PR-URL: https://github.com/nodejs/node/pull/11958 Reviewed-By: Colin Ihrig &lt;cjihrig@gmail.com&gt; Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt; Reviewed-By: Jeremiah Senkpiel &lt;fishrock123@rocketmail.com&gt; Reviewed-By: Michael Dawson &lt;michael_dawson@ca.ibm.com&gt; Reviewed-By: Daijiro Wachi &lt;daijiro.wachi@gmail.com&gt;
8 years ago
at evalScript (bootstrap_node.js:*:*)
at run (bootstrap_node.js:*:*)
at run (bootstrap_node.js:*:*)
at startup (bootstrap_node.js:*:*)
at bootstrap_node.js:*:*
Report errors properly from --eval and stdin
13 years ago
100
[eval]:1
var x = 100; y = x;
^
vm: refactor vm module Switch to the more efficient module.exports = {} pattern. PR-URL: https://github.com/nodejs/node/pull/11392 Reviewed-By: Michaël Zasso &lt;targos@protonmail.com&gt; Reviewed-By: Colin Ihrig &lt;cjihrig@gmail.com&gt;
8 years ago
Report errors properly from --eval and stdin
13 years ago
ReferenceError: y is not defined
at [eval]:1:16
lib: fix event race condition with -e Commit c5b07d4 (&#34;lib: fix beforeExit not working with -e&#34;) runs the to-be-evaluated code at a later time than before because it switches from `process.nextTick()` to `setImmediate()`. It affects `-e &#39;process.on(&#34;message&#34;, ...)&#39;` because there is now a larger time gap between startup and attaching the event listener, increasing the chances of missing early messages. I&#39;m reasonably sure `process.nextTick()` was also susceptible to that, only less pronounced. Avoid the problem altogether by evaluating the code synchronously. Harmonizes the logic with `Module.runMain()` from lib/module.js which also calls `process._tickCallback()` afterwards. PR-URL: https://github.com/nodejs/node/pull/11958 Reviewed-By: Colin Ihrig &lt;cjihrig@gmail.com&gt; Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt; Reviewed-By: Jeremiah Senkpiel &lt;fishrock123@rocketmail.com&gt; Reviewed-By: Michael Dawson &lt;michael_dawson@ca.ibm.com&gt; Reviewed-By: Daijiro Wachi &lt;daijiro.wachi@gmail.com&gt;
8 years ago
at ContextifyScript.Script.runInThisContext (vm.js:*:*)
at Object.runInThisContext (vm.js:*:*)
test-message: fix message output 1. The net changes add a stack frame to stdin errors. 2. The error line numbers were overly strict in many places.
13 years ago
at Object.<anonymous> ([eval]-wrapper:*:*)
at Module._compile (module.js:*:*)
lib: fix event race condition with -e Commit c5b07d4 (&#34;lib: fix beforeExit not working with -e&#34;) runs the to-be-evaluated code at a later time than before because it switches from `process.nextTick()` to `setImmediate()`. It affects `-e &#39;process.on(&#34;message&#34;, ...)&#39;` because there is now a larger time gap between startup and attaching the event listener, increasing the chances of missing early messages. I&#39;m reasonably sure `process.nextTick()` was also susceptible to that, only less pronounced. Avoid the problem altogether by evaluating the code synchronously. Harmonizes the logic with `Module.runMain()` from lib/module.js which also calls `process._tickCallback()` afterwards. PR-URL: https://github.com/nodejs/node/pull/11958 Reviewed-By: Colin Ihrig &lt;cjihrig@gmail.com&gt; Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt; Reviewed-By: Jeremiah Senkpiel &lt;fishrock123@rocketmail.com&gt; Reviewed-By: Michael Dawson &lt;michael_dawson@ca.ibm.com&gt; Reviewed-By: Daijiro Wachi &lt;daijiro.wachi@gmail.com&gt;
8 years ago
at evalScript (bootstrap_node.js:*:*)
at run (bootstrap_node.js:*:*)
at run (bootstrap_node.js:*:*)
at startup (bootstrap_node.js:*:*)
at bootstrap_node.js:*:*
vm: refactor vm module Switch to the more efficient module.exports = {} pattern. PR-URL: https://github.com/nodejs/node/pull/11392 Reviewed-By: Michaël Zasso &lt;targos@protonmail.com&gt; Reviewed-By: Colin Ihrig &lt;cjihrig@gmail.com&gt;
8 years ago
Report errors properly from --eval and stdin
13 years ago
[eval]:1
var ______________________________________________; throw 10
^
10
vm: refactor vm module Switch to the more efficient module.exports = {} pattern. PR-URL: https://github.com/nodejs/node/pull/11392 Reviewed-By: Michaël Zasso &lt;targos@protonmail.com&gt; Reviewed-By: Colin Ihrig &lt;cjihrig@gmail.com&gt;
8 years ago
Report errors properly from --eval and stdin
13 years ago
[eval]:1
var ______________________________________________; throw 10
^
10
done