I have today hit the exact same error. I have a temperature feed from a DHT22 running on an ESP32 pumping data into emoncms’s MQTT broker, and it has clearly had a single outlier spike at -1°C at some stage recently, and I want it edited to smooth out that graph (because another virtual feed is doing a ‘flow - return temperature difference’ calculation, and that outlier is ruining my axis and wrecking my OCD )
So I did the same as you - went into Visualisations, chose EditRealtime, selected the feed in question (in my case, #77) and got exactly the same error (aside from the feedid). Same everything else - line and column number. I get it on all feeds, it turns out.
And in my case, selecting ‘full-screen’ instead of ‘view’, I see the same error but on line 346. Is this the same for you?
I’m on latest stable everything. Running emoncms et al, on a Raspberry Pi (albeit on Buster I think). Everything else seems nominal.
Good point, @borpin - I confess I didn’t think of checking the github earlier when I posted.
Just checking this morning, and I realise it’s been on the issues list since 16-March.
All good - it’s logged. We just have to sit tight now until it gets sorted. Might even have a crack at myself, but not sure I’m brave enough
(reading deeper, it’s a security change in Chrome/Chromium that’s causing this, based on the fact that the URLs have whitespace-codes and < brackets in them. Short-term solve @Techno might be just to use Edge or Firefox to do that job? Gonna give it a whirl when I’m back from the school-run…)
I guess as Edge is based on Chromium as well then it’s something in the core thats rejecting the code
Yay some success, I’m not getting the error using Firefox on a Mac and it seems to be removing some of the peaks, I need to pay more attention to the time code to verify if the reading I’m editing doesn’t last for more than one record.
However if I try the “delete data in window” option in Firefox then I get a new error.
To achieve the edition function, please note they must be run in full screen mode
maybe give that a whirl in fullscreen mode instead of View mode, and see whether it still fails? The ‘modal’ error tends to support the hunch (given that modal is probably missing unless the display is fullscreen, maybe?)
Apologies if this is a goose-chase.
Looking at the code, I’ll put my hand up and say my knowledge of MVC website coding is not good enough to actually solve this issue and make a pull-request - at least, not yet.