node-red / node-red/node-red-nodes
Node-red-node-Twitter - Twitter In and the All Public Tweets option filled in throws an exception
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.1k
- Forks
- 612
- Avg merge
- 13h 57m
- Merged PRs (30d)
- 3
Description
Node-red-node-Twitter - Twitter In and All Public Tweets filled in with a term throws an exception terminating node-red when first deploying the node with credentials and all subsequent deployments. It works as expected but requires node-red to be re-started after every redeployment. The watchdog does that automatically on HomeAsssistant.
Node-red on HomeAssistant was restarting every deploy, by running node-red on windows, I narrowed it down to the Twitter/public tweets node by stripping everything out, node by node since the logs weren’t giving me any clues. I’ve added and removed the node multiple times and verified it was that that was causing the restarts on Home Assistant and crashes on Windows.
Contributor guide
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 failure with the Node-red-node-Twitter Twitter In node, the All Public Tweets option, a search term, and credentials, then inspect that node's entry point. Verify the fix by deploying repeatedly on a Node-RED installation and confirming that the process no longer terminates or requires a restart.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100