February 2019 - Pharo-dev - lists.pharo.org

Startup Metacello Error
by Sean P. DeNigris Feb. 26, 2019

Feb. 26, 2019

While loading a project from a class-side #startUp: method, I'm getting a DNU #ifTrue:ifFalse which seemed to come from somewhere deep inside Metacello [1]. On the Metacello ML, Dale suggested that the startup mechanism might be the cause: > MetacelloSkipDirtyPackageLoad is a subclass of Notification, so if some > piece of code is catching Notification or above and doing a simple resume, > then you've found your culprit ... sounds like something startup code > might do when the system isn't able to handle GUI interaction ... but it's > a pretty harsh solution ... This same code was not throwing an error on P6.1. Has something changed re startup in P7 that could account for this error? Thanks! [1] The top of the call chain is: DoItIn: arg1 ^ (MetacelloSkipDirtyPackageLoad signal: self) ifTrue: [ | tmp2 | tmp2 := Transcript. tmp2 cr; show: 'Skipping load of modified package: ' , self file. arg1 home return: self ] ifFalse: [ | tmp4 | tmp4 := Transcript. tmp4 cr; ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

1 1

Apparently Zodiac plugin can crash VM on Linux
by Max Leske Feb. 26, 2019

Feb. 26, 2019

Hi, I'm writing on behalf of Martin (eMBee) who's experiencing crashes when using SSL. You can find a VM crash stack trace here: http://ws.stfx.eu/AKVNLUPMPGLG. He says he hasn't updated openssl since December 15th but that the crashes started to happen only recently (within the last couple of days). I asked him to try HTTP only connections and those work. The VM crashes immediately when using SSL. To me it looks like the cuplrit is the Zodiac plugin, or at least the library it works with. His system: linux, fedora 29, and from the system reporter i get: Pharo/vms/70-x64/lib/pharo/5.0-201806281256/pharo CoInterpreter VMMaker.oscog-eem.2401 uuid: 29232e0e-c9e3-41d8-ae75-519db862e02c Jun 28 2018 StackToRegisterMappingCogit VMMaker.oscog-eem.2401 uuid: 29232e0e-c9e3-41d8-ae75-519db862e02c Jun 28 2018 VM: 201806281256 https://github.com/OpenSmalltalk/opensmalltalk-vm.git Date: Thu Jun 28 14:56:30 2018 CommitHash: a8a1dc1 Plugins: 201806281256 https://github.com/OpenSmalltalk/opensmalltalk-vm.git cheers, Max

2 4

[Pharo 8.0] Build #107: 2725-When-doing-a-FileOut-propose-to-open-the-folder-containing-the-fileout
by ci-pharo-ci-jenkins2＠inria.fr Feb. 25, 2019

Feb. 25, 2019

There is a new Pharo build available! The status of the build #107 was: FAILURE. The Pull Request #2726 was integrated: "2725-When-doing-a-FileOut-propose-to-open-the-folder-containing-the-fileout" Pull request url: https://github.com/pharo-project/pharo/pull/2726 Issue Url: https://pharo.fogbugz.com/f/cases/2725 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #106: 2718-Rubric-should-not-depend-on-TextEditor
by ci-pharo-ci-jenkins2＠inria.fr Feb. 25, 2019

Feb. 25, 2019

There is a new Pharo build available! The status of the build #106 was: SUCCESS. The Pull Request #2719 was integrated: "2718-Rubric-should-not-depend-on-TextEditor" Pull request url: https://github.com/pharo-project/pharo/pull/2719 Issue Url: https://pharo.fogbugz.com/f/cases/2718 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #149: 2699 - backport pharo-vcs/tonel bug fix
by ci-pharo-ci-jenkins2＠inria.fr Feb. 25, 2019

Feb. 25, 2019

There is a new Pharo build available! The status of the build #149 was: SUCCESS. The Pull Request #2700 was integrated: "2699 - backport pharo-vcs/tonel bug fix" Pull request url: https://github.com/pharo-project/pharo/pull/2700 Issue Url: https://pharo.fogbugz.com/f/cases/Pharo7.0 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Esteban's ChangeLog week of 18 February 2019
by estebanlm＠gmail.com Feb. 25, 2019

Feb. 25, 2019

