node/test/fixtures/errors/async_error_nexttick_main.snapshot

Error: test
    at one (*fixtures*async-error.js:4:9)
    at two (*fixtures*async-error.js:17:9)
    at process.processTicksAndRejections (node:internal*process*task_queues:105:5)
    at async three (*fixtures*async-error.js:20:3)
    at async four (*fixtures*async-error.js:24:3)
    at async main (*async_error_nexttick_main.js:7:5)
process: reduce the number of internal frames in async stack trace Previously, we call the JS land `runNextTicks` implementation immediately from JS land after evaluating the main module or the input, so these synchronous JS call frames would show up in the stack trace of the async errors, which can be confusing. This patch moves those calls into C++ so that more of these internal scheduler implementation details can be hidden and the users can see a cleaner a cleaner async JS stack trace. PR-URL: https://github.com/nodejs/node/pull/27392 Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: Gus Caplan <me@gus.host> Reviewed-By: Minwoo Jung <minwoo@nodesource.com> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> 2019-04-24 19:03:48 +00:00			`Error: test`
			`at one (fixturesasync-error.js:4:9)`
			`at two (fixturesasync-error.js:17:9)`
lib: rewrite AsyncLocalStorage without async_hooks PR-URL: https://github.com/nodejs/node/pull/48528 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Rafael Gonzaga <rafael.nunu@hotmail.com> Reviewed-By: Chengzhong Wu <legendecas@gmail.com> Reviewed-By: Santiago Gimeno <santiago.gimeno@gmail.com> Reviewed-By: Gerhard Stöbich <deb2001-github@yahoo.de> 2024-08-02 19:44:20 +00:00			`at process.processTicksAndRejections (node:internalprocesstask_queues:105:5)`
process: reduce the number of internal frames in async stack trace Previously, we call the JS land `runNextTicks` implementation immediately from JS land after evaluating the main module or the input, so these synchronous JS call frames would show up in the stack trace of the async errors, which can be confusing. This patch moves those calls into C++ so that more of these internal scheduler implementation details can be hidden and the users can see a cleaner a cleaner async JS stack trace. PR-URL: https://github.com/nodejs/node/pull/27392 Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: Gus Caplan <me@gus.host> Reviewed-By: Minwoo Jung <minwoo@nodesource.com> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> 2019-04-24 19:03:48 +00:00			`at async three (fixturesasync-error.js:20:3)`
			`at async four (fixturesasync-error.js:24:3)`
test: migrate message tests to use assertSnapshot PR-URL: https://github.com/nodejs/node/pull/47498 Reviewed-By: Geoffrey Booth <webadmin@geoffreybooth.com> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> 2023-04-27 06:41:58 +00:00			`at async main (*async_error_nexttick_main.js:7:5)`