machty

Activity Graph

Page 1 of 3 | Next »

2018-11-26

[09:25:34] machty: *.net *.split

2018-10-10

[01:38:09] machty: *.net *.split
[01:46:00] machty: has joined #spree
[01:46:21] machty: has joined #spree

2018-08-20

[20:08:59] machty: Ping timeout: 256 seconds

2018-08-16

[00:43:48] machty: has joined #spree

2018-08-08

[23:02:49] machty: *.net *.split

2018-06-20

[03:41:41] machty: Ping timeout: 256 seconds
[03:45:37] machty: has joined #spree
[03:45:47] machty: has joined #ruby
[03:51:27] machty: Ping timeout: 260 seconds
[06:10:44] machty: has joined #spree
[06:10:54] machty: has joined #ruby

2018-05-29

[02:47:10] machty: *.net *.split
[02:48:03] machty: has joined #ruby
[02:48:14] machty: has joined #spree

2018-05-19

[14:43:06] machty: Ping timeout: 256 seconds

2018-04-25

[12:25:39] machty: *.net *.split
[12:26:47] machty: has joined #spree
[12:27:13] machty: has joined #ruby
[15:01:09] machty: *.net *.split
[15:03:23] machty: has joined #ruby
[15:03:33] machty: has joined #spree

2018-04-22

[15:59:39] machty: *.net *.split
[16:25:31] machty: has joined #spree
[16:25:32] machty: has joined #ruby

2018-04-20

[13:21:02] machty: has joined #spree
[13:21:12] machty: has joined #ruby

2018-04-10

[14:07:06] machty: has joined #spree
[14:07:26] machty: has joined #ruby

2018-03-18

[07:18:46] machty: Read error: Connection reset by peer

2018-03-02

[04:16:10] machty: has joined #spree
[04:16:30] machty: has joined #ruby

2018-02-28

[23:18:53] machty: Ping timeout: 265 seconds
[23:19:50] machty: has joined #spree
[23:20:10] machty: has joined #ruby

2018-02-06

[12:11:13] machty: has joined #spree
[12:11:23] machty: has joined #ruby

2018-01-07

[20:35:04] machty: *.net *.split
[21:07:13] machty: has joined #spree
[21:07:16] machty: has joined #ruby
[21:10:13] machty: Ping timeout: 250 seconds
[21:11:07] machty: has joined #spree
[21:11:13] machty: has joined #ruby

2017-12-27

[19:13:52] machty: Ping timeout: 240 seconds
[19:42:51] machty: has joined #spree
[19:42:57] machty: has joined #ruby

2017-12-07

[14:48:11] machty: *.net *.split
[14:54:12] machty: has joined #spree
[14:54:17] machty: has joined #ruby
[14:55:58] machty: Max SendQ exceeded
[14:59:22] machty: has joined #ruby
[14:59:22] machty: has joined #spree

2017-12-01

[02:28:24] machty: has joined #spree
[02:28:54] machty: has joined #ruby

2017-11-09

[03:13:37] machty: Ping timeout: 250 seconds
[03:16:12] machty: has joined #RubyOnRails
[03:16:35] machty: has joined #spree
[03:16:38] machty: has joined #ruby

2017-11-08

[09:43:36] machty: *.net *.split
[09:49:02] machty: has joined #spree
[09:49:07] machty: has joined #ruby
[09:49:08] machty: has joined #RubyOnRails
[09:50:10] machty: Max SendQ exceeded
[09:51:06] machty: has joined #RubyOnRails
[09:51:28] machty: has joined #spree
[09:51:32] machty: has joined #ruby

2017-10-16

[06:26:48] machty: has joined #RubyOnRails
[06:27:10] machty: has joined #spree
[06:27:14] machty: has joined #ruby

2017-08-06

[19:07:55] machty: *.net *.split
[19:13:22] machty: has joined #RubyOnRails
[19:13:44] machty: has joined #spree
[19:13:48] machty: has joined #ruby

2017-07-26

[14:49:11] machty: how can i configure/decorate the default log message that fires when a rails controller handles a request to include other information (e.g. the id of the admin user logged in, etc) ?
[14:50:55] machty: actually this seems helpful http://www.paperplanes.de/2012/3/14/on-notifications-logsubscribers-and-bringing-sanity-to-rails-logging.html

2017-06-20

[00:17:10] machty: *.net *.split
[00:22:37] machty: has joined #RubyOnRails
[00:22:59] machty: has joined #ruby

2017-06-17

[18:48:50] machty: *.net *.split
[18:50:00] machty: has joined #RubyOnRails
[18:50:22] machty: has joined #spree
[18:50:26] machty: has joined #ruby

2017-06-07

[21:29:24] machty: Ping timeout: 240 seconds

2017-05-08

[18:11:34] machty: has joined #RubyOnRails
[18:11:56] machty: has joined #spree
[18:12:00] machty: has joined #ruby

2017-04-26

