From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Daniel Tschlatscher <d.tschlatscher@proxmox.com>,
pbs-devel@lists.proxmox.com, pmg-devel@lists.proxmox.com
Subject: [pve-devel] applied: [PATCH common v4] return whole log file if limit is 0
Date: Thu, 24 Nov 2022 17:24:38 +0100 [thread overview]
Message-ID: <b90a7f8e-e6fb-21a7-88e8-cf57b279f1c9@proxmox.com> (raw)
In-Reply-To: <20221123145210.592981-5-d.tschlatscher@proxmox.com>
Am 23/11/2022 um 15:52 schrieb Daniel Tschlatscher:
> The dump_logfile now returns the whole log file if the limit parameter
> is set to 0. This must be done explicitely though, as in the case of
> 'limit' being undefined, the default as before, 50 will be used.
>
> Signed-off-by: Daniel Tschlatscher <d.tschlatscher@proxmox.com>
> ---
> Changes from v3:
> * NEW patch
>
> This patch also affects the API endpoints for:
> * the ceph log file
> * replication log files
> * firewall Guest and Host log files
>
> It does not change how they behave in the GUI though, as all of the
> corresponding API calls there do not specify a 'limit=0' parameter.
> In fact, none of them specify any limit, therefore, the default value
> of 50 still applies.
>
> src/PVE/Tools.pm | 17 +++++++++++------
> 1 file changed, 11 insertions(+), 6 deletions(-)
applied, thanks!
>
> diff --git a/src/PVE/Tools.pm b/src/PVE/Tools.pm
> index eb81b96..6072eb7 100644
> --- a/src/PVE/Tools.pm
> +++ b/src/PVE/Tools.pm
> @@ -1278,9 +1278,10 @@ sub dump_logfile {
> return ($count, $lines);
> }
>
> - $start = 0 if !$start;
> - $limit = 50 if !$limit;
> + $start = $start // 0;
> + $limit = $limit // 50;
>
> + my $read_until_end = ($limit == 0) ? 1 : 0;
no need for transform booleans to booleans ;-)
WARNING: multiple messages have this Message-ID
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Daniel Tschlatscher <d.tschlatscher@proxmox.com>,
pbs-devel@lists.proxmox.com, pmg-devel@lists.proxmox.com
Subject: [pbs-devel] applied: [pve-devel] [PATCH common v4] return whole log file if limit is 0
Date: Thu, 24 Nov 2022 17:24:38 +0100 [thread overview]
Message-ID: <b90a7f8e-e6fb-21a7-88e8-cf57b279f1c9@proxmox.com> (raw)
In-Reply-To: <20221123145210.592981-5-d.tschlatscher@proxmox.com>
Am 23/11/2022 um 15:52 schrieb Daniel Tschlatscher:
> The dump_logfile now returns the whole log file if the limit parameter
> is set to 0. This must be done explicitely though, as in the case of
> 'limit' being undefined, the default as before, 50 will be used.
>
> Signed-off-by: Daniel Tschlatscher <d.tschlatscher@proxmox.com>
> ---
> Changes from v3:
> * NEW patch
>
> This patch also affects the API endpoints for:
> * the ceph log file
> * replication log files
> * firewall Guest and Host log files
>
> It does not change how they behave in the GUI though, as all of the
> corresponding API calls there do not specify a 'limit=0' parameter.
> In fact, none of them specify any limit, therefore, the default value
> of 50 still applies.
>
> src/PVE/Tools.pm | 17 +++++++++++------
> 1 file changed, 11 insertions(+), 6 deletions(-)
applied, thanks!
>
> diff --git a/src/PVE/Tools.pm b/src/PVE/Tools.pm
> index eb81b96..6072eb7 100644
> --- a/src/PVE/Tools.pm
> +++ b/src/PVE/Tools.pm
> @@ -1278,9 +1278,10 @@ sub dump_logfile {
> return ($count, $lines);
> }
>
> - $start = 0 if !$start;
> - $limit = 50 if !$limit;
> + $start = $start // 0;
> + $limit = $limit // 50;
>
> + my $read_until_end = ($limit == 0) ? 1 : 0;
no need for transform booleans to booleans ;-)
WARNING: multiple messages have this Message-ID
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Daniel Tschlatscher <d.tschlatscher@proxmox.com>,
pbs-devel@lists.proxmox.com, pmg-devel@lists.proxmox.com
Subject: [pmg-devel] applied: [pve-devel] [PATCH common v4] return whole log file if limit is 0
Date: Thu, 24 Nov 2022 17:24:38 +0100 [thread overview]
Message-ID: <b90a7f8e-e6fb-21a7-88e8-cf57b279f1c9@proxmox.com> (raw)
In-Reply-To: <20221123145210.592981-5-d.tschlatscher@proxmox.com>
Am 23/11/2022 um 15:52 schrieb Daniel Tschlatscher:
> The dump_logfile now returns the whole log file if the limit parameter
> is set to 0. This must be done explicitely though, as in the case of
> 'limit' being undefined, the default as before, 50 will be used.
>
> Signed-off-by: Daniel Tschlatscher <d.tschlatscher@proxmox.com>
> ---
> Changes from v3:
> * NEW patch
>
> This patch also affects the API endpoints for:
> * the ceph log file
> * replication log files
> * firewall Guest and Host log files
>
> It does not change how they behave in the GUI though, as all of the
> corresponding API calls there do not specify a 'limit=0' parameter.
> In fact, none of them specify any limit, therefore, the default value
> of 50 still applies.
>
> src/PVE/Tools.pm | 17 +++++++++++------
> 1 file changed, 11 insertions(+), 6 deletions(-)
applied, thanks!
>
> diff --git a/src/PVE/Tools.pm b/src/PVE/Tools.pm
> index eb81b96..6072eb7 100644
> --- a/src/PVE/Tools.pm
> +++ b/src/PVE/Tools.pm
> @@ -1278,9 +1278,10 @@ sub dump_logfile {
> return ($count, $lines);
> }
>
> - $start = 0 if !$start;
> - $limit = 50 if !$limit;
> + $start = $start // 0;
> + $limit = $limit // 50;
>
> + my $read_until_end = ($limit == 0) ? 1 : 0;
no need for transform booleans to booleans ;-)
next prev parent reply other threads:[~2022-11-24 16:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 14:52 [pve-devel] [PATCH backup/pmg-api/manager/common v4] fix: #3971 Tasklog download button Daniel Tschlatscher
2022-11-23 14:52 ` [pmg-devel] " Daniel Tschlatscher
2022-11-23 14:52 ` [pbs-devel] " Daniel Tschlatscher
2022-11-23 14:52 ` [pve-devel] [PATCH backup v4] make tasklog downloadable in the backup server backend Daniel Tschlatscher
2022-11-23 14:52 ` [pmg-devel] " Daniel Tschlatscher
2022-11-23 14:52 ` [pbs-devel] " Daniel Tschlatscher
2022-11-24 10:26 ` [pve-devel] applied: " Wolfgang Bumiller
2022-11-24 10:26 ` [pmg-devel] " Wolfgang Bumiller
2022-11-24 10:26 ` [pbs-devel] applied: " Wolfgang Bumiller
2022-11-23 14:52 ` [pve-devel] [PATCH pmg-api v4] make tasklog downloadable in the PMG backend Daniel Tschlatscher
2022-11-23 14:52 ` [pmg-devel] " Daniel Tschlatscher
2022-11-23 14:52 ` [pbs-devel] " Daniel Tschlatscher
2022-11-23 14:52 ` [pve-devel] [PATCH manager v4] make task log downloadable in the PVE manager backend Daniel Tschlatscher
2022-11-23 14:52 ` [pmg-devel] " Daniel Tschlatscher
2022-11-23 14:52 ` [pbs-devel] " Daniel Tschlatscher
2022-11-23 14:52 ` [pve-devel] [PATCH common v4] return whole log file if limit is 0 Daniel Tschlatscher
2022-11-23 14:52 ` [pmg-devel] " Daniel Tschlatscher
2022-11-23 14:52 ` [pbs-devel] " Daniel Tschlatscher
2022-11-24 16:24 ` Thomas Lamprecht [this message]
2022-11-24 16:24 ` [pmg-devel] applied: [pve-devel] " Thomas Lamprecht
2022-11-24 16:24 ` [pbs-devel] " Thomas Lamprecht
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=b90a7f8e-e6fb-21a7-88e8-cf57b279f1c9@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=d.tschlatscher@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
--cc=pmg-devel@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal