03:25 <headius> Yeah I am in Minnesota in the US where we have -30C winters and 40C summers so we have to handle both

17:13 <headius> enebo: so that PR is green but rsim has not confirmed it and this issue has only been reported under an OSGi rig

17:13 <headius> it's safe to go forward with but I don't know for certain that it fixes his issue

19:28 <headius> I am bisecting this regression on master in registry.rb

19:31 <headius> wow compose key really screws up vbox

19:39 <headius> hmm unsurprising but not particularly helpful... seems like it regressed around the time we updated net-* libraries to use gems

19:52 <headius> looks like the only change in there was that it now requires resolv.rb so I think I can narrow this further

20:38 <headius> well this update seems to be the one that brought in the breaking changes... small changes to win32/registry.rb: 900c531bd9bc57fb012290b9775eec548cc384f2

20:39 <headius> I will play with those changes in a bit and see if I can get back to working (and figure out why these changes broke)

22:39 <headius> ok so not the greatest news

22:39 <headius> the basic problem is that win32/registry switched from using our win32 FFI bindings to using Fiddle, and our Fiddle is not working right mapping parameters to types during the call

22:41 <headius> so it is able to bind the functions now but does not know when registry.rb passes a Fixnum for a pointer that it should be treated as a pointer value

22:41 <headius> since FFI wants a Pointer instance

22:41 <headius> the big fix is fiddle

22:42 <headius> short term fix might be simply reverting registry.rb to back to using our FFI win32

22:53 <headius> in any case I'm not fixing it today and it only affects master on Windows... so we'll revisit this next week

22:53 <headius> enebo: I'm logging off for the weekend. That PR above could be merged any time, but maybe we wait a bit and see if rsim can respond. Other than that I think we're on track for an early week 9.3.7 release