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

Warning in Node-Red Console at startup - [warn] [twitter-credentials:1f783c2a.4bb984] Failed to get user profile

Open
#571 3 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

So you have a real issue to raise...

To help us understand the issue, please fill-in as much of the following information as you can:
-->

Which node are you reporting an issue on?

Node-Red-Node-Twitter

What are the steps to reproduce?

I updated my Twitter credentials after being away from using the node-red-twitter node for about 8 months, I completed the registration on twitter, and then supplied the node with the new api creds. When I restarted node-red it showed the warning in the subject.

What happens?

It shows the warning in the subject when I start node-red

What do you expect to happen?

I expect it to start without warning,

Please tell us about your environment:
  • Node-RED version:Node-RED version: v0.20.7
  • node.js version: v8.10.0
  • npm version: 3.5.2
  • Platform/OS:Linux Mint 19.1 5.0.0-25-generic #26~18.04.1-Ubuntu SMP
  • Browser: Google Chrome Version 75.0.3770.100 (Official Build) (64-bit)

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 Node-Red-Node-Twitter node and reproduce startup on Node-RED v0.20.7 using the updated Twitter credentials described in the report. Trace the startup path that requests the Twitter user profile and determine why the warning occurs; done means valid credentials no longer produce the startup warning.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
api
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.