dnewkerk

Activity Graph

Page 1 of 4 | Next »

2018-11-15

[06:29:35] dnewkerk: has joined #ruby
[06:29:35] dnewkerk: has joined #RubyOnRails
[08:21:53] dnewkerk: Quit: dnewkerk

2018-10-25

[03:10:52] dnewkerk: Ping timeout: 264 seconds
[03:12:42] dnewkerk: has joined #ruby
[03:12:42] dnewkerk: has joined #RubyOnRails
[13:18:39] dnewkerk: Ping timeout: 252 seconds
[13:19:39] dnewkerk: has joined #ruby
[13:19:39] dnewkerk: has joined #RubyOnRails
[14:05:01] dnewkerk: Ping timeout: 250 seconds

2018-10-24

[02:43:27] dnewkerk: Ping timeout: 240 seconds
[03:40:38] dnewkerk: has joined #ruby
[03:40:38] dnewkerk: has joined #RubyOnRails

2018-10-23

[23:45:54] dnewkerk: has joined #ruby
[23:45:54] dnewkerk: has joined #RubyOnRails

2018-07-24

[06:18:56] dnewkerk: has left #ruby: ()
[06:18:56] dnewkerk: has left #RubyOnRails: ()

2018-07-23

[22:43:05] dnewkerk: has joined #ruby
[22:43:05] dnewkerk: has joined #RubyOnRails

2018-07-14

[09:41:51] dnewkerk: Quit: dnewkerk

2018-07-13

[21:16:49] dnewkerk: has joined #ruby
[21:16:49] dnewkerk: has joined #RubyOnRails

2018-03-29

[02:09:47] dnewkerk: has joined #ruby
[02:09:47] dnewkerk: has joined #RubyOnRails
[03:21:35] dnewkerk: Quit: dnewkerk

2018-03-28

[01:18:53] dnewkerk: has joined #ruby
[01:18:53] dnewkerk: has joined #RubyOnRails
[06:05:57] dnewkerk: Quit: dnewkerk

2018-03-26

[03:53:22] dnewkerk: has joined #RubyOnRails
[03:54:11] dnewkerk: Client Quit
[03:55:42] dnewkerk: has joined #ruby
[03:55:42] dnewkerk: has joined #RubyOnRails
[04:47:15] dnewkerk: Quit: dnewkerk

2018-03-22

[07:37:30] dnewkerk: Quit: dnewkerk

2018-03-21

[23:27:09] dnewkerk: has joined #ruby
[23:27:09] dnewkerk: has joined #RubyOnRails
[23:31:16] dnewkerk: Client Quit
[23:32:29] dnewkerk: has joined #RubyOnRails
[23:32:56] dnewkerk: has joined #ruby

2018-03-16

[03:38:59] dnewkerk: has joined #RubyOnRails
[03:38:59] dnewkerk: has joined #ruby
[05:41:39] dnewkerk: Ping timeout: 260 seconds

2018-03-15

[04:24:59] dnewkerk: Client Quit
[04:24:59] dnewkerk: has joined #RubyOnRails
[04:24:59] dnewkerk: has joined #ruby
[04:25:17] dnewkerk: has joined #ruby
[04:25:17] dnewkerk: has joined #RubyOnRails
[09:05:44] dnewkerk: Quit: Textual IRC Client: www.textualapp.com

2018-02-21

[01:13:49] dnewkerk: Quit: My MacBook has gone to sleep. ZZZzzz…
[02:24:37] dnewkerk: has joined #RubyOnRails
[02:24:37] dnewkerk: has joined #ruby
[03:59:02] dnewkerk: Quit: Textual IRC Client: www.textualapp.com

2018-02-20

[19:09:57] dnewkerk: has joined #RubyOnRails
[19:09:58] dnewkerk: has joined #ruby
[19:18:14] dnewkerk: Quit: dnewkerk
[19:18:51] dnewkerk: has joined #ruby
[19:18:51] dnewkerk: has joined #RubyOnRails

2017-10-17

[02:00:25] dnewkerk: has joined #ruby
[02:00:25] dnewkerk: has joined #RubyOnRails
[08:56:16] dnewkerk: Quit: dnewkerk

2017-08-10

[05:23:35] dnewkerk: has joined #ruby
[05:23:35] dnewkerk: has joined #RubyOnRails
[06:43:48] dnewkerk: Quit: dnewkerk

2017-05-25

[00:18:50] dnewkerk: Quit: dnewkerk

2017-05-24

[00:07:02] dnewkerk: has left #ruby: ()
[00:07:02] dnewkerk: has left #RubyOnRails: ()
[20:25:32] dnewkerk: has joined #ruby
[20:25:32] dnewkerk: has joined #RubyOnRails

2017-05-23

[18:05:33] dnewkerk: has joined #ruby
[18:05:33] dnewkerk: has joined #RubyOnRails
[23:03:09] dnewkerk: Read error: Connection reset by peer
[23:03:32] dnewkerk: has joined #RubyOnRails
[23:03:33] dnewkerk: has joined #ruby

2016-07-15

[01:47:55] dnewkerk: has joined #ruby
[01:47:55] dnewkerk: has joined #RubyOnRails
[01:52:47] dnewkerk: with Rails 5 has_secure_token, is finding a matching record in my controller via the token secure like this? Video.find_by_preview_token(params[:preview_token])
[02:05:52] dnewkerk: adam12: thanks. that’s basically it besides def show around it, render :show if the token matches. Namely I was worried about if code could be injected into the query, though I just found some indication on http://guides.rubyonrails.org/security.html#sql-injection-countermeasures that this input does get sanitized
[02:07:35] dnewkerk: cool that’s what I was hoping for
[02:10:40] dnewkerk: adam12: yeah I thought it was still valid… http://edgeguides.rubyonrails.org/active_record_querying.html#dynamic-finders
[02:11:19] dnewkerk: yeah I remember something about that too
[04:41:50] dnewkerk: Read error: Connection reset by peer
[04:45:55] dnewkerk: has joined #RubyOnRails
[04:45:56] dnewkerk: has joined #ruby
[05:16:11] dnewkerk: has left #RubyOnRails: ()
[05:16:12] dnewkerk: has left #ruby: ()

2016-06-28

[03:21:41] dnewkerk: Quit: dnewkerk

2016-06-27

[21:08:11] dnewkerk: has joined #ruby
[21:08:11] dnewkerk: has joined #RubyOnRails

2016-06-23

[02:22:15] dnewkerk: Read error: Connection reset by peer
[02:24:00] dnewkerk: has joined #ruby
[02:24:00] dnewkerk: has joined #RubyOnRails
[09:54:08] dnewkerk: Read error: Connection reset by peer

2016-06-22

[20:59:12] dnewkerk: has joined #ruby
[20:59:12] dnewkerk: has joined #RubyOnRails
[21:19:05] dnewkerk: I have a standard Rails resource with some general attributes on its new/edit form, but would like to add a separate page with a form for other specialized attributes of the same model, some of which need validations (but should not be validated on the new/edit form)… what technique is best to accomplish something like this?

2016-06-18

[00:20:55] dnewkerk: has joined #ruby
[00:20:55] dnewkerk: has joined #RubyOnRails
[02:52:28] dnewkerk: Read error: Connection reset by peer
[02:56:21] dnewkerk: has joined #ruby
[02:56:21] dnewkerk: has joined #RubyOnRails
[07:01:14] dnewkerk: Quit: dnewkerk

2016-06-14

[02:40:03] dnewkerk: Quit: dnewkerk

2016-06-13

[23:32:50] dnewkerk: has joined #RubyOnRails
[23:32:51] dnewkerk: has joined #ruby

2016-05-01

[02:27:00] dnewkerk: Quit: dnewkerk

2016-04-30

[23:10:37] dnewkerk: has joined #ruby
[23:10:37] dnewkerk: has joined #RubyOnRails

2016-04-24

[00:43:37] dnewkerk: Ping timeout: 260 seconds
[00:47:45] dnewkerk: Client Quit

2016-04-23

[23:12:24] dnewkerk: has joined #ruby
[23:12:24] dnewkerk: has joined #RubyOnRails

2016-04-04

[04:57:43] dnewkerk: has joined #ruby
[04:57:43] dnewkerk: has joined #RubyOnRails
[07:30:27] dnewkerk: Quit: dnewkerk
[18:21:26] dnewkerk: has joined #ruby
[18:21:26] dnewkerk: has joined #RubyOnRails
[19:32:07] dnewkerk: Quit: dnewkerk

2016-04-03

[09:05:51] dnewkerk: Quit: dnewkerk

2016-04-02

[02:11:48] dnewkerk: has joined #ruby
[02:11:48] dnewkerk: has joined #RubyOnRails
[03:31:22] dnewkerk: Quit: dnewkerk
[23:29:51] dnewkerk: has joined #RubyOnRails
[23:29:52] dnewkerk: has joined #ruby

2016-03-26

