Describe the bug
We are using a single elastic layout for tuning all our subsystems. When activating it with the robot it is unusable because it disconnects, reconnects, disconnects, reconnects over and over.
When we remove all but one tab, and thus reduce the number of topics Elastic subscribes to, it becomes usable again. (We haven't found the actual point when it becomes usable again - we know it's usable with one tab and 4 widgets and unusable with all.)
Expected behavior
It should not disconnect.
Desktop (please complete the following information):
Additional context
I asked Codex 5.3 to look at this codebase. Here is its analysis. I haven't verified any of its claims, although they seem consistent with the behavior we are seeing. Codex proposed this fix which I also haven't vetted.
I'm leaving this bug report here mainly to see if others have experienced similar issues. Our hope was to use Elastic as our main dashboard during competition, but we can't if it's not stable.
Describe the bug
We are using a single elastic layout for tuning all our subsystems. When activating it with the robot it is unusable because it disconnects, reconnects, disconnects, reconnects over and over.
When we remove all but one tab, and thus reduce the number of topics Elastic subscribes to, it becomes usable again. (We haven't found the actual point when it becomes usable again - we know it's usable with one tab and 4 widgets and unusable with all.)
Expected behavior
It should not disconnect.
Desktop (please complete the following information):
Additional context
I asked Codex 5.3 to look at this codebase. Here is its analysis. I haven't verified any of its claims, although they seem consistent with the behavior we are seeing. Codex proposed this fix which I also haven't vetted.
I'm leaving this bug report here mainly to see if others have experienced similar issues. Our hope was to use Elastic as our main dashboard during competition, but we can't if it's not stable.