public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: pve-devel@lists.proxmox.com, Michal Fox <me@dualfroz.com>
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	[thread overview]
Message-ID: <179388544182.1046459.14761114131900217711.b4-ty@proxmox.com> (raw)
In-Reply-To: <20261004143202.7-1-me@dualfroz.com>


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 <f.gruenbichler@proxmox.com>




      parent reply	other threads:[~2026-11-05 13:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-04 14:32 [PATCH common 0/2] cli formatter: fix double UTF-8 encoding of YAML Michal Fox
2026-10-04 14:32 ` [PATCH common 1/2] fix #6305: cli formatter: avoid encoding YAML output twice Michal Fox
2026-10-04 14:32 ` [PATCH common 2/2] cli formatter: decode the output of the yaml renderer Michal Fox
2026-11-05 13:30 ` Fabian Grünbichler [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=179388544182.1046459.14761114131900217711.b4-ty@proxmox.com \
    --to=f.gruenbichler@proxmox.com \
    --cc=me@dualfroz.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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal