Page 1 of 1
[11:34:00] duncan_bayne: Hi :) On my system, File.stat('/tmp').writable? returns true when run under MRI 2.5.1, but false when run under JRuby 22.214.171.124. This means that Dir.tmpdir is failing under JRuby, because it thinks /tmp isn't writable.
[11:34:35] duncan_bayne: I suspect I'm running into an obscure bug here, but couldn't find anything obvious.
[03:37:11] duncan_bayne: Hey :) We've just upgraded a Rails 4 project from MRI 2.2.2 -> 2.4.2, and we're seeing some odd behaviour in some of our specs. Specifically, assertions that kept failing until Timeout#timeout gave up no longer raise Timeout::Error, and thus no longer time out.
[03:37:37] duncan_bayne: Are there are any known issues w/ Timeout in 2.4.2? Did the usual Googling for issues, etc., but couldn't find anything.
[03:48:58] duncan_bayne: Also I still need to bring my rspec electrocution rig to Melbourne Ruby and hook you up to it :)
[03:49:12] duncan_bayne: If you place the little patches right you can provoke involuntary muscle spasms when your tests fail
[03:51:24] duncan_bayne: Not unless you count 'run a particular spec in our suite that does not seem to be different to any others' as M
[03:52:41] duncan_bayne: When it 'works', the debug trace shows a Timeout::Error being raised (eventually) after successive expectation failures
[03:52:58] duncan_bayne: When it doesn't, you see the expectation failure, but it just keeps trying forever (well, until CI or an operator kills it)
[03:56:22] duncan_bayne: RickHull: yeah we don't use it directly, it's the https://github.com/laserlemon/rspec-wait gem
[03:59:22] duncan_bayne: Radar: Pez isn't a fan of those; he wanted greater flexibility around matchers, IIRC.
[04:35:14] duncan_bayne: RickHull: let me know how you go, would be interested to try your fork against our test suite
[04:49:22] duncan_bayne: pars: Speaking for myself, trying to work out why Timeout#timeout ... isn't ... but only in one of our specs, and only since 2.2.2
[05:04:48] duncan_bayne: Will definitely let you know how we get on; milewski reports that the first test run on 2.4 HEAD didn't repro the problem. But it is intermittent ...
[06:16:34] duncan_bayne: RickHull: pez has asked me to let you know that he's commented on https://github.com/rickhull/rspec-wait/commit/985aa88dfe4ade70d290aa5c61e57d3872e6b7fc
[22:00:31] duncan_bayne: Hi, quick question - are thread pools the default for JRuby 126.96.36.199? I get 'jruby: warning: unknown property jruby.thread.pooling' when I try to use thread pools with 188.8.131.52 but not with 1.7.22.
[22:00:52] duncan_bayne: I've had a look at the documentation, but it doesn't say anything about support being dropped / defaulted.
[22:02:08] duncan_bayne: When I set it in JRUBY_OPTS, e.g. JRUBY_OPTS="-J-Djruby.thread.pooling=true" ruby myscript.rb
[22:03:07] duncan_bayne: Of course it might be I'm passing in an altogether invalid option, and it's just that 1.7.22 is silent about it :)
[10:50:32] duncan_bayne: Hi, can anyone recommend a library for parsing Excel files that doesn't barf on large spreadsheets (~ 30MiB or so)? I've just filed https://github.com/weshatheleopard/rubyXL/issues/199 and https://github.com/woahdae/simple_xlsx_reader because both those libraries burn 6.0GiB+ to open a 30MiB spreadsheet, then my system falls over :(
[05:03:56] duncan_bayne: Hi, I'm seeing some unexpected behaviour using in_time_zone() in Australia. It uses 'EST +10:00' instead of AEST, and 'EST +11:00' instead of AEDT. Details here: https://gist.github.com/duncan-bayne/62bd46da5167c6b5bc93
[05:11:39] duncan_bayne: @sevenseacat I'm pretty sure it should be EDT (or AEDT) not EST during daylight savings.
[05:18:55] duncan_bayne: Hi, I'm trying to call a set accessor from C with 'rb_funcall(output, rb_intern("state"), 1, T_TRUE);'. It's failing silently :( Am I doing something obviously wrong here?
[11:04:14] duncan_bayne: Hey is help with Rubywarrior (https://github.com/ryanb/ruby-warrior) on-topic here? Want to check before referring people here in a presentation.
[11:04:39] duncan_bayne: It's a 'how to learn Ruby with rubywarrior' meetup presentation for newbies.
[00:30:46] duncan_bayne: Hi all, quick question: does anyone know how to configure max_nesting for multi_json in Rails 3? I'm regularly working with JSON nested deeper than the default maximum of 20.
[04:05:21] duncan_bayne: Hi all. Got a quick question: I've upgraded a Rails 2 app to 3.2.8. Coffeescript files are being re-compiled when changed, but frequently the old version is being served up in the browser.
[04:05:40] duncan_bayne: Symptom is I make a change, save, refresh the page, see the change, refresh, don't see it (old version is served).
[04:08:19] duncan_bayne: @micaeked: That does indeed fix it, as does a precompile. But the issue is that by my understanding it shouldn't happen at all. Once recompiled the new asset should be served consistently. Which means either my understanding is flawed or I'm doing something wrong.
[04:11:48] duncan_bayne: @rknLA: it does, but it's happening on both FF and Chrome. And it doesn't happen on a fresh Rails 3.2.8 app which leads me to suspect our app is doing something retarded.
[04:28:13] duncan_bayne: @micaeked: Yeah, that's what we did too. Our app is large, so we actually scripted it. Basically incrementally worked on this script to build a Rails 3 app from the guts of our Rails 2 app, then 'flicked the switch', merged, and we were in Rails 3. Then a bunch of sundry little issues to fix, of which this is the last.
[04:39:03] duncan_bayne: @micaeked: Ahah. Having had a look through our Rake tasks, I think we may be precompiling automatically in dev :-/
[04:39:27] duncan_bayne: @micaeked: I think that may be some sort of weird legacy from the asset pipeline stuff we were doing in Rails 2.