« Back to channel list

#RubyOnRails - 27 January 2019

« Back 1 day Forward 1 day »
[00:04:59] dviola: has joined #RubyOnRails
[00:15:53] brandoncc: has joined #RubyOnRails
[00:18:17] zandimna: has joined #RubyOnRails
[00:20:16] zandimna: hello, has anyone successfully used ruby 2.6 for rails? I just installed a manjaro on a virtualbox and the rails on there returned the same error as i had on my arch.
[00:30:03] jottr: has joined #RubyOnRails
[00:34:37] Xiti: has joined #RubyOnRails
[00:35:41] cnsvc: has joined #RubyOnRails
[00:38:02] beingjohnm: has joined #RubyOnRails
[00:56:06] zandimna: has joined #RubyOnRails
[00:57:59] NeXTSUN: has joined #RubyOnRails
[01:07:36] Zabot: has joined #RubyOnRails
[01:11:41] Zabot: What's the preferred way to run migrations against a production db? I know I can run rake:schema:load etc, but I don't want to give the rails db user create/delete access, much less the superuser access I would need to enable some postgres extensions.
[01:12:50] NeXTSUN: has joined #RubyOnRails
[01:55:38] Technodrome: has joined #RubyOnRails
[02:37:11] jottr: has joined #RubyOnRails
[02:45:31] Jervis_: has joined #RubyOnRails
[02:54:48] orbyt_: has joined #RubyOnRails
[03:06:16] cschneid: has joined #RubyOnRails
[03:50:35] agent_white: has joined #RubyOnRails
[04:10:06] braincrash: has joined #RubyOnRails
[04:45:25] jottr: has joined #RubyOnRails
[04:47:03] dedRabbit: has joined #RubyOnRails
[04:49:15] mr_roybot: has joined #RubyOnRails
[04:49:16] mr_roybot: has joined #RubyOnRails
[05:04:26] Technodrome: has joined #RubyOnRails
[05:14:45] tfitts: has joined #RubyOnRails
[05:17:57] mr_roybot: has joined #RubyOnRails
[05:49:51] uks: has joined #RubyOnRails
[06:12:44] Saukk: has joined #RubyOnRails
[06:19:43] uplime: has joined #RubyOnRails
[06:42:02] xall: has joined #RubyOnRails
[06:44:51] Zabot: has joined #RubyOnRails
[06:53:56] jottr: has joined #RubyOnRails
[06:57:19] aidanh010: has joined #RubyOnRails
[07:19:36] Vircung: has joined #RubyOnRails
[08:24:54] ravenousmoose: has joined #RubyOnRails
[08:30:14] Jervis_: has joined #RubyOnRails
[08:55:43] jottr: has joined #RubyOnRails
[09:01:53] KeyJoo: has joined #RubyOnRails
[09:08:56] jottr: has joined #RubyOnRails
[09:25:25] RiPuk: has joined #RubyOnRails
[09:26:17] jottr: has joined #RubyOnRails
[09:29:25] ravenousmoose: has joined #RubyOnRails
[09:44:25] mikecmpbll: has joined #RubyOnRails
[10:06:38] Fernando-Basso: has joined #RubyOnRails
[10:09:21] Fernando-Basso: has joined #RubyOnRails
[10:19:34] lxsameer: has joined #RubyOnRails
[10:30:43] ravenousmoose: has joined #RubyOnRails
[11:33:01] Saukk: has joined #RubyOnRails
[11:55:38] ariedler: has joined #RubyOnRails
[11:57:35] ariedler: has joined #RubyOnRails
[12:22:42] conta: has joined #RubyOnRails
[12:27:23] za1b1tsu: has joined #RubyOnRails
[12:53:40] Aces1up: has joined #RubyOnRails
[14:04:04] nakuku: has joined #RubyOnRails
[14:04:11] nakuku: Does it make sense to check subscription status on every request? (single query) Or set user status to 'subscribed' in database and make a job that runs once a day that checks if subscription ended?
[14:05:22] mikecmpbll: on each request.
[14:06:40] nakuku: Get it. So simpler = better in this case. At least it stateless, less error-prone and won't really affect performance, right?
[14:07:32] mikecmpbll: simpler is almost always better. you gotta have a pretty compelling case to do something more complex, and the performance of checking a date on each request isn't really compelling.
[14:08:11] mikecmpbll: if performance really was a concern, a cache would be better than introducing an aync process anyway.
[14:19:15] nakuku: Nice, get it! Thank you Mike.
[14:33:24] conta: has joined #RubyOnRails
[14:44:29] segy: has joined #RubyOnRails
[14:46:54] lexileo: has joined #RubyOnRails
[15:01:11] reber: has joined #RubyOnRails
[15:02:28] Fridtjof: has joined #RubyOnRails
[15:12:42] mr_roybot: has joined #RubyOnRails
[15:51:25] ravenousmoose: has joined #RubyOnRails
[15:52:12] blackmesa: has joined #RubyOnRails
[16:39:38] brandoncc: has joined #RubyOnRails
[16:52:02] mr_roybot: has joined #RubyOnRails
[16:52:59] EXCHGR: has joined #RubyOnRails
[16:57:48] mr_roybot: has joined #RubyOnRails
[16:59:16] squaresurf: has joined #RubyOnRails
[17:04:01] defsdoor: has joined #RubyOnRails
[17:06:02] mr_roybot: has joined #RubyOnRails
[17:08:05] defsdoor: has joined #RubyOnRails
[17:11:03] Pupeno: has joined #RubyOnRails
[17:12:23] Pupeno: I'm converting a project from MySQL to PostgreSQL. After configuring it, I get the error: ActiveRecord::ConnectionTimeoutError: could not obtain a connection from the pool within 5.000 seconds (waited 5.000 seconds); all pooled connections were in use. I tried increasing the pool to 50. Another rails project on the same machine uses postgresql just fine. Any ideas what might be going ?
[17:17:18] brandoncc: has joined #RubyOnRails
[17:33:35] havenwood: Pupeno: What are you using for your Rack web server? Puma?
[17:34:24] Pupeno: havenwood: this is happening during rake db:migrate or rake db:create, so, I'm not sure the web server would have any effect, would it?
[17:34:58] Pupeno: I am using puma though.
[17:36:03] havenwood: Pupeno: Test workers maybe?
[17:36:23] Pupeno: What do you mean by test worker?
[17:36:41] havenwood: Pupeno: Like Sidekiq workers in your tests.
[17:37:08] havenwood: Pupeno: Are you using a worker queue?
[17:37:14] havenwood: Pupeno: What version of Rails?
[17:37:22] Pupeno: This project uses delayed jobs.
[17:37:28] Pupeno: No sidekiq as far as I can se.
[17:37:31] Pupeno: Rails 5.1.x
[17:37:46] havenwood: Pupeno: https://github.com/mperham/sidekiq/issues/3879
[17:37:59] havenwood: Pupeno: "looks like AR clears active connections after initialize in 5.2"
[17:38:50] havenwood: Pupeno: I wonder if it's related to that ^ issue, which was fixed in Rails 5.2.
[17:39:01] mikecmpbll: unlikely given he's not using sidekiq :p
[17:39:32] havenwood: mikecmpbll: well, it's not a Sidekiq-specific issue :P
[17:39:53] havenwood: https://github.com/rails/rails/pull/28057/files#diff-18d566ee525de376b1a3741881545631R173
[17:40:08] mikecmpbll: you've got something pretty weird going on if you can't load your rails environment without without exhausting the connection pool
[17:42:53] Pupeno: Found the problem. By an error in database.yml, the pool size ended up being 0.
[17:43:04] havenwood: that would do it!
[17:43:09] mikecmpbll: 🤦‍♀️
[17:43:34] havenwood: slightly too small
[17:43:47] mikecmpbll: i've had some good results with 0. query performance is excellent
[17:44:02] mikecmpbll: don't necessarily get the results i want tho
[17:44:03] havenwood: 0 lines of code also runs really fast on 0 connnections
[17:44:07] Pupeno: _facepalm_ sorry guys.
[17:49:38] tdy: has joined #RubyOnRails
[18:20:47] dedRabbit: has joined #RubyOnRails
[18:39:30] uplime: has joined #RubyOnRails
[18:39:58] ravenousmoose: has joined #RubyOnRails
[18:44:24] ariedler: has joined #RubyOnRails
[18:58:33] Technodrome: has joined #RubyOnRails
[19:03:09] blackcross: has joined #RubyOnRails
[19:04:07] Technodrome: has joined #RubyOnRails
[19:21:34] ravenousmoose: has joined #RubyOnRails
[19:26:20] armyriad: has joined #RubyOnRails
[19:43:23] cschneid: has joined #RubyOnRails
[19:56:24] ariedler: has joined #RubyOnRails
[20:03:40] orbyt_: has joined #RubyOnRails
[20:16:33] liya: has joined #RubyOnRails
[20:16:46] liya: sqlite3 not working on windows
[20:19:49] ariedler: has joined #RubyOnRails
[20:21:56] EXCHGR: has joined #RubyOnRails
[20:31:46] Tempesta: has joined #RubyOnRails
[20:32:41] cschneid: has joined #RubyOnRails
[21:08:37] Xiti: has joined #RubyOnRails
[21:22:40] cschneid: has joined #RubyOnRails
[22:14:17] fragamus: has joined #RubyOnRails
[22:16:04] DTZUZO_: has joined #RubyOnRails
[22:24:03] cschneid: has joined #RubyOnRails
[22:31:04] Zabot: has joined #RubyOnRails
[22:32:04] cschneid: has joined #RubyOnRails
[22:32:05] dviola: has joined #RubyOnRails
[23:02:30] tdy: has joined #RubyOnRails
[23:23:31] eckhardt: has joined #RubyOnRails
[23:26:31] cschneid: has joined #RubyOnRails
[23:31:10] fragamus: has joined #RubyOnRails
[23:33:11] Zabot: Is there a way to generate a SQL script from a migration without actually running against a db?
[23:41:26] uplime: has joined #RubyOnRails
[23:59:27] cschneid: has joined #RubyOnRails