Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 8F023200C88 for ; Fri, 19 May 2017 01:28:48 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 8D94D160BC4; Thu, 18 May 2017 23:28:48 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id CCA68160BB5 for ; Fri, 19 May 2017 01:28:47 +0200 (CEST) Received: (qmail 60150 invoked by uid 500); 18 May 2017 23:28:42 -0000 Mailing-List: contact dev-help@zookeeper.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@zookeeper.apache.org Delivered-To: mailing list dev@zookeeper.apache.org Received: (qmail 60139 invoked by uid 99); 18 May 2017 23:28:41 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 May 2017 23:28:41 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 99150DFF17; Thu, 18 May 2017 23:28:41 +0000 (UTC) From: hanm To: dev@zookeeper.apache.org Reply-To: dev@zookeeper.apache.org References: In-Reply-To: Subject: [GitHub] zookeeper issue #240: ZOOKEEPER-2757: Incorrect path crashes zkCli Content-Type: text/plain Message-Id: <20170518232841.99150DFF17@git1-us-west.apache.org> Date: Thu, 18 May 2017 23:28:41 +0000 (UTC) archived-at: Thu, 18 May 2017 23:28:48 -0000 Github user hanm commented on the issue: https://github.com/apache/zookeeper/pull/240 How about catch the IllegalArgumentException at ZooKeeperMain.processCmd and directly print the exception message? This way we don't need to make change to individual command. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastructure@apache.org or file a JIRA ticket with INFRA. ---