From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com,
Thomas Ellmenreich <t.ellmenreich@proxmox.com>
Subject: applied: [PATCH proxmox-acme v3 1/1] fix #7749: always serialize in same order
Date: Thu, 3 Sep 2026 01:21:11 +0200 [thread overview]
Message-ID: <178839126712.1135632.9500063983608101469.b4-ty@b4> (raw)
In-Reply-To: <20260812115128.135004-1-t.ellmenreich@proxmox.com>
On Wed, 12 Aug 2026 13:51:28 +0200, Thomas Ellmenreich wrote:
> All objects are now serialized with "canonical => 1" so that the
> resulting bytes are directly comparable. Perls randomized hash key
> orders lead to different serialization outputs even with the same input.
>
> The 'tojs' function also now explicitly overrides the utf8 and canonical
> options to make sure that they are always set.
>
> [...]
Applied, thanks!
[1/1] fix #7749: always serialize in same order
commit: 579d78f9fdd15277f5df0870ddc0bc5e391dd221
prev parent reply other threads:[~2026-09-02 23:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-12 11:51 [PATCH proxmox-acme v3 1/1] fix #7749: always serialize in same order Thomas Ellmenreich
2026-08-14 10:11 ` Elias Huhsovitz
2026-09-02 23:21 ` 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=178839126712.1135632.9500063983608101469.b4-ty@b4 \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=t.ellmenreich@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