-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ERR_INVALID_ARG_TYPE The "string" argument must be of type string or an instance of Buffer or ArrayBuffer. Received undefined #54
Comments
I'm facing that issue also very often. Can't tell exactly when it is happening and I somehow can't catch it ..
|
same issue |
I have not been able to determine a way to reproduce it as it happens at different moments with the very same requests. As this library does not have any changes in the last 10 months and this issue is recent, could it be an incompatibility with some versions of Node, Redis, or both? Node versions: As it cannot be catched in any way, this bug seems pretty critical. |
Happens for Node versions
as well. Also tried to reinsert the data with v11. Same problem. Running redis 4.x.x I have seen that @cBiscuitSurprise has worked on the protocol here: cBiscuitSurprise#1 |
This issue will be investigated and fixed |
same issue :/ |
get by key the issue got it
const tediss = new Tedis({
port: 6379,
host: "127.0.0.1"
});
TypeError [ERR_INVALID_ARG_TYPE]: The "string" argument must be of type string or an instance of Buffer or ArrayBuffer. Received undefined
at Function.byteLength (buffer.js:725:11)
at Protocol.parse (/home/lap53_claysol/Public/cms/serverless/cmsContentpartners/cp/node_modules/tedis/src/core/protocol.ts:74:29)
at Socket. (/home/lap53_claysol/Public/cms/serverless/cmsContentpartners/cp/node_modules/tedis/src/core/base.ts:133:23)
at Socket.emit (events.js:314:20)
at Socket.EventEmitter.emit (domain.js:483:12)
at addChunk (_stream_readable.js:297:12)
at readableAddChunk (_stream_readable.js:272:9)
at Socket.Readable.push (_stream_readable.js:213:10)
at TCP.onStreamRead (internal/stream_base_commons.js:188:23)
The text was updated successfully, but these errors were encountered: