node-red / node-red/node-red-nodes

TypeError

Open
#207 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
1.1k
Forks
612
Avg merge
13h 57m
Merged PRs (30d)
3

Description

Hello I've been running my mongo and node-red code and after a while this happened:

  • TypeError: Cannot read property 'done' of null

    at /home/pi/.node-red/node_modules/mongodb/lib/mongodb/auth/mongodb_scram.js:165:17

    at /home/pi/.node-red/node_modules/mongodb/lib/mongodb/db.js:1169:16

    at /home/pi/.node-red/node_modules/mongodb/lib/mongodb/db.js:1878:9

    at Server.Base._callHandler (/home/pi/.node-red/node_modules/mongodb/lib/mongodb/connection/base.js:453:41)

    at /home/pi/.node-red/node_modules/mongodb/lib/mongodb/connection/server.js:487:18

    at MongoReply.parseBody (/home/pi/.node-red/node_modules/mongodb/lib/mongodb/responses/mongo_reply.js:68:5)

    at . (/home/pi/.node-red/node_modules/mongodb/lib/mongodb/connection/server.js:445:20)

    at emitOne (events.js:96:13)

    at emit (events.js:188:7)

    at . (/home/pi/.node-red/node_modules/mongodb/lib/mongodb/connection/connection_pool.js:201:13)

how could i fix this?

thanks, will

Contributor guide

Open the contributing guide

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.

Research direction

Start with the stack-trace location in mongodb/lib/mongodb/auth/mongodb_scram.js at line 165, then inspect the surrounding calls through db.js and the connection files. Reproduce the failure with the reported MongoDB and Node-RED setup after prolonged use; done means the null callback condition is explained and a verified fix or dependency resolution is documented.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.