Cannot click Deploy button

[Jon Murphy]

I think I’ve done too many deploy’s and I wore out the big red Deploy button.  I installed an updated node-red-contrib-nest v0.1.9 and something went bad.  If I make any change to any flow and then click Deploy nothing happens.  I've tried a nodered restart and I tried a RasPi reboot. There doesn't appear to be anything odd in the syslog (I think this is where node-red stores messages).

The only hint of an error is in the Console for Safari or Web Console for Firefox.  (I also cleared the browser caches)

Any hints would be greatly appreciated! Thank you! Jon

Environment:

• Raspberry Pi 2B
• Jessie
• Node-RED version: v0.14.6
• Node.js version: v4.4.7
• Linux 4.4.13-v7+ arm LE

Commands I ran (below). All of my node-red-contrib-* installs are done without "-g" (global)

pi@emonpi:~/.node-red $ rpi-rw
Filesystem is unlocked - Write access
type ' rpi-ro ' to lock
pi@emonpi:~/.node-red $ sudo npm install node-red-contrib-nest
node-red-c...@0.1.9 node_modules/node-red-contrib-nest
└── req...@2.74.0 (aws-...@0.6.0, tunnel...@0.4.3, oauth...@0.8.2, foreve...@0.6.1, is-typ...@1.0.0, case...@0.11.0, string...@0.0.5, isst...@0.1.2, json-stri...@5.0.1, aw...@1.4.1, ext...@3.0.0, tough-...@2.3.1, node...@1.4.7, q...@6.2.1, combine...@1.0.5, mime-...@2.1.11, ha...@3.1.3, b...@1.1.2, http-si...@1.1.1, har-va...@2.0.6, form...@1.0.1)

PS: this is double posted on the creator’s github and here. At the moment I am note sure if this is a Node-RED issue or a node-red-contrib-nest issue.  Sorry - I know this is bad form!

[Jon Murphy]

Still looking for an assist.  Please?!?

I have tried:

• writing to the Nest node creator and uninstalled the Nest node via `sudo npm uninstall node-red-contrib-nest`.  That did not help.
• uninstalling and reinstalling nodejs, nodered and npm.  And that did not help.
• three different browsers of Safari v9.1.2, Firefox v48.0.2 and Chrome v52.0.2743.116.  All act the same way with no Deploy action.
• Two other computers. Same issue.  And I tried iOS Safari.  Same issue.

The Deploy issue seems to point to a file named `red.min.js` in the `/usr/lib/node_modules/node-red/public/red` directory.  (see image enclosed) I’m not sure what installs this file but it seems like node-red itself.  I am not sure why it did not change or update when I removed and installed node-red 0.14.6.

Help?!?

[sebasti...@gmail.com]

Are you always taking the same settings / flows for your test? 

may you drop them here?

From what you see above it seems, that RED wants to gather a "subflow" which is not there (any more?) --> hover in to a.z to see the content of a.z ... maybe you get an idea then what RED is looking for.

But I agree, that NR should handle such cases more user friendly by ref/return-value checking and notification to the user.

From your first Post ... I do not know if it  is related to the second post, it more indicates some failure in a node configuration.

Is there any log output from NR on the console (not in the browser but of the node red process) at startup ?

[Nicholas O'Leary]

Yes, this is a bug in node-red, it should never leave you hanging like this. It is just a matter of working out what edge case you've stumbled into.

From the error message you've shared, the code is building its list of unused configuration nodes so it can warn you about them. One of those nodes claims to be on a tab/subflow, but there is not a tab/subflow with a matching id. Quite how you've got here, I'm not sure ... it should not be possible which is why this isn't an error case the code expects to handle.

Steps to recover:

1. take a copy of your flow file - I would appreciate it if you could send me a copy (email directly, not via the mailing list) as I'd really like to understand this better

2. open the configuration node sidebar (dropdown menu -> configuration nodes)

3. ensure the 'all' filter is selected, look through the list for any marked as unused (dotted border, a '0' on the right). Double click to open the edit dialog for any such unused nodes and delete them. Given this started after you added the nest node, look for any nest-related config nodes in particular - it may be coincidental.

If that doesn't work, or you can't find any unused config nodes in that sidebar, definitely do send me your flow file and I'll sort it out.

Nick

--
http://nodered.org
 
Join us on Slack to continue the conversation: http://nodered.org/slack
---
You received this message because you are subscribed to the Google Groups "Node-RED" group.
To unsubscribe from this group and stop receiving emails from it, send an email to node-red+unsubscribe@googlegroups.com.
To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.
For more options, visit https://groups.google.com/d/optout.

[sebasti...@gmail.com]

Hi Nick,

today I ran into the same situation as Jon.

I cannot deploy anymore .. just from second to another... (If I remind me correctly, I just deleted a flow - the flow from the dashboard issue with the toggle button yesterday here out of this forum) ...

It seems related to the dashboard: see attached screenshot

I fixed the issue by just deleting the "Home" Tabs from the dashboard - I then could deploy the changes again.

 

 BTW: is it possible to just copy/paste images here into the forum via clipboard and not by file attachement?

[Julian Knight]

Only really possible using an email client to mail into the list unfortunately. It's a real pain.

On Friday, 2 September 2016 11:03:41 UTC+1, sebasti...@gmail.com wrote:

Hi Nick,

[Julian Knight]

Just to say that I've also had some very odd issues with Dashboard pages. I've not had the chance to put them together to raise an issue yet I'm afraid.

In a nutshell, if I move cards around using the sidebar between tabs, they don't always actually move. Similarly deleting them from the sidebar often doesn't work either. They come back. I've not been sure whether that is related to having converted from UI v1?

On Friday, 2 September 2016 11:03:41 UTC+1, sebasti...@gmail.com wrote:

Hi Nick,

today I ran into the same situation as Jon.

I cannot deploy anymore .. just from second to another... (If I remind me correctly, I just deleted a flow - the flow from the dashboard issue with the toggle button yesterday here out of this forum) ...

It seems related to the dashboard: see attached screenshot

I fixed the issue by just deleting the "Home" Tabs from the dashboard - I then could deploy the changes again.

 

 BTW: is it possible to just copy/paste images here into the forum via clipboard and not by file attachement?

[Nicholas O'Leary]

Sebastian, still not been able to reproduce here. In your screenshot, you can see the 'z' property of the node starting with "f73f90b...". 

It would be useful to know what you get if you run RED.nodes.workspace("f73...") in the console. Equally, what if you run RED.nodes.subflow("f73...");

Nick

--

[sebasti...@gmail.com]

Hi Nick,

I could reproduce with the following recipe.:

Create new flow

paste Need help to finish my dashboard toggle button 

deploy

open dashboard --> see toggle button

delete flow

(deploy not red,need to move a node from a flow so that NR assumes "dirty" flow for deployment)

deploy

dashboard is updated, tab is gone

editor is working fine now ...

just close it and reload editor

add a new empty flow tab

put a node in it

try to deploy ... does not work

Am Freitag, 2. September 2016 16:22:21 UTC+2 schrieb Nick O'Leary:

Sebastian, still not been able to reproduce here. In your screenshot, you can see the 'z' property of the node starting with "f73f90b...". 

It would be useful to know what you get if you run RED.nodes.workspace("f73...") in the console. Equally, what if you run RED.nodes.subflow("f73...");

Nick

On 2 September 2016 at 12:07, Julian Knight <j.kni...@gmail.com> wrote:

Just to say that I've also had some very odd issues with Dashboard pages. I've not had the chance to put them together to raise an issue yet I'm afraid.

In a nutshell, if I move cards around using the sidebar between tabs, they don't always actually move. Similarly deleting them from the sidebar often doesn't work either. They come back. I've not been sure whether that is related to having converted from UI v1?

On Friday, 2 September 2016 11:03:41 UTC+1, sebasti...@gmail.com wrote:

Hi Nick,

today I ran into the same situation as Jon.

I cannot deploy anymore .. just from second to another... (If I remind me correctly, I just deleted a flow - the flow from the dashboard issue with the toggle button yesterday here out of this forum) ...

It seems related to the dashboard: see attached screenshot

I fixed the issue by just deleting the "Home" Tabs from the dashboard - I then could deploy the changes again.

 

 BTW: is it possible to just copy/paste images here into the forum via clipboard and not by file attachement?

--
http://nodered.org
 
Join us on Slack to continue the conversation: http://nodered.org/slack
---
You received this message because you are subscribed to the Google Groups "Node-RED" group.

To unsubscribe from this group and stop receiving emails from it, send an email to node-red+u...@googlegroups.com.

[sebasti...@gmail.com]

Edit:

Nick, may you fix the behaviour on deletion of a flow as well? I assume that it should mark the configuration dirty, right?

[Jon Murphy]

Nick - The Deploy does not work for any flow/tab.  There are two unused configuration nodes, but when I double click one and Delete it, then I cannot Deploy the change.  (see image below)

FYI - I get the Node-Red Dashboard unused config node most every day.  I’ve tried deleting them but they keep coming back.

1 - Send flows: There are 14 flows/tabs.  I hope this is OK to send.  I think the file is flows_emonpi.json.  I’ll send it once I locate your email address.

Also - After I removed and installed everything nodered-ish, I can now longer run or use any of the flows.  If I click Inject or a Debug then I get a Error: node not deployed message.

Jon

[Jon Murphy]

Nick - Could not locate your email address.

Jon

On Friday, September 2, 2016 at 2:45:38 AM UTC-5, Nick O'Leary wrote:

[Jon Murphy]

The Deploy error is for all flows/tabs and there are 14 tabs.  I'm not sure I want to add that big of file to the Group.

There is a duplicate sub-flow, but I cannot delete it or change it since I cannot Deploy.

Here is the hover over "a.z".  This is over my head so i'm not sure what to make of this info.

Object

_

_def

dirty

id

name

type

valid

z

changed?

date?

forecastio?

icon?

inputs?

key?

label?

lat?

lon?

order?

outputs?

ports?

time?

units?

users?

x?

y?

Object Prototype

__defineGetter__

__defineSetter__

__lookupGetter__

__lookupSetter__

constructor

hasOwnProperty

isPrototypeOf

propertyIsEnumerable

toLocaleString

toString

valueOf

__proto__

All of the Node-RED messages seem to go to "syslog".  The only bad messages are related to the Nest node I removed

Sep  1 20:13:53 emonpi Node-RED[451]: 1 Sep 20:13:53 - [info] Waiting for missing types to be registered:

Sep  1 20:13:53 emonpi Node-RED[451]: 1 Sep 20:13:53 - [info]  - nest-config

Sep  1 20:13:53 emonpi Node-RED[451]: 1 Sep 20:13:53 - [info]  - nest request

[Nicholas O'Leary]

Jon,

the 'node not deployed' error is because you have nest nodes deployed in your flow, but you have uninstalled the nest node module. As you can see in the log output, the flows are not started as they are waiting for the nest nodes to register.

As for the deploy button issue - thanks for providing your flow file. That, along with Sebastian's steps to reproduce should mean I can get to the bottom of it this evening.

Nick

--
http://nodered.org
 
Join us on Slack to continue the conversation: http://nodered.org/slack
---
You received this message because you are subscribed to the Google Groups "Node-RED" group.

To unsubscribe from this group and stop receiving emails from it, send an email to node-red+unsubscribe@googlegroups.com.

[Nicholas O'Leary]

Jon,

in the editor, open the dashboard sidebar, and click edit on the 'Home' tab in the Tabs tree. Ensure the select box at the bottom of the edit dialog says 'Global', hit 'update' then you should be able to Deploy.

Sebastian - so far, no luck in recreating it following your steps. Deleting a flow does mark the flows as dirty and enable the deploy button... not sure why that isn't working for you.

Nick

[Jon Murphy]

Nick - Yes!  It worked!  Woo-Hoo!

---

From: Nicholas OLeary
Sent: September 2, 2016 at 12:55:34 PM CDT
To: Node-RED Mailing List
Subject: Re: [node-red] Re: Cannot click Deploy button

[sebasti...@gmail.com]

my NR version is 14.4 does this help?

To unsubscribe from this group and stop receiving emails from it, send an email to node-red+u...@googlegroups.com.

[Nicholas O'Leary]

Sebastian, could you upgrade to the latest, 0.14.6 and see if you can recreate?

Nick

To unsubscribe from this group and stop receiving emails from it, send an email to node-red+unsubscribe@googlegroups.com.

[Jon Murphy]

Nick - Thank you for all your help!

I am curious if this was an issue with how I setup the Dashboard?  Or was it an edge case bug?

Jon

[sebasti...@gmail.com]

Hi Nick,

upgraded to 0.14.6 and same behaviour.

Same way of reproduction. node-red-dashboard is 2.0.1

The callstack on exception is as follows:

c (red.min.js:17)
(anonymous function) (red.min.js:17)
eachConfig (red.min.js:16)
e (red.min.js:17)
(anonymous function) (red.min.js:17)
dispatch (vendor.js:4)
r.handle (vendor.js:4)

Nevertheless I walked through the minimized code and it seems to be related to a subflow:

function c(a){var b="";if(a.z){var c=RED.nodes.workspace(a.z);c?b=c.label:(c=RED.nodes.subflow(a.z),b=c.name)

Checking a.z --> the subflow id gives the following:

RED.nodes.workspace("9abcbfc3.8821e")
undefined

RED.nodes.subflow("9abcbfc3.8821e")
undefined

From the global picture it looks to me as follows:

I pasted in a flow with dashboard component. The dashboard component contained a dashboard tab which was created afterwards.

Then on deletion of the flow the component was gone - thats fine.

But in the dashboard configuration --> the uitab related to the deleted flowtab was still there ...

So when I click on deploy  the editor goes through the configuuration and at the dashboard configuration it seems to miss a related flowtab/subflow (which is clear, because I just deleted it before, right?)

Then, when I delete this configuration (the ui-tab from the dashboard configuration) ... deployment works again (which seems to obvious because no the dashboard confiugration crating the  issue above is away).

... 

So I looked more at the deletion process and why process button was not "red-coloured" after removal of the flow. And yes, on the console was an error message from the dashboard.

VM425:785 Uncaught TypeError: Cannot read property 'data' of undefined

For further information see attached image. 

As there is no exeption handling the removal process of the dashboard is not fully completed and I think this is why the deploy button is not redcolored...

And it may explain why there is some gargabe from the dashboard configuration...

BTW: Is it possible to install node-red without minification of RED.js etc. ? It could create more meaningful debug data and it would it make more easy to support you in analysis

If you need anything more, just let me know.

[Nicholas O'Leary]

Thanks, that is a very useful piece of investigation and will certainly help to identify why the ui_tab delete is going awry.

If you run node-red with the NODE_ENV environment variable set to 'development' it will run with the non-minified version of the editor source.

Nick

[sebasti...@gmail.com]

That's great ! As I am new to node.js / express I found this very interesting http://apmblog.dynatrace.com/2015/07/22/the-drastic-effects-of-omitting-node_env-in-your-express-js-applications/

One  question though: This environment variable does not seems to work with node-red-dashboard. Is there a way to easy create a development version?

 

[Nicholas O'Leary]

Correct - that env var only applies to core node-red. Don't think the dashboard has an equivalent.

Nick

On 5 September 2016 at 18:40, <sebasti...@gmail.com> wrote:

That's great ! As I am new to node.js / express I found this very interesting http://apmblog.dynatrace.com/2015/07/22/the-drastic-effects-of-omitting-node_env-in-your-express-js-applications/

One  question though: This environment variable does not seems to work with node-red-dashboard. Is there a way to easy create a development version?

 

--

[Jon Silver]

This worked for me as well - I had a couple of Dashboard tabs not set to Global.

Thanks Nick!

Jon (another one)

To unsubscribe from this group and stop receiving emails from it, send an email to node-red+u...@googlegroups.com.

[Stephen Haesung Lee]

Hi John Murpy.

Excuse me. How can I use the tool. It looks very helpful!! 

=====================================

2016년 9월 2일 금요일 오후 1시 3분 34초 UTC+10, Jon Murphy 님의 말:

[Zenofmud]

Stephen,

If you are talking about what you see in the bottom half of the image, that is the ‘Web Inspector’ that is part of Safari. You could also use th eFireBug extension in FireFox or the Chrome ‘Developer Tools’

-- 
http://nodered.org
 
Join us on Slack to continue the conversation: http://nodered.org/slack
--- 
You received this message because you are subscribed to the Google Groups "Node-RED" group.
To unsubscribe from this group and stop receiving emails from it, send an email to node-red+u...@googlegroups.com.
To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.

To view this discussion on the web, visit https://groups.google.com/d/msgid/node-red/03e463e2-0a51-467d-bd64-aab62ee6da4c%40googlegroups.com.

[Jon Murphy]

What Paul said!  Thank you!  Jon