Cannot set property 'debug_mode' of null

[coreybutler]

Received the following after an update to Node 6.1:

/usr/local/lib/node_modules/redis/index.js:249
    this.parser_module.debug_mode = exports.debug_mode;
                                  ^
TypeError: Cannot set property 'debug_mode' of null
    at RedisClient.init_parser (/usr/local/lib/node_modules/redis/index.js:249:35)
    at RedisClient.on_connect (/usr/local/lib/node_modules/redis/index.js:206:10)
    at Socket.<anonymous> (/usr/local/lib/node_modules/redis/index.js:62:14)
    at Socket.emit (events.js:64:17)
    at Object.afterConnect [as oncomplete] (net.js:588:10)

[mranney]

Something did change around this in the last few versions, but I've not seen this particular error before. Can you make sure you are using the latest version of the redis package?

A common thing that happens in some node upgrade scenarios is that modules get installed in multiple places. It might be that npm has updated the module in some place, but that node finds a different copy at runtime. That'd be another good thing to check for.

[coreybutler]

I'll double check everything... I'm going to configure a clean environment and I'll report my results.

Perhaps it's irrelevant, but I did add a console.log(this); on line 248. I noticed the parser_module object was null... so I expected everything referencing an element of that object to fail.

[mranney]

There was a bug a while back where we changed the place where the parser was initialized to after the connection was established, because it needed to be re-initialized on each new connection. It sounds like you are getting caught by that change somehow.

[coreybutler]

I verified everything and ran a simple set/get successfully, so it looks like something with my code is causing the issue. Looks like I just need to put on my boots and get digging into my own code. I'll take a look at the changes and see if that helps expedite things. Thanks for your help.