> On 17 Aug 2019, at 12:50, Ben Coman <b...@openinworld.com> wrote: > > hi Stef, > I feel you missed my point. Probably I wasn't clear this has already been > tested with latest Pharo 8 launched by PharoLauncher. > The problem occurs with Pharo 7.0.3(64 bit) and with > Pharo8.0-SNAPSHOT-build.635(64 bit) > after Microsoft Windows Update 1903... > https://www.computerworld.com/article/3409621/microsoft-starts-windows-10s-1803-to-1903-forced-upgrade.html > > <https://www.computerworld.com/article/3409621/microsoft-starts-windows-10s-1803-to-1903-forced-upgrade.html> > > > If indeed 1903 is the cause, with this update now being *forced* down on > people, this will potentially soon impact more and more Windows users. > But my guess that 1903 is the culprit needs to be confirmed. > So I am requesting someone with access to multiple Windows machines directly > compare a 1903 machine with a pre-1903 machine.
indeed I misunderstood you :) > > cheers -ben > > On Sat, 17 Aug 2019 at 12:58, ducasse <steph...@netcourrier.com > <mailto:steph...@netcourrier.com>> wrote: > Hi ben > > in the pharo launcher if you click on P8.0 (development version) you get > access to all the builds. > > Stef > >> On 16 Aug 2019, at 16:02, Ben Coman <b...@openinworld.com >> <mailto:b...@openinworld.com>> wrote: >> >> IThis morning the May 2019 Windows Update "1903" forced itself onto my >> computer and now 64-bits Pharo seems to have a problem with >> git_remote_fetch() FFI callout. I no longer have a non-1903 machine to >> directly compare behaviour before "1903". Can someone familiar with this >> area with both "pre-1903" and "1903" machines triage whether "1903" is >> indeed the cause? >> >> A few other recent reports are noted here... >> https://github.com/pharo-project/pharo/issues/3418 >> <https://github.com/pharo-project/pharo/issues/3418> >> >> cheers -ben >