Hello! This is my weekly ChangeLog, from 18 February 2019 to 24 February 2019. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=18/2/2019&to=24/2/2019 ChangeLog ========= 19 February 2019: ----------------- * Small-fix-a-day: [critiques icons are not managed correctly](https://github.com/pharo-project/pharo/pull/2655) cheers! Esteban

1 0

Re: [Pharo-dev] Proposal to remove [Stream|Collection]>>#write:
by Sven Van Caekenberghe Feb. 25, 2019

Feb. 25, 2019

<intellectual response> Many system classes contain lots of methods that are confusing, duplicates of similar functionality, bogus, old, unused, untested and undocumented . This makes the system more complex, especially for newcomers, but also for everyone else trying to make changes. This is often technical debt, cleanup that has been postponed. It is important that knowledgeable developers try to clean up by simplifying things. If not, the situation will never improve. Of course we have to be careful, in this particular case I was. We have done many hundreds of these removals in the past years, with very little problems. We have also done way more dangerous things, like change signatures and semantics of existing methods. In my opinion we can safely go ahead and remove this. A couple of others concurred. If someone wants to go through the trouble to do this with deprecation and a rewrite rule, fine. <emotional response> Sure, the responses "Trying to be *somewhat* compatible and verifying (even quickly) that it's not breaking a gazillion things is the very least someone can do... Backward compatibility is NOT a sin! ;):" and "Check the selectors used in the latest packages on squeaksource, ss3, smalltalkhub and decide." are pure technical, intellectual arguments and not passive-aggressive criticism. Right. > On 22 Feb 2019, at 19:54, Benoit St-Jean via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > > > From: Benoit St-Jean <bstjean(a)yahoo.com> > Subject: Re: [Pharo-dev] Proposal to remove [Stream|Collection]>>#write: > Date: 22 February 2019 at 19:54:55 GMT+1 > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > > > Trying to be *somewhat* compatible and verifying (even quickly) that it's not breaking a gazillion things is the very least someone can do... Backward compatibility is NOT a sin! ;) > > On 2019-02-22 13:45, Sven Van Caekenberghe wrote: >> >>> On 22 Feb 2019, at 19:39, Stephan Eggermont <stephan(a)stack.nl> wrote: >>> >>> Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>> . >>>> So I propose to remove [Stream|Collection]>>#write: >>>> >>>> What say thou ? >>> Check the selectors used in the latest packages on squeaksource, ss3, >>> smalltalkhub and decide. >>> >>> Stephan >> You forgot GitHub and all private company repositories in the world. >> >> > -- > ----------------- > BenoÃ®t St-Jean > Yahoo! Messenger: bstjean > Twitter: @BenLeChialeux > Pinterest: benoitstjean > Instagram: Chef_Benito > IRC: lamneth > Blogue: endormitoire.wordpress.com > "A standpoint is an intellectual horizon of radius zero". (A. Einstein) > > > >

3 2

bootstrap desync information?
by ducasse Feb. 24, 2019

Feb. 24, 2019

Hi guys Ideally I would like to add a simple and little package with DisplayableObject because I do not want to put it in the System-Model package. I was wondering what is the impact on the bootstrap and I think that the impact is null since BaselineOfBootstrap does not contain System-Model but only UIManager. Now I found in the rule checker that System-Model is listed there and I found that it could be a desync between the information. What do you think? Now I have the impression that for now I could try to keep DisplayableObject with Model in System-Model and see how it goes. Because the decomposition between the different baseline is still something that need some iterations. Stef bootstrapPackages ^ #( #'AST-Core' #'Announcements-Core' #CodeExport #CodeImport #CodeImportCommandLineHandlers #Collections #Compression #'FileSystem-Core' #'FileSystem-Disk' #Files #Jobs #Kernel #Monticello #'Multilingual-Encodings' #'Multilingual-Languages' #'Multilingual-TextConversion' #'Network-UUID' #'OpalCompiler-Core' #'Random-Core' #'RPackage-Core' #'Ring-Deprecated-Core-Containers' #'Ring-Deprecated-Core-Kernel' #'Ring-Deprecated-Monticello' #'Ring-Deprecated-ChunkImporter' #'Slot-Core' #'System-Announcements' #'System-BasicCommandLineHandler' #'System-Changes' #'System-CommandLine' #'System-CommandLineHandler' #'System-Finalization' #'System-Hashing' #'System-Localization' #'System-Model' #'System-Platforms' #'System-SessionManager' #'System-Sources' #'System-Support' #Traits #'Transcript-Core' #UIManager #'Collections-Abstract' #'Collections-Arithmetic' #'Collections-Native' #'Collections-Sequenceable' #'Collections-Stack' #'Collections-Streams' #'Collections-Strings' #'Collections-Support' #'Collections-Unordered' #'Collections-Weak' #'Zinc-Character-Encoding-Core' #'Zinc-Resource-Meta-Core' #'PharoBootstrap-Initialization' #'Transcript-NonInteractive' ) Stef

1 1

[Pharo 8.0] Build #105: 2712-Retrying
by ci-pharo-ci-jenkins2＠inria.fr Feb. 24, 2019

Feb. 24, 2019

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

1 0

[Pharo 8.0] Build #104: 2659-Update-and-rename-KmGlobalDispatcherclassst-to-KMGlobalDispatcherc
by ci-pharo-ci-jenkins2＠inria.fr Feb. 23, 2019

Feb. 23, 2019

There is a new Pharo build available! The status of the build #104 was: SUCCESS. The Pull Request #2710 was integrated: "2659-Update-and-rename-KmGlobalDispatcherclassst-to-KMGlobalDispatcherc" Pull request url: https://github.com/pharo-project/pharo/pull/2710 Issue Url: https://pharo.fogbugz.com/f/cases/2659 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0