From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Dietmar Maurer <dietmar@proxmox.com>
Subject: applied: [PATCH rest-server] rest-server: stop a json-seq stream once its client is gone
Date: Sat, 17 Oct 2026 22:29:30 +0200 [thread overview]
Message-ID: <179226896539.3596035.7744026011567707271.b4-ty@b4> (raw)
In-Reply-To: <20261017161656.3529676-1-dietmar@proxmox.com>
On Sat, 17 Oct 2026 18:16:56 +0200, Dietmar Maurer wrote:
> The task forwarding the records of a streamed response only noticed
> a closed connection when sending the next record failed. A stream
> that stays silent for a long time, such as an API handler waiting on
> a slow backend, thus kept running after its client went away, and so
> did the work behind it, as the producer only learns of the gone
> client once the stream is dropped.
>
> [...]
FYI: Wolfgang and I picked up some older patches from an experiment
I did a while ago and that covered this and some other changes that might
(hopefully) be also useful for your current work. This is all now rolled out
with some bigger schema changes.
The test part of you change here was missing though, as its definitively
useful to have I applied test part here of this patch and dropped the rest on
merge conflict resolution, thanks!
[1/1] rest-server: stop a json-seq stream once its client is gone
commit: f553d4278995bd1e2c70aa031b28157f97312e8a
prev parent reply other threads:[~2026-10-17 20:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-17 16:16 [PATCH rest-server] rest-server: stop a json-seq stream once its client is gone Dietmar Maurer
2026-10-17 20:29 ` Thomas Lamprecht [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=179226896539.3596035.7744026011567707271.b4-ty@b4 \
--to=t.lamprecht@proxmox.com \
--cc=dietmar@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox