lacrymology

Activity Graph

Page 1 of 6 | Next »

2017-06-19

[14:48:57] lacrymology: Read error: Connection reset by peer

2017-06-18

[15:19:59] lacrymology: Ping timeout: 268 seconds
[15:21:33] lacrymology: has joined #RubyOnRails

2017-06-14

[03:35:21] lacrymology: Ping timeout: 255 seconds
[14:20:40] lacrymology: has joined #RubyOnRails
[14:36:17] lacrymology: Ping timeout: 255 seconds
[14:57:09] lacrymology: has joined #RubyOnRails
[16:34:38] lacrymology: Ping timeout: 240 seconds
[17:09:28] lacrymology: has joined #RubyOnRails
[17:25:50] lacrymology: Ping timeout: 240 seconds
[18:21:39] lacrymology: has joined #RubyOnRails
[22:41:27] lacrymology: Ping timeout: 240 seconds

2017-06-13

[12:08:09] lacrymology: Ping timeout: 240 seconds
[14:55:24] lacrymology: has joined #RubyOnRails
[16:18:50] lacrymology: Ping timeout: 240 seconds
[16:59:50] lacrymology: has joined #RubyOnRails

2017-06-12

[16:53:34] lacrymology: has joined #RubyOnRails

2017-06-11

[17:44:43] lacrymology: has joined #RubyOnRails
[18:04:57] lacrymology: Ping timeout: 240 seconds

2017-06-09

[00:25:00] lacrymology: Ping timeout: 255 seconds
[14:42:36] lacrymology: has joined #RubyOnRails
[15:09:23] lacrymology: Ping timeout: 246 seconds
[15:13:07] lacrymology: has joined #RubyOnRails
[20:01:32] lacrymology: Ping timeout: 260 seconds

2017-03-25

[16:16:23] lacrymology: has joined #ruby
[17:50:38] lacrymology: Quit: leaving

2017-03-24

[13:29:10] lacrymology: has joined #ruby
[14:27:59] lacrymology: Ping timeout: 246 seconds
[14:30:17] lacrymology: has joined #ruby
[15:31:21] lacrymology: Ping timeout: 260 seconds
[17:24:08] lacrymology: has joined #ruby
[18:09:05] lacrymology: Ping timeout: 260 seconds

2017-03-23

[03:44:32] lacrymology: has joined #ruby
[04:11:05] lacrymology: Ping timeout: 258 seconds
[14:25:27] lacrymology: has joined #ruby
[16:24:25] lacrymology: Ping timeout: 260 seconds
[16:49:58] lacrymology: has joined #ruby
[19:26:06] lacrymology: Ping timeout: 240 seconds

2017-03-22

[00:46:44] lacrymology: Ping timeout: 268 seconds
[00:53:24] lacrymology: has joined #ruby
[12:16:14] lacrymology: Ping timeout: 240 seconds
[13:11:51] lacrymology: has joined #ruby
[15:48:20] lacrymology: Ping timeout: 246 seconds
[16:38:12] lacrymology: has joined #ruby
[19:01:46] lacrymology: Ping timeout: 260 seconds
[22:18:57] lacrymology: has joined #ruby
[22:43:06] lacrymology: Ping timeout: 240 seconds
[22:52:06] lacrymology: has joined #ruby
[23:14:09] lacrymology: Ping timeout: 240 seconds
[23:32:29] lacrymology: has joined #ruby
[23:47:29] lacrymology: Ping timeout: 240 seconds

2017-03-21

[00:26:46] lacrymology: Ping timeout: 240 seconds
[14:17:53] lacrymology: has joined #ruby
[19:33:49] lacrymology: Ping timeout: 240 seconds
[23:25:03] lacrymology: has joined #ruby

2017-03-20

[16:41:27] lacrymology: has joined #ruby
[16:41:46] lacrymology: does anyone know what's going on here? http://dpaste.com/3151PTC
[17:28:36] lacrymology: baweaver: sorry, didn't see that
[17:28:40] lacrymology: rake, version 10.5.0
[17:28:40] lacrymology: 14:00 $ bundle exec rake --version
[17:40:47] lacrymology: baweaver: that seems to work
[19:52:31] lacrymology: Ping timeout: 256 seconds
[19:54:20] lacrymology: has joined #ruby
[20:42:36] lacrymology: what's a good interactve debugger? I'm used to pdb in python, which is very much like gdb
[20:43:12] lacrymology: they use pry in my project, but I can't figure out how to step out of the current method, navigate the stacktrace, etc
[20:43:25] lacrymology: Disavowed: any good use guides?
[20:51:21] lacrymology: Disavowed, matthewd: it's weird, it seems like it's installed but some documented commands don't work: up, down, backtrace
[21:10:10] lacrymology: matthewd: "including" is doing `gem 'byebug'` somewhere appropriate in the Gemfile, right?
[21:16:40] lacrymology: ah, gotcha. Sorry

2016-02-29

[15:33:48] lacrymology: has joined #RubyOnRails
[17:22:54] lacrymology: Ping timeout: 246 seconds
[17:57:16] lacrymology: has joined #RubyOnRails
[23:16:21] lacrymology: has left #RubyOnRails: ()

2016-02-26

[15:28:46] lacrymology: has joined #RubyOnRails
[20:24:37] lacrymology: Ping timeout: 252 seconds
[22:08:53] lacrymology: has joined #RubyOnRails
[22:49:34] lacrymology: Ping timeout: 240 seconds

2016-02-25

[14:21:59] lacrymology: has joined #RubyOnRails
[14:23:07] lacrymology: has joined #RubyOnRails
[14:35:59] lacrymology: Ping timeout: 240 seconds
[16:01:14] lacrymology: has joined #RubyOnRails
[19:21:29] lacrymology: Ping timeout: 240 seconds
[19:37:21] lacrymology: has joined #RubyOnRails
[22:20:28] lacrymology: Quit: Lost terminal
[22:28:05] lacrymology: has joined #RubyOnRails
[23:29:51] lacrymology: Quit: leaving

2016-02-24

[14:08:04] lacrymology: has joined #RubyOnRails
[20:57:57] lacrymology: Ping timeout: 244 seconds
[21:15:07] lacrymology: has joined #RubyOnRails
[23:04:15] lacrymology: Ping timeout: 250 seconds

2016-02-23

[00:03:04] lacrymology: Ping timeout: 240 seconds
[15:03:50] lacrymology: has joined #RubyOnRails
[22:19:13] lacrymology: Ping timeout: 250 seconds
[22:33:52] lacrymology: has joined #RubyOnRails

2016-02-22

[14:23:05] lacrymology: has joined #RubyOnRails

2016-02-19

[11:45:34] lacrymology: has joined #RubyOnRails
[12:09:06] lacrymology: Ping timeout: 276 seconds
[13:57:43] lacrymology: has joined #RubyOnRails
[15:08:11] lacrymology: Ping timeout: 250 seconds
[15:20:54] lacrymology: has joined #RubyOnRails
[21:50:20] lacrymology: Quit: leaving

2016-02-18

[14:45:33] lacrymology: has joined #RubyOnRails
[17:00:28] lacrymology: Quit: Lost terminal
[17:01:23] lacrymology: has joined #RubyOnRails
[22:40:19] lacrymology: Quit: leaving
[22:41:54] lacrymology: has joined #RubyOnRails
[22:49:26] lacrymology: Quit: leaving

2016-02-17

[21:41:56] lacrymology: Ping timeout: 248 seconds

2016-02-16

[02:10:15] lacrymology: Quit: leaving
[12:48:33] lacrymology: has joined #RubyOnRails
[13:34:26] lacrymology: Ping timeout: 272 seconds
[14:00:04] lacrymology: has joined #RubyOnRails
[20:46:26] lacrymology: Ping timeout: 250 seconds
[22:03:57] lacrymology: has joined #RubyOnRails
[23:43:32] lacrymology: Ping timeout: 250 seconds

2016-02-15

[14:03:38] lacrymology: has joined #RubyOnRails
[17:07:09] lacrymology: has left #RubyOnRails: ()
[18:54:34] lacrymology: has joined #RubyOnRails

2016-02-13

[00:16:18] lacrymology: Quit: leaving

2016-02-12

[14:41:30] lacrymology: has joined #RubyOnRails
[16:45:45] lacrymology: Disconnected by services
[18:35:11] lacrymology: has joined #RubyOnRails
[20:35:43] lacrymology: Quit: Lost terminal
[21:48:34] lacrymology: has joined #RubyOnRails

2016-02-10

[10:05:54] lacrymology: has joined #RubyOnRails
[12:59:48] lacrymology: Ping timeout: 248 seconds
[13:40:51] lacrymology: has joined #RubyOnRails
[18:18:58] lacrymology: Quit: Lost terminal
[18:19:32] lacrymology: has joined #RubyOnRails
[21:27:26] lacrymology: Ping timeout: 256 seconds

2016-02-09

[15:18:18] lacrymology: Quit: leaving
[15:18:30] lacrymology: has joined #RubyOnRails
[19:53:39] lacrymology: Quit: Lost terminal
[19:58:52] lacrymology: has joined #RubyOnRails
[23:12:39] lacrymology: Quit: leaving

2016-02-08

[16:40:00] lacrymology: has joined #RubyOnRails
[22:43:01] lacrymology: has left #RubyOnRails: ()

2016-02-06

[09:43:03] lacrymology: has joined #RubyOnRails
[11:04:14] lacrymology: Ping timeout: 272 seconds

2016-02-05

[00:47:35] lacrymology: Ping timeout: 264 seconds
[11:03:59] lacrymology: has joined #RubyOnRails
[11:19:12] lacrymology: Quit: leaving
[11:19:22] lacrymology: has joined #RubyOnRails
[16:14:30] lacrymology: *.net *.split
[16:15:45] lacrymology: has joined #RubyOnRails
[16:40:36] lacrymology: Ping timeout: 248 seconds
[16:42:15] lacrymology: has joined #RubyOnRails
[21:48:47] lacrymology: Ping timeout: 264 seconds

2016-02-04

[09:30:26] lacrymology: has joined #RubyOnRails
[10:35:26] lacrymology: Ping timeout: 240 seconds
[13:35:54] lacrymology: has joined #RubyOnRails
[16:32:15] lacrymology: I have a problem with two models that are pretty interdependent. I've got an Event model which has a description, and a Recurrence model which has recurrence data for the event: the limit dates, start day and hour for the event. It's a one-to-one. I check overlaps on the Recurrence object, but that requires the event to be set, because the event is tied to a User and the User knows what's the
[16:32:21] lacrymology: correct time zone to do the math. So at validation time, event.user needs to be set, and recurrence.event needs to be set. To make things even more complex, there's two types of recurrence: weekly and monthly which is implemented with STI, there's a base class Recurrence which so far shouldn't be used directly (but maybe in the near future they'll represent one-off events). So the problem is that
[16:32:27] lacrymology: I can't validate overlaps because recurrence.event doesn't exist before event is saved
[22:55:05] lacrymology: Ping timeout: 260 seconds
[23:16:24] lacrymology: has joined #RubyOnRails

2016-02-03

[15:12:02] lacrymology: has joined #RubyOnRails
[17:15:48] lacrymology: Ping timeout: 248 seconds
[17:16:20] lacrymology: has joined #RubyOnRails
[18:15:27] lacrymology: I'm using STI in combination with accept_nested_attributes. The result is that when I just build an object, I get an instance of the parent model, rather than the actual one I'm trying to create.
[18:15:52] lacrymology: Is there a way to somehow "cast" these objects?
[18:17:40] lacrymology: I'm overriding `recurrence_attributes=` (the STI model) so I could do something there, such as creating a new instance if type is set, or something
[18:18:29] lacrymology: maybe self.recurrence = self.recurrence.type.constantize.build(self.recurrence.attributes) << how's that look?
[19:55:12] lacrymology: Read error: Connection reset by peer
[19:55:21] lacrymology: has joined #RubyOnRails
[20:25:55] lacrymology: Read error: Connection reset by peer
[20:29:58] lacrymology: has joined #RubyOnRails
[21:37:19] lacrymology: Ping timeout: 250 seconds

2016-02-02

[10:15:05] lacrymology: has joined #RubyOnRails
[10:29:16] lacrymology: Ping timeout: 272 seconds
[11:57:34] lacrymology: has joined #RubyOnRails
[12:20:56] lacrymology: Ping timeout: 240 seconds
[15:47:07] lacrymology: has joined #RubyOnRails
[16:38:24] lacrymology: Quit: leaving

2016-02-01

[15:32:38] lacrymology: has joined #RubyOnRails
[18:22:46] lacrymology: Read error: Connection reset by peer
[18:26:59] lacrymology: has joined #RubyOnRails
[21:41:26] lacrymology: Ping timeout: 240 seconds
[22:01:59] lacrymology: has joined #RubyOnRails
[22:13:24] lacrymology: Ping timeout: 248 seconds

2016-01-31

[15:58:03] lacrymology: has joined #RubyOnRails
[16:54:42] lacrymology: Quit: leaving
[16:54:52] lacrymology: has joined #RubyOnRails
[17:12:11] lacrymology: Ping timeout: 264 seconds

2016-01-30

[20:59:07] lacrymology: has joined #RubyOnRails
[22:19:59] lacrymology: Ping timeout: 264 seconds

2016-01-29

[14:01:18] lacrymology: has joined #RubyOnRails
[16:18:06] lacrymology: Ping timeout: 240 seconds
[16:29:39] lacrymology: has joined #RubyOnRails
[16:43:00] lacrymology: does Hash#merge work recursively with dicts?
[17:15:18] lacrymology: can I have rspec jump into byebug when there's a failure?
[17:16:38] lacrymology: smathy: yeah, but I have a test that's failing randomly
[17:16:53] lacrymology: and I haven't been able to see it fail when stopping before
[17:18:08] lacrymology: tbuehlmann: I'll look into that, thanks
[17:21:49] lacrymology: tubbo: thanks, that's really usefulk
[20:50:42] lacrymology: Read error: Connection reset by peer
[20:55:04] lacrymology: has joined #RubyOnRails
[21:13:25] lacrymology: Quit: leaving

2016-01-28

[11:46:21] lacrymology: has joined #RubyOnRails
[11:58:40] lacrymology: Ping timeout: 256 seconds
[12:00:04] lacrymology: has joined #RubyOnRails
[12:52:30] lacrymology: Ping timeout: 256 seconds
[13:03:14] lacrymology: has joined #RubyOnRails
[18:51:37] lacrymology: Quit: leaving

2016-01-27

[00:50:55] lacrymology: Ping timeout: 240 seconds
[09:55:08] lacrymology: has joined #RubyOnRails
[10:44:06] lacrymology: Ping timeout: 240 seconds
[13:41:01] lacrymology: has joined #RubyOnRails
[14:14:08] lacrymology: Ping timeout: 272 seconds
[14:23:42] lacrymology: has joined #RubyOnRails
[17:24:09] lacrymology: doesn't delegate of a column allow assignment? I'm getting a #<NoMethodError: undefined method `start_date=' for #<Event:0x0055852c257658>> where event delegates start_date to another model
[18:02:38] lacrymology: arup_r: http://dpaste.com/1831CCB << delegating the `=` methods explicitly did the trick, but should that be necessary?
[18:02:59] lacrymology: also with accepts_nested_attributes_for :recurrence
[18:03:49] lacrymology: with accepts_nested_attributes_for, on #update when assigning partial attributes I'm getting a new model being created instead of the existing one being updated. Is that normal? is there a way around that?
[18:08:30] lacrymology: arup_r: even so, then I've got to manually set it when I update?
[18:09:02] lacrymology: I mean, I need the client to send it? I seriously don't want that. I was hoping to keep the fact that these are two separate models as invisible as possible
[18:11:36] lacrymology: gbgdev: yeah, I thought I'd read it correctly but..
[23:06:39] lacrymology: Quit: leaving

2016-01-26

[12:37:49] lacrymology: has joined #RubyOnRails
[13:51:30] lacrymology: Ping timeout: 260 seconds
[15:12:15] lacrymology: has joined #RubyOnRails
[16:36:17] lacrymology: Ping timeout: 276 seconds
[16:39:26] lacrymology: has joined #RubyOnRails
[16:39:56] lacrymology: has joined #RubyOnRails
[18:29:45] lacrymology: Ping timeout: 260 seconds
[19:49:01] lacrymology: has joined #RubyOnRails
[21:58:26] lacrymology: I have a model which belongs_to another. I want to create the parent model as a nested resource for the child, and the child needs to run some validations that include both the parent and its own fields.. will that work?
[21:59:24] lacrymology: I've been trying some things, right now I've got the relationship backwards, and I'm having issues with the future parent (current child) validating based on the other model's fields because sometimes they're not set yet on create

2016-01-25

[12:18:04] lacrymology: has joined #RubyOnRails
[15:17:49] lacrymology: can a concern run a method on the including class? like, declare a before_filter or something?
[22:50:30] lacrymology: with single table inheritance, can I have a relation to the base class, and have it be polimorphic? I want to have WeeklyRecurrence and MonthlyRecurrence and event.recurrence to be a reference to either
[22:51:02] lacrymology: has_one: :recurrence; event.recurrence = MonthlyRecurrence.new << this will work as expected?
[23:24:04] lacrymology: Ping timeout: 256 seconds

2016-01-23

[18:27:21] lacrymology: has joined #RubyOnRails

2016-01-22

[10:56:51] lacrymology: has joined #RubyOnRails
[11:03:49] lacrymology: has joined #RubyOnRails
[13:14:14] lacrymology: Ping timeout: 272 seconds
[15:17:52] lacrymology: has joined #RubyOnRails
[21:50:24] lacrymology: Ping timeout: 272 seconds
[21:51:56] lacrymology: has joined #RubyOnRails
[23:47:46] lacrymology: Ping timeout: 240 seconds

2016-01-21

[17:39:57] lacrymology: has joined #RubyOnRails
[22:41:44] lacrymology: Ping timeout: 250 seconds