Telegram Unhandled rejection TypeError

[guidone]

Telegram Unhandled rejection TypeError

[guidone]

@cnavigato can you tell me which NodeRed version are you using?

[TomKelross]

I was having a similar problem with the FacebookHandler,
when using version 0.15 or 0.15.1 of node-red.

When I downgraded to version 0.14.6 it worked again

[guidone]

It appears that the global context in NodeRed is not present, that is strange.

I've upgraded to 0.15.1 but I was not able to reproduce the error, I've been working with 0.15.0 for days and I never got this error, I also inspected the changed files from 0.15.0 to 0.15.1 but nothing touches the contexts in Node-Red.

• do you have something in you configuration for the key functionGlobalContext?
• is your flow working in a particular environment (like Raspberry)?
• can you reproduce it in a small flow that you can send over (without the chatbot token of course)?

I've a beta version, I'll release it soon, you can try if the bug can be reproduced with the bet

npm install [email protected]

Thanks for the feedback

[monkeydave]

I am new to node-red and I am also receiving the error, I tried your beta and I still got the error.

This is my system setup
Ubuntu 16.04.1 LTS
Node-RED version: v0.15.1
Node.js version: v4.6.1
npm version 2.15.9

In my settings.js I have the following

functionGlobalContext: {
        // os:require('os'),
        // octalbonescript:require('octalbonescript'),
        // jfive:require("johnny-five"),
        // j5board:require("johnny-five").Board({repl:false})
},

[bseishen]

Also having the same issue.
Ubuntu 16.04.1 LTS
Node-RED version: v0.15.2
Node.js version: v4.6.2
npm version 3.5.2

[{"id":"532c1e7f.0af2","type":"tab","label":"Flow 1"},{"id":"ff5f7c36.bccd","type":"chatbot-telegram-send","z":"532c1e7f.0af2","bot":"73f98b2f.d76824","track":false,"outputs":0,"x":735,"y":84,"wires":[]},{"id":"98b2e3fd.a1f19","type":"chatbot-telegram-receive","z":"532c1e7f.0af2","bot":"73f98b2f.d76824","x":404,"y":149,"wires":[["ff5f7c36.bccd","fcb98f6.a73537"]]},{"id":"fcb98f6.a73537","type":"debug","z":"532c1e7f.0af2","name":"","active":true,"console":"false","complete":"true","x":662,"y":208,"wires":[]},{"id":"73f98b2f.d76824","type":"chatbot-telegram-node","z":"","botname":"Test2","usernames":"","polling":"1000","log":""}]

[bseishen]

Reverted to Node-RED 14.6, then installed 15.2 again. Seem to have fix the problem.

[guidone]

@bseishen this bug is giving me a really hard time, does it happen sistematically or sometimes?

Is Node-RED crashing at the very first message it receives or after a while?

Is there any particular node-red plugin that can cause this side effect (for example something that was no longer present after you reinstalled version 15.2)?

[aleonnet]

Hi @guidone,
Sorry but, I'm having the same issue on a Raspberry Pi 3 (Node-RED version: v0.15.2, Node.js version: v4.6.1, Linux 4.4.21-v7+ arm LE)

<<Unhandled rejection TypeError: Cannot read property 'get' of undefined
at TelegramBotNode.handleMessage (/root/.node-red/node_modules/node-red-contrib-chatbot/chatbot-telegram-receive.js:182:39)

Already figured out what is going on?

Thanks!

[bseishen]

@guidone Only other package installed before this was node-red-contrib-telegrambot. Other than that it was a clean install of Ubuntu server. Node-Red is crashing at the very first message. Now I'm pretty new at Node.js/NPM/Node-Red so could be user error.

[guidone]

@bseishen I'm preparing a patch for that, it's just a more defensive code since I still cannot figure out why Node-RED is returning a null global context (it should not)

[aleonnet]

Just for you guys to know, the node-red-contrib-telegrambot works perfectly.

[guidone]

Ok

npm install [email protected]

should fix the problem, at least it doesn't break if the global context is not available.
Sorry it took so long to fix.