GRPCUnavailableError:UNAVAILABLE: No connection established
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 546
- Forks
- 76
- Avg merge
- 22h 46m
- Merged PRs (30d)
- 13
Description
It's just happened when trying running the quick-start in the redmi file
const { Etcd3 } = require('etcd3');
const client = new Etcd3();
(async () => {
await client.put('foo').value('bar');
const fooValue = await client.get('foo').string();
console.log('foo was:', fooValue);
const allFValues = await client.getAll().prefix('f').keys();
console.log('all our keys starting with "f":', allFValues);
await client.delete().all();
})();
The output error is:
node:internal/process/promises:279
triggerUncaughtException(err, true /* fromPromise */);
^
GRPCUnavailableError: 14 UNAVAILABLE: No connection established
Node version is 17.6.0
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the quick-start snippet from the reported file with Node.js 17.6.0 and inspect how the client establishes its connection. The payload names no source file, test, endpoint, or etcd setup, so first identify those details and determine whether the failure is environmental, documentation-related, or a client bug. Done means a reproducible diagnosis and a verified resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grpc, node.js, typescript
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100