mroutis

Activity Graph

Page 1 of 6 | Next »

2018-11-16

[01:37:29] mroutis: Ping timeout: 268 seconds
[02:36:05] mroutis: has joined #ruby
[07:01:23] mroutis: Quit: leaving
[18:42:12] mroutis: has joined #ruby
[20:27:50] mroutis: Ping timeout: 268 seconds
[22:58:02] mroutis: has joined #ruby
[23:32:27] mroutis: Remote host closed the connection
[23:34:39] mroutis: has joined #ruby
[23:40:31] mroutis: Remote host closed the connection

2018-11-15

[01:38:15] mroutis: has joined #ruby
[02:00:55] mroutis: Quit: leaving
[03:50:02] mroutis: has joined #ruby
[05:28:51] mroutis: Remote host closed the connection
[23:09:49] mroutis: has joined #ruby
[23:38:09] mroutis: ivanskie: piotr the mythical solnica?

2018-11-14

[23:17:57] mroutis: has joined #ruby
[23:37:38] mroutis: Read error: Connection reset by peer

2018-11-12

[04:13:47] mroutis: has joined #ruby
[04:21:04] mroutis: Remote host closed the connection

2018-11-09

[00:30:11] mroutis: Read error: Connection reset by peer
[00:34:22] mroutis: has joined #ruby
[03:01:25] mroutis: Read error: Connection reset by peer
[03:07:17] mroutis: has joined #ruby
[04:25:53] mroutis: Read error: Connection reset by peer
[22:40:39] mroutis: has joined #ruby
[22:42:08] mroutis: Client Quit

2018-11-08

[02:29:56] mroutis: Ping timeout: 272 seconds
[03:46:10] mroutis: has joined #ruby
[04:25:46] mroutis: Read error: Connection reset by peer
[04:26:16] mroutis: has joined #ruby
[05:51:35] mroutis: Remote host closed the connection
[21:39:33] mroutis: has joined #ruby
[22:19:42] mroutis: Read error: Connection reset by peer
[23:18:17] mroutis: has joined #ruby
[23:38:16] mroutis: Read error: Connection reset by peer
[23:39:05] mroutis: has joined #ruby

2018-11-07

[02:42:09] mroutis: Read error: Connection reset by peer
[02:43:08] mroutis: has joined #ruby
[04:50:58] mroutis: Read error: Connection reset by peer
[04:51:40] mroutis: has joined #ruby
[06:21:02] mroutis: Read error: Connection reset by peer
[17:18:17] mroutis: has joined #ruby
[18:57:49] mroutis: Read error: Connection reset by peer
[18:58:20] mroutis: has joined #ruby
[20:30:03] mroutis: Ping timeout: 245 seconds
[21:27:02] mroutis: has joined #ruby

2018-11-06

[19:07:38] mroutis: has joined #ruby
[21:27:06] mroutis: Read error: Connection reset by peer
[21:27:31] mroutis: has joined #ruby
[21:44:16] mroutis: Ping timeout: 246 seconds
[22:53:52] mroutis: has joined #ruby

2018-11-02

[18:14:46] mroutis: has joined #ruby
[18:37:27] mroutis: Remote host closed the connection

2018-11-01

[00:31:48] mroutis: has joined #ruby
[01:31:35] mroutis: Remote host closed the connection

2018-10-30

[02:58:07] mroutis: Ping timeout: 240 seconds
[14:37:07] mroutis: has joined #ruby
[14:54:49] mroutis: Ping timeout: 244 seconds
[15:44:33] mroutis: has joined #ruby
[15:46:38] mroutis: has left #ruby: ()

2018-10-29

[18:36:08] mroutis: has joined #ruby
[19:31:27] mroutis: Ping timeout: 240 seconds
[20:36:37] mroutis: has joined #ruby

2018-10-26

[00:41:24] mroutis: has joined #ruby
[03:34:50] mroutis: Remote host closed the connection

2018-10-25

[16:45:12] mroutis: has joined #ruby
[21:39:37] mroutis: Ping timeout: 244 seconds

2018-10-24

