- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Debugger opening on user halt and not Object>>halt

by Ben Coman

On Sat, 2 Feb 2019 at 08:35, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Ben Coman wrote > > The first was me. Not sure about the second. The latter two were someone > > else. > > I always thought that DNU should be on this list too. Am I the only one? > It seem to already do this? In Playground evaluating... 1 + 1. 2 unknown. 3 + 3 opens a debugger on the second line with "unknown" highlighted. See <debuggerCompleteToSender> at the top of Object>>doesNotUnderstand: Or do you mean something else? cheers -ben

Feb. 2, 2019

Spotter shortcut reset

by Ben Coman

I upgraded Pharo 7.0.1 to latest Pharo 8.0 branch. Now when I hit <Ctrl-Enter> I get a debugger... Instance of AnObsoleteGTSpotterGlobalShortcut class did not understand #openGlobalSpotter Although not a certified way to upgrade, its maybe useful. I've looked through settings and class-side methods for some way to reset this. Is there some class reset or initialization that can be run to clear this up? cheers -ben

Feb. 2, 2019

Re: [Pharo-dev] [Pharo-users] Class name with diacritic character and Pharo

by Sven Van Caekenberghe

That is also an already existing problem, it has to do with the decoding of environment variables. If I find the time, I will try to do a couple of tests this WE. > On 2 Feb 2019, at 09:19, Hilaire <hilaire(a)drgeo.eu> wrote: > > If understood correctly , BenoÃ®t can't event start P7 on Windows 10 > because of the accent character in his name. I guess it may affect a lot > of Windows users in this same situation. If understood correctly the > problem does not show up with P5 and the same Windows version. > > Hilaire > > -- > Dr. Geo > http://drgeo.eu > > >

Feb. 2, 2019

Re: [Pharo-dev] [Pharo-users] Class name with diacritic character and Pharo

by Hilaire

If understood correctly , BenoÃ®t can't event start P7 on Windows 10 because of the accent character in his name. I guess it may affect a lot of Windows users in this same situation. If understood correctly the problem does not show up with P5 and the same Windows version. Hilaire -- Dr. Geo http://drgeo.eu

Feb. 2, 2019

[Pharo 8.0] Build #50: 2385 Badly formatted character/charset support code

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

There is a new Pharo build available! The status of the build #50 was: FAILURE. The Pull Request #2386 was integrated: "2385 Badly formatted character/charset support code" Pull request url: https://github.com/pharo-project/pharo/pull/2386 Issue Url: https://pharo.fogbugz.com/f/cases/2385 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 2, 2019

Re: [Pharo-dev] Debugger opening on user halt and not Object>>halt

by Sean P. DeNigris

Ben Coman wrote > The first was me. Not sure about the second. The latter two were someone > else. I always thought that DNU should be on this list too. Am I the only one? ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Feb. 2, 2019

[Pharo 8.0] Build #49: 2395-Non-ASCII-class-and-author-names-break-SourceFileArraygetPreambleFromat

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

There is a new Pharo build available! The status of the build #49 was: SUCCESS. The Pull Request #2433 was integrated: "2395-Non-ASCII-class-and-author-names-break-SourceFileArraygetPreambleFromat" Pull request url: https://github.com/pharo-project/pharo/pull/2433 Issue Url: https://pharo.fogbugz.com/f/cases/2395 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 1, 2019

[Pharo 8.0] Build #48: 2393 integrate file attributes plugin

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

There is a new Pharo build available! The status of the build #48 was: FAILURE. The Pull Request #2431 was integrated: "2393 integrate file attributes plugin" Pull request url: https://github.com/pharo-project/pharo/pull/2431 Issue Url: https://pharo.fogbugz.com/f/cases/21368 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 1, 2019

Re: [Pharo-dev] Contribute to pharo8.0 ?

by ducasse

