Not sure if this will be fixed since it’s a legacy node, but I’ll mention it in case there’s something else amiss, or in case someone else has this same error.
For a few years over multiple versions of KNIME, I’ve used Table View (JavaScript) in a component. I’ve never had any issue until I upgraded to 5.5. Now it throws an error.
To reproduce in 5.5 (I’m on Windows 11), get a normal input table (Data Generator node will do) and send it to Table View (JavaScript) (legacy).
In that node click the “Enable lazy loading” button, click ok.
thanks for reporting, we have tried to reproduce the issue, but we are currently unable to reproduce. Is there anything special to your setup?
Just to be sure, this all happens in the KNIME Analytics Platform and not on the Hub or Server?
I’ve never had a problem with this happening before now.
Test 1: I went back to a 5.4.4 installation on the same (second) computer and it did not produce the error. I saved the workflow, and re-opened in 5.5.0 and the error came up without making any wf changes.
Going the opposite way:
Test 2: If I create the WF in 5.5.0 and save, then open in 5.4.4 (ignoring version warnings) it doesn’t have any issues.
Test 3: I tried with a 3rd computer and it initially didn’t throw the error. Then after a few times of opening the node it threw the error and continued to intermittently.
Test 4: I went back to the first computer, started recording again, and as you can see in the recording, it intermittently/randomly threw the error in 5.5.0, and other times it worked. So it’s reproduceable just by opening/closing the view over and over. The same happened on the second computer.
Since it happens across 3 computers with 5.5.0 and not 5.4.4, that feels like it’s strongly pointing to 5.5.0 as the culprit.
thanks for providing the additional tests. I agree that this points towards a problem in 5.5.0. I am currently still a bit puzzled why we can’t reproduce it internally, but will further investigate and update this thread as soon as I figured it out.
Sorry for the inconvenience and thanks for the help,
Daniel
Good news. We were able to reproduce. Putting more than one of these views into a component and opening that reveals the problem very reliable. Now the good part, we already fixed this problem in the upcoming 5.5.1, which should be released soon.
Ah that is a good way to start the week. Thanks so much for investigating and fixing. I was in two minds as to whether I should report as it’s a legacy node, but I’m glad I did now. Looking forward to 5.5.1!
