-
Notifications
You must be signed in to change notification settings - Fork 326
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Regressions in visualizations and drop-downs behavior #7001
Comments
Tested newest develop (372bc8f) and we for some reason attach visualization on all nodes during project open. It clutters the engine with "attachVisualization" requests, and some returns timeouts (the engine's timeouts, not IDE's). So the problem is twofold:
@hubertp Ad 2. Do you have any issue for those "attaching visualization" timeouts? They seem to come back like a chorus on various vis problems. |
Regarding point 1 from above comment, the offending commit seems to be 72b202b @MichaelMauderer However, given the above note, this bug should be considered only a catalyst, not the root cause. I would not revert it @sylwiabr |
I think the attachVisualization to all nodes is possibly due to the widget evaluation rather than the vizzes. |
No, we attach them also on nodes. It's easy to spot when you actually click the eye icon while tracking network log: first visualization show does not send attach visualization (because it's already attached). Also, when browsing all "attach visualization" on project startup you can clearly see the difference between widget visualizations (which call "get_widget_json" as preprocessor) and "normal" visualizations (calling "default_preprocessor"). Below we have 11 of them, before Michael's commit there was only one.
|
As requested we attempted to open all the visualizations on the little workflow and after 9 were open opening any more failed and the viz closed. After that it became the same as with develop where if we do another action (like changing a locale) the previous change then calculates. 2023-06-09_13-58-23.mp4 |
@farmaazon thanks for the details. I don't understand one comment here: "However, given the above note, this bug should be considered only a catalyst, not the root cause." – so is Michaels commit introducing a bug or not? Earlier you told that before the commit visualizations were not attached to all the nodes. I'm just trying to understand better what happens :) |
@jdunkerley What you shown on the video is worrying. Why changing one node would affect another to recompute? I'm not sure whether this is the same bug as this one. |
Look at my comment #7001 (comment) The second point was always a problem, Michael's bug just made it visible on every project. So Michale's commit introduced bug, but not the bug described in this issue. |
@farmaazon all clear now! Thank you! |
This part is fixed in my upcoming PR #6954, as it was the root of major performance issues. |
Only occurs once you overload the vizzes. |
#7005 is the task to investigate the timeouts on the LS side. Since it is not yet clear whether it is LS to blame, I am also attaching |
So I mark those two tasks as tracked by this one (see the top of the description). |
Both the frontend and backend tasks to fix this are closed, so I'll mark this fixed. |
Tasks
AttachVisualizationHandler
#7005Discord username
No response
What type of issue is this?
Permanent – Occurring repeatably
Is this issue blocking you from using Enso?
Is this a regression?
What issue are you facing?
The package from 2.06 is working perfectly fine.
The package from the 6.06 has those issue.
The Package from 09.06 has even bigger problems with showing drop-downs.
I am assuming this was at the beginning caused by 72b202b .
Please confirm the root cause of the issues and revert the problematic commits.
We were testing different versions of the IDE with newest Engine to make sure it is the regression on the IDE side.
Expected behaviour
visualizations should work fluently and update when drop-down is changed. Drop-downs should appear on the project start.
How we can reproduce it?
No response
Screenshots or screencasts
Screencast form the IDE from 02.06 + Engine from 09.06
02.06.mov
Screencast form the IDE from 06.06 + Engine from 09.06
06.06.mov
Screencast form the IDE from 09.06 + Engine from 09.06
09.06_720.mov
Logs
No response
Enso Version
nightly 09.06
Browser or standalone distribution
Standalone distribution (local project)
Browser Version or standalone distribution
standalone
Operating System
Windows
Operating System Version
No response
Hardware you are using
No response
The text was updated successfully, but these errors were encountered: