We have a machine for development, running more than 100 NodeJS containers, all connected to a same docker network, interconnected by container names.

Recently, we encountered a strange problem: when the containers communicate with one another, they might sometimes report errors like getaddrinfo EAI_AGAIN, which means DNS query failed.

@litert/redis is a Redis client library developed entirely in TypeScript, for NodeJS.

All asynchronous operations are based on Promise, and it supports transactions and messaging.

Features

• Support read/write separation.
• Support pipeline.
• Support multi and exec.
• Support subscribe and publish.

Installation

1npm install @litert/redis@^3.0.3

v3.0.3 CHANGES

Versions before v3.0.3 are marked as deprecated. Please upgrade to the latest version ASAP.

• build(deps-dev): bump braces from 3.0.2 to 3.0.3 by @dependabot in https://github.com/litert/redis.js/pull/10
• fix(command): return keys in HMGET command correctly by @fenying in https://github.com/litert/redis.js/pull/11
• fix(protocol): decode “*-1” correctly by @fenying in https://github.com/litert/redis.js/pull/12
• Feat blmove command by @yunbookf in https://github.com/litert/redis.js/pull/13

Contributors

• @yunbookf #13

@litert/televoke is a RPC library for NodeJS, written in TypeScript.

Installation

1npm install @litert/televoke@^1.1.0

v1.1.0 CHANGELOG

• feat(protocol): added experimental supports for transports between worker thread.

  You can run Televoke servers in main thread or worker threads now.

• feat(protocol): added feature flag properties for channel objects.

  Now you can detect whether the server supports push messages and binary stream transport.

• fix(protocol): simplified the ITransporter.end method.

• fix(decoder): should decode protocol error as special error.

• fix(protocol): put protocol-error code in server_internal_server data.

The buffer-based encoding utility method for node.js.

Following types of encodings are supported:

Encoding urlencode

This is a real urlencode implement, it will escape all bytes as %xx format, excepting A-Z, a-z and 0-9. This is a binary-safe encoding.

Binary-safe means it could work with binary data perfectly, without gibberish. And it’s all the same below.

Encoding uri

This is a simple reference of method encodeURIComponent, so it works as method encodeURIComponent does. And it’s not a binary-safe encoding.

Encoding strict_uri

This is based on uri, but all special chars including "-", ".", "_", "!", "*", "(", ")", "~", "'" will be escaped. However, it’s still not a binary-safe encoding.

NOTE: The data of strict_uri encoding, could be simply decoded by function decodeURIComponent.

Encoding base64url

This is based on base64, while charactors "=", "+", "/" will be replaced with URL-safe charactors. This is a binary-safe encoding.

Encoding base62x

This is a variation of base64. And it is a binary-safe encoding.

Installation

1npm install @litert/encodings@^2.3.0

v2.3.0 CHANGELOG

• config(deps): updated dependencies.
• fix(encoding): fixed decoding of the urlencode.
• build(test): added test cases.
• build(project): upgraded the minimum version of Node.js to v14.

Another strange problem in Bug 11, the “Slideshow” in the lock screen doesn’t work at all. No matter how you choose the images directory, it always shows two kinds of error messages:

• The directory you selected cannot be used as the picture directory.
• You need more than one picture for slideshow

However, if you choose a single image in “Picture” mode, it can display normally.

All right, I can’t stand M$ stupid engineers anymore, so let’s solve this problem with a Powershell script.