From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [45.144.208.40]) by lore.proxmox.com (Postfix) with ESMTPS id 528C91FF0B7 for ; Fri, 16 Oct 2026 01:21:26 +0200 (CEST) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 0D7AF21400; Fri, 16 Oct 2026 01:21:26 +0200 (CEST) From: Thomas Lamprecht To: yew-devel@lists.proxmox.com, Dietmar Maurer Subject: applied: [PATCH yew-comp] http stream: return each json-seq record once it is complete Date: Fri, 16 Oct 2026 01:21:12 +0200 Message-ID: <179210637496.3746002.7225025225619336356.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20261015060555.1048633-1-dietmar@proxmox.com> References: <20261015060555.1048633-1-dietmar@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1792106482800 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.516 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: 2O5DGL2EM4DQLY53W6QBMKE2FKGHTGSY X-Message-ID-Hash: 2O5DGL2EM4DQLY53W6QBMKE2FKGHTGSY X-MailFrom: t.lamprecht@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Yew framework devel list at Proxmox List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Thu, 15 Oct 2026 08:05:55 +0200, Dietmar Maurer wrote: > proxmox-router frames each record of a json-seq stream as RFC 7464 > describes it: a record separator, the JSON text and a line feed. The > readers split at the record separators, so they returned a record only > once the next one started. The latest record was held back for as long > as the server had nothing new to send, which a streaming UI shows as a > status or result that lags one event behind, for example a finished > tool call that only shows while a slow language model answers. > > [...] Applied, thanks! [1/1] http stream: return each json-seq record once it is complete commit: 72822c05507270748f9e33519efa276232b0081c