public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Fiona Ebner <f.ebner@proxmox.com>
To: Hannes Laimer <h.laimer@proxmox.com>, pve-devel@lists.proxmox.com
Subject: Re: [PATCH cluster v4 5/5] cluster files: support registering UTF-8 configuration file
Date: Tue, 10 Mar 2026 12:01:09 +0100	[thread overview]
Message-ID: <41e62095-021e-4b17-93e3-d8541d6574c1@proxmox.com> (raw)
In-Reply-To: <2045463e-f1ef-464f-b74d-b4e3ce45d561@proxmox.com>

Am 10.03.26 um 11:39 AM schrieb Hannes Laimer:
> On 2026-03-10 11:16, Fiona Ebner wrote:
>> A configuration file registered as UTF-8 will be automatically decoded
>> from UTF-8 to Perl's internal string format after reading and encoded
>> in the other direction before writing.
>>
>> Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
>> ---
>>
>> Versioned dependency bump pve-cluster -> pve-common needed!
>>
>> Changes in v4:
>> * tell the parser() directly whether the file was registered as UTF-8
>>
>>  src/PVE/Cluster.pm | 18 ++++++++++++++----
>>  1 file changed, 14 insertions(+), 4 deletions(-)
>>
>> diff --git a/src/PVE/Cluster.pm b/src/PVE/Cluster.pm
>> index cd5d6b5..c1e7d4c 100644
>> --- a/src/PVE/Cluster.pm
>> +++ b/src/PVE/Cluster.pm
>> @@ -519,7 +519,7 @@ sub verify_token {
>>  my $file_info = {};
>>  
>>  sub cfs_register_file {
>> -    my ($filename, $parser, $writer) = @_;
>> +    my ($filename, $parser, $writer, $options) = @_;
>>  
>>      $observed->{$filename} || die "unknown file '$filename'";
>>  
>> @@ -529,12 +529,13 @@ sub cfs_register_file {
>>          parser => $parser,
>>          writer => $writer,
>>      };
>> +    $file_info->{$filename}->{utf8} = 1 if $options && $options->{utf8};
>>  
>>      return;
>>  }
>>  
>>  my $ccache_read = sub {
>> -    my ($filename, $parser, $version) = @_;
>> +    my ($filename, $parser, $version, $utf8) = @_;
>>  
>>      $ccache->{$filename} = {} if !$ccache->{$filename};
>>  
>> @@ -544,7 +545,14 @@ my $ccache_read = sub {
>>          # we always call the parser, even when the file does not exist
>>          # (in that case $data is undef)
>>          my $data = get_config($filename);
>> -        $ci->{data} = &$parser("/etc/pve/$filename", $data);
>> +        my $options = {};
>> +
>> +        if ($utf8) {
>> +            $data = decode('UTF-8', $data);
> 
> The docs[1] mention calling decode with undef is harmless, but will
> produce a warning, we should probably check for undef before decode

Good catch! get_config() returns undef if the file does not exist. I
cannot see a warning though:

[I] root@pve9a1 ~# cat asdf.pl
#!/usr/bin/perl
use warnings;
use strict;
use Data::Dumper;
use Encode;
my $res = decode('UTF-8', undef);
print Dumper($res);
[I] root@pve9a1 ~# perl asdf.pl
$VAR1 = undef;

I can add a check in v5, but will wait for further reviews first.

> not sure if we need one, but are we missing a
> ```
> +use Encode qw(decode);
> ```
> in Cluster.pm?

There already is
use Encode;
which auto-imports 'decode' and 'encode' (among others)
If we change it, we also need to import 'encode' explicitly (and check
if any others are used) to not break the existing calls to 'encode'.

> 
> 
> [1]
> https://perldoc.perl.org/5.8.2/Encode#$string-=-decode(ENCODING,-$octets-%5B,-CHECK%5D)




  reply	other threads:[~2026-03-10 11:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-10 10:13 [RFC common/cluster v4 0/5] " Fiona Ebner
2026-03-10 10:13 ` [PATCH common v4 1/5] file: set contents: use strict UTF-8 encoding with $force_utf8 Fiona Ebner
2026-03-10 10:13 ` [PATCH common v4 2/5] section config: prepare for supporting UTF-8 encoded configurations Fiona Ebner
2026-03-10 10:13 ` [PATCH cluster v4 3/5] cfs register file: avoid implicit return Fiona Ebner
2026-03-10 10:13 ` [PATCH cluster v4 4/5] d/control: add versioned breaks for libpve-access-control Fiona Ebner
2026-03-10 10:13 ` [PATCH cluster v4 5/5] cluster files: support registering UTF-8 configuration file Fiona Ebner
2026-03-10 10:40   ` Hannes Laimer
2026-03-10 11:01     ` Fiona Ebner [this message]
2026-03-10 11:47       ` Hannes Laimer

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=41e62095-021e-4b17-93e3-d8541d6574c1@proxmox.com \
    --to=f.ebner@proxmox.com \
    --cc=h.laimer@proxmox.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