public inbox for pdm-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Wolfgang Bumiller <w.bumiller@proxmox.com>
To: Dominik Csapak <d.csapak@proxmox.com>
Cc: pdm-devel@lists.proxmox.com
Subject: Re: [pdm-devel] [RFC PATCH datacenter-manager] server: api: resources: use root cause for errors for remote fetching
Date: Wed, 10 Sep 2025 10:15:51 +0200	[thread overview]
Message-ID: <5e6jb7tq2pmmmfnyucinmkch2c2o55u34c73wxqpelcjjcbmmd@ed2z44jgrve7> (raw)
In-Reply-To: <20250909082608.1018103-1-d.csapak@proxmox.com>

On Tue, Sep 09, 2025 at 10:25:51AM +0200, Dominik Csapak wrote:
> when we can't reach a remote for any reason, we want to return the error
> as a string here over the API. Since most errors that can occur here are
> client/network related (wrong credentials, no route to host, timeout,
> etc.) converting this error directly to a string gives us
> errors like:
> 
> `client error (Connect)`
> 
> which is not really helpful most of the time.
> Instead if we use the `root_cause()`, we get the most underlying error
> 
> e.g.
> 
> `error connecting to https://0.0.0.0:8006/ - tcp connect error: No route to host (os error 113)`
> 
> which is much more helpful.
> 
> We could also think about printing the whole error chain, but in my test
> cases here this was not more helpful, e.g. i got two times the above
> `client error (Connect)` and once the root cause from above.

Curious, because from a quick grep, `client error (*)` comes from hyper.
Otherwise I'd say it may have been one our own error types or
one-too-many same `.context()` calls.

I'm still not sure this is a good idea though, as we may still lose some
useful contest. I wish anyhow had an easy method to just shave off a
single layer.

What if we do this, but first throw in a:

    tracing::debug!("{error:?}");

just so we still have the option to see everything if we need to?

> 
> Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
> ---
>  server/src/api/resources.rs | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/server/src/api/resources.rs b/server/src/api/resources.rs
> index 98c4dea..cca8bcb 100644
> --- a/server/src/api/resources.rs
> +++ b/server/src/api/resources.rs
> @@ -245,7 +245,7 @@ pub(crate) async fn get_resources_impl(
>          let handle = tokio::spawn(async move {
>              let (mut resources, error) = match get_resources_for_remote(remote, max_age).await {
>                  Ok(resources) => (resources, None),
> -                Err(error) => (Vec::new(), Some(error.to_string())),
> +                Err(error) => (Vec::new(), Some(error.root_cause().to_string())),
>              };
>  
>              if remotes_only {
> -- 
> 2.47.2


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


  reply	other threads:[~2025-09-10  8:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-09  8:25 Dominik Csapak
2025-09-10  8:15 ` Wolfgang Bumiller [this message]
2025-09-10  8:31   ` Dominik Csapak
2025-09-10 10:19     ` Wolfgang Bumiller
2025-09-10 15:12 ` [pdm-devel] applied: " 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=5e6jb7tq2pmmmfnyucinmkch2c2o55u34c73wxqpelcjjcbmmd@ed2z44jgrve7 \
    --to=w.bumiller@proxmox.com \
    --cc=d.csapak@proxmox.com \
    --cc=pdm-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