🐞 Describe the bug
First, the client seems to limit the size of an attachment to 1MB, at least when using stdin.
I've set attachment-file-size-limit: 5M on the server and in my local client.yml but it doesn't change the behavior.
Additionally, and maybe with a higher severity, when piping the output of a process to ntfy, it closes the pipe once the limit is reached, killing the process at the start of the chain.
There should be a way to say to ntfy "OK, attach only data to the size limit and discard the rest, but don't exit when data is still flowing" so that the first process would keep going instead of being killed by a Broken pipe.
💻 Components impacted
Self-hosted ntfy, version 2.19.2
Local ntfy client, same version.
🐞 Describe the bug
First, the client seems to limit the size of an attachment to 1MB, at least when using stdin.
I've set
attachment-file-size-limit: 5Mon the server and in my local client.yml but it doesn't change the behavior.Additionally, and maybe with a higher severity, when piping the output of a process to
ntfy, it closes the pipe once the limit is reached, killing the process at the start of the chain.There should be a way to say to ntfy "OK, attach only data to the size limit and discard the rest, but don't exit when data is still flowing" so that the first process would keep going instead of being killed by a
Broken pipe.💻 Components impacted
Self-hosted ntfy, version 2.19.2
Local ntfy client, same version.