all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: "Shan Shaji" <s.shaji@proxmox.com>
To: "Dominik Csapak" <d.csapak@proxmox.com>,
	"Proxmox VE development discussion" <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH proxmox_dart_api_client] fix: ios: add type check to catch `NSErrorClientException`
Date: Fri, 17 Oct 2025 13:09:43 +0200	[thread overview]
Message-ID: <DDKJUACH7LAQ.ZO163AQH6P92@proxmox.com> (raw)
In-Reply-To: <df415d02-2a85-433c-b48f-aac1fbb301c0@proxmox.com>

On Fri Oct 17, 2025 at 9:40 AM CEST, Dominik Csapak wrote:
> wouldn't it be easier and more robust if we simply reverse the two
> catch blocks?
> e.g

I think, yes that's better. Will send an updated patch. 

Since `NsClientErrorException` was a subclass i added the additional check
inside the ClientErrorException but adding the seperate on clauses
branches are more readable and clear. Thank you!

>
> try {
> } on... {
> ...
> } on NSErrorClientException catch (e) {
> ...
> } on http.ClientException catch (e) {
> ...
> }
>
> ?
>
> On 10/1/25 11:52 AM, Shan Shaji wrote:
>> The `NSErrorClientException` catch clause was not being executed because
>> it's a subtype of `ClientException`. This resulted in showing the
>> actual error from the package instead of our custom error message when
>> the SSL/TLS handshake failed. Fixed the issue by adding a type check
>> inside the `ClientException` catch clause.
>> 
>> Signed-off-by: Shan Shaji <s.shaji@proxmox.com>
>> ---
>>   lib/src/authenticate.dart | 12 ++++++------
>>   1 file changed, 6 insertions(+), 6 deletions(-)
>> 
>> diff --git a/lib/src/authenticate.dart b/lib/src/authenticate.dart
>> index 04f363f..aaae50b 100644
>> --- a/lib/src/authenticate.dart
>> +++ b/lib/src/authenticate.dart
>> @@ -61,12 +61,12 @@ Future<ProxmoxApiClient> authenticate(
>>       if (e.message.contains('net::ERR_CERT_AUTHORITY_INVALID')) {
>>         throw HandshakeException(e.message);
>>       }
>> -    rethrow;
>> -  } on NSErrorClientException catch (e) {
>> +
>>       // Treat untrusted server certificate (-1202) as a handshake failure.
>> -    if (e.error.code == -1202) {
>> +    if (e is NSErrorClientException && e.error.code == -1202) {
>>         throw HandshakeException(e.message);
>>       }
>> +
>>       rethrow;
>>     }
>>   }
>> @@ -91,12 +91,12 @@ Future<List<PveAccessDomainModel?>> accessDomains(
>>       if (e.message.contains('net::ERR_CERT_AUTHORITY_INVALID')) {
>>         throw HandshakeException(e.message);
>>       }
>> -    rethrow;
>> -  } on NSErrorClientException catch (e) {
>> +
>>       // Treat untrusted server certificate (-1202) as a handshake failure.
>> -    if (e.error.code == -1202) {
>> +    if (e is NSErrorClientException && e.error.code == -1202) {
>>         throw HandshakeException(e.message);
>>       }
>> +
>>       rethrow;
>>     }
>>   }



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


  reply	other threads:[~2025-10-17 11:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-01  9:52 Shan Shaji
2025-10-17  7:40 ` Dominik Csapak
2025-10-17 11:09   ` Shan Shaji [this message]
2025-10-17 11:51   ` Shan Shaji

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=DDKJUACH7LAQ.ZO163AQH6P92@proxmox.com \
    --to=s.shaji@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