[BUG] Save to Disk crashes Pod

[sychyoboN]

Environment

Self-Hosted (containerd)

System

Kubernetes rke2 v1.29.11+rke2r1

Version

lissy93/dashy:release-3.1.1

Describe the problem

Application has been deployed used this helm chart and using default values except for changing servicetype to NodePort and enabling an nginx ingress.

When attempting to Save config locally using interactive UI, Pod crashes with the following error message:

node:events:496
      throw er; // Unhandled 'error' event
      ^
Error [ERR_STREAM_WRITE_AFTER_END]: write after end
    at ServerResponse.end (node:_http_outgoing:1021:15)
    at /app/server.js:159:47
    at module.exports (/app/services/save-config.js:69:9)
Emitted 'error' event on ServerResponse instance at:
    at emitErrorNt (node:_http_outgoing:857:9)
    at process.processTicksAndRejections (node:internal/process/task_queues:83:21) {
  code: 'ERR_STREAM_WRITE_AFTER_END'
}
Node.js v20.11.1
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
ERROR: "start" exited with 1.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

I'm curious to know how this config change is persisted with no PVC configured, I'm assuming it needs to persist these changes in the configmap but unsure exactly.

Additional info

No response

Please tick the boxes

• You have explained the issue clearly, and included all relevant info
• You are using a supported version of Dashy
• You've checked that this issue hasn't already been raised
• You've checked the docs and troubleshooting guide
• You agree to the code of conduct

[sychyoboN]

Okay so just to add, it looks possible to export the conf.yaml from the browser and manually edit the configmap data directly with the modifications, is this expected behaviour?