Flooding a project with visualization requests on startup leads to some of them being "dropped"

[hubertp]

A rather common image on a slow system is

More surprisingly, closing the visualization and attaching it again will work.

This is because the sheer number of requests appears to overload the workqueue limit set for job executor. A bit surprising, since we are not seeing any rejection failures (TBD). Increasing the limit fixed the problem for me immediately, when previously I would consistently get the problem on a given project.

[enso-bot]

Hubert Plociniczak reports a new STANDUP for the provided date (2024-07-11):

Progress: Debugging another project that has trouble opening, as reported. Unable to reproduce so far. Additionally, visualizations don't show up consistently on startup It should be finished by 2024-07-12.

Next Day: Next day I will be working on the #10538 task. Continue investigating visualizations and reproducing startup issues.

[enso-bot]

Hubert Plociniczak reports a new STANDUP for the provided date (2024-07-12):

Progress: Reproduced the startup problem on a slow machine (responses being lost due to timeouts). Created PR with a fix for that and visualizations. On 07/12 missed to report closing #9915 PR that failed to produce viable results. Will need to be further investigated. It should be finished by 2024-07-12.

Next Day: Next day I will be working on the #10538 task. Continue investigating startup issues.