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

Rails 5 follow-up fixes #2787

Closed
2 tasks done
jywarren opened this issue Jun 7, 2018 · 15 comments · Fixed by #2788 or #2794
Closed
2 tasks done

Rails 5 follow-up fixes #2787

jywarren opened this issue Jun 7, 2018 · 15 comments · Fixed by #2788 or #2794
Assignees

Comments

@jywarren
Copy link
Member

jywarren commented Jun 7, 2018

Just compiling some things from the #2726 #278 Rails 5 upgrades now that it's in stable!

  • POST https://stable.publiclab.org/tag/suggested/tag 404 (Not Found) - did route change? A GET route exists:
    get 'tag/suggested/:id' => 'tag#suggested'
  • top navbar search autocomplete doesn't work (doesn't seem to trigger a request at all?) (existing bug!)

@Souravirus any help appreciated but I imagine it's late there!

@Souravirus
Copy link
Member

Yeah lets check what has happened

@jywarren
Copy link
Member Author

jywarren commented Jun 7, 2018

Oh wait! The top bar nav search does work on a note page! But not on a /post page. Let's test more!

@Souravirus
Copy link
Member

I was checking on the dashboard and it was working fine there. That's why I said in gitter

@jywarren
Copy link
Member Author

jywarren commented Jun 7, 2018

Ha, and yes, https://publiclab.org/post also doesn't autocomplete. so that's an existing bug! Removing it from above.

@Souravirus
Copy link
Member

yeah its not auto completing but the search is working fine here

@jywarren
Copy link
Member Author

jywarren commented Jun 7, 2018

Also Travis seems to have trouble with this... the post-merge run failed with some kind of timeout very early in the process: https://travis-ci.org/publiclab/plots2/builds/389444495 -- adding to list, but @icarito any idea why it would get stuck on:

Step 1/16 : FROM ruby:2.4.1-jessie
2.4.1-jessie: Pulling from library/ruby
No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.
Check the details on how to adjust your build configuration on: https://docs.travis-ci.com/user/common-build-problems/#Build-times-out-because-no-output-was-received
The build has been terminated

@Souravirus
Copy link
Member

yeah there was timeout sometimes but restarting the build worked

@jywarren
Copy link
Member Author

jywarren commented Jun 7, 2018

OK - can you change the GET to a POST and open a PR? That's the only thing I've found now!

@Souravirus
Copy link
Member

Ok I will change 'get' to 'post'

@Souravirus Souravirus mentioned this issue Jun 7, 2018
5 tasks
@ghost ghost assigned Souravirus Jun 7, 2018
@ghost ghost added the in progress label Jun 7, 2018
@ghost ghost removed the in progress label Jun 7, 2018
@jywarren jywarren reopened this Jun 7, 2018
@jywarren
Copy link
Member Author

jywarren commented Jun 7, 2018

Just going to re-open this for a question -- locally, I'm seeing:

ActiveRecord::StatementInvalid (Mysql2::Error: Expression #1 of SELECT list is not in GROUP BY clause and contains nonaggregated column 'plots.node_revisions.vid' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_by: SELECT  `node_revisions`.* FROM `node_revisions` INNER JOIN `node` ON `node`.`nid` = `node_revisions`.`nid` WHERE (type = ('page')) AND (node.status = 1) AND (node_revisions.status = 1) AND (timestamp - node.created > 300) GROUP BY node.title ORDER BY timestamp DESC LIMIT 10):
  
app/controllers/home_controller.rb:127:in `activity'
app/controllers/home_controller.rb:163:in `block in set_activity'
app/controllers/home_controller.rb:162:in `set_activity'
app/controllers/home_controller.rb:15:in `home'

Did you ever see this error? Thanks!

@Souravirus
Copy link
Member

No I haven't seen this error.

@Souravirus
Copy link
Member

behind this error

@Souravirus
Copy link
Member

Hi @jywarren according to this stackoverflow post https://stackoverflow.com/questions/34115174/error-related-to-only-full-group-by-when-executing-a-query-in-mysql since we are doing group by by a node.title, that's why it is giving that error. We should try adding group by node.id then it would be perfect.

@jywarren
Copy link
Member Author

jywarren commented Jun 8, 2018 via email

@Souravirus
Copy link
Member

Yeah I will open a PR

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