18:11 <eebs> I'm seeing an issue were if I add a formatted logger where the output is a File object, the logs are not written to the file immediately. There is a several minute delay between the logs being generated (and displayed in stdout) and the logs being written to the file. I see that the logger uses a mutex to allow multiple threads to write to the log, could that be causing an issue? I am creating the bot/loggers like so: https://gist.github.com/anonymous/68d10f7b3e2

18:13 <leftylink> complete wild guess that I have no basis for believing is correct but gotta throw it out there anyway

18:13 <eebs> leftylink: those are the best! ;)

18:13 <leftylink> is this just normal behavior that writes to files are buffered? maybe should flush?

18:14 <leftylink> I give less probability to the mutex being a problem because logs to the console generaly seem snappy, see...

18:14 <eebs> leftylink: that was kinda my thought as well. I didn't see anything in cinch that really looked like it would cause this

18:15 <eebs> I'll see if I can find anything regarding file buffering

18:17 <eebs> Okay yup. If I call File.sync=true on my file objet it writes immediately

18:18 <leftylink> oooh

18:24 <eebs> So that at least achieves the behavior I wanted. What that really does is turns off ruby internal buffering. It looks like calling IO.fsync will flush the buffers on demand, but that would perhaps have to be called after each call to @output.puts <message>, and thus require a change in cinch

20:16 <dominikh> if Ruby wasn't insane, then it wouldn't apply buffering by default ;)

20:17 <dominikh> and yeah, I won't flush, so set sync=true :)

20:17 <eebs1> dominikh: sounds good, I figured you wouldn't want to make that a core change