Alert but where?

[Giamma]

Good morning and good Sunday ....
I have one timer at 00.01 that perform some function node and link out node.

Yesterday I modified this function and this morning I found this alert in debug section ...

There's no reference to a specific node and so I don't know what to do because
all the function have worked fine ...

Can you help me?

[fugit185]

Can you share your function before and after?

[Giamma]

It's a problem because are a lot of functions ....

[Colin]

You said you changed a function, or were you using the word function generically rather than to a Function node?
I haven't seen that error but it suggests that a context/flow/global get or set is specifying an illegal context store. Are you using a context store other than the default? If not then you probably have an extra parameter in one of the get or set calls.

[Giamma]

Sorry,
I wrote "Yesterday I modified this function" but it's not a specific function but "some function" and those functions works fine .....
No, I don't use an other context store than the default .....

[Steve-Mcl]

Open every function node & inspect every line with ...

context.get
flow.get
global.get
These should have only 1 parameter.

context.set
flow.set
global.set
These should have only 2 parameters

[Steve-Mcl]

Additionally, if you use Monaco (setting in settings.js) it has MUCH better code completion, snippet, error highlighting & function parameter help - that would tell you how to use content properly

[Giamma]

Ok, I'll check all my functions one more time, this afternoon with more calmly ...

Thank you .....

[Colin]

I have started a fresh thread in the development category to ask if the error message can be improved to include the node id, so that others will not have the problem.

Use of unknown context store in function node error doesn't ref node

The use of an unknown context store in a function node generates a warning (should it be an error?) which does not indicate the node where the error exists. For example, in a Function node, the line let x = context.get("x","31") Shows [image] So it can be difficult to determine where the fault lies. If it is not difficult to improve this then I suggest that would be worth doing. Should I raise an issue?

[TotallyInformation]

If you search your flows for "30") or '30') or 30), you may well find the offending node.

[Giamma]

Yes, it's first thing that's what I did and I found ....

global.set("var_temp_esternamin_prec", 30);
global.get("var_temp_internamin_prec", 30);

and

var y = global.get("var_temp_internamin_prec")||30;

This are the only "30" that I found.

[zenofmud]

Maybe you should read this part of the documentation;
https://nodered.org/docs/user-guide/writing-functions#storing-data
And see if that helps you figure it out.

[Colin]

@Giamma

global.get("var_temp_internamin_prec", 30);

That's the one causing the problem. The second argument of get() is the context store. Compare that with the other one you showed

var y = global.get("var_temp_internamin_prec")||30;

[Giamma]

@Giamma

global.get("var_temp_internamin_prec", 30);

SET not GET !!!!
and yes, I am an idiot !!!!
Sorry .....

[Colin]

@Giamma

and yes, I am an idiot

No, we have all had typos like that where the brain sees what it thinks is there, not what is actually there.

[Steve-Mcl]

@Colin

we have all had typos like that

Absolutely, but using monaco helps...

[Colin]

@Steve-Mcl

using monaco helps

I agree, but of course had it been
global.get("var_temp_internamin_prec", "30")
then even monaco would not have helped.

[Steve-Mcl]

Yeah, true.