public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: James Brown via pve-devel <pve-devel@lists.proxmox.com>
To: "Andrew via pve-devel" <pve-devel@lists.proxmox.com>
Cc: "James Brown" <randomvoidmail@foxmail.com>
Subject: Re: [pve-devel] [PATCH] Patch for UTF8 encoding in Tools.pm
Date: Sun, 13 Oct 2024 18:26:43 +0800	[thread overview]
Message-ID: <mailman.302.1728815220.332.pve-devel@lists.proxmox.com> (raw)

[-- Attachment #1: Type: message/rfc822, Size: 7712 bytes --]

From: "James Brown" <randomvoidmail@foxmail.com>
To: "Andrew via pve-devel" <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH] Patch for UTF8 encoding in Tools.pm
Date: Sun, 13 Oct 2024 18:26:43 +0800
Message-ID: <tencent_DB84E383BD2F5E1012CFF0A56CC9FC44DA05@qq.com>

Do you mean if I operate this within the ESXi file reading sub block then it would be fine?


How about putting these lines on top of /usr/share/perl5/PVE/Storage/ESXiPlugin.pm?


Or just within "get_manifest" and&nbsp; "get_import_metadata" sub blocks in ESXiPlugin.pm?



---Original---
From: "Thomas Lamprecht"<t.lamprecht@proxmox.com&gt;
Date: Wed, Oct 9, 2024 14:10 PM
To: "James Brown"<randomvoidmail@foxmail.com&gt;;"pve-devel"<pve-devel@lists.proxmox.com&gt;;
Subject: Re: [pve-devel] [PATCH] Patch for UTF8 encoding in Tools.pm


Am 09/10/2024 um 02:45 schrieb James Brown:
&gt; From 8ed0c20251c464a058ea08872bc7d54f6701d912 Mon Sep 17 00:00:00 2001
&gt; From: James Brown <randomvoidmail@foxmail.com&gt;
&gt; Date: Wed, 9 Oct 2024 08:40:10 +0800
&gt; Subject: [PATCH] Add UTF8 encoding
&gt; 

Please provide some actual commit message for why this is done, and evaluating
the actual fall out of the change.

&gt; ---
&gt; &nbsp;src/PVE/Tools.pm | 4 ++++
&gt; &nbsp;1 file changed, 4 insertions(+)
&gt; 
&gt; 
&gt; diff --git a/src/PVE/Tools.pm b/src/PVE/Tools.pm
&gt; index bd305bd..cf86a0e 100644
&gt; --- a/src/PVE/Tools.pm
&gt; +++ b/src/PVE/Tools.pm
&gt; @@ -3,6 +3,10 @@ package PVE::Tools;
&gt; &nbsp;use strict;
&gt; &nbsp;use warnings;

the patch is broken, please submit it with a mail user agent that does not
messes with whitespace, if in doubt use git send-email [0].

[0]: https://git-send-email.io/
 
&gt; +use open qw(:std :utf8);

that can have lots of fallout, or did you check all sites using PVE::Tools and
opening files to ensure that all definitively will write valid UTF-8 only?

&gt; +use Encode qw(decode_utf8);
&gt; +@ARGV = map { decode_utf8($_, 1) } @ARGV;

why are you re-encoding the system argument list in some library module?!
That is really a no-go, this must stay in the control of the actual executable.

&gt; +
&gt; &nbsp;use Date::Format qw(time2str);
&gt; &nbsp;use Digest::MD5;
&gt; &nbsp;use Digest::SHA;
&gt; --
&gt; 2.34.1

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

             reply	other threads:[~2024-10-13 10:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-13 10:26 James Brown via pve-devel [this message]
     [not found] <tencent_A1C4A34146193A960D99A3486B70D4B0370A@qq.com>
2024-10-09  6:10 ` Thomas Lamprecht
  -- strict thread matches above, loose matches on Subject: below --
2024-10-09  0:45 James Brown via pve-devel

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=mailman.302.1728815220.332.pve-devel@lists.proxmox.com \
    --to=pve-devel@lists.proxmox.com \
    --cc=randomvoidmail@foxmail.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