[21:11:11] machty: man, getting by butt kicked
[21:11:41] machty: I'm using IO.pipe and a separate thread to read chunks from HTTP and write to the pipe, and i'm passing the read side to CSV.new(rd)
[21:11:54] machty: but the csv immediately thinks the it has reached eof
[21:12:04] machty: and doesn't parse/produce any rows
[21:12:11] machty: rd.gets works just fine
[21:12:25] machty: each_line and variants work just fine, but CSV is barfing. wtf could be the issue?
[21:26:13] machty: nvm, i'm just not going to use CSV.new but do a piecemeal CSV.parse
[21:26:17] machty: toooooo much magic

2017-04-19

[19:39:06] machty: i have a background job that does a mass import to replace lots of items in the database
[20:03:10] machty: i have a background task that does a batch import; i wrap the whole thing in a DB transaction in case the import fails halfway through, but i also want to be able to update a `state` attribute on a Job in the database so i can see the state of this long running vjob
[20:03:29] machty: unfortunately if i'm just using a single DB connection it's going to include that Job.state set in the transaction
[20:03:38] machty: which means i won't see anything until the whole job is complete
[20:03:46] machty: i believe the answer is just i need to check out a separate connection

2017-03-18

[03:11:30] machty: i am attempting a tricky refactor that involves splitting an ActiveRecord model/table into two
[03:12:19] machty: for the purpose of minimizing code changes i've attempted an approach where legacy code that i dont' want to change can still interface with a facade class that pretends to be that old style class
[03:12:26] machty: but really it delegates to the two new active record classes/models
[03:12:36] machty: it's working _pretty_ well so far
[03:12:54] machty: but now there's an `old_class_instance.update_attribute()` call
[03:13:17] machty: and basically the attribute being updated might live on one new class or the other
[03:13:28] machty: i'm wondering if rails has a built in mechanism to support this
[03:13:33] machty: this kind of refactor
[03:13:46] machty: so that i don't have to keep pulling this sweater thread

2016-07-25

[18:31:23] machty: is the activerecord connection pool per-process?
[18:31:42] machty: e.g. if i set the database.yml max to 20, will each puma process try and make 20 connections?
[18:31:46] machty: puma worker process
[18:34:36] machty: tubbo: that seems correct to me, just realizing that after the puma fork, it tries to reconnect and the pool size seems like it'll be 20 for each worker process
[18:46:12] machty: tubbo: this excellent SO post answered all of my questions http://stackoverflow.com/a/22404491/914123

2016-07-02

[05:04:51] machty: *.net *.split
[13:10:01] machty: has joined #RubyOnRails
[13:10:07] machty: has joined #spree
[13:10:10] machty: has joined #ruby

2016-06-23

[20:31:19] machty: Ping timeout: 258 seconds
[20:39:06] machty: has joined #RubyOnRails
[20:39:13] machty: has joined #spree
[20:39:16] machty: has joined #ruby

2016-06-09

[05:24:32] machty: Ping timeout: 260 seconds
[05:31:16] machty: has joined #RubyOnRails
[05:33:10] machty: has joined #spree
[05:34:20] machty: has joined #ruby

2016-06-07

[21:13:04] machty: is it possible in action cable to send back data to a particular connection?
[21:13:25] machty: e.g. i send "gimme x" to a channel action and it sends me "ack", and only sends it to me and no one els
[21:13:43] machty: i can't find the api for doing this that doesn't go through the Channel abstraction
[21:20:52] machty: (resolved my actioncable issue: i can use `transmit({ lol: 'wat' })` in my Channel class)

2016-05-18

[08:45:40] machty: Ping timeout: 250 seconds
[08:54:32] machty: has joined #RubyOnRails
[08:56:26] machty: has joined #spree
[08:57:37] machty: has joined #ruby

2016-04-27

[06:58:41] machty: Ping timeout: 264 seconds
[07:01:55] machty: has joined #RubyOnRails
[07:03:49] machty: has joined #spree
[07:04:59] machty: has joined #ruby

2016-04-25

[15:17:18] machty: i'd like to spin up a quick server that just barfs the request payload so that i can debug/test webhooks. is there a one-liner httpd esque thing i could use in ruby or what's the easiest way to do this?

2016-04-11

[19:39:05] machty: Is there a way to specify a cascading delete policy within a rails migration t.references, something like t.references :location, index: true, foreign_key: true, on_delete: :cascade
[19:39:20] machty: docs only mention on_delete: :cascade on add_foreign_key
[19:47:03] machty: smathy: i looked at the code, doesn't seem to be supported
[19:51:06] machty: smathy: i misspoke! it totally does work the way you suggested :)
[19:51:11] machty: good call
[19:52:05] machty: epochwolf: not sure if it shows up in db/schema but definitely in db/structure

2016-04-05

[21:18:54] machty: Ping timeout: 248 seconds
[21:21:29] machty: has joined #RubyOnRails
[21:23:39] machty: has joined #spree
[21:25:14] machty: has joined #ruby

