Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Give more time to ElasticSearch to startup #329

Closed
wants to merge 0 commits into from

Conversation

ajs6f
Copy link
Member

@ajs6f ajs6f commented Dec 12, 2017

No description provided.

@afs
Copy link
Member

afs commented Dec 17, 2017

There is a different commit ee9c98b 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.

@ajs6f
Copy link
Member Author

ajs6f commented Dec 17, 2017

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.

@ajs6f
Copy link
Member Author

ajs6f commented Dec 17, 2017

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants