[Reactor] Variables not updating correctly in latest-25201-2aa18550
-
@toggledbits thanks for fixing! Another more cosmetic issue is that there seems to be a quite long delay until "Set Rules" widget gets populated? Using Chrome v141
@tunnus said in [Reactor] Variables not updating correctly in latest-25201-2aa18550:
Another more cosmetic issue is that there seems to be a quite long delay until "Set Rules" widget gets populated? Using Chrome v141
Haven't observed anything like that. More detail needed. Proximate to a restart? Is the delay 3 seconds or 30? ...?
-
@tunnus said in [Reactor] Variables not updating correctly in latest-25201-2aa18550:
Another more cosmetic issue is that there seems to be a quite long delay until "Set Rules" widget gets populated? Using Chrome v141
Haven't observed anything like that. More detail needed. Proximate to a restart? Is the delay 3 seconds or 30? ...?
@toggledbits I was using a mobile hotspot when observing this behaviour, and now that I'm back on a high speed connection, delay is 1-2 seconds after browser hard refresh, so nothing to worry about.
-
Oh that's not horrible, considering the amount of information it has to retrieve. But, I may be able to improve on it slightly. Stay tuned... the changelog is getting long for this release...
-
@toggledbits updated to this build, and can report one bug (although it might have been present earlier, but I only noticed this behaviour with this build).
I have a rule with following local variables:
If I click "play" (run) in edit mode on any of these local expressions, I get a runtime error "request failed" (with no other information). Also, if MSR is restarted and expressions get re-evaluated, some of these will be incorrect. E.g. "night_prices" should be first 24 entries of "price_array", but instead it contains first 24 entries of of "sorted_array". Likewise "evening_prices" contains last entries of "sorted_array" when it should have last entries of "price_array".
"highs_array" seems to be okay for some reason.
If you want to test this, I've attached "price_array" below:
[0.125,0.124,0.122,0.062,0.001,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0.001,0.099,0.123,0.125,0.15,0.309,0.29,0.269,0.271,0.428,0.5,1.166,2.073,3.399,4.84,5,6.481,7.292,7.789,8.893,8.915,9.567,9.948,9.027,7.044,8.687,8.001,7.315,6.658,7.902,6.843,6.36,6.098,6.595,6.061,5.838,5.639,6.194,6.036,5.814,5.842,5.378,5.804,6.632,7.254,5.613,6.531,7.357,8.272,6.046,7.089,8.029,10.411,7.843,9.741,13.613,15.002,13.305,16.292,16.651,17.314,15,15.686,15.592,14.559,13.656,13.081,10.844,9.922,11.692,9.631,9.201,8.912,10.17,9.889,9.28,8.79]
@toggledbits using your workaround (clone), but the problem remains with variables not updating correctly as price_array changes, e.g. sum variables do not update. If I (temporarily) modify one of the variables (e.g. change rounding & save), then all the rest changes correctly.
With this particular rule I cannot use Script Action workaround to force updates as I'm using those sum variables as triggers.
-
OK. Follow the instructions from this prior post to set up a log file just for this rule. Restart Reactor and just change the
price_array
. Then capture that log file. I will send you a link when I get home tonight where you can upload it. -
Got the log files; looking at them. Did you newly create this rule for the test?
-
Got the log files; looking at them. Did you newly create this rule for the test?
@toggledbits no, it has been around for a while. Has been renamed though
-
OK. I just pushed 25291 for 64-bit Intel/AMD only (should be correct for your Synology NAS). Give that a try.
-
OK. I just pushed 25291 for 64-bit Intel/AMD only (should be correct for your Synology NAS). Give that a try.
@toggledbits will report shortly (price_array updates at midnight), but wow, Set Rules widget is now lightning fast!
-
@toggledbits will report shortly (price_array updates at midnight), but wow, Set Rules widget is now lightning fast!
@tunnus said in [Reactor] Variables not updating correctly in latest-25201-2aa18550:
wow, Set Rules widget is now lightning fast!
Haha! Yeah, I gave it a specialized API endpoint. It's much faster to gather the necessary data on the server side and just push it through.