[00:01:07] mroutis: has joined #ruby
[00:22:19] mroutis: bye, phaul
[01:28:09] mroutis: Ping timeout: 252 seconds
[01:39:18] mroutis: has joined #ruby
[02:31:27] mroutis: Ping timeout: 240 seconds
[04:19:26] mroutis: has joined #ruby
[05:44:46] mroutis: Remote host closed the connection

2018-10-21

[00:39:46] mroutis: What's the name of this "early return" from functions, instead of nesting a lot of "if" cases?
[00:41:31] mroutis: guard clauses!
[00:42:10] mroutis: it was not a trivia, just me fighting my memory out loud
[02:12:09] mroutis: Ping timeout: 244 seconds
[03:32:12] mroutis: has joined #ruby
[04:35:58] mroutis: Remote host closed the connection
[16:41:57] mroutis: has joined #ruby
[17:43:24] mroutis: c-c: there's a Maybe in dry-rb
[17:43:42] mroutis: https://dry-rb.org/gems/dry-monads/
[18:16:03] mroutis: Ping timeout: 252 seconds
[19:40:52] mroutis: has joined #ruby
[22:51:08] mroutis: Remote host closed the connection

2018-10-20

[23:52:23] mroutis: has joined #ruby

2018-10-09

[02:56:54] mroutis: has joined #ruby
[04:56:23] mroutis: Remote host closed the connection
[18:09:24] mroutis: has joined #ruby
[19:55:16] mroutis: Ping timeout: 272 seconds
[20:26:19] mroutis: has joined #ruby

2018-10-08

[15:19:33] mroutis: has joined #ruby
[18:42:39] mroutis: Ping timeout: 252 seconds
[19:40:13] mroutis: has joined #ruby
[19:50:42] mroutis: zenspider: is this ruby related? I haven't heard anything about `ivar`s or RTypedData
[19:52:29] mroutis: today I learned ^ :O
[20:08:33] mroutis: if you don't mind me asking, what are you writing that requires such _low-level_ management?
[22:14:03] mroutis: Ping timeout: 244 seconds

2018-10-07

[01:47:48] mroutis: Remote host closed the connection

2018-10-06

[20:44:30] mroutis: has joined #ruby
[20:44:35] mroutis: Remote host closed the connection
[21:03:18] mroutis: has joined #ruby
[21:05:43] mroutis: What's a good way to read from IO (line by line) without a huge memory impact?
[21:33:28] mroutis: ohh, right
[21:44:11] mroutis: apeiros: what about each_line?
[21:44:19] mroutis: right, thanks
[21:45:39] mroutis: what added code are you refering to?
[21:56:41] mroutis: ohh, silly me, I was doing ARGF.each_line, wondering why it was consuming a lot of memory; I guess is trying to read everything at once
[22:23:48] mroutis: sure, apeiros, I was trying to solve the first and easiest codechef problem using ruby: https://www.codechef.com/viewsolution/18471591
[22:24:45] mroutis: basically, you've a file with numbers, and you output just the lines that have `42` included
[22:25:08] mroutis: using sed, it would be `sed -n /42/p`
[22:25:18] mroutis: lines are just a number
[22:25:40] mroutis: if you have a look at the proposed solution in their dashboard, it says that it consumes 28M !
[22:25:43] mroutis: https://www.codechef.com/status/TEST,mroutis?sort_by=Mem&sorting_order=asc&language=All&status=All
[22:27:23] mroutis: ACTION facepalm
[22:27:42] mroutis: right, it stops at the first 42 number
[22:28:34] mroutis: so, it would be `sed -n 1,/42/p`
[22:30:15] mroutis: It's weird, apeiros, because there are other solutions consuming 0M of memory
[22:30:27] mroutis: take a look https://www.codechef.com/status/TEST?sort_by=Mem&sorting_order=asc&language=17&status=All&Submit=GO
[22:31:30] mroutis: everyone is doing this `gets.chomp` thingy; it's more fun if you can write "efficient" and readable code
[22:31:58] mroutis: I think they don't take into account the memory accumulated before running the code
[22:42:17] mroutis: yes, I misread my code, apeiros ... I thought it was intended to output just `42` (the `next` solution), but it's about printing until you match the first 42 (`break` one)
[22:42:29] mroutis: sorry for that one, hehe
[22:46:16] mroutis: lol, I copypasted the solution with 0M and submitted it again with my account
[22:47:19] mroutis: I don't know if they are loading more stuff than needed, or it is the base runtime memspace of ruby 2.3.3
[22:48:50] mroutis: well, mystery solved, thank you a lot, apeiros, it was bugging me like crazy

