Skip to content

fix: [2318] Dashboard keeps disconnecting when a widget's history has more than 10 Buffers - #2323

Open
n-lark wants to merge 1 commit into
mainfrom
2318-socket-buffer-fix
Open

n-lark wants to merge 1 commit into
mainfrom
2318-socket-buffer-fix

Conversation

@n-lark

@n-lark n-lark commented Oct 20, 2026

Copy link
Copy Markdown
Contributor

Description

socket.io-parser 4.2.6 limits packets to 10 binary attachments (CVE-2026-33151). A chart history with more than 10 Buffers (e.g. Modbus data) breaks that limit, so the browser keeps disconnecting. This removes the limit on the client only, as suggested in socketio/socket.io#5504. The server keeps it.

Related Issue(s)

Resolves #2318

Checklist

  • I have read the contribution guidelines
  • Suitable unit/system level tests have been added and they pass
  • Documentation has been updated
    • Upgrade instructions
    • Configuration details
    • Concepts
  • Changes flowforge.yml?
    • Issue/PR raised on FlowFuse/helm to update ConfigMap Template
    • Issue/PR raised on FlowFuse/CloudProject to update values for Staging/Production
  • Link to Changelog Entry PR, or note why one is not needed.

Labels

  • Includes a DB migration? -> add the area:migration label

@n-lark n-lark self-assigned this Oct 20, 2026

@allthedoll allthedoll left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚀

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Dashboard disconnecting when Chart node is used

3 participants