Broken pipe with RVM (or whatever) about culerity

[phoet]

one more thing:

when i surf the page on localhost:3001 i get the same broken pipe errors in my browser, but after reloading the page the error is gone. this happens every second call?!

[phoet]

i did some more testing on versions of ruby and gems and i now pinned the problem:

broken pipe errors do NOT occur using OSX system ruby. i tried various versions of 1.8.7 and ree with RVM and i always got the broken pipe errors.

with system ruby there are no errors, BUT every second call will result in a blank page, which seems to be the same error, just different...

[phoet]

it seems that somehow the $stdout pipe goes away and the rails logging output can not be printed. maybe something with the log-file? less tries to open it as a binaray file:

less log/culerity.log
"log/culerity.log" may be a binary file. See it anyway?

i played around a little bit with rack/log_tailer.rb, in which the broken-pipe occurs and patched line 30 to rescue the output:

$stdout.print(contents) rescue $stderr.print("error #{$!} with #{contents}")

now the logging-output goes into the console, which is way better than an error on every second request.

[simianarmy]

Thanks a million, phoet - that was driving me craaazy. I tried OS X ports jruby, rvm install jruby, and jruby from source (latest), and got the same error each time. Your fix solved the issue for me (still seeing the broken pipe error, but it's not causing all my tests to fail!)

[phoet]

maybee you should try steam https://github.com/svenfuchs/steam

[simianarmy]

Thanks phoet, will do. I also ran into some issue with culerity running under the development environment during browser navigation calls ($browser.goto) but under culerity otherwise..made it impossible to do simple session based testing, so right now just working with selenium.