June 2018 - Pharo-dev - lists.pharo.org

Pharo Bootstrap

by Guido Chari

I followed the instructions for building the image in https://github.com/guillep/PharoBootstrap and I get: ...RETRY->BaselineOfPharoBootstrapProcess ...RETRY->BaselineOfPharoBootstrapProcess ...FAILED->BaselineOfPharoBootstrapProcessCould not resolve: BaselineOfPharoBootstrapProcess [BaselineOfPharoBootstrapProcess] in /Users/guidochari/Documents/Projects/Research/Nopsys/CogNOS/image/pharo-local/package-cache filetree:///Users/guidochari/Documents/Projects/Research/Nopsys/PharoBootstrap I then resort to just execute the command that travis executes ( ./scripts/install-packages.sh) and it works. But when I open the image I can not find PBBootstrapSpur3250, needed for running the bootstrapping. Best, Guido

June 25, 2018

Esteban's ChangeLog week of 18 June 2018

by estebanlm＠gmail.com

Hello! This is my weekly ChangeLog, from 18 June 2018 to 24 June 2018. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=18/6/2018&to=24/6/2018 ChangeLog ========= 21 June 2018: ------------- * I made a port of [OmniBase](https://github.com/estebanlm/OmniBase) for Pharo 6+ . While this is a discussed DB, some peple likes it so is good to have it available. 20 June 2018: ------------- * I'm working on getting Pharo and the PharoVM to work properly on win 64bit. While there is still work to do, I already get a compilation that works for most cases (including iceberg). Which is sad about this is I needed to split the build into parts and prepare the VM with dependencies upload to a repository. This works, and simplifies a lot the building process. Next days I will continue the remaining dependency: cairo. 19 June 2018: ------------- * again, I spent last two days on makign [this PR](https://github.com/pharo-project/pharo/pull/1546) to pass. The PR is about "[case: 22146](https://pharo.fogbugz.com/f/cases/22146) - update metacello to allow alternate filetree formats", and is important to allow baselines to use tonel format without changing all their baselines and without needing to create a special notation for tonel formats. This way, all baselines referred as "github://", etc. will be correctly interpreted as tonel or cypress format automatically. cheers! Esteban

June 25, 2018

Re: [Pharo-dev] http://ss3.gemstone.com/ down ?

by Gabriel Cotelli

Well it is something out of my control.. because it is in the dependency chain of SmalltalkCI. I will report an issue so it can be fixed. Thanks James. On Sun, Jun 24, 2018 at 12:48 PM James Foster <Smalltalk(a)jgfoster.net> wrote: > For several years now we have not had control over the gemstone.com domain. > Please try http://ss3.gemtalksystems.com/ instead. > > James Foster > > On Jun 24, 2018, at 10:26 AM, Gabriel Cotelli <g.cotelli(a)gmail.com> wrote: > > http://ss3.gemstone.com/ seems to be unavailble. So some builds are > failing due to > > Could not resolve: STON-Core [STON-Core-SvenVanCaekenberghe.87] in /home/travis/smalltalkCI-master/_builds/pharo-local/package-cache http://ss3.gemstone.com/ss/STON ERROR: 'GoferRepositoryError: Could not access http://ss3.gemstone.com/ss/STON: ZnHttpUnsuccessful: 500 Internal Server Error' > > > >

June 24, 2018

Re: [Pharo-dev] http://ss3.gemstone.com/ down ?

by James Foster

For several years now we have not had control over the gemstone.com <http://gemstone.com/> domain. Please try http://ss3.gemtalksystems.com/ <http://ss3.gemtalksystems.com/> instead. James Foster > On Jun 24, 2018, at 10:26 AM, Gabriel Cotelli <g.cotelli(a)gmail.com> wrote: > > http://ss3.gemstone.com/ <http://ss3.gemstone.com/> seems to be unavailble. So some builds are failing due to > Could not resolve: STON-Core [STON-Core-SvenVanCaekenberghe.87] in /home/travis/smalltalkCI-master/_builds/pharo-local/package-cache http://ss3.gemstone.com/ss/STON <http://ss3.gemstone.com/ss/STON> ERROR: 'GoferRepositoryError: Could not access http://ss3.gemstone.com/ss/STON <http://ss3.gemstone.com/ss/STON>: ZnHttpUnsuccessful: 500 Internal Server Error' >

June 24, 2018

Re: [Pharo-dev] http://ss3.gemstone.com/ down ?

by Sean P. DeNigris

gcotelli wrote > http://ss3.gemstone.com/ seems to be unavailble Confirmed: https://downforeveryoneorjustme.com/ss3.gemstone.com ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

June 24, 2018

http://ss3.gemstone.com/ down ?

by Gabriel Cotelli

http://ss3.gemstone.com/ seems to be unavailble. So some builds are failing due to Could not resolve: STON-Core [STON-Core-SvenVanCaekenberghe.87] in /home/travis/smalltalkCI-master/_builds/pharo-local/package-cache http://ss3.gemstone.com/ss/STON ERROR: 'GoferRepositoryError: Could not access http://ss3.gemstone.com/ss/STON: ZnHttpUnsuccessful: 500 Internal Server Error'

June 24, 2018

Re: [Pharo-dev] Launcher 1.2 External Processes Hang

by Sean P. DeNigris

Sean P. DeNigris wrote > I tried to launch an image with Launcher 1.2. "Determining image version" > appeared, but the image didn't not launch. Fixed with `ThisOSProcess initialize`. Not sure why that was needed, butâ¦ ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

June 24, 2018

Launcher 1.2 External Processes Hang

by Sean P. DeNigris

I tried to launch an image with Launcher 1.2. "Determining image version" appeared, but the image didn't not launch. I had launched this image previously before upgrading. OS X 10.13.4 As a sanity check, I tried to run a few OSProcess commands, which all hung as well:(PipeableOSProcess waitForCommand: 'ls') output. (PipeableOSProcess waitForCommand: 'sleep 5'). Anyone else seeing this? ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

June 24, 2018

Re: [Pharo-dev] Empirical Analysis of Programming Language Adoption

by askoh

In Smalltalk, you understand code by running it. Not just reading it. Set a breakpoint. When the debugger hits it, just step, enter, jump and see the code in live action. You almost never need to exit the debugger. Rewind as often as you like. You can even save the image with the debugger active. When you restart, you in the debugger where you left off. You can change code outside the debugger and come back to run the new code. Always remain in the debugger as much as possible. All the best, Aik-Siong Koh -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

June 23, 2018

Re: [Pharo-dev] strange debugging

by Marcus Denker

> On 22 Jun 2018, at 02:54, Ben Coman <btc(a)openinworld.com> wrote: > > >> On 15 Jun 2018, at 01:07, Ben Coman <btc(a)openinworld.com <mailto:btc@openinworld.com>> wrote: > >> > >> Not sure if this is intended behaviour... > >> > >> in a brand new build 71053, open a browser GTGenericStackDebuggerTest >> testBasic > >> > >> right-click and choose "Debug" > >> > >> the debugger opens about on the third statement. > >> Clicking <Restart> doesn't improve things, > >> and then clicking <Into> shows the stack on MetaLink>>uninstall. > >> > >> cheers -ben > > > > > On 15 Jun 2018, at 12:18, Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: > > > > Thanks, I made a note and will look (I hope next week) > > > > On 21 June 2018 at 22:24, Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: > Hello, > > The reason seems to be that the mechanism uses a âonceâ breakpoint which is for now implemented by > removing the breakpoint at runtime. This leads to the debugger getting text/bytecode offset wrong > as we install a different method. > > runTest: testSelector of: testClass > > | breakpoint | > breakpoint := Breakpoint new > node: (testClass lookupSelector: testSelector) ast; > once; > install. > [super runTest: testSelector of: testClass] ensure: [ breakpoint remove ] > > Thanks for the update. > > > I am thinking of implementing the once breakpoints using a condition instead (so that the byte code is unchanged). > The other nice effect is that one can more easily re-enable those breakpoints (like haltOnce). > > That sounds like a good idea. Will that change the semantics at all? In the first step noâ¦ it would work like haltOnce now. > IIRC, prior to metalinks the Halt-once was a global reset only, and post metalinks it was reset by a method save. > So will the condition-state be global or per method? > And then mild curiousity about the implementation - how would that state be stored? > Im the first step I guess in the breakpoint object. For haltOnce: it does not really use MetaLinks, just AST annotationsâ¦ I liked the simplicity and the fact that it would be âper statementâ and not global. But what is bad is that we lose the state at recompileâ¦ it would be nice to fix that. Marcus

June 22, 2018