public inbox for pbs-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Gabriel Goller <g.goller@proxmox.com>
To: Lukas Wagner <l.wagner@proxmox.com>
Cc: Proxmox Backup Server development discussion
	<pbs-devel@lists.proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox v5 2/4] enable tracing logger, remove task_log macros
Date: Tue, 25 Jun 2024 10:49:56 +0200	[thread overview]
Message-ID: <20240625084956.hrd5ryjtxqq7odim@luna.proxmox.com> (raw)
In-Reply-To: <3486aeae-4ddc-4b16-9b11-5989abc52304@proxmox.com>

Thanks for the review!

On 24.06.2024 13:09, Lukas Wagner wrote:
>2 nits inline
>
>On  2024-06-13 15:56, Gabriel Goller wrote:
>> diff --git a/proxmox-rest-server/src/worker_task.rs b/proxmox-rest-server/src/worker_task.rs
>> index 5bab4cdc..58537f54 100644
>> --- a/proxmox-rest-server/src/worker_task.rs
>> +++ b/proxmox-rest-server/src/worker_task.rs
>> @@ -1,3 +1,4 @@
>> +use std::cell::{Cell, RefCell};
>>  use std::collections::{HashMap, VecDeque};
>>  use std::fs::File;
>>  use std::io::{BufRead, BufReader, Read, Write};
>> @@ -12,21 +13,23 @@ use futures::*;
>>  use lazy_static::lazy_static;
>>  use nix::fcntl::OFlag;
>>  use once_cell::sync::OnceCell;
>> +use proxmox_log::{LOGGER, WARN_COUNTER};
>
>Nit: Order of imports, let's put this import to the other
>proxmox_* imports below

Fixed!

>> @@ -340,11 +346,9 @@ pub fn cleanup_old_tasks(worker: &dyn WorkerTaskContext, compressed: bool) -> Re
>>                  let file = match file {
>>                      Ok(file) => file,
>>                      Err(err) => {
>> -                        task_warn!(
>> -                            worker,
>> -                            "could not check some task log in '{:02X}': {}",
>> -                            i,
>> -                            err
>> +                        warn!(
>> +                            tasklog = true,
>> +                            "could not check some task log in '{:02X}': {}", i
>err
>
>Nit: You could inline these vars if you edit these lines any way.

Fixed! Also removed the 'tasklog = true' parameter, which we removed in
a previous version.



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




  reply	other threads:[~2024-06-25  8:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-13 13:56 [pbs-devel] [PATCH proxmox{, -backup} v5 0/4] proxmox-log introduction Gabriel Goller
2024-06-13 13:56 ` [pbs-devel] [PATCH proxmox v5 1/4] proxmox-log: add tracing infrastructure Gabriel Goller
2024-06-24 11:10   ` Lukas Wagner
2024-06-25  8:44     ` Gabriel Goller
2024-06-25  9:04       ` Lukas Wagner
2024-06-26  7:55         ` Fabian Grünbichler
2024-06-13 13:56 ` [pbs-devel] [PATCH proxmox v5 2/4] enable tracing logger, remove task_log macros Gabriel Goller
2024-06-24 11:09   ` Lukas Wagner
2024-06-25  8:49     ` Gabriel Goller [this message]
2024-06-13 13:56 ` [pbs-devel] [PATCH proxmox-backup v5 3/4] switch from task_log! macro to tracing Gabriel Goller
2024-06-24 11:10   ` Lukas Wagner
2024-06-13 13:56 ` [pbs-devel] [PATCH proxmox-backup v5 4/4] api: " Gabriel Goller
2024-06-24 11:13 ` [pbs-devel] [PATCH proxmox{, -backup} v5 0/4] proxmox-log introduction Lukas Wagner
2024-06-26 13:10 ` Gabriel Goller

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=20240625084956.hrd5ryjtxqq7odim@luna.proxmox.com \
    --to=g.goller@proxmox.com \
    --cc=l.wagner@proxmox.com \
    --cc=pbs-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