shellac has quit [Quit: Computer has gone to sleep.]
drbobbeaty has joined #jruby
drbobbeaty has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
shellac has joined #jruby
drbobbeaty has joined #jruby
shellac has quit [Quit: Computer has gone to sleep.]
rdubya has quit [Ping timeout: 276 seconds]
rdubya has joined #jruby
shellac has joined #jruby
bbrowning is now known as bbrowning_away
claudiuinberlin has quit [Ping timeout: 252 seconds]
<enebo>
lopex: new theory on that windows issue
<enebo>
lopex: second time run it is trying to mv something into place and it fails because it thinks the mv operation cannot be performed. by third time whatever the second time did fixes it so that mv works.
<enebo>
lopex: it always works first time with nothing there because there it nothing there yet?
<lopex>
enebo: it appears so yea
<enebo>
lopex: I even see in RubyFile how rename could be doing this so I am trying to first add a hack to see if error goes away
<lopex>
enebo: you mean that fix with exists ?
<enebo>
lopex: it was a cross fs check but that did not seem like it could be the issue but I noticed it as a big change
<enebo>
it did not fix it though
<enebo>
I now think we are swallowing some random error in a way which we were not before
<enebo>
Or the new mechanism for copy using nio.2 just does not work on windows for some at of yet unknown reason
<enebo>
heh well we try to rename twice...that is odd
<enebo>
Files.move has no return on success...so we do it again
<enebo>
with renameTo
<enebo>
but it begs a question that I would expect to see renameTo fall on more than just windows
<enebo>
oh but on linux/macos we are copying frmo another FS 100% so we IOExcept at that point
xardion has quit [Remote host closed the connection]