From: "Michael Köppl" <m.koeppl@proxmox.com>
To: Dominik Csapak <d.csapak@proxmox.com>,
Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH dart_api_client 1/1] change exception toString to only print details if not null
Date: Fri, 23 May 2025 09:51:09 +0200 [thread overview]
Message-ID: <a57d3cdd-1bcb-4db0-a3a2-48a74f73540b@proxmox.com> (raw)
In-Reply-To: <1d17d554-0905-4ab5-86bf-9d8d97c453a9@proxmox.com>
Thanks for having a look at this. I did not encounter this in the app.
The places where I could have, avoid this by either printing `e.message`
directly or simply throwing. This patch was a reaction to [0], where
"Host unreachable, possibly offline. -> null" would have been printed if
the the error had been wrapped in a ProxmoxApiException. Of course you
could just throw and avoid this altogether, but I think consistently
wrapping errors in ProxmoxApiException makes sense if we wanted to make
changes to error messages in the future and still keep things
consistent. Also, since `details` is defined as `Map<String, dynamic>?`,
I figured it might as well be treated as possibly null as there are
cases where there are no details (e.g. authentication timeout).
[0]
https://lore.proxmox.com/pve-devel/680650ab-aa4b-4cc7-8d2b-69516ffabef6@proxmox.com/
On 5/21/25 13:04, Dominik Csapak wrote:
> patch looks good to me, but do you remember where you encountered this?
> would make the commit message a bit better if we know how we could trigger
> this (especially when trying to test this ;) )
>
> If you want i can fix up the commit message with an example on applying
>
> On 5/5/25 09:28, Michael Köppl wrote:
>> Without this check, the toString method returns '-> null' at the end of
>> the exception message if there are no details.
>>
>> Signed-off-by: Michael Köppl <m.koeppl@proxmox.com>
>> ---
>> lib/src/proxmox_api_exception.dart | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/lib/src/proxmox_api_exception.dart b/lib/src/
>> proxmox_api_exception.dart
>> index 8dddc7c..5c6f343 100644
>> --- a/lib/src/proxmox_api_exception.dart
>> +++ b/lib/src/proxmox_api_exception.dart
>> @@ -7,6 +7,6 @@ class ProxmoxApiException implements Exception {
>> @override
>> String toString() {
>> - return '$message -> $details';
>> + return details != null ? '$message -> $details' : message;
>> }
>> }
>
>
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-05-23 7:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-05 7:28 Michael Köppl
2025-05-05 15:44 ` Shan Shaji
2025-05-21 11:04 ` Dominik Csapak
2025-05-23 7:51 ` Michael Köppl [this message]
2025-06-04 11:11 ` [pve-devel] applied: " Dominik Csapak
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=a57d3cdd-1bcb-4db0-a3a2-48a74f73540b@proxmox.com \
--to=m.koeppl@proxmox.com \
--cc=d.csapak@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