2018-10-05

[22:23:07] mroutis: has joined #ruby
[22:43:07] mroutis: Remote host closed the connection

2018-09-11

[17:24:24] mroutis: has joined #ruby
[19:12:45] mroutis: Ping timeout: 252 seconds
[21:32:31] mroutis: has joined #ruby
[23:18:48] mroutis: Ping timeout: 245 seconds

2018-09-08

[00:20:57] mroutis: has joined #ruby
[02:04:47] mroutis: Ping timeout: 240 seconds
[02:30:25] mroutis: has joined #ruby
[02:35:53] mroutis: Ping timeout: 245 seconds
[04:52:51] mroutis: has joined #ruby
[05:39:46] mroutis: Ping timeout: 272 seconds
[12:15:39] mroutis: has joined #ruby
[12:29:07] mroutis: Ping timeout: 240 seconds

2018-09-07

[01:00:45] mroutis: has joined #ruby-offtopic
[01:00:45] mroutis: has joined #ruby
[01:50:47] mroutis: Remote host closed the connection
[17:04:12] mroutis: has joined #ruby
[18:29:15] mroutis: Ping timeout: 252 seconds
[22:40:20] mroutis: has joined #ruby
[23:40:39] mroutis: Read error: Connection reset by peer

2018-09-06

[01:01:12] mroutis: Read error: Connection reset by peer
[01:01:49] mroutis: has joined #ruby-offtopic
[01:01:49] mroutis: has joined #ruby
[01:29:51] mroutis: Ping timeout: 252 seconds
[02:00:05] mroutis: has joined #ruby-offtopic
[02:00:05] mroutis: has joined #ruby
[04:26:37] mroutis: Read error: Connection reset by peer
[16:43:38] mroutis: has joined #ruby-offtopic
[16:43:38] mroutis: has joined #ruby
[19:09:24] mroutis: Ping timeout: 272 seconds
[21:51:56] mroutis: has joined #ruby-offtopic
[21:51:56] mroutis: has joined #ruby
[23:55:22] mroutis: Ping timeout: 244 seconds

2018-09-05

[02:49:50] mroutis: has joined #ruby-offtopic
[02:49:50] mroutis: has joined #ruby
[04:12:58] mroutis: Ping timeout: 245 seconds
[14:28:06] mroutis: has joined #ruby-offtopic
[14:28:06] mroutis: has joined #ruby
[15:06:47] mroutis: Ping timeout: 240 seconds
[16:04:30] mroutis: has joined #ruby-offtopic
[16:04:30] mroutis: has joined #ruby
[17:55:28] mroutis: Ping timeout: 245 seconds
[21:32:54] mroutis: has joined #ruby-offtopic
[21:32:54] mroutis: has joined #ruby

2018-09-04

[03:12:43] mroutis: Read error: Connection reset by peer
[03:13:42] mroutis: has joined #ruby-offtopic
[03:13:42] mroutis: has joined #ruby
[03:33:27] mroutis: Ping timeout: 240 seconds
[14:44:29] mroutis: has joined #ruby-offtopic
[14:44:29] mroutis: has joined #ruby
[18:38:47] mroutis: Ping timeout: 240 seconds
[20:43:04] mroutis: has joined #ruby-offtopic
[20:43:04] mroutis: has joined #ruby
[21:23:28] mroutis: Read error: Connection reset by peer

2018-09-03

[18:14:49] mroutis: has joined #ruby
[18:37:46] mroutis: Ping timeout: 244 seconds
[22:09:18] mroutis: has joined #ruby
[22:11:25] mroutis: has joined #ruby-offtopic

2018-08-31

[15:36:05] mroutis: has joined #ruby
[18:35:27] mroutis: Ping timeout: 252 seconds
[22:16:14] mroutis: has joined #ruby
[23:36:15] mroutis: Remote host closed the connection

2018-08-30

[02:07:30] mroutis: has joined #ruby
[02:48:23] mroutis: Ping timeout: 245 seconds
[16:19:00] mroutis: has joined #ruby
[16:30:03] mroutis: Remote host closed the connection
[16:46:43] mroutis: has joined #ruby
[16:59:15] mroutis: Remote host closed the connection
[17:06:57] mroutis: has joined #ruby
[17:14:27] mroutis: Ping timeout: 240 seconds
[18:14:47] mroutis: has joined #ruby
[18:23:52] mroutis: tubbo: are you a musician/composer?
[18:24:34] mroutis: has joined #ruby-offtopic
[18:33:41] mroutis: Remote host closed the connection
[18:45:43] mroutis: has joined #ruby
[20:34:00] mroutis: Remote host closed the connection

2018-08-29

[00:48:34] mroutis: has joined #ruby
[02:57:15] mroutis: Ping timeout: 252 seconds
[12:17:53] mroutis: has joined #ruby
[18:27:16] mroutis: Remote host closed the connection

2018-08-23

[00:13:29] mroutis: Ping timeout: 272 seconds

2018-08-22

[00:22:11] mroutis: thoraxe: maybe you can run a headless chrome and call it as written on the documentation
[00:22:40] mroutis: `distill http://example.com/article.html`
[02:39:22] mroutis: has joined #ruby-offtopic
[02:40:04] mroutis: night, all
[02:41:37] mroutis: what are some small open source gems with good quality code?
[02:42:44] mroutis: (with good quality, I mean pleasant to the eyes / with _a e s t h e t i c s_)
[04:12:45] mroutis: Ping timeout: 265 seconds
[14:10:12] mroutis: has joined #ruby
[15:29:31] mroutis: hehe, I also switched from minitest to rspec because of stub/mocks
[15:31:48] mroutis: no, havenwood, I enjoy the expresiveness of rspec `allow x to receive y`
[15:34:33] mroutis: (in the ruby on rails context, where the convention is a lot of side-effects)
[15:36:28] mroutis: for example, I have a controller that does something like: `if resource.save?; send_info_to_third_party; notify_user; render... end`
[15:37:26] mroutis: with rspec, I can describe "POST #create", and before(:each) do "allow(controller).to receive(:sedn_info_to_third_party) and (:notify_user)"
[15:38:26] mroutis: and have a case: "when data is invalid, expect(controller).to_not have_received(:send_info_to_third_party)"
[15:42:06] mroutis: indeed, ineb, but something like `s/current_function/new_function/` will do the work
[15:43:59] mroutis: yes, that's true, minitests encourages to being able to mock objects in order to add stubs to it
[15:47:45] mroutis: sure! also, if you are collaborating with more people, you need to take into account their skill level and their _code perspective_
[15:48:51] mroutis: sometimes, you are working with someone more "procedural", and they'll make horrible decisions if they are forced to write good OOP code
[15:53:20] mroutis: I guess that the best test suite / codebase is the one where all the involved can be as productive as possible
[15:54:58] mroutis: has joined #ruby-offtopic

2018-08-21

[03:12:18] mroutis: has joined #ruby
[04:20:58] mroutis: Ping timeout: 260 seconds
[15:23:42] mroutis: has joined #ruby
[16:05:16] mroutis: Remote host closed the connection
[17:16:05] mroutis: has joined #ruby

2018-08-20

[01:31:48] mroutis: indeed, wild_buffalo, however, I couldn't found info about that function, is it defined elsewhere?
[01:36:46] mroutis: wild_buffalo: yes, function names accept a question mark as correct syntax, so it's used for functions that returns a boolean
[01:42:06] mroutis: oh, true, elomatreb, the bang (!) convention is for methods that change data in a "destructive" way (modifying the object they are called on, instead of just outputting the result)
[01:42:12] mroutis: wild_buffalo: ^
[01:46:23] mroutis: ACTION scratches head
[01:46:29] mroutis: that's true, elomatreb
[01:51:15] mroutis: ohh right, the "may raise", as in "save!" or "create!" in ruby on rails
[02:22:57] mroutis: Ping timeout: 240 seconds
[02:40:37] mroutis: has joined #ruby-offtopic
[02:40:37] mroutis: has joined #ruby
[03:21:40] mroutis: Remote host closed the connection