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 920BC1FF0DF for ; Thu, 05 Nov 2026 14:31:37 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 18DCA215CA; Thu, 05 Nov 2026 14:31:35 +0100 (CET) From: =?UTF-8?q?Fabian=20Gr=C3=BCnbichler?= To: pve-devel@lists.proxmox.com, Michal Fox Subject: applied-series: [PATCH common 0/2] cli formatter: fix double UTF-8 encoding of YAML Date: Thu, 5 Nov 2026 14:30:46 +0100 Message-ID: <179388544182.1046459.14761114131900217711.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20261004143202.7-1-me@dualfroz.com> References: <20261004143202.7-1-me@dualfroz.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: 1793885490965 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.620 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: SD7KN7L57LHDITRERV6GGQXAQNNG5OVK X-Message-ID-Hash: SD7KN7L57LHDITRERV6GGQXAQNNG5OVK X-MailFrom: f.gruenbichler@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: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Sun, 04 Oct 2026 14:32:00 +0000, Michal Fox wrote: > both the 'yaml' output format and the 'yaml' renderer of the text output > still handled the output of YAML::XS::Dump as a character string, which > was right for CPAN::Meta::YAML used before 99d0252, so any non-ASCII > character got encoded twice. > > 1/2 fixes the 'yaml' output format from #6305, as the reporter suggested > in the bug. 2/2 does the same for the renderer, which is used for > example for the ACME account details. > > [...] Applied, thanks! [1/2] fix #6305: cli formatter: avoid encoding YAML output twice commit: 8b5fe67907b941f2206864b6a19f1762fe9b6904 [2/2] cli formatter: decode the output of the yaml renderer commit: d4928b944b531b3f3700af02acb26d6e3c43c03b Best regards, -- Fabian Grünbichler