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 72265200BF2 for ; Mon, 19 Dec 2016 02:42:51 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 70C80160B36; Mon, 19 Dec 2016 01:42:51 +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 B8EC8160B30 for ; Mon, 19 Dec 2016 02:42:50 +0100 (CET) Received: (qmail 21032 invoked by uid 500); 19 Dec 2016 01:42:49 -0000 Mailing-List: contact issues-help@eagle.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@eagle.incubator.apache.org Delivered-To: mailing list issues@eagle.incubator.apache.org Received: (qmail 21023 invoked by uid 99); 19 Dec 2016 01:42:49 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Dec 2016 01:42:49 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 01E181A0265 for ; Mon, 19 Dec 2016 01:42:49 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -7.019 X-Spam-Level: X-Spam-Status: No, score=-7.019 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-2.999] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id xKBRQermSvuK for ; Mon, 19 Dec 2016 01:42:47 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with SMTP id C265C5F19B for ; Mon, 19 Dec 2016 01:42:46 +0000 (UTC) Received: (qmail 21004 invoked by uid 99); 19 Dec 2016 01:42:45 -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; Mon, 19 Dec 2016 01:42:45 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id B8ADDDFB01; Mon, 19 Dec 2016 01:42:45 +0000 (UTC) From: lifove To: issues@eagle.incubator.apache.org Reply-To: issues@eagle.incubator.apache.org Message-ID: Subject: [GitHub] incubator-eagle pull request #751: [EAGLE-844] Fix a potential NPE Content-Type: text/plain Date: Mon, 19 Dec 2016 01:42:45 +0000 (UTC) archived-at: Mon, 19 Dec 2016 01:42:51 -0000 GitHub user lifove opened a pull request: https://github.com/apache/incubator-eagle/pull/751 [EAGLE-844] Fix a potential NPE Be sure to do all of the following to help us incorporate your contribution quickly and easily: - [ ] Make sure the PR title is formatted like: `[EAGLE-] Description of pull request` - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable Travis-CI on your fork and ensure the whole test matrix passes). - [ ] Replace `` in the title with the actual Jira issue number, if there is one. - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.txt). --- You can merge this pull request into a Git repository by running: $ git pull https://github.com/lifove/incubator-eagle master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/751.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #751 ---- commit dc73f0e92d9c617d562105c0353ecb3714c87f27 Author: JC Date: 2016-12-19T01:36:10Z [EAGLE-844] Fix potential NPE ---- --- 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. ---