mirror of
https://github.com/nodejs/node.git
synced 2025-05-02 22:31:35 +00:00
1432065e9d
Historically `error.errno` of system errors thrown by Node.js
can sometimes be the same as `err.code`, which are string
representations of the error numbers. This is useless and incorrect,
and results in an information loss for users since then they
will have to resort to something like
`process.binding('uv'[`UV_${errno}`])` to get to the numeric
error codes.
This patch corrects this behavior by always setting `error.errno`
to be negative numbers. For fabricated errors like `ENOTFOUND`,
`error.errno` is now undefined since there is no numeric equivalent
for them anyway. For c-ares errors, `error.errno` is now undefined
because the numeric representations (negated) can be in conflict
with libuv error codes - this is fine since numeric codes was
not available for c-ares errors anyway.
Users can use the public API `util.getSystemErrorName(errno)`
to retrieve string codes for these numbers.
PR-URL: https://github.com/nodejs/node/pull/28140
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
54 lines
1.4 KiB
JavaScript
54 lines
1.4 KiB
JavaScript
'use strict';
|
|
require('../common');
|
|
|
|
// This test checks that the maxBuffer option for child_process.execFileSync()
|
|
// works as expected.
|
|
|
|
const assert = require('assert');
|
|
const { getSystemErrorName } = require('util');
|
|
const { execFileSync } = require('child_process');
|
|
const msgOut = 'this is stdout';
|
|
const msgOutBuf = Buffer.from(`${msgOut}\n`);
|
|
|
|
const args = [
|
|
'-e',
|
|
`console.log("${msgOut}");`
|
|
];
|
|
|
|
// Verify that an error is returned if maxBuffer is surpassed.
|
|
{
|
|
assert.throws(() => {
|
|
execFileSync(process.execPath, args, { maxBuffer: 1 });
|
|
}, (e) => {
|
|
assert.ok(e, 'maxBuffer should error');
|
|
assert.strictEqual(e.code, 'ENOBUFS');
|
|
assert.strictEqual(getSystemErrorName(e.errno), 'ENOBUFS');
|
|
// We can have buffers larger than maxBuffer because underneath we alloc 64k
|
|
// that matches our read sizes.
|
|
assert.deepStrictEqual(e.stdout, msgOutBuf);
|
|
return true;
|
|
});
|
|
}
|
|
|
|
// Verify that a maxBuffer size of Infinity works.
|
|
{
|
|
const ret = execFileSync(process.execPath, args, { maxBuffer: Infinity });
|
|
|
|
assert.deepStrictEqual(ret, msgOutBuf);
|
|
}
|
|
|
|
// Default maxBuffer size is 1024 * 1024.
|
|
{
|
|
assert.throws(() => {
|
|
execFileSync(
|
|
process.execPath,
|
|
['-e', "console.log('a'.repeat(1024 * 1024))"]
|
|
);
|
|
}, (e) => {
|
|
assert.ok(e, 'maxBuffer should error');
|
|
assert.strictEqual(e.code, 'ENOBUFS');
|
|
assert.strictEqual(getSystemErrorName(e.errno), 'ENOBUFS');
|
|
return true;
|
|
});
|
|
}
|