You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@jena.apache.org by ajs6f <gi...@git.apache.org> on 2017/12/12 18:26:16 UTC

[GitHub] jena pull request #329: Give more time to ElasticSearch to startup

GitHub user ajs6f opened a pull request:

    https://github.com/apache/jena/pull/329

    Give more time to ElasticSearch to startup

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/ajs6f/jena MoreTimeForESStartup

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/jena/pull/329.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 #329
    
----
commit 90f4e037ef489d446e602f7a45810574fdb9eb82
Author: ajs6f <aj...@apache.org>
Date:   2017-12-12T18:25:00Z

    Give more time to ElasticSearch to startup

----


---

[GitHub] jena pull request #329: Give more time to ElasticSearch to startup

Posted by ajs6f <gi...@git.apache.org>.

Github user ajs6f closed the pull request at:

    https://github.com/apache/jena/pull/329


---

[GitHub] jena issue #329: Give more time to ElasticSearch to startup

Posted by afs <gi...@git.apache.org>.

Github user afs commented on the issue:

    https://github.com/apache/jena/pull/329
  
    There is a different commit ee9c98b108942f258fd9a6b2e02cc6104a648368 on the Jena ASF git repository.
    
    This can be closed?
    
    For next time, it would be good to use the same commit:
    
    ```
    git pull URL-for-github pull/329/head
    git push
    ```
    
    should pull down the same commit as the PR then send it to the codebase.
    



---

[GitHub] jena issue #329: Give more time to ElasticSearch to startup

Posted by ajs6f <gi...@git.apache.org>.

Github user ajs6f commented on the issue:

    https://github.com/apache/jena/pull/329
  
    Dang it! This is the second time this has happened. I've been merging my PR branches into `master` and then pushing them. It normally works fine... I need to figure out what's nutty on my end. In the meantime, I'll clean this up.


---

[GitHub] jena issue #329: Give more time to ElasticSearch to startup

Posted by ajs6f <gi...@git.apache.org>.

Github user ajs6f commented on the issue:

    https://github.com/apache/jena/pull/329
  
    Ah, I think I figured it out-- for future reference, this seems to happen when you merge a branch into `master` and push it, but the branch on Github isn't up to date with the local repo. Okay, I should be able to stop annoying people with this.


---