- Pharo-dev - lists.pharo.org

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

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

by HernÃ¡n Morales Durand

Here it is. Let me know if you want to see the Linux crash report. 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] Non-deterministic ombu errors

by Stephane Ducasse

Tx martin I added https://pharo.fogbugz.com/f/cases/20492/Update-EPICEA Do you have a bug entry for the 7.0 integration or should I create one? Stef On Tue, Oct 3, 2017 at 7:58 PM, Martin Dias <tinchodias(a)gmail.com> wrote: > I've put ConfigurationOfEpicea 8.2.4 in p6 inbox. > MartÃn > > On Tue, Oct 3, 2017 at 1:40 PM, Martin Dias <tinchodias(a)gmail.com> wrote: >> >> Hi >> >> On Tue, Oct 3, 2017 at 11:40 AM, Gabriel Cotelli <g.cotelli(a)gmail.com> >> wrote: >>> >>> Yes, please backport the changes to Pharo 6.1 because the travis builds >>> are failing a lot with this kind of errors when you have a project with >>> non-ASCII characters. >> >> >> Ok >> >>> >>> >>> Probably it makes no sense to enable Epicea in the images used by >>> SmalltalkCI. Is there some way to disable it? >> >> >> Sure, you can evaluate: EpMonitor reset >> >> >> >>> >>> >>> >>> On Mon, Oct 2, 2017 at 10:18 AM, Stephane Ducasse >>> <stepharo.self(a)gmail.com> wrote: >>>> >>>> Martin >>>> >>>> if you publish a fix for 6.1 we will port it back because this is >>>> important. >>>> >>>> Stef >>>> >>>> On Fri, Sep 29, 2017 at 3:55 PM, Martin Dias <tinchodias(a)gmail.com> >>>> wrote: >>>> > Now I do not know the best way for you to get the new fixed version. >>>> > It's >>>> > too late to include it in P6.1, I guess, so... either add epicea into >>>> > metacello configuration or wait until P7. >>>> > >>>> > >>>> > >>>> > On Fri, Sep 29, 2017 at 5:34 AM, Jan BlizniÄenko >>>> > <bliznjan(a)fit.cvut.cz> >>>> > wrote: >>>> >> >>>> >> I'm glad it has known reason then, thank you for looking into it, all >>>> >> I >>>> >> was >>>> >> able to find out was that it relates to non-ascii characters and that >>>> >> build >>>> >> on our production server fails because of that :) >>>> >> >>>> >> Jan >>>> >> >>>> >> >>>> >> tinchodias wrote >>>> >> > On Sun, Sep 24, 2017 at 5:49 AM, Sven Van Caekenberghe < >>>> >> >>>> >> > sven@ >>>> >> >>>> >> > > wrote: >>>> >> > >>>> >> >> >>>> >> >> > On 23 Sep 2017, at 22:42, Jan BlizniÄenko < >>>> >> >>>> >> > bliznjan@.cvut >>>> >> >>>> >> > > wrote: >>>> >> >> > >>>> >> >> > Hello >>>> >> >> > >>>> >> >> > I am having very similar errors from time to time when manually >>>> >> >> > loading >>>> >> >> code >>>> >> >> > into Pharo from filetree (gitfiletree), but only in one of my >>>> >> >> > projects >>>> >> >> which >>>> >> >> > contains non-ASCII characters like ÄÅ¡ÄÅÅ¾Ã½Ã¡ÃÃ©Å¯ÃºÅ¥Ä. For the very >>>> >> >> > same >>>> >> >> reason >>>> >> >> > (not able to find why sometimes the error is there and sometimes >>>> >> >> > is >>>> >> >> not), I >>>> >> >> > did not report it yet, but it is quite annoying. Retrying >>>> >> >> > loading the >>>> >> >> > package helps every time. >>>> >> >> >>>> >> >> I think was reported before. I believe Ombu somewhere takes an >>>> >> >> arbitrary >>>> >> >> chunk of bytes out of an UTF-8 encoded file (like the last 100 of >>>> >> >> something >>>> >> >> like that) and then starts reading that. With UTF-8, a variable >>>> >> >> length >>>> >> >> encoding, that can be dangerous because you could end up in the >>>> >> >> middle >>>> >> >> of >>>> >> >> a >>>> >> >> character, not between encoded character boundaries. This would >>>> >> >> also >>>> >> >> explain the randomness, as it is highly dependent on the contents. >>>> >> >> >>>> >> >> ZnUTF8Encoder>>#backOnStream: can be used to make sure you are >>>> >> >> really >>>> >> >> at >>>> >> >> the start of an encoded character. >>>> >> >> >>>> >> > >>>> >> > >>>> >> > Hello >>>> >> > >>>> >> > This issue was reported as: >>>> >> > >>>> >> > >>>> >> > >>>> >> > https://pharo.fogbugz.com/f/cases/20112/Epicea-can-fail-while-reading-non-a… >>>> >> > >>>> >> > My apologies for the bug... I introduced that code as an i/o >>>> >> > optimization >>>> >> > but wasn't properly tested. >>>> >> > >>>> >> > Thnks Sven, but I finally used stream's #basicNext (as Henrik >>>> >> > suggested >>>> >> > in >>>> >> > fogbugz) which skips forward. >>>> >> > >>>> >> > >>>> >> > Martin >>>> >> >>>> >> >>>> >> >>>> >> >>>> >> >>>> >> -- >>>> >> Sent from: >>>> >> http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >>>> >> >>>> > >>>> >>> >> >

Oct. 5, 2017

Call for spec user

by Stephane Ducasse

Hi I did some changes and I would like to know if you could load the following issues and report potential problems. https://pharo.fogbugz.com/f/cases/20490/NewValueHolder-substituable-for-Val… Stef

Oct. 5, 2017

Re: [Pharo-dev] pharo --help returning non-zero exit status

by Esteban Lorenzano

> On 5 Oct 2017, at 10:51, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > Sure. > It probably skipped Esteban view. I talked yesterday with Ben. As long as is backward compatible (and should be), Iâm ok. Esteban > > > On Tue, Oct 3, 2017 at 9:37 PM, Nicolas Cellier > <nicolas.cellier.aka.nice(a)gmail.com> wrote: >> >> Having the discussions scattered in Pharo-dev vm-dev github may help >> extending the indecision phase... >> >> There has been another important thread in vm-dev (Validation builds >> failing) >> http://lists.squeakfoundation.org/pipermail/vm-dev/2017-June/025417.html >> >> The conclusion was that we ask for some Pharo authority to approve the >> change >> We thus asked for Esteban's blessing, but unfortunately it seems that you >> have assigned much more work to Esteban without taking the precaution to >> clone him first... IMO you need about 4 or 5 Esteban. >> >> If Pharo is OK, then we can just accept the PR and clean a bit the list of >> stale PR >> >> 2017-10-02 15:21 GMT+02:00 Stephane Ducasse <stepharo.self(a)gmail.com>: >>> >>> Esteban, Eliot, Clement was is the process to get this fix in the VM? >>> >>> On Sun, Oct 1, 2017 at 9:05 AM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >>>> Ah, perfect. Thanks! >>>> >>>> peter >>>> >>>> On Sun, Oct 1, 2017 at 8:41 AM, K K Subbu <kksubbu.ml(a)gmail.com> wrote: >>>>> >>>>> On Sunday 01 October 2017 11:27 AM, Peter UhnÃ¡k wrote: >>>>>> >>>>>> Hi, >>>>>> >>>>>> why does executing `pharo --help` return exit status 1? The operation >>>>>> succeeded, so I don't see a reason for a failure return state. >>>>> >>>>> >>>>> This is a bug. See the thread at >>>>> >>>>> >>>>> >>>>> >>>>> http://forum.world.st/Re-Pharo-dev-pharo-help-returns-exit-code-1-on-ubuntu… >>>>> >>>>> The proposed fix is pending review at: >>>>> >>>>> https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/136 >>>>> >>>>> Regards .. Subbu >>>>> >>>>> >>>> >>> >> >

Oct. 5, 2017