October 2017 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Reproducible VM Crash using UFFI

by HernÃ¡n Morales Durand

I tried, now I get an exception "Use ExternalAddress instead!" I guess the message means Use ExternalAddres in the "out" parameter. But replacing byte with ExternalAddress also crashes the VM (crash.dmp attached). 2017-10-05 10:03 GMT-03:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > >> On 5 Oct 2017, at 14:55, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: >> >> Forgot to comment that Nacl worked in Pharo 5. > > yes but that was with NB and there are some minimum differences. > I do not have the library and I lack the time to try more, but seems to me that here: > > apiCryptoHashSha512Output: outByteArray input: inByteArray inputLength: inByteArrayLength > > ^ self > ffiCall: #(long crypto_hash_sha512_ref (byte * outByteArray, byte * inByteArray, ulonglong * inByteArrayLength)) > module: 'libsodiumâ. > > > instead "byte * outByteArrayâ, you want "byte **outByteArrayâ > > can you try? > > Esteban > > > >> >> Cheers, >> >> HernÃ¡n >> >> 2017-10-05 3:23 GMT-03:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >>> H Hernani, >>> >>> Most probably is a problem in the library and not UFFI, but I could not know without a crash report. >>> >>> Esteban >>> >>>> On 5 Oct 2017, at 06:00, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: >>>> >>>> Hi, >>>> >>>> I ported Nacl (a libsodium wrapper) from the old FFI apicall: format >>>> to use the UFFI ffiCall:, but there should be something terribly wrong >>>> because is crashing the VM, in both Windows 8.1 and Linux. >>>> >>>> How to reproduce in Pharo 6.1 >>>> >>>> Metacello new >>>> smalltalkhubUser: 'tonyg' project: 'Crypto-Nacl'; >>>> configuration: 'Nacl'; >>>> version: #development; >>>> load. >>>> >>>> (Nacl hashString: 'The quick brown fox jumps over the lazy dog') hex >>>> >>>> This one does deserve a bug entry? >>>> >>>> Cheers, >>>> >>>> HernÃ¡n >>>> >>> >>> >> > >

Oct. 5, 2017

[Pharo 7.0-dev] Build #168: 20464 Cleanup SystemVersion and SystemVersionTest (but stay compatible)

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #168 was: SUCCESS. The Pull Request #309 was integrated: "20464 Cleanup SystemVersion and SystemVersionTest (but stay compatible)" Pull request url: https://github.com/pharo-project/pharo/pull/309 Issue Url: https://pharo.fogbugz.com/f/cases/20464 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 5, 2017

Re: [Pharo-dev] Reproducible VM Crash using UFFI

by Esteban Lorenzano

> On 5 Oct 2017, at 14:55, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > > Forgot to comment that Nacl worked in Pharo 5. yes but that was with NB and there are some minimum differences. I do not have the library and I lack the time to try more, but seems to me that here: apiCryptoHashSha512Output: outByteArray input: inByteArray inputLength: inByteArrayLength ^ self ffiCall: #(long crypto_hash_sha512_ref (byte * outByteArray, byte * inByteArray, ulonglong * inByteArrayLength)) module: 'libsodiumâ. instead "byte * outByteArrayâ, you want "byte **outByteArrayâ can you try? Esteban > > Cheers, > > HernÃ¡n > > 2017-10-05 3:23 GMT-03:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >> H Hernani, >> >> Most probably is a problem in the library and not UFFI, but I could not know without a crash report. >> >> Esteban >> >>> On 5 Oct 2017, at 06:00, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: >>> >>> Hi, >>> >>> I ported Nacl (a libsodium wrapper) from the old FFI apicall: format >>> to use the UFFI ffiCall:, but there should be something terribly wrong >>> because is crashing the VM, in both Windows 8.1 and Linux. >>> >>> How to reproduce in Pharo 6.1 >>> >>> Metacello new >>> smalltalkhubUser: 'tonyg' project: 'Crypto-Nacl'; >>> configuration: 'Nacl'; >>> version: #development; >>> load. >>> >>> (Nacl hashString: 'The quick brown fox jumps over the lazy dog') hex >>> >>> This one does deserve a bug entry? >>> >>> Cheers, >>> >>> HernÃ¡n >>> >> >> >

Oct. 5, 2017

Re: [Pharo-dev] Reproducible VM Crash using UFFI

by HernÃ¡n Morales Durand

Forgot to comment that Nacl worked in Pharo 5. Cheers, HernÃ¡n 2017-10-05 3:23 GMT-03:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > H Hernani, > > Most probably is a problem in the library and not UFFI, but I could not know without a crash report. > > Esteban > >> On 5 Oct 2017, at 06:00, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: >> >> Hi, >> >> I ported Nacl (a libsodium wrapper) from the old FFI apicall: format >> to use the UFFI ffiCall:, but there should be something terribly wrong >> because is crashing the VM, in both Windows 8.1 and Linux. >> >> How to reproduce in Pharo 6.1 >> >> Metacello new >> smalltalkhubUser: 'tonyg' project: 'Crypto-Nacl'; >> configuration: 'Nacl'; >> version: #development; >> load. >> >> (Nacl hashString: 'The quick brown fox jumps over the lazy dog') hex >> >> This one does deserve a bug entry? >> >> Cheers, >> >> HernÃ¡n >> > >

Oct. 5, 2017

Re: [Pharo-dev] Spec enhancements

by HernÃ¡n Morales Durand

Hi Stephane, You may check the SpecUIAddOns Metacello new smalltalkhubUser: 'hernan' project: 'SpecUIAddOns'; configuration: 'SpecUIAddOns'; version: #bleedingEdge; load: 'Core'. Most widgets has examples in class side. Cheers, HernÃ¡n 2017-10-05 4:55 GMT-03:00 Stephane Ducasse <stepharo.self(a)gmail.com>: > Hi rob > > I like you extensions to label and text. > I harvested them with the tests and I will slowly generalise that > to other widgets. > > I published my current code experiments to > > MCSmalltalkhubRepository > owner: 'Pharo' > project: 'Spec' > user: '' > password: '' > > > Stef >

Oct. 5, 2017

Re: [Pharo-dev] State of files.pharo.org

by Christophe Demarey

> Le 5 oct. 2017 Ã 13:50, Marcus Denker <marcus.denker(a)inria.fr> a Ã©crit : > > > >> On 5 Oct 2017, at 13:35, Norbert Hartl <norbert(a)hartl.name <mailto:norbert@hartl.name>> wrote: >> >> I'm trying to download images from files.pharo.org <http://files.pharo.org/>. Either it takes a lot of time or get something like >> >> Downloading the latest 70 Image: >> http://files.pharo.org/get-files/70/pharo.zip <http://files.pharo.org/get-files/70/pharo.zip> >> error: invalid compressed data to inflate image.7vLfZK/Pharo7.0-32bit-6bff78c.image >> image.7vLfZK/Pharo7.0-32bit-6bff78c.sources bad CRC 724d27ab (should be f4d1baa8) >> >> That is really sad. What use is this wonderful environment if nobody can download it? We need to sort that out. >> >> So is this hosted in Inria data center? >> > > Yes, and the admins can not find any problem. They closed the ticket I opened, but there is a new > ticket open since last weekâ¦ not a good situation. Yes, it is hosted at Inria datacenter. They are investigating the problem. I have an audio conf with them tomorrow on this pb. I will give a feedback after this meeting. Christophe

Oct. 5, 2017

Re: [Pharo-dev] State of files.pharo.org

by Marcus Denker

> On 5 Oct 2017, at 13:35, Norbert Hartl <norbert(a)hartl.name> wrote: > > I'm trying to download images from files.pharo.org <http://files.pharo.org/>. Either it takes a lot of time or get something like > > Downloading the latest 70 Image: > http://files.pharo.org/get-files/70/pharo.zip <http://files.pharo.org/get-files/70/pharo.zip> > error: invalid compressed data to inflate image.7vLfZK/Pharo7.0-32bit-6bff78c.image > image.7vLfZK/Pharo7.0-32bit-6bff78c.sources bad CRC 724d27ab (should be f4d1baa8) > > That is really sad. What use is this wonderful environment if nobody can download it? We need to sort that out. > > So is this hosted in Inria data center? > Yes, and the admins can not find any problem. They closed the ticket I opened, but there is a new ticket open since last weekâ¦ not a good situation. Marcus

Oct. 5, 2017

Re: [Pharo-dev] State of files.pharo.org

by serge.stinckwich＠gmail.com

Maybe this is a transient problem, because we had some problems this morning to dl files from files.pharo.org from Cameroun. EnvoyÃ© de mon iPhone > Le 5 oct. 2017 Ã 12:35, Norbert Hartl <norbert(a)hartl.name> a Ã©crit : > > I'm trying to download images from files.pharo.org. Either it takes a lot of time or get something like > > Downloading the latest 70 Image: > http://files.pharo.org/get-files/70/pharo.zip > error: invalid compressed data to inflate image.7vLfZK/Pharo7.0-32bit-6bff78c.image > image.7vLfZK/Pharo7.0-32bit-6bff78c.sources bad CRC 724d27ab (should be f4d1baa8) > > That is really sad. What use is this wonderful environment if nobody can download it? We need to sort that out. > > So is this hosted in Inria data center? > > Norbert >

Oct. 5, 2017

State of files.pharo.org

by Norbert Hartl

I'm trying to download images from files.pharo.org <http://files.pharo.org/>. Either it takes a lot of time or get something like Downloading the latest 70 Image: http://files.pharo.org/get-files/70/pharo.zip error: invalid compressed data to inflate image.7vLfZK/Pharo7.0-32bit-6bff78c.image image.7vLfZK/Pharo7.0-32bit-6bff78c.sources bad CRC 724d27ab (should be f4d1baa8) That is really sad. What use is this wonderful environment if nobody can download it? We need to sort that out. So is this hosted in Inria data center? Norbert

Oct. 5, 2017

removing deprecation of #pin methods

by Esteban Lorenzano

Hi, I will remove deprecation of pin methods. Why? - because that change is causing a lot of incompatibilities with running 6.1 code. - because that change is causing some errors on current Pharo 7.0 development. So instead deprecate, it will be âmarked for deprecationâ, then deprecation will happen in Pharo 8.0. And just as a side note: next time I say âis is not a good ideaâ, believe me, it is not. Esteban

Oct. 5, 2017