« Back to channel list

#ruby - 07 September 2018

« Back 1 day Forward 1 day »
[00:00:15] baweaver: It's not out for a few more years
[00:00:22] baweaver: Not much more to say on it brkkyk
[00:01:25] brkkyk: i heard it will be 3 times faster than version 2
[00:01:35] brkkyk: but i dont have any idea how they'll achieve this
[00:01:58] baweaver: https://blog.heroku.com/ruby-3-by-3
[00:02:16] baweaver: Just google around for Ruby 3x3, and most of the first page articles will go into it.
[00:05:42] baweaver: headed off for now, be back later.
[00:22:09] havenwood: brkkyk: https://medium.com/square-corner-blog/rubys-new-jit-91a5c864dd10
[00:22:14] havenwood: brkkyk: https://medium.com/@k0kubun/the-method-jit-compiler-for-ruby-2-6-388ee0989c13
[00:24:10] havenwood: brkkyk: Compiling parsed code into Ruby IR is a great speed win after first run. This could also be done for gems at install-time. This cuts out about a third of Ruby execution time. Then a JIT can make it faster to go from IR to machine code.
[00:25:04] havenwood: brkkyk: See the yomikomu and bootsnap gems for examples of compiling Ruby files into YARV IR files so they don't have to be re-parsed to be re-run.
[00:25:22] dendazen: has joined #ruby
[00:25:30] havenwood: brkkyk: You can try out the new JIT in Ruby 2.6.0-preview2 or nightly builds today.
[00:26:10] havenwood: Improvements to the JIT should add speed increases for years to come.
[00:28:15] dendazen: has joined #ruby
[00:29:25] havenwood: brkkyk: Ruby 2.5 already has a number of performance increases on the path to 3.0. The goal is for 3.0 to be 3x faster than 2.0.
[00:29:45] havenwood: brkkyk: 2.6 and 2.7 will edge closer to that goal.
[00:32:39] graphene: has joined #ruby
[00:42:21] graphene: has joined #ruby
[00:46:42] orbyt_: has joined #ruby
[00:58:16] Pisuke: has joined #ruby
[00:58:31] wojnar: has joined #ruby
[00:58:31] brandoncc: has joined #ruby
[01:00:45] mroutis: has joined #ruby
[01:08:14] Guest58115: has joined #ruby
[01:10:20] cagomez: has joined #ruby
[01:11:48] bga57: has joined #ruby
[01:22:33] shakes: has joined #ruby
[01:41:13] esrse: has joined #ruby
[01:46:44] Tharbakim: has joined #ruby
[01:49:07] matcouto: has joined #ruby
[02:09:43] tdy: has joined #ruby
[02:21:52] orbyt_: has joined #ruby
[02:40:38] EXCHGR: has joined #ruby
[02:48:46] ShekharReddy: has joined #ruby
[02:52:29] duderonomy: has joined #ruby
[02:56:31] DTZUZO: has joined #ruby
[03:02:02] tty: has joined #ruby
[03:10:16] braincrash: has joined #ruby
[03:24:44] brandoncc: has joined #ruby
[03:25:27] nikivi: has joined #ruby
[03:37:41] gix: has joined #ruby
[03:55:22] sonOfRa: has joined #ruby
[04:06:43] Guest58115: has joined #ruby
[04:09:19] duderonomy: has joined #ruby
[04:19:59] darix: has joined #ruby
[04:23:45] hays_: has joined #ruby
[04:24:27] hays_: this is my favorite piece of code today: https://github.com/tablador/rpn_calc/blob/master/rpn_calc.rb
[04:27:41] hays_: not sure i've seen any examples this generic
[04:30:33] hays_: i feel like this might be a good beginning to an obfuscated ruby contest
[04:30:57] planigan: has joined #ruby
[04:31:04] baweaver: It's also fairly bad Ruby.
[04:35:02] hays_: oh, please tell me all the reasons it is bad
[04:37:29] baweaver: It's using a for loop, it's using a case statement for a two-prong branch, it assumes the format of the input to have formatted operators as symbols, it doesn't raise with an error message to clarify the intent of the error, and a few others.
[04:37:52] baweaver: each or reduce would be more in line with common practice
[04:38:55] baweaver: that, and it's not using varadic args
[04:43:11] baweaver: Also send vs public_send
[04:43:24] hays_: i considered reduce, but it seemed that it would reduce clarity. and to me, each isn't an idiom that implies that order is important.
[04:45:20] hays_: i do not see a problem with a two pronged case statement, nor do I see a problem with using the symbols. I should raise a better error message--agreed. varadic args also might be a good idea
[04:45:44] baweaver: RPN typically assumes a string input
[04:46:21] baweaver: Normally one that hasn't been split
[04:46:54] baweaver: Assuming symbols and numbers from the start is interesting
[04:47:13] baweaver: each not implying order is an odd comment
[04:47:36] hays_: who says it has to be numbers
[04:47:57] hays_: it can be any method.
[04:48:14] hays_: that seems more flexible to me
[04:48:53] hays_: I think that a reasonable implementation of each (maybe not in ruby) would ignore order and happen in parallel
[04:49:03] hays_: whereas a for loop implies ordering
[04:49:12] baweaver: That's... odd
[04:50:02] hays_: If I tell you to chop each of these 5 vegetables, do you think you much chop them in the order i handed them to you?
[04:50:27] baweaver: You're conflating quite a bit here
[04:50:38] baweaver: The first of which is that there's a difference between each and for
[04:51:42] baweaver: Then you're applying that ideal to Ruby syntax as it exists, implying that it _should_ go that direction for an ideal language, but not Ruby
[04:51:46] baweaver: so you don't use that in Ruby
[04:51:52] baweaver: feels hand wavy
[04:52:46] baweaver: I mean sure, one could parallelize a Unit iterator in Haskell or Scala or what have you, and there are implementations of parallel each in Ruby
[04:53:00] hays_: so, are you saying that there is no use case in ruby for a for loop?
[04:53:04] baweaver: but as is Ruby iterates in order, even for Hashes which technically aren't supposed to do that.
[04:53:08] hays_: since .each is equivalent?
[04:53:39] baweaver: Essentially, yes. Idiomatically it's more commonly in use, and lends itself to blocks and functions that exist in other Enumerable methods
[04:53:56] baweaver: as well as allows extension of the Enumerable module, so in ways no, they're not the same
[04:54:21] baweaver: It depends on what you want to define as same
[04:55:01] hays_: I am just surprised to hear the opinion that the use of for loops is bad ruby
[04:55:27] baweaver: That's not remotely new
[04:55:53] hays_: are you saying you've held this opinion for a while?
[04:55:57] baweaver: Find _any_ style guide in common use for Ruby
[04:56:07] orpl: has joined #ruby
[04:56:37] baweaver: https://github.com/rubocop-hq/ruby-style-guide#no-for-loops
[04:56:57] baweaver: There are other more technical reasons as well including block level scoping
[04:57:17] baweaver: Implying further that it's solely my opinion is a bit off too
[04:58:21] baweaver: This goes back to probably 1.8.7 or before.
[04:58:23] hays_: we are just two people talking. I'm just trying to understand your ideas, which are probably coming from a place of deeper understanding of ruby
[04:59:31] baweaver: The point I'm trying to make is this is not something unique to me, it's common across the Ruby ecosystem and across millions of Ruby projects
[04:59:40] hays_: i wouldn't think code is bad if it clearly expresses what is happening, but it does appear that at least the rubocop style guide labels for loops as bad also
[05:00:21] baweaver: It's bad if it goes against common idioms, causing newer programmers confusion.
[05:00:36] hays_: someone who doesn't know what a for loop is
[05:01:02] havenwood: hays_: Here's a riff on your idea, for fun: https://gist.github.com/havenwood/97fcd886031df964d44f1ae8cef8fb61
[05:01:09] baweaver: I've taught them before.
[05:01:23] orbyt_: has joined #ruby
[05:01:30] hays_: i wonder if we counted developers who didn't know what a for loop was and then counted developers who didn't know what .each does, which would be higher
[05:01:51] baweaver: you keep doing that thing
[05:01:52] havenwood: hays_: that ^ version is the same as yours, except it returns nil instead of raising
[05:01:58] baweaver: setting up a strawman
[05:02:06] hays_: havenwood: cool. each_with_object is fancy. yeah
[05:02:15] havenwood: hays_: #reduce and #each_with_object are fun
[05:02:21] baweaver: We're talking about Ruby
[05:02:27] havenwood: hays_: or #with_object if you already have an Enumerator
[05:02:38] baweaver: What other languages do or don't do is irrelevant to conversations on what is or is not common and idiomatic in Ruby
[05:03:40] hays_: baweaver: there is a world where people must know many languages and not know them in great detail. I don't think that's necessarily a strawman. but I am not disagreeing with you, really. Except that I am not sure I would say that a for loop is bad. Maybe less idiomatic, sure
[05:04:10] havenwood: hays_: we just don't use for loops in Ruby - honestly mostly for aesthetic reasons but they're also not optimized
[05:04:16] havenwood: hays_: the idiomatic path is encouraged
[05:04:24] hays_: havenwood: yeah, each_with_object is one of those things that pops up quite a bit
[05:04:57] havenwood: hays_: you can always easily convert a for to an each, so it's kinda hand wavey to do
[05:05:02] havenwood: hays_: it's handy!
[05:06:43] hays_: your version really uses a lot of ruby-specific ideas
[05:07:20] baweaver: I still prefer push to << for clarity
[05:07:34] havenwood: ACTION chants "shovel! shovel!"
[05:07:34] hays_: some things I am actually reluctant to use in practice, maybe because of the people I work with, including myself, who have to switch between a lot of languages
[05:07:36] baweaver: also because << does bad things to numbers :D
[05:07:48] havenwood: >> 42 << 42
[05:07:49] ruby[bot]: havenwood: # => 184717953466368 (https://eval.in/1055081)
[05:08:01] baweaver: well, shifts, but anyways
[05:08:06] hays_: heh is that SHL
[05:08:52] hays_: i tend to prefer ruby that could be trivially converted to .. say.. python without much deep though
[05:09:05] baweaver: Then you're not writing Ruby
[05:09:15] havenwood: hays_: I'd prefer it be easily converted to Elixir or Clojure without much deep thought. :-
[05:09:22] baweaver: You _could_ make Ruby like Javascript too
[05:09:43] baweaver: Then you'd need polish notation instead of reverse for clojure
[05:10:22] hays_: its the world I live in. in fact, we might be dumping ruby soon. for probably arbitrary reasons
[05:11:03] baweaver: There are ways Ruby makes sense, and ways it doesn't
[05:11:10] baweaver: Use the right tool for the job.
[05:11:40] havenwood: hays_: We're using Ruby as much as ever.
[05:11:54] havenwood: hays_: What're using instead?
[05:12:16] havenwood: More than ever. Morever. Mever. Mer.
[05:12:28] baweaver: We even managed to convince some yahoo over here to speak at RubyConf this year
[05:13:36] hays_: havenwood: well.. we backed into Ruby via Rails, and its been fine. but we're reconsidering rails, and some other things we're doing would indicate Python as a smart choice because of its rather strong set of libraries for .. well a lot o things
[05:14:19] hays_: I personally don't think the problem is Rails. I think the problem is we don't have a strong enough team and its leading to bad implementations in Rails
[05:14:20] baweaver: Mostly data science, ml, and things around it.
[05:14:42] baweaver: You _really_ don't want to go more wild west with a loose team
[05:14:54] hays_: baweaver: yep, but its also solid with web, comms, and other IT glue stuff
[05:14:56] reber: has joined #ruby
[05:15:39] hays_: like I can pull down a iec 61850 implementation in python, but not in Ruby. its just so big
[05:16:21] baweaver: If you have a bad team, nothing will save that.
[05:16:28] hays_: It isn't going to be my call--software engineering is going to decide what to do with the Rails stuff
[05:16:35] hays_: baweaver: yep
[05:16:36] baweaver: Well, I say bad
[05:16:40] baweaver: Inexperienced would be better
[05:16:59] hays_: its just not a deep enough bench for the experience
[05:17:53] hays_: im on the sidelines, but I am seeing just huge problems everytime I glance across it. last time I did, I found some huge resource leak with threads and sockets due to the way they were being created and managed. causing the app to crash the server
[05:18:16] hays_: but we have one developer, and then a 'team in India'
[05:18:35] hays_: all managed by the developer--a person who cannot manage a team
[05:18:45] hays_: but this is wayyy off topic sorry
[05:19:42] hays_: The stuff I'm working on is probably best suited to be Python. So I may have less occasion to use Ruby, which will make me a little sad, because I like Ruby
[05:22:01] hays_: havenwood: small bug, your pops are backwards I think
[05:22:16] hays_: [15, 3, :/] should yield 5
[05:22:39] havenwood: oops. you're right
[05:22:52] hays_: my version 1 did that too heh
[05:29:01] hays_: why .instance_of and not .is_a ?
[05:34:23] duderonomy: has joined #ruby
[05:38:41] sauvin: has joined #ruby
[05:44:43] sidepocket: has joined #ruby
[05:49:55] marz_d`ghostman: has joined #ruby
[05:50:28] marz_d`ghostman: with ruby's logger, can it be customized to roll logs for everytime the app runs instead of daily/weekly/monthly?
[05:55:21] duderonomy: has joined #ruby
[06:03:11] rlawrence: has joined #ruby
[06:03:11] v01d4lph4: has joined #ruby
[06:06:37] baweaver: marz_d`ghostman https://ruby-doc.org/stdlib-2.4.0/libdoc/logger/rdoc/Logger.html#method-c-new
[06:06:55] baweaver: Just don't set a frequency of rotation
[06:07:12] baweaver: Just do a detection on the last log file present in a dir instead
[06:07:17] baweaver: and make that the name
[06:09:40] rlawrence_: has joined #ruby
[06:13:59] marz_d`ghostman: baweaver: I currently have this one Logger.new(log_file, formatter: proc {|severity, datetime, progname, msg| "[#{Process.pid}:#{Thread.current.object_id}][#{datetime}] #{severity} -- #{msg}\n" })
[06:14:03] MoritaShinobu: has joined #ruby
[06:14:11] marz_d`ghostman: baweaver: It seems to rotate daily
[06:14:16] Nicmavr: has joined #ruby
[06:14:17] duderonomy: has joined #ruby
[06:15:19] marz_d`ghostman: baweaver: I'll just set the suffix though, maybe it gets appended due to it having the same suffix
[06:19:28] rlawrence_: Hi there! I'm trying to make a ioctl system call via IO#ioctl from ruby and get some information from nvme block device. The code looks like this: https://dpaste.de/6hEz. Unfortunately, I run into errors like 'free(): Invalid pointer' (https://dpaste.de/Dsay). Despite this, I can successfully get the information about first three fields of the struct and then the behaviour is unpredictable. Could somebody explain what's wrong?
[06:20:57] rlawrence_: BTW, I'm also trying to avoid using FFI due to additional dependency. Thanks in advance!
[06:24:45] rlawrence_: The same purpose code in python looks like this: https://gist.github.com/lbernail/d851e5b06eb32180a4b8ead2ce4f45db
[06:26:12] duderonomy: has joined #ruby
[06:34:12] joelroa: has joined #ruby
[06:35:11] duderonomy: has joined #ruby
[06:37:03] dionysus69: has joined #ruby
[06:39:46] marz_d`ghostman: is Time.parse() still supported in Ruby 2.4? Cant' seem to see it here: https://ruby-doc.org/core-2.4.0/Time.html#method-i-strftime
[06:42:42] duderonomy: has joined #ruby
[06:47:58] aufi: has joined #ruby
[06:48:03] nowhere_man: has joined #ruby
[06:52:30] duderonomy: has joined #ruby
[06:59:44] kapil___: has joined #ruby
[07:07:53] marz_d`ghostman: How do I make this shortcut work? date = DateTime.parse('2018-09-07 13:38:38 +0800') { |date| date.strftime('%a,%d %b-%H:%M:%S')}
[07:09:09] rlawrence: has joined #ruby
[07:13:45] bomb: has joined #ruby
[07:26:04] Guest58115: has joined #ruby
[07:31:40] lomex: has joined #ruby
[07:48:52] vondruch: has joined #ruby
[07:51:44] mikecmpbll: has joined #ruby
[07:58:12] akem: has joined #ruby
[08:07:37] rlawrence: has joined #ruby
[08:11:57] lomex: has joined #ruby
[08:30:09] clorisu: has joined #ruby
[08:35:20] Beams: has joined #ruby
[08:36:20] alem0lars: has joined #ruby
[08:39:22] alem0lars: has joined #ruby
[08:42:27] alem0lars: has joined #ruby
[08:44:56] alem0lars: has joined #ruby
[08:46:16] marz_d`ghostman: If I pass a shift_age: 10 to Logger.new, it will keep 10 logs files right?
[08:47:15] alem0lars: has joined #ruby
[08:47:30] Stan: has joined #ruby
[08:50:14] alem0lars: has joined #ruby
[08:52:33] zenspider: man... color math is just grotesque...
[08:52:50] alem0lars: has joined #ruby
[08:53:36] bak1an: has joined #ruby
[08:55:18] alem0lars: has joined #ruby
[08:55:24] zenspider: rlawrence: still there?
[08:57:12] DTZUZO: has joined #ruby
[08:57:55] alem0lars: has joined #ruby
[09:00:29] leitz: has joined #ruby
[09:00:47] alem0lars: has joined #ruby
[09:00:50] rlawrence: zenspider: yep
[09:02:56] zenspider: apropos of nothing, check out a cleaner way to format your templates: https://dpaste.de/AZeG
[09:03:33] alem0lars: has joined #ruby
[09:04:55] rlawrence: zenspider: yeah, looks good!
[09:05:54] tristanp: has joined #ruby
[09:06:08] alem0lars: has joined #ruby
[09:07:03] bak1an_: has joined #ruby
[09:07:39] zenspider: so your code is getting up to the first null terminated string in the struct and then bombing out?
[09:08:11] alem0lars: has joined #ruby
[09:10:16] alem0lars: has joined #ruby
[09:10:48] redlegion: has joined #ruby
[09:11:37] zenspider: I don't have access to the structure or header you're grabbing... it might be nice to isolate whether this is a problem with the pack/unpack side of things or the actual call to ioctl.
[09:12:08] zenspider: I found https://wisesciencewise.wordpress.com/2017/07/06/c-program-to-send-identify-controller-command-to-an-nvme-storage-drive/ which has some equivalent C code... maybe run that or the python, grab the blob in question, and just try to unpack that?
[09:12:21] alem0lars: has joined #ruby
[09:12:42] aupadhye: has joined #ruby
[09:12:44] zenspider: it _could_ be that you found a bug... but that's pretty unlikely. that said, if there is going to be a dangling free, it's probably in someplace obscure like ioctl
[09:13:01] rlawrence: The structure I'm trying to grab: https://github.com/linux-nvme/nvme-cli/blob/d9a12812dfe1fe3edf92d71442677cac97bb312e/linux/nvme.h#L198
[09:14:46] alem0lars: has joined #ruby
[09:15:28] zenspider: this doco is so strange: https://nvmexpress.org/wp-content/uploads/NVM_Express_1_2_Gold_20141209.pdf the byte ranges are literally written backwards
[09:16:33] leitz: Anyone use MongoDB? I'm getting an 'invalid document' but the string passes seems to be a string and works if used manually. https://gist.github.com/LeamHall/0ca34a8bca8f30a2319fb5136faba8a9
[09:17:22] alem0lars: has joined #ruby
[09:17:38] zenspider: rlawrence: yeah. I'd use the python to do the same action, save it off into a binary file, then use ruby to read it in and test your template against. assuming that works fine, then try to isolate the ioctl stuff more
[09:18:01] zenspider: mongodb?? really? for your thing?
[09:18:42] leitz: zenspider, yup.
[09:19:45] alem0lars: has joined #ruby
[09:20:16] leitz: Hmm...the issue isn't in the passing of the query, but the translation of the query itself, it seems.
[09:20:19] zenspider: !connection alem0lars
[09:20:20] ruby[bot]: +bbb $a:alem0lars$#ruby-fix-your-connection alem0lars!*@*$#ruby-fix-your-connection *!*@host152.lan.imolinfo.it$#ruby-fix-your-connection
[09:20:20] ruby[bot]: ruby[bot] kicked alem0lars: join/part detected
[09:20:27] rlawrence: zenspider: thanks, I'll try
[09:20:35] zenspider: rlawrence: good luck. sorry I couldn't be more help
[09:20:50] leitz: Setting the query inside the find method still fails.
[09:21:02] zenspider: I do find that removing noise and lining stuff up so the human brain can pattern match more does help a lot
[09:22:13] zenspider: leitz: look at line 3
[09:23:10] leitz: zenspider, I had thought it turned the query into a hash, but a "puts query.class" shows it as a string.
[09:23:18] leitz: What am I missing?
[09:23:30] leitz: Besides the usual "brain, clue, and life"?
[09:23:30] zenspider: compare it to line 16, which works...
[09:26:39] leitz: Okay, added spaces, but not seeing the difference. If I cut and past the string that is the query into the db, it works.
[09:27:06] leitz: The "{}" doesn't seem to convert it into a hash, as I earlier thought.
[09:27:22] zenspider: what is the arg on line 16?
[09:28:42] leitz: ACTION ours coffee and then pours over the question.
[09:31:07] leitz: AH! It's SUPPOSED TO BE a hash. I'm still stuck in the "=>" mode.
[09:34:16] clemens3: has joined #ruby
[09:35:57] rlawrence: zenspider: anyhow, thanks for your help!
[09:45:32] sticaz: has joined #ruby
[09:48:15] unCork: has joined #ruby
[10:07:20] savolla: has joined #ruby
[10:12:32] doubledup: has joined #ruby
[10:19:07] bak1an: has joined #ruby
[10:33:23] akem: has joined #ruby
[10:56:11] dionysus70: has joined #ruby
[10:56:28] AJA4350: has joined #ruby
[11:06:30] aupadhye_: has joined #ruby
[11:08:16] johnny56: has joined #ruby
[11:24:20] apeiros_: has joined #ruby
[11:28:35] aupadhye_: has joined #ruby
[11:36:23] dellavg_: has joined #ruby
[11:36:54] rlawrence: zenspider: unpack works as expected: the code: https://dpaste.de/TH3P, output of the script: https://dpaste.de/trmk (nvme id-ctrl -b produces binary string of 4096 symbols)
[11:44:15] rlawrence: zenspider: I'm not sure how to correctly pass a pointer to the allocated buffer...
[11:48:24] magellanicloud: has joined #ruby
[12:01:52] akem: has joined #ruby
[12:07:20] jcalla: has joined #ruby
[12:11:41] gr33n7007h: has joined #ruby
[12:12:17] mostlybadfly: has joined #ruby
[12:15:04] Mike11: has joined #ruby
[12:19:26] wojnar: has joined #ruby
[12:23:57] garyserj: has joined #ruby
[12:24:46] Stan: has joined #ruby
[12:28:06] thy0: has joined #ruby
[12:28:38] nowhere_man: has joined #ruby
[12:28:43] garyserj: i'm having trouble getting pry byebug to work. I did require 'pry' and I did binding.pry, Then I run the program and it pauses, which is good. But I can't get it to step through the code. I tried c/continue, no use. I tried n/next. No use. I tried s/step, no use. I tried 'help' but i don't see a command to step!
[12:30:28] bmurt: has joined #ruby
[12:37:54] al2o3-cr: has joined #ruby
[12:39:36] garyserj: ah i think require 'pry-byebug' and binding.pry do it
[12:47:36] bak1an: has joined #ruby
[12:49:29] argoneus: has joined #ruby
[12:50:09] wolfshappen: has joined #ruby
[12:51:30] hays_: has joined #ruby
[12:54:40] BaroMeter: has joined #ruby
[13:00:19] bak1an: has joined #ruby
[13:14:53] gr33n7007h: has joined #ruby
[13:23:48] thejs: has joined #ruby
[13:30:38] rlawrence: zenspider: I've found the root cause. I had a doubts about passing the pointer and I was right.
[13:33:38] jamesaxl: has joined #ruby
[13:33:41] jamesaxl: I hope that you are interested about HardnenedBSD
[13:36:59] RougeR: has joined #ruby
[13:37:28] thy0: has joined #ruby
[13:41:14] aufi: has joined #ruby
[13:41:42] RougeR: anyone able to give me a hand with some s3 stubbing?
[13:42:29] rlawrence: zenspider: diff: https://dpaste.de/0GCW working solution: https://dpaste.de/uqqQ
[13:42:47] aufi: has joined #ruby
[13:44:36] RougeR: https://gist.github.com/CodePint/fc02aa99d7c09fff84caae9d436d0256
[13:49:30] Rapture: has joined #ruby
[13:50:20] yohji: has joined #ruby
[13:51:47] rippa: has joined #ruby
[13:55:26] al2o3-cr: has joined #ruby
[14:01:08] dionysus70: has joined #ruby
[14:17:31] v01d4lph4: has joined #ruby
[14:17:52] brandoncc: has joined #ruby
[14:18:59] gnufied: has joined #ruby
[14:32:06] v01d4lph4: has joined #ruby
[14:59:52] Dbugger: has joined #ruby
[15:03:57] RougeR: has joined #ruby
[15:04:49] NL3limin4t0r: has joined #ruby
[15:25:36] kapil___: has joined #ruby
[15:28:00] gr33n7007h: has joined #ruby
[15:51:53] duderonomy: has joined #ruby
[15:56:15] orbyt_: has joined #ruby
[15:59:18] al2o3-cr: has joined #ruby
[15:59:33] cagomez: has joined #ruby
[16:24:57] Inline: has joined #ruby
[16:26:16] cthulchu: has joined #ruby
[16:26:57] Inline: has joined #ruby
[16:28:19] Inline: has joined #ruby
[16:37:11] brandoncc: has joined #ruby
[16:42:09] Guest58115: has joined #ruby
[16:43:42] dionysus69: has joined #ruby
[16:51:41] anubhav996: has joined #ruby
[17:04:12] mroutis: has joined #ruby
[17:08:43] desperek: has joined #ruby
[17:20:33] ShekharReddy: has joined #ruby
[17:32:42] RougeR: has joined #ruby
[17:37:08] ellcs: has joined #ruby
[17:39:33] eckhardt: has joined #ruby
[17:41:07] duderonomy: has joined #ruby
[17:45:19] segy: has joined #ruby
[17:56:19] ebobby: has joined #ruby
[18:00:52] dbz: has joined #ruby
[18:11:20] johnny56: has joined #ruby
[18:15:36] rlawrence: has joined #ruby
[18:17:32] illuzion: has joined #ruby
[18:19:48] phatcat: has joined #ruby
[18:20:17] phatcat: heya, has anyone played with https://github.com/lobsters/lobsters?
[18:23:14] bak1an_: has joined #ruby
[18:23:41] ule: I did a while ago.. I was planning to help out in the project but never got a chance
[18:23:47] ule: phatcat: are you planning to?
[18:24:28] phatcat: ule: I managed to bring up a dev instance but am having problems with the production one
[18:24:38] phatcat: no idea what I'm doing wrong
[18:26:22] phatcat: I was wondering whether there's a DO snapshot or smth that I could deploy
[18:26:31] dr3wo: has joined #ruby
[18:28:18] ule: I didn't run the project in Prod mode. As far as I remember there is a Docker somewhere
[18:29:48] phatcat: yeah, https://github.com/jamesbrink/docker-lobsters
[18:29:54] phatcat: mind if I pm?
[18:37:05] cthu|: has joined #ruby
[18:38:08] thejs: has joined #ruby
[18:48:06] Guest58115: has joined #ruby
[18:49:41] cthulchu: has joined #ruby
[18:51:35] jottr: has joined #ruby
[18:58:34] Guest58115: has joined #ruby
[19:03:38] ramfjord: has joined #ruby
[19:08:15] Guest58115: has joined #ruby
[19:12:56] johnny56: has joined #ruby
[19:17:50] graphene: has joined #ruby
[19:20:29] jottr: has joined #ruby
[19:22:41] n13z: has joined #ruby
[19:24:44] graphene: has joined #ruby
[19:25:30] mikecmpbll: has joined #ruby
[19:26:56] akem: has joined #ruby
[19:32:09] SeepingN: has joined #ruby
[19:51:23] dionysus69: has joined #ruby
[19:59:18] jottr: has joined #ruby
[20:12:59] bak1an: has joined #ruby
[20:15:27] jottr: has joined #ruby
[20:26:09] Freshnuts: has joined #ruby
[20:33:47] lomex: has joined #ruby
[20:35:40] tdy: has joined #ruby
[20:35:47] cthu|: has joined #ruby
[20:39:01] gr33n7007h: has joined #ruby
[20:45:03] ramfjord: has joined #ruby
[20:58:27] gr33n7007h: has joined #ruby
[20:59:16] knight33: has joined #ruby
[21:00:47] SeepingN: has joined #ruby
[21:05:14] ineb: has joined #ruby
[21:07:48] mynameisdebian: has joined #ruby
[21:13:18] fredlinhares: has joined #ruby
[21:16:05] Guest58115: has joined #ruby
[21:20:53] ivanskie: has joined #ruby
[21:33:22] Guest58115: has joined #ruby
[21:37:35] rlawrence: has joined #ruby
[21:38:31] gr33n7007h: has joined #ruby
[21:41:38] beowuff: has joined #ruby
[21:43:20] Guest58115: has joined #ruby
[21:47:34] postmodern: has joined #ruby
[21:48:35] bmurt: has joined #ruby
[21:50:51] graphene: has joined #ruby
[21:53:14] Guest58115: has joined #ruby
[21:58:13] mynameisdebian: has joined #ruby
[22:03:20] Guest58115: has joined #ruby
[22:07:40] graphene: has joined #ruby
[22:10:29] agent_white: has joined #ruby
[22:13:19] Guest58115: has joined #ruby
[22:20:38] beowuff: has joined #ruby
[22:21:43] nicesignal: has joined #ruby
[22:23:22] Guest58115: has joined #ruby
[22:33:17] Guest58115: has joined #ruby
[22:35:13] cthulchu: has joined #ruby
[22:40:20] mroutis: has joined #ruby
[22:42:53] nicesignal: has joined #ruby
[22:43:16] Guest58115: has joined #ruby
[22:45:20] thejs: has joined #ruby
[22:47:57] cthu|: has joined #ruby
[22:53:15] Guest58115: has joined #ruby
[23:02:59] brandoncc: has joined #ruby
[23:03:17] Guest58115: has joined #ruby
[23:13:23] Guest58115: has joined #ruby
[23:23:25] Guest58115: has joined #ruby
[23:28:51] havenwood: has joined #ruby
[23:29:06] cthulchu: has joined #ruby
[23:33:18] Guest58115: has joined #ruby
[23:36:27] bmurt: has joined #ruby
[23:40:44] mroutis_: has joined #ruby
[23:43:18] Guest58115: has joined #ruby
[23:46:56] govg: has joined #ruby
[23:53:10] Guest58115: has joined #ruby
[23:55:49] bmurt: has joined #ruby