Cool! > On 1 Feb 2019, at 16:54, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > OK, I think I did it ;-) > > https://github.com/pharo-project/pharo/pull/2433 > >> On 1 Feb 2019, at 16:35, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >> You need to select pharo-project remote (because issues are listed there). >> >> Esteban >> >>> On 1 Feb 2019, at 16:04, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>> >>> I am still stuck. >>> >>> I did >>> >>> $ curl -L get.pharo.org/64/80+vm | bash >>> >>> Repaired by specifying my local clone >>> >>> Repaired by fetching >>> >>> Not in detached state, cannot make branch from issue, screenshot: >>> >>> <Screenshot 2019-02-01 at 16.01.17.png> >>> >>> What am I doing wrong ? >>> >>> How do other people do it ? >>> >>>> On 31 Jan 2019, at 08:18, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: >>>> >>>> It is working now again as expected. >>>> >>>> The only difference is that you need to use "Github-Create new branch for issue..." instead of "Pharo-Create new branch for issue..." for the new issues reported on GitHub. >>>> >>>> -- Pavel >>>> >>>> st 30. 1. 2019 v 9:42 odesÃlatel Guillermo Polito <guillermopolito(a)gmail.com> napsal: >>>> Hi, >>>> >>>> there is an issue for this problem, >>>> >>>> https://github.com/pharo-project/pharo/issues/2379 >>>> >>>> We have identified the cause, I'll propose a fix now >>>> >>>> On Wed, Jan 30, 2019 at 8:44 AM ducasse <stepharo(a)netcourrier.com> wrote: >>>>> >>>>> There is currently a bug eating one character of the commit hash. So >>>>> Iceberg does not find the hash and thinks we need a fetch. So currently >>>>> we need to checkout Pharo8.0 in order to be in a good state :( >>>> >>>> OOPs is there a bug entry? >>>>> >>>>>> I also don't understand how to make an issue branch for >>>>>> >>>>>> https://github.com/pharo-project/pharo/issues/2395 >>>>>> >>>>>> Is it Iceberg > Pharo > Create new branch for issue or Iceberg > Github > Create new branch for issue ? >>>>> >>>>> Just create a branch and choose the option to create a branch from a >>>>> Github option. >>>>> >>>>> The other one was for Manuscript and is now useless for Pharo 8. I >>>>> opened an issue in Iceberg to remove it but I did not got the time to >>>>> contribute the change. >>>>> >>>>>> What is the difference ? >>>>>> What about the Remote ? >>>>>> Can I work with only an issue on GitHub ? >>>>>> >>>>> >>>>> Yes! >>>>> >>>>> What I am doing currently: >>>>> >>>>> - Open an issue XX >>>>> - Sync my fork Pharo8.0 branch via command line (This is optional and >>>>> can also be done in Pharo. I just do it via command line because I like >>>>> it better that way) >>>> >>>> how do you do it? Pull? >>>> >>>>> - Download a Pharo 8 image >>>>> - Checkout the Pharo8.0 branch to get in a clean state because of the >>>>> hash eating bug I mentioned earlier >>>>> - Create a new branch from a github issue of the pharo remote >>>>> - Do the changes and commit. I add `Fixes #XX` in the commit message to >>>>> close automatically the issue when the PR is merged. >>>>> - Push to my remote >>>>> - Open a PR against Pharo8.0 through Iceberg > GitHub > Create new pull >>>>> request >>>> >>>> and checkout the pharo 8 branch to fix the next one. >>>>> >>>>>> Is the documentation >>>>>> >>>>>> https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo >>>>>> >>>>>> really up to date ? >>>>>> >>>>> >>>>> No >>>>> >>>>> We should correct the hash eating bug before updating it I think. >>>>> >>>>>> Sven >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Cyril Ferlicot >>>>> https://ferlicot.fr >>>>> >>>> >>>> >>>> >>>> >>>> >>>> -- >>>> >>>> Guille Polito >>>> Research Engineer >>>> >>>> Centre de Recherche en Informatique, Signal et Automatique de Lille >>>> CRIStAL - UMR 9189 >>>> French National Center for Scientific Research - http://www.cnrs.fr >>>> >>>> Web: http://guillep.github.io >>>> Phone: +33 06 52 70 66 13 >>> >> > >

Feb. 1, 2019

Re: [Pharo-dev] Pharo Downloads are sluggish

by Esteban Maringolo

I'm bumping this, just in case it helps somebody. I tried to download the latest Pharo Launcher 1.6, and I had the same issues as the ones stated in this thread (slow download, timeouts, etc.). But I downloaded it with a download manager [1], and by means of ten simultaneous connections the download speed was fast enough as to download the 50 MB in a minute or so. So I don't know if there is a restriction from the file server or somewhere in the way out, but you can work around it by means of a Download Manager. Regards! [1] FreeDownloadManager.org Esteban A. Maringolo El miÃ©., 3 oct. 2018 a las 5:04, Marcus Denker (<marcus.denker(a)inria.fr>) escribiÃ³: > Ok, so the upgrade of the server contract did not help. > > There is a CDN included, I will try to enable that next (but CDNs cache by > name, so we need to make sure we invalidate the cacheâ¦) > > I will do a calculation what S3 would cost, too. > > Marcus > > On 3 Oct 2018, at 00:59, Esteban Maringolo <emaringolo(a)gmail.com> wrote: > > I'm reviving this because I can't finish the download of an image using > the latest Pharo launcher. > > I'm timeout errors when attempting to download it. Tried 5 times at > different intervals. > > > <image.png> > > Any idea of what could be happening? > > Esteban A. Maringolo > > > El mar., 18 sept. 2018 a las 21:03, Esteban Maringolo (< > emaringolo(a)gmail.com>) escribiÃ³: > >> Is there a reason why the latest version of the builds linked from the >> website are not hosted in some CDN, Amazon S3 or similar? >> >> Maybe in Europe the speed is fast, but where I am (Argentina) it is >> really slow, the screenshot shows 3.5KB/s, it averages 10KB/s, with peaks >> of 40KB/s. >> >> This is an pitiful boarding experience, that will make many cancel it >> even before getting to open the downloaded launcher. >> >> <node-pharo.png> >> >> The screenshot shows that is not a problem with my home connection, which >> isn't the fastest but is "normal" for my use cases. >> >> Regards, >> >> Esteban A. Maringolo >> >> ps: When I finished writing this email, this was the progress... >> <image.png> >> > >

Feb. 1, 2019