[01:11:34] dnewkerk: has joined #ruby
[01:11:34] dnewkerk: has joined #RubyOnRails
[01:16:41] dnewkerk: Quit: dnewkerk

2016-03-22

[21:56:56] dnewkerk: has joined #ruby
[21:56:56] dnewkerk: has joined #RubyOnRails
[22:42:51] dnewkerk: Quit: dnewkerk

2016-03-18

[01:23:17] dnewkerk: Quit: dnewkerk
[01:24:56] dnewkerk: has joined #ruby
[01:24:56] dnewkerk: has joined #RubyOnRails
[01:26:37] dnewkerk: Client Quit

2016-03-17

[21:15:45] dnewkerk: has joined #ruby
[21:15:45] dnewkerk: has joined #RubyOnRails

2016-03-14

[20:45:03] dnewkerk: has joined #ruby
[20:45:03] dnewkerk: has joined #RubyOnRails
[23:55:51] dnewkerk: Quit: dnewkerk

2016-03-13

[06:16:34] dnewkerk: Quit: dnewkerk

2016-03-12

[23:29:16] dnewkerk: has joined #ruby
[23:29:16] dnewkerk: has joined #RubyOnRails

2016-03-03

[01:32:00] dnewkerk: has joined #ruby
[01:32:00] dnewkerk: has joined #RubyOnRails
[01:47:06] dnewkerk: I upgraded an app I’m working on to Rails 5 beta3 and for some reason all of my tests (minitest) are running twice… anyone else run into this?
[01:49:08] dnewkerk: slash_nick: yeah it must be something with my current config then
[01:50:43] dnewkerk: rails test (whole suite) or rails test test/models/something_test.rb (specific file)… it even happens if I run just a specific test by line number
[01:52:33] dnewkerk: I guess I can temporarily revert my test_helper.rb to Rails 5 default and disable any test related gems, then add things back in until the problem returns… oh so fun :P
[01:54:22] dnewkerk: slash_nick: yes, though I upgraded to beta1, 2 and 3 in sequence as they came out, each time I installed a separate plain Rails 5 app to diff the previous version against and observe exactly what files changed
[02:02:11] dnewkerk: slash_nick: yeah at the time I was fairly confident that I had correctly modified all Rails 4 files with their Rails 5 updates (and added/removed files as required), and same with beta2 and beta3. No I don’t have custom test tasks, and no doesn’t do it in a new generated app (well haven’t tried since beta1 actually, though I recall a simple test there worked as expected)
[02:04:23] dnewkerk: slash_nick: yep I often stop spring when anything weird is happening (it’s often to blame haha)
[02:08:08] dnewkerk: slash_nick: lots, though nothing I’d call unusual… requiring things like capybara, various extracted helper methods, etc
[02:09:26] dnewkerk: slash_nick: no not requiring minitext/autorun
[02:09:36] dnewkerk: minitest/autorun
[02:12:55] dnewkerk: slash_nick: yeah that’s probably a good bet… I just now confirmed it is not due to any customization in test_helper.rb so it very well may be some gem. I reset test_helper to Rails 5 default, stopped spring, and still get the same issue
[02:16:26] dnewkerk: slash_nick: yeah it began happening as soon as I upgraded to beta1 and has continued. I’ve been working around it and tolerating it since I couldn’t figure it out, but ahhhh I really want to fix it haha
[02:17:17] dnewkerk: right now I’m disabling lots of gems and their associated configs, will see what happens… love version control :P
[02:19:11] dnewkerk: runs twice, has a different seed, and yeah whenever I use binding.pry, if I “continue” which would usually complete the test, it runs again and brings me back to pry again
[02:23:42] dnewkerk: slash_nick: “good” news… I slashed and burned everything and now the problem is not occuring… so now have to put it back together piece by piece until I determine the culprit
[04:27:58] dnewkerk: slash_nick: turned out the issue with tests running twice in Rails 5 was coming from minitest-rails gem… https://github.com/blowmage/minitest-rails/issues/185#issuecomment-126718418
[04:28:32] dnewkerk: adding the suggested ENV["MT_RAILS_NO_AUTORUN"] = "true" did the trick for now
[04:29:42] dnewkerk: timmmaaaayyy: how large are the uploads?
[04:30:42] dnewkerk: are you uploading to the server and then pushing the file to s3 after?
[04:33:37] dnewkerk: timmmaaaayyy: yeah there are two common ways (I know of) for uploading, either you’re uploading the file to the server running Rails, and then a background job might push the file to cloud storage like S3, or you can upload directly to S3 using ajax, bypassing sending the file to the Rails server at all
[04:37:44] dnewkerk: timmmaaaayyy: are you running on heroku, or something else?
[04:43:55] dnewkerk: timmmaaaayyy: ok, definitely with heroku that would happen no matter what, though likely the same on your own aws server (a bit less strict but still will happen on large files). For starters here is a SO post that’s probably relevant http://stackoverflow.com/questions/19035817/timeout-error-from-unicorn-while-uploading-a-file
[04:44:39] dnewkerk: essentially you’re running a long single process while the upload is going, and the app server says “nope too long, bye!"
[04:45:53] dnewkerk: a workaround is to let processes stay alive longer, but that may bite you down the line so probably not a good idea
[04:50:09] dnewkerk: timmmaaaayyy: yeah there are several upload gems that can help. One newer popular one is https://github.com/refile/refile
[04:51:19] dnewkerk: there could be other config options getting in the way… same as back in my php days, there were like 3+ options that had to be set correctly in php.ini in order for moderately large file uploads to work
[04:54:03] dnewkerk: timmmaaaayyy: yep I use sidekiq in my app for background jobs, love it… it’s powerful and might be a bit complex to set up, so if you’re just starting out with background jobs there are a few you may prefer that don’t require setting up Redis. If you write your background jobs with ActiveJob then you can easily switch to sidekiq or whatever when you’re ready
[04:55:41] dnewkerk: no, the background job is what would take over pushing the file to s3 “after” your Rails server receives it
[04:56:09] dnewkerk: you still have to get it to the server first, so it’s not really a solution to what you’re experiencing
[04:56:40] dnewkerk: I’d recommend trying refile or another upload helper gem that has direct to s3 capability
[04:58:00] dnewkerk: or there may be gems that can get a “chunked” upload to your server and reassemble the small parts once the upload is done… that’s the only way I’d say you could stick with uploading to the app server first and avoid the timeout issues
[05:00:14] dnewkerk: also for background jobs, https://github.com/brandonhilkert/sucker_punch is a good option to get your feet wet with before going all out with sidekiq, again using the ActiveJob API to write the jobs so you can switch adapters later
[05:13:21] dnewkerk: timmmaaaayyy: open the network pane of your browser’s dev tools, reload the page, and then try the upload… tell what you see
[05:22:51] dnewkerk: timmmaaaayyy: it is odd… 5TB limit is for multipart uploads, though I think even non-multipart can do 5GB or something
[05:23:21] dnewkerk: what is the URL of the request?
[05:26:19] dnewkerk: timmmaaaayyy: when you try the upload, in the network pane where you found that error message, what is the URL that got called when you started the upload?
[05:26:25] dnewkerk: it should show there in the network pane
[05:30:35] dnewkerk: timmmaaaayyy: you said you’re using this gem already right? https://github.com/waynehoover/s3_direct_upload
[05:30:45] dnewkerk: it has a max_file_size option, so I’d check into that
[05:33:33] dnewkerk: yeah check the view that contains the upload/form and I suspect you may find it says max_file_size: 100.megabytes
[05:34:12] dnewkerk: no problemo
[05:35:41] dnewkerk: I’ve worked a lot with uploading large files, so always happy to help :D My own custom direct to S3 uploader regularly handles files 300GB+ each
[05:36:05] dnewkerk: (raw HD video files)
[07:29:16] dnewkerk: Quit: dnewkerk

2016-02-28

[05:06:06] dnewkerk: has joined #ruby
[05:06:06] dnewkerk: has joined #RubyOnRails
[06:42:55] dnewkerk: Quit: dnewkerk

2016-02-20

[01:04:29] dnewkerk: has joined #ruby
[01:04:29] dnewkerk: has joined #RubyOnRails
[03:31:10] dnewkerk: Quit: dnewkerk

2016-02-17

[00:07:17] dnewkerk: has joined #ruby
[00:07:17] dnewkerk: has joined #RubyOnRails
[00:52:18] dnewkerk: I’m a regex newbie and struggling to get this regex to match all of the lines of text, was wondering if anyone can give me a hint on how to fix it? http://rubular.com/r/kb0JQDOerh … originally found it on https://regex101.com/r/jV9oV2/3 where it does match in pcre format but not when bringing it to ruby
[01:03:14] dnewkerk: Ox0dea: interesting… I’m still running 2.2 on my dev machine so hadn’t tried with 2.3
[01:12:06] dnewkerk: bnagy: thanks that worked! Thank you too Ox0dea for having a look. Yeah I agree it’s not a good idea to take this route, just came across this snippet and was hoping to just use it to get an early version of my subtitles parser working and then refactor it better (but then got stumped when the regex didn’t work as expected)
[01:14:04] dnewkerk: bnagy: as you’re definitely more knowledgable with regex than me, could you refer me to a trusted resource to learn best practices? So far I’m at the point where I can’t tell good from evil so to speak :P
[01:20:11] dnewkerk: thanks everyone :) and thanks jimeh I’ll compare the two examples and learn how you simplified it
[01:25:31] dnewkerk: jimeh: it’s a start :)
[01:26:25] dnewkerk: jimeh: in the case of parsing a big block of text like this, would you take a different approach? perhaps like breaking it down into single lines and analyzing each with simpler conditions?
[01:28:31] dnewkerk: thanks I’ll give it a try
[08:14:09] dnewkerk: Quit: dnewkerk

2016-01-25

[00:44:38] dnewkerk: has joined #ruby
[00:44:38] dnewkerk: has joined #RubyOnRails
[03:41:52] dnewkerk: das3in: it looks like you are rendering an empty/new instance of the milestone ??? look into reject_if: :all_blank
[03:42:38] dnewkerk: das3in: might be something like???. accepts_nested_attributes_for :milestones, allow_destroy: true, reject_if: :all_blank
[03:46:59] dnewkerk: das3in: cool glad you got it working :) Also in your goals controller, you don???t need the separate operations for associating the goal with the user??? in your create action, try @goal = current_user.goals.build(goal_params)
[06:37:31] dnewkerk: Quit: dnewkerk

2016-01-18

[05:02:20] dnewkerk: has joined #ruby
[05:02:20] dnewkerk: has joined #RubyOnRails
[05:40:06] dnewkerk: Ping timeout: 240 seconds

2016-01-13

[04:07:02] dnewkerk: felixdd: Rails.logger.deug
[04:07:34] dnewkerk: sorry Rails.logger.debug
[04:11:49] dnewkerk: felixdd: http://guides.rubyonrails.org/debugging_rails_applications.html#log-levels
[05:07:13] dnewkerk: diggitydane: https://hackhands.com might be a good option
[07:31:53] dnewkerk: Quit: dnewkerk

2016-01-12

[04:08:31] dnewkerk: has joined #ruby
[04:08:31] dnewkerk: has joined #RubyOnRails
[04:31:52] dnewkerk: do people often implement authentication on their own for Rails apps, or is the use of tools like devise or sorcery more common/recommended? Devise recommends ???do it yourself??? at first, though this seems to imply ???while you???re learning Rails??? not necessarily in a real/public site
[04:37:33] dnewkerk: the simplicity of DIY authentication with has_secure_password is definitely appealing, though I worry that my lack of deep understanding of security issues will come back to bite me later
[04:38:36] dnewkerk: right, and lots of chance to overlook something and make a mistake
[04:44:32] dnewkerk: also the request of facilitating login via 3rd parties comes up a lot with clients
[04:47:56] dnewkerk: sevenseacat: as you use it in all your apps, have you ever run into trouble with devise that made you wish you???d used something simpler, or is it usually easily surmountable?
[04:50:24] dnewkerk: yeah - feels like Rails Tutorial is almost entirely about building DIY authentication :P
[04:51:10] dnewkerk: (I know its not, just a large number of pages about the topic)
[10:11:58] dnewkerk: Quit: dnewkerk
[22:50:34] dnewkerk: has joined #ruby
[22:50:34] dnewkerk: has joined #RubyOnRails

2016-01-10

[06:45:53] dnewkerk: has joined #RubyOnRails
[06:45:54] dnewkerk: has joined #ruby
[06:54:26] dnewkerk: Quit: dnewkerk

2016-01-09

[04:45:49] dnewkerk: has joined #ruby
[04:45:49] dnewkerk: has joined #RubyOnRails
[07:08:41] dnewkerk: Quit: dnewkerk

2015-12-24

[00:31:54] dnewkerk: Read error: Connection reset by peer
[00:32:27] dnewkerk: has joined #ruby
[00:32:27] dnewkerk: has joined #RubyOnRails
[01:19:52] dnewkerk: Quit: dnewkerk

2015-12-23

[08:17:27] dnewkerk: has joined #ruby
[09:27:54] dnewkerk: Quit: dnewkerk
[09:28:22] dnewkerk: has joined #ruby
[09:28:22] dnewkerk: has joined #RubyOnRails
[09:32:26] dnewkerk: Ping timeout: 240 seconds
[21:48:37] dnewkerk: has joined #ruby
[21:48:37] dnewkerk: has joined #RubyOnRails