Closed onkelandy closed 2 years ago
"no series for path.." is thrown if smartVISU tries to cancel a series which has already been cancelled. This happens if e.g. an event triggers a page change to the actual page. Old versions of the return home function do this and some users have copied that code into their own pages e.g. in order to show daytime related content. If your pages use this function you should implement a check whether the target page is already on display and then avoid the change. See actual code for the return home function in root.html.
IMHO the Websocket should send the "no series for path.." message to the client for debugging but avoid throwing a warning inside shNG. Why? Smartvisu wants to end series subscription and this is correctly fulfilled ;)
Hmm, I don't have any additional code on my pages. Maybe it's in quad_root.html but I don't think so. Any further ideas?
There have been some obsolete event handlers in quad_root.html. The new file is now pushed to smartvisu/develop. Could you help testing and check if the double series_cancel is avoided?
Updated to the most recent develop branch. Still get the series cancellation stuff :( Mai 19 21:48:15 WARNING modules.websocket Series cancelation: No series for path licht.eg.bad.spiegel.dimmen found in list
No seriers for path … is thrown whenever smartVISU is requesting/canceling a series (for drawing plots) and the item does not exist.
For,me it happens mostly when having a visu page open, that used to reference the item and the cached page still calls formthatbitem.
Have you cleared all caches (sv and Browser)?
The abnormal closing of the websocket connection code = 1001 (going away), no reason
is now logged as info (like code 1005 and 1006) and not raising an exception any more.
Since the issue is for the websocket module and not for the plugin, it should be placed in the core repo and not in the plugin repo.
I've made a new issue there though I am not sure if it still is an issue... Will observe.
Came "out of the blue". The exceptions happened just once so far but I guess could be catched easily. The "no series for path.." happens quite often, still not sure why