samu

Activity Graph

Page 1 of 1

2019-04-30

[01:35:53] samu: has joined #ruby
[01:36:07] samu: Client Quit

2015-11-13

[13:28:22] samu: has joined #ruby
[14:17:56] samu: Ping timeout: 250 seconds
[14:36:47] samu: has joined #ruby
[17:09:52] samu: Quit: Leaving

2015-11-12

[04:06:17] samu: has joined #ruby
[04:32:35] samu: Ping timeout: 264 seconds

2015-11-10

[04:05:55] samu: has joined #ruby
[04:10:46] samu: Hi there, sorry for bothering everyone...a bit of a newbie question here, but I have looked and can't find what I'm looking for. I'd like to see ruby documentation in the command line. I've been trying to massage ri to fit the need, but keep running into issues and have read that when used in conjunction with rvm it will eat a lot of memory. Can anyone recommend a way to find ruby documentation that interrupts one's workflow less than naviga
[04:10:47] samu: ting to ruby-doc.org?
[04:31:22] samu: Ox0dea, thank you, I will try harder to get it working.
[04:32:49] samu: Remote host closed the connection
[04:33:36] samu: has joined #ruby
[04:37:08] samu: bnagy, what would you type in a pry or irb prompt
[04:39:20] samu: Ox0dea, thanks
[05:05:37] samu: Ox0dea and bnagy, I know you probably think me a fool (and are likely right) but your simple instructions helped me out worlds - I wasn't using half of what pry is good for.
[05:05:55] samu: Thank you
[05:06:10] samu: Ox0dea, even that's generous
[06:03:44] samu: Maybe a good day to skip breakfast
[08:14:21] samu: Ping timeout: 246 seconds

2015-08-12

[11:49:36] samu: has left #ruby: ()

2015-08-09

[18:02:18] samu: has joined #ruby
[18:02:53] samu: I have a customer running ruby-1.8.7-p374 on FreeBSD 10.2-RC3 via rvm (which should not be the case here)
[18:03:13] samu: I'm trying to install mysql2 gem for him, but the gem utility keeps complaining that it can't find the mysql.h header file
[18:03:37] samu: yes, the devel packages are also installed
[18:03:59] samu: but because it's freebsd, the include and lib files are prefixed under /usr/local, so mysql.h is actually under /usr/local/include/mysql/mysql.h
[18:04:45] samu: now, in the gem output I can see that it tries to use /usr/local/bin/mysql_config, and that script gives the right information, the -I and -L flags point to the right directories: -I/usr/local/include/mysql and -L/usr/local/lib/mysql
[18:05:25] samu: I cannot re-create this problem under my account on the same type of server (exact same os/hardware), so I'm blindly asking for help now
[18:06:12] samu: here's the `gem install mysql2` output: https://dpaste.de/ur9g
[18:13:12] samu: crap, I have to make this work somehow ;D

2014-02-21

[00:19:31] samu: cause I'm getting some weird errors with `gem`, which may really be related to such own resolver.
[00:22:23] samu: Errno::EPERM: Operation not permitted - bind(2) for "0.0.0.0" port 34600
[00:22:23] samu: > p Resolv.getaddress "google.com"
[00:22:48] samu: now that's funny, it used to work in previous ruby versions.
[00:23:22] samu: ddd: ok, but... why did ruby wrote own resolver?
[00:23:30] samu: and why is it so screwed?
[00:23:56] samu: havenwood: cool... but why the hell does it randomize bind port by itself?
[00:24:20] samu: well, I'll probably fill a bug report tommorow
[00:24:25] samu: because, yes, this is a implementation bug
[00:24:43] samu: no, that ruby's own resolver is randomizing bind ports by itself.
[00:24:56] samu: 01:23 < ddd> samu I think its required you pass the IP outbound now.
[00:25:06] samu: ddd: a word of explanation here - on this machine I have a restricted bind policy.
[00:25:27] samu: You can only bind to a port I allow you to, UNLESS you're binding to autoport, which for this syscall is simply '0'.
[00:25:37] samu: this is a standard feature of my (and some other) operating systems.
[00:25:53] samu: practically every udp software uses it.
[00:26:06] samu: to be honest, it's the first time I see something like this in a production code.
[00:26:31] samu: not linux, freebsd actually.
[00:26:43] samu: but anyway, autoport is the standard, randomizing ports by ruby itself - not.
[00:27:14] samu: yeah, it is something I enabled. but that's not the point.
[00:27:25] samu: a standard way on practically every unix system is to bind to port 0, which is autoport.
[00:27:52] samu: I'll just fill a bug report, and advise my customers not to use latest ruby until it's fixed.
[00:45:23] samu: rjhunter: that doesn't really seem to be a CVE of ruby's concern at all.
[00:45:35] samu: havenwood: are you asking for my ruby version, or how loong am I using ruby?
[00:45:53] samu: havenwood: 2.1.0p0
[00:46:26] samu: havenwood: I have also 1.9 installed here, so I don't really know when it has changed.
[00:46:43] samu: I've tried to search in the changelog, but I couldn't find anything, so I'd have to check in every release
[00:47:03] samu: and it worked for me on 1.9.3p429
[00:48:12] samu: havenwood: funny then, that I can observe it on 2.1.0 ;)