2016-03-24

[19:08:29] machty: has joined #RubyOnRails
[19:08:51] machty: has left #RubyOnRails: ()
[19:08:56] machty: has joined #RubyOnRails

2016-02-28

[00:02:02] machty: Ping timeout: 268 seconds
[00:11:11] machty: has joined #RubyOnRails
[00:14:06] machty: has joined #spree
[00:16:07] machty: has joined #ruby
[03:36:01] machty: Ping timeout: 268 seconds
[03:37:07] machty: has joined #RubyOnRails
[03:39:49] machty: has joined #spree
[03:41:32] machty: has joined #ruby
[03:53:54] machty: Ping timeout: 268 seconds
[04:02:21] machty: has joined #RubyOnRails
[04:05:02] machty: has joined #spree
[04:06:48] machty: has joined #ruby
[04:26:46] machty: Ping timeout: 244 seconds
[04:32:16] machty: has joined #RubyOnRails
[04:34:58] machty: has joined #spree
[04:37:14] machty: has joined #ruby
[04:42:37] machty: Ping timeout: 268 seconds
[04:44:32] machty: has joined #RubyOnRails
[04:47:13] machty: has joined #spree
[04:48:59] machty: has joined #ruby
[05:01:23] machty: Ping timeout: 244 seconds
[05:02:48] machty: has joined #RubyOnRails
[05:05:28] machty: has joined #spree
[05:07:13] machty: has joined #ruby
[05:19:37] machty: Ping timeout: 268 seconds
[05:22:36] machty: has joined #RubyOnRails
[05:25:18] machty: has joined #spree
[05:27:02] machty: has joined #ruby
[05:57:17] machty: Ping timeout: 268 seconds

2016-02-27

[22:43:23] machty: has joined #ruby
[22:43:24] machty: has joined #spree
[22:43:24] machty: has joined #RubyOnRails
[22:48:44] machty: Max SendQ exceeded
[22:54:05] machty: has joined #RubyOnRails
[22:54:34] machty: has joined #spree
[22:59:27] machty: has joined #ruby

2016-02-16

[23:38:43] machty: *.net *.split

2016-02-04

[04:12:47] machty: Ping timeout: 260 seconds
[04:18:06] machty: has joined #RubyOnRails
[04:21:07] machty: has joined #spree
[04:22:57] machty: has joined #ruby

2016-01-19

[18:34:48] machty: Ping timeout: 255 seconds
[18:37:41] machty: has joined #RubyOnRails
[18:40:41] machty: has joined #spree
[18:42:31] machty: has joined #ruby

2016-01-13

[18:10:19] machty: has joined #RubyOnRails
[18:13:19] machty: has joined #spree
[18:15:09] machty: has joined #ruby

2016-01-02

[00:00:24] machty: Ping timeout: 240 seconds

2015-12-13

[10:26:01] machty: Ping timeout: 250 seconds
[10:49:40] machty: has joined #RubyOnRails
[10:52:07] machty: has joined #spree
[10:53:47] machty: has joined #ruby
[18:13:56] machty: Ping timeout: 240 seconds

2015-12-12

[17:42:16] machty: *.net *.split

2015-12-02

[15:39:24] machty: *.net *.split
[15:41:50] machty: has joined #spree
[15:41:50] machty: has joined #RubyOnRails
[15:52:48] machty: *.net *.split
[16:35:00] machty: has joined #spree
[16:41:47] machty: has joined #spree
[16:41:47] machty: Changing host
[16:44:57] machty: *.net *.split
[16:47:38] machty: has joined #ruby
[16:48:09] machty: has joined #RubyOnRails
[16:48:10] machty: has joined #spree
[18:41:55] machty: Remote host closed the connection
[18:58:01] machty: has joined #RubyOnRails
[19:00:28] machty: has joined #spree
[19:02:08] machty: has joined #ruby

2015-11-30

[03:50:04] machty: has joined #spree
[03:51:49] machty: has joined #ruby
[05:05:01] machty: Ping timeout: 264 seconds
[05:07:26] machty: has joined #RubyOnRails
[05:09:57] machty: has joined #spree
[05:11:43] machty: has joined #ruby
[05:46:24] machty: Ping timeout: 264 seconds
[05:50:12] machty: has joined #RubyOnRails
[05:52:57] machty: has joined #spree
[05:54:44] machty: has joined #ruby
[08:04:25] machty: Ping timeout: 264 seconds
[08:06:02] machty: has joined #RubyOnRails
[08:08:46] machty: has joined #spree
[08:10:44] machty: has joined #ruby
[08:23:00] machty: Ping timeout: 264 seconds
[08:24:46] machty: has joined #spree
[08:26:31] machty: has joined #ruby
[08:31:05] machty: has joined #RubyOnRails
[08:31:05] machty: has joined #spree
[08:31:05] machty: has joined #ruby
[08:31:05] machty: Changing host