'created_at DESC' is performed twice
If you are already sorting in descending order in the created_at, it is run twice when you run the .recent.
It has passed in the string 'created_at DESC'.
Ruby on Rails is directly given to the SQL.
It is a slow query in MySQL.
Merge request reports
Activity
@catatsuy nice! Can you please enable gitlab ci for your fork (Project->Settings->Project Services) and push a commit to this branch again (either rebase and push again or add a CHANGELOG entry)?
Then all tests will run with your change. If CI is green we can mergeAdded 52 commits:
- 3638e3d4...c0d9cbfd - 51 commits from branch
gitlab-org:master
- 9b680165 - 'created_at DESC' is performed twice
- 3638e3d4...c0d9cbfd - 51 commits from branch
Added 4 commits:
- 9b680165...74a6732c - 3 commits from branch
gitlab-org:master
- 00942598 - 'created_at DESC' is performed twice
- 9b680165...74a6732c - 3 commits from branch
@haynes I rebase and push again this branch. I enable GitLab CI. But it fail the test by "Cannot allocate memory".
What next?
@catatsuy please retry the 2 failed builds. That error happens sometimes with the public runners.
@haynes I retried the 2 failed builds many times. This error always happens.
I cannot do anything any more...@catatsuy We're looking into the reason. We'll figure it out soon :)
I'll ping you when we know more.@catatsuy Can you please rebase and push once more? We did some changes to the runner and the tests so it should work now.
Added 175 commits:
- 00942598...7aa8e12c - 174 commits from branch
gitlab-org:master
- 11fbc960 - 'created_at DESC' is performed twice
- 00942598...7aa8e12c - 174 commits from branch
@haynes I retry the test again. But the tests fails...
Added 56 commits:
- 11fbc960...9f166a86 - 55 commits from branch
gitlab-org:master
- cc9c8c8a - 'created_at DESC' is performed twice
- 11fbc960...9f166a86 - 55 commits from branch
/cc @haynes CI build failed, but it seems that there is nothing to do with this commit. The same error occurred in my MR(!898 (merged)).
indeed. The error that occurs is because of a missing package in the docker image of the public runners.
That should be fixed now I think. (Or at least the fix is merged. Not sure if it's deployed yet)
@catatsuy Can you please add aCHANGELOG
entry? I'll merge it then :)@catatsuy You are welcome!