Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

movide data loader fails at start

Open
  • Is something wrong?
#33 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
elasticsearch, javascript, node.js
Domain
backend, search

Research direction

Start by reproducing the data-loader startup and inspect the Elasticsearch connection shown in node_modules/@elastic/elasticsearch/lib/Connection.js:123, along with the startup path that logs “starting movie indexing.” Done means the loader starts without the connection rejection and movie indexing proceeds; the issue does not name a source file or test.

Written by the indexing model from the issue text.

Description

2024-05-17 06:57:44 (node:1) UnhandledPromiseRejectionWarning: ConnectionError: connect ECONNREFUSED 172.19.0.3:9200
2024-05-17 06:57:44     at ClientRequest.onError (/app/node_modules/@elastic/elasticsearch/lib/Connection.js:123:16)
2024-05-17 06:57:44     at ClientRequest.emit (events.js:400:28)
2024-05-17 06:57:44     at TLSSocket.socketErrorListener (_http_client.js:475:9)
2024-05-17 06:57:44     at TLSSocket.emit (events.js:400:28)
2024-05-17 06:57:44     at emitErrorNT (internal/streams/destroy.js:106:8)
2024-05-17 06:57:44     at emitErrorCloseNT (internal/streams/destroy.js:74:3)
2024-05-17 06:57:44     at processTicksAndRejections (internal/process/task_queues.js:82:21)
2024-05-17 06:57:44 (Use `node --trace-warnings ...` to show where the warning was created)
2024-05-17 06:57:44 (node:1) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
2024-05-17 06:57:44 (node:1) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
2024-05-17 06:57:44 starting movie indexing
Dominant language
JavaScript
Stars
42
Forks
31
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from elastic/observability-examples

All issues in elastic/observability-examples

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.