You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vadim Pakhnushev (Jira)" <ji...@apache.org> on 2022/06/14 12:15:00 UTC

[jira] [Commented] (IGNITE-17109) Error handling for invalid url passed to any command

    [ https://issues.apache.org/jira/browse/IGNITE-17109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17554073#comment-17554073 ] 

Vadim Pakhnushev commented on IGNITE-17109:
-------------------------------------------

After the IGNITE-17093, first two messages would be:
{code:java}
Expected URL scheme 'http' or 'https' but no colon was found {code}
and
{code:java}
Could not determine IP address when connecting to URL: http://thsjdfksjdfkjd:10300 {code}

> Error handling for invalid url passed to any command
> ----------------------------------------------------
>
>                 Key: IGNITE-17109
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17109
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Aleksandr
>            Priority: Major
>              Labels: ignite-3
>
> h2. Description
> Different commands given the wrong URL display different messages. For example
>  
> {code:java}
> disconnected]> connect lkhjasdflkjhhasdf
> 2022-06-06 10:41:04:665 +0100 [ERROR][main][ExceptionHandler] Unhandled exception
> java.lang.IllegalArgumentException: Expected URL scheme 'http' or 'https' but no colon was found
>         at okhttp3.HttpUrl$Builder.parse$okhttp(HttpUrl.kt:1260)
>         at okhttp3.HttpUrl$Companion.get(HttpUrl.kt:1633)
>         at okhttp3.Request$Builder.url(Request.kt:184)
> ...
> Internal error! {code}
>  
> {code:java}
> [disconnected]> connect http://kjhasdflkjhhasdf:10300/
> Api error: null
> {code}
>  
> {code:java}
> [disconnected]> sql -u=hdbkljghhgasdflkjhasdf
> Connection failed. {code}
> h2. To-Do
>  * Test all possible variations of incorrect URLs with integration/interface tests
>  * Define a single error handler for the wrong URL, port, etc.
> As a result, all variations of wrong data passed should be handled on a consistent way. The user has to see the same messages for the same mistakes regardless of the command is used.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)