Skip to content

[Model] Fix ActiveRecord sorted collection #618

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

Closed
wants to merge 2 commits into from
Closed

[Model] Fix ActiveRecord sorted collection #618

wants to merge 2 commits into from

Conversation

inkstak
Copy link
Contributor

@inkstak inkstak commented Aug 17, 2016

This is a fix for #608.
It also introduces tests against ActiveRecord 5.0.

The fix about sorted records is cover by a test, but there are still 10 errors on other subjects when running tests with AR 5.
I'didn't run unit tests as they are already failing.

@inkstak inkstak changed the title Issue 608 [Model] Fix ActiveRecord sorted collection Aug 17, 2016
@nickrivadeneira
Copy link

@inkstak You'll need to sign the contributor agreement: https://www.elastic.co/contributor-agreement

Would love for this to be merged in.

@inkstak
Copy link
Contributor Author

inkstak commented Nov 9, 2016

Done !

nickrivadeneira added a commit to nickrivadeneira/elasticsearch-rails that referenced this pull request Nov 11, 2016
nickrivadeneira added a commit to nickrivadeneira/elasticsearch-rails that referenced this pull request Nov 11, 2016
@sfcgeorge
Copy link

Confirm this fix works for me, without it result order is all over the place. Had to monkeypatch it in as Rails 5 has been out long enough.

@connorshea
Copy link

@nickrivadeneira any updates on this?

@nickrivadeneira
Copy link

nickrivadeneira commented Dec 12, 2016

@connorshea I'm not an elasticsearch member unfortunately, I was just making sure that instak signed the agreement so this could be merged in when the elasticsearch team looks at it. This repo seems to be dead though :( The person we need is @karmi

@inkstak
Copy link
Contributor Author

inkstak commented Dec 12, 2016

I confirm I signed the agreement. The github check is not up to date.

@karmi
Copy link
Contributor

karmi commented Dec 12, 2016

@inkstak, you were correct, the check has indeed been out of sync -- it's corrected now.

@nickrivadeneira, it's not dead, I just have a hard time keeping up with all the gems across the two repos. I'll pull the patch and verify locally and merge.

@nickrivadeneira
Copy link

@karmi Makes sense. Thanks for looking into this one

@karmi karmi closed this in c9c4d2f Dec 13, 2016
@karmi
Copy link
Contributor

karmi commented Dec 13, 2016

Hi, I've merged the patch into master, many thanks for that, and apologies again for the delay. I'm not sure when I'll get to a release, but if you want a patch release with the change, I can do it anytime.

(So, one reason why processing PRs is not a simple "pull, run tests, rewrite commit message, push" is that I needed fix all this while doing the pull, so the tests are green and we can add more patches on top of the branch without fear...)

@inkstak
Copy link
Contributor Author

inkstak commented Dec 13, 2016

Thanks 👍

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.

5 participants