Hi I opened an issue: https://github.com/pharo-project/pharo/issues/4437
I believe this should be treated as critical given that we cannot load code in Pharo 7 (or 8) which makes it almost useless for users. Cheers, Doru > On Aug 27, 2019, at 10:54 AM, Tudor Girba <tu...@tudorgirba.com> wrote: > > Hi, > > We just encountered this on two different machines. We got this after the > update to Windows 1903. For us it’s a critical issue at this point. What can > we do to help with this? > > Cheers, > Doru > > > >> On Aug 17, 2019, at 12:50 PM, 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 >> >> >> 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. >> >> cheers -ben >> >> On Sat, 17 Aug 2019 at 12:58, ducasse <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> 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 >>> >>> cheers -ben >> > > -- > feenk.com > > "Not knowing how to do something is not an argument for how it cannot be > done." > -- feenk.com “Live like you mean it."
