blob: a0de01f09229641c3490227532599c9e4817dde9 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
|
'use strict';
// This test makes sure that when throwing from within a timer's callback,
// its active domain at the time of the throw is not the process' active domain
// for the next timers that need to be processed on the same turn of the event
// loop.
const common = require('../common');
const assert = require('assert');
const domain = require('domain');
// Use the same timeout value so that both timers' callbacks are called during
// the same invocation of the underlying native timer's callback (listOnTimeout
// in lib/timers.js).
setTimeout(err, 50);
setTimeout(common.mustCall(secondTimer), 50);
function err() {
const d = domain.create();
d.on('error', handleDomainError);
d.run(err2);
function err2() {
// This function doesn't exist, and throws an error as a result.
err3(); // eslint-disable-line no-undef
}
function handleDomainError(e) {
assert.strictEqual(e.domain, d);
// Domains' error handlers are called outside of their domain's context, so
// we're not expecting any active domain here.
assert.strictEqual(process.domain, undefined);
}
}
function secondTimer() {
// secondTimer was scheduled before any domain had been created, so its
// callback should not have any active domain set when it runs.
if (process.domain !== null) {
console.log('process.domain should be null in this timer callback, but is:',
process.domain);
// Do not use assert here, as it throws errors and if a domain with an error
// handler is active, then asserting wouldn't make the test fail.
process.exit(1);
}
}
|
