public inbox for pbs-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Gabriel Goller <g.goller@proxmox.com>
To: Wolfgang Bumiller <w.bumiller@proxmox.com>
Cc: pbs-devel@lists.proxmox.com
Subject: Re: [pbs-devel] applied: [PATCH proxmox-backup] fix: proxmox-backup-manager network reload wait on worker
Date: Fri, 30 Aug 2024 10:18:22 +0200	[thread overview]
Message-ID: <20240830081822.gtk62nmcqjtw7wdg@luna.proxmox.com> (raw)
In-Reply-To: <ozfohkma3enwnuk2cj6gnzqzcteexwysxsn7ul75xsv7hfsnrt@2kic5ojtb2h7>

On 29.08.2024 14:17, Wolfgang Bumiller wrote:
>applied, thanks
>
>On Wed, Aug 21, 2024 at 12:22:36PM GMT, Gabriel Goller wrote:
>> Make the `network reload` command in proxmox-backup-manager wait on the
>> api handler's workertask. Otherwise the task would be killed when the
>> client exits.
>>
>> Signed-off-by: Gabriel Goller <g.goller@proxmox.com>
>> ---
>>  src/bin/proxmox_backup_manager/network.rs | 21 +++++++++++++++++++--
>>  1 file changed, 19 insertions(+), 2 deletions(-)
>>
>> diff --git a/src/bin/proxmox_backup_manager/network.rs b/src/bin/proxmox_backup_manager/network.rs
>> index deac5b1b2960..0f0a50a8932a 100644
>> --- a/src/bin/proxmox_backup_manager/network.rs
>> +++ b/src/bin/proxmox_backup_manager/network.rs
>> @@ -129,6 +129,24 @@ fn pending_network_changes(
>>      Ok(Value::Null)
>>  }
>>
>> +#[api()]
>> +/// Reload network changes
>> +async fn reload_network_changes(
>> +    mut param: Value,
>> +    rpcenv: &mut dyn RpcEnvironment,
>> +) -> Result<Value, Error> {
>> +    param["node"] = "localhost".into();
>> +
>> +    let info = &api2::node::network::API_METHOD_RELOAD_NETWORK_CONFIG;
>> +    let result = match info.handler {
>> +        ApiHandler::Async(handler) => (handler)(param, info, rpcenv).await?,
>> +        _ => unreachable!(),
>> +    };
>
>Note: we have the above pattern a lot. For `Schema` we already have a
>bunch of `const fn unwrap_<type>_schema()`.
>We can now also use `const {}` expressions, so maybe we should have
>something like this for `ApiHandler` as well, with all these handler
>functions then using something like:
>
>    let handler = const { info.handler.unwrap_async_handler() };
>    let result = (handler)(param, info, rpcenv).await?
>

Hmm on a second glance, I don't think we can do this currently.

I tried this:

     pub const fn unwrap_async_handler(&self) -> &ApiAsyncHandlerFn {
         match self {
             ApiHandler::Async(a) => a,
             _ => panic!("unwrap_async_handler called on wrong apihandler"),
         }
     }

But it doesn't compile because we have a &mut reference in
`ApiAsyncHandlerFn` and mutable references in `const fn`'s currently
don't work [0]. 

Obviously we can make everything non-const and still improve the
readability.

[0]: https://github.com/rust-lang/rust/issues/57349.


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


  reply	other threads:[~2024-08-30  8:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-21 10:22 [pbs-devel] " Gabriel Goller
2024-08-29 12:17 ` [pbs-devel] applied: " Wolfgang Bumiller
2024-08-30  8:18   ` Gabriel Goller [this message]
2024-08-30  9:00     ` Wolfgang Bumiller

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=20240830081822.gtk62nmcqjtw7wdg@luna.proxmox.com \
    --to=g.goller@proxmox.com \
    --cc=pbs-devel@lists.proxmox.com \
    --cc=w.bumiller@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