- Pharo-dev - lists.pharo.org

Estebanâs list of blocking issues for release Pharo 6.0 (updated to April 03)

by Esteban Lorenzano

Hello, This are the things I believe still needs to be solved to be able to release Pharo 6.0: VM: === - win32, cairo fonts problem (I submitted a new VM to test, I think this is fixed :P) - make all tests pass (there are still some failing tests when compiling a new VM)/. - libgit2: Still not there, Jan and Ben were trying and sent some suggestions but I still didnât had the time to test it. Image: ===== - iceberg still needs to go inside the image, Iâm running to release version 0.4 (maybe this week?) and then we can integrate. - I'm still convinced there is a leak. I need to check this in detail. And of course some help on thisâ¦ Pavel?â¦ would be cool :) List is a lot smaller now :) If everything goes well, we can target to release next week. Next: - Test the new process and tape some videos explaining how we will contribute with a bootstrapped process using github :) cheers! Esteban

April 3, 2017

Re: [Pharo-dev] the new "fixed" compactor VM has FT broken...

by Esteban Lorenzano

Hi Peter, I think I fixed the problem, can you try latest vm? Esteban > On 31 Mar 2017, at 14:55, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > Peter I took the latest mac VM and Moose 6.1 and I used your example > then I played during 15 min with all the roassal examples and I cannot reproduce > but I'm on mac. > > > > On Fri, Mar 31, 2017 at 2:23 PM, Stephane Ducasse <stepharo.self(a)gmail.com <mailto:stepharo.self@gmail.com>> wrote: > Tx peter! > I really really sorry for this state of affair. > I would like to tell you that I thank you for all the feedback you sent. Please continue. > I imagine what it is to get a system that blow up under your fingers. > I'm always trying to work with the alpha version (because I attract bugs) > I got some crashes playing with roassal - but I updated to the latest vm and trying. > > Can you sync with esteban so that he can access your setup? And yes we are burning > esteban on this.... We should pay attention that our faery does not get too exhausted :). > > Stef > > > On Fri, Mar 31, 2017 at 1:10 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com <mailto:i.uhnak@gmail.com>> wrote: > > > On Wed, Mar 29, 2017 at 3:03 PM, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: > BTWâ¦ I just checked Latest VM with a Pharo 5.0 (50771), and FT2 DOES NOT CRASHESâ¦ and it looks working fine, just installed somethings, etc. so I cannot be sure it will remain like that, but I can tell you: FT2 fonts are working fine in Windows (tested in 7) and Pharo 5.0 *with* latest VM. > > So, all this discussion is informative, but the mail that originates it can be reviewed :) > > No, this is still broken, even in Pharo 6 (with the latest VM). Maybe it's yet another cairo issue? But it complains about FT fonts... > > I did mention that it crashed on Athens canvas, so e.g. any Roassal presentation that contains text > > v := RTView new. > v add: (RTLabel new elementOn: '-_-'). > v > > <fml.png> > â > > Or running AthensSurfaceExamples class>>exampleDrawText > > <fml_squared.png> > > > In the past 15 months there was not a single week when the VM would just work without crashing or failing, and seeing that Pharo 6/lastest VM one day before release still doesn't work makes me really question why I still put up with this. > > Peter > > > > Esteban > > >> On 29 Mar 2017, at 14:43, phil(a)highoctane.be <mailto:phil@highoctane.be> wrote: >> >> We cannot work in 5.0 professionally with the VM released at the time. >> I am also using an intermediate VM thing to do the job. >> >> That is a pain. And not helping me push more Pharo to sysadmin people because they cannot have a stable reference point. >> >> Phil >> >> On Wed, Mar 29, 2017 at 12:05 PM, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: >> >> > On 29 Mar 2017, at 11:39, Peter Uhnak <i.uhnak(a)gmail.com <mailto:i.uhnak@gmail.com>> wrote: >> > >> > On Wed, Mar 29, 2017 at 11:05:28AM +0200, Esteban Lorenzano wrote: >> >> wellâ¦ >> >> >> >> Latest VM is intended to work with latest Pharo, not with older versions. >> >> Latest VM is *always* an experimental/unstable VM that needs to be consideredâ¦ that, experimental and unstable. Otherwise there would not be point on having the distinction between stable/latest, isnât? >> >> >> > >> >> So, no, Latest VM (which can also be known as âalpha vmâ) has not broken FT, it works fine in Pharo 6.0, which can also be know as âPharo 6.0 Alphaâ). >> >> >> >> BTWâ¦ Thatâs why in zeroconf you cannot download a âlatest vm for Pharo 5â. >> >> >> >> Of course, you can live at the edge, but that doesnât means something is broken when something fails if premises are not fulfilled :) >> > >> > Well considering VM for Pharo 5 never worked for me properly, whether it was crashing on BitBlt/Cairo, FT, or who knows what, I don't really have a choice but to use the latest. If there is a better way then I am all ears, constantly dealing with crashing VM when I need to get work done is extremely frustrating... >> > >> > Also I was under the impression that newer VM should work with older images, with the only exception being Cog/Spur change. Or should I have six different VMs and Pharo Launcher with six different VM configurations? >> >> we moved the paradigm a couple of years ago: each Pharo version comes with his own VM version (Other smalltalks do that too). >> Being infinite backward compatible is a lot of pain :) >> >> so yes, PharoLauncher needs to adapt to itâ¦ I added that requirement for PharoLauncher: you ship with latest stable but you can always download newers or olders (this is not yet implemented, is just a requirement I addedâ¦ well, couple of years ago when we changed the way we wanted VMs to work). >> >> Esteban >> >> > >> > Peter >> > >> >> >> >> Said thatâ¦ I had no problems with Latest VM + Pharo 6.0 (and they may happen, since this is all alfa :P) >> >> >> >> I donât know if âworkarounding the VMâ (by renaming libfreetype) will work, but if that works, ONCE we move latest vm to stable status we can consider backporting it to Pharo 5. >> >> >> >> Esteban >> >> >> >>> On 29 Mar 2017, at 10:37, Peter Uhnak <i.uhnak(a)gmail.com <mailto:i.uhnak@gmail.com>> wrote: >> >>> >> >>> The new "fixed" compactor VM has broken FT... >> >>> >> >>> So any text drawn on Athens canvas results in red cross... >> >>> >> >>> Error in... >> >>> >> >>> CairoFontFace class>>primFtFace:loadFlags: >> >>> >> >>> 'Unable to find function address' >> >>> >> >>> Apparently because someone renamed libfreetype-6.dll to libfreetype.dll >> >>> >> >>> (Windows VM latest, Pharo 5) >> >>> >> >> >> >> >> > >> >> >> > > > >

April 3, 2017

[pharo-project/pharo-core] 44de21: 60458

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 44de2196272d35434853ef65d929ece4f351e466 https://github.com/pharo-project/pharo-core/commit/44de2196272d35434853ef65… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-04-03 (Mon, 03 Apr 2017) Changed paths: M Compression.package/DeflateStream.class/instance/deflating/deflateBlock.st M Compression.package/FastInflateStream.class/instance/inflating/decompressBlock_with_.st M Kernel-Tests.package/ProcessTest.class/instance/testing/testTerminationShouldProceedEnsureBlocks.st M Morphic-Widgets-Windows.package/SystemWindow.class/instance/label/setLabel_.st M Morphic-Widgets-Windows.package/SystemWindow.class/instance/resize%2Fcollapse/extent_.st M RPackage-Core.package/extension/CompiledMethod/instance/packageFromOrganizer_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60457.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60458.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60457.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60458.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60458 19898 CompiledMethod package detection logic has bug when same selector is defined on instance and class side https://pharo.fogbugz.com/f/cases/19898 19886 Add a popup in case the title of a window is too large https://pharo.fogbugz.com/f/cases/19886 19905 ZlibPlugin reads past the zipCollection boundary https://pharo.fogbugz.com/f/cases/19905 19900 Better ProcessTest about ensure processing https://pharo.fogbugz.com/f/cases/19900 http://files.pharo.org/image/60/60458.zip

April 3, 2017

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60458 Home: https://github.com/pharo-project/pharo-core

April 3, 2017

Today is GSOC deadline

by Serge Stinckwich

Dear all, just a reminder for all mentors&students: the deadline for submitting your GSOC proposal is today at 6pm CEST. You have to submit the final pdf paper before that time. Thank you. Regards, -- Serge Stinckwich UCN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

April 3, 2017

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60457 Home: https://github.com/pharo-project/pharo-core

April 3, 2017

[pharo-project/pharo-core] ed1da4: 60457

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: ed1da41a85e4be145809d717e68682a2dc7abd1c https://github.com/pharo-project/pharo-core/commit/ed1da41a85e4be145809d717… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-04-03 (Mon, 03 Apr 2017) Changed paths: M Collections-Strings.package/ByteString.class/class/primitives/findFirstInString_inSet_startingAt_.st M Collections-Strings.package/ByteString.class/class/primitives/indexOfAscii_inString_startingAt_.st M Collections-Strings.package/ByteString.class/class/primitives/stringHash_initialHash_.st M Collections-Strings.package/ByteString.class/class/primitives/translate_from_to_table_.st M Collections-Strings.package/String.class/instance/comparing/findSubstringViaPrimitive_in_startingAt_matchTable_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60456.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60457.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60456.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60457.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-Tools.package/MessageBrowser.class/instance/private/isMethodDefinition_.st A System-Settings-Tests.package/SettingBrowserTest.class/instance/tests/testOpeningOnPackage.st M System-Settings.package/SettingBrowser.class/instance/updating/changePackageSet_.st M System-Settings.package/SettingBrowser.class/instance/user interface/choosePackagesIn_.st M System-Settings.package/SettingBrowser.class/instance/user interface/toolBarIn_.st Log Message: ----------- 60457 19892 Socket problem with LatestVM https://pharo.fogbugz.com/f/cases/19892 19870 Removing a method using Nautilus while it is present in a message browser raises #ast was sent to nil https://pharo.fogbugz.com/f/cases/19870 19860 MC generates duplicated trait methods https://pharo.fogbugz.com/f/cases/19860 19899 SettingBrowser>>choosePackagesIn: is not documented at all https://pharo.fogbugz.com/f/cases/19899 http://files.pharo.org/image/60/60457.zip

April 3, 2017

Esteban's ChangeLog week of 27 March 2017

by estebanlm＠gmail.com

Hello! This is my weekly ChangeLog, from 27 March 2017 to 2 April 2017. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=27/3/2017&to=2/4/2017 ChangeLog ========= 31 March 2017: -------------- * Yesterday I spent most of the day verifying why the pharo site was going down time to time... as a result, we found a problem in Voyage that may cause a deadlock under heavy load. Finally, with the help of Guille we help a possible cause in the way the +VOLazyProxy+ is implemented. This is +#doesNotUnderstand:+ current implementation: ---- VOLazyProxy>>doesNotUnderstand: aMessage | realObject | realObject := self obtainRealObject. realObject ifNil: [ (repository descriptionBuilder for: objectClass) isAllowMissingContent ifTrue: [ realObject := VOMissingObject class: objectClass id: objectId ] ifFalse: [ VOError signal: ('Lazy reference not found {1}: {2}' format: {objectClass name. objectId}) ] ]. VOLazyProxy mutex critical: [ self == realObject ifFalse: [ self becomeForwardKeepingHash: realObject ] ]. ^realObject perform: aMessage selector withArguments: aMessage arguments. ---- It is designed to prevent double attempt to become when trying to access same proxy at concurrent moments (in webapps is very frequent). We discovered this implementation has some problems: * When doing the comparisson of of +self+ with +realObject+ self can already be in the stack, and then it can fail. * apparently the error handler handles the occurrence of +Semaphore+ in a stack in weird ways (to ensure is debuggable) :) So, now I'm testing (and proposing to Voyage) this implementation: ---- VOLazyProxy>>#doesNotUnderstand: aMessage | realObject thisObject error | realObject := self obtainRealObject. realObject ifNil: [ (repository descriptionBuilder for: objectClass) isAllowMissingContent ifTrue: [ realObject := VOMissingObject class: objectClass id: objectId ] ifFalse: [ VOError signal: ('Lazy reference not found {1}: {2}' format: {objectClass name. objectId}) ] ]. error := nil. thisObject := self. VOLazyProxy mutex critical: [ thisObject == realObject ifFalse: [ [ self becomeForwardKeepingHash: realObject ] on: Error do: [ :e | error := e ] ] ]. error ifNotNil: [ VOLazyProxyBecomeError new error: error; signal ]. ^realObject perform: aMessage selector withArguments: aMessage arguments. ---- If this works, I will submit an update to [Voyage](http://github.com/pharo-nosql/voyage) immediately :) 29 March 2017: -------------- * I validated some changes to Athens and copyBits primitive to fix the crashing problem. Seems to be working so I will integrate it... thanks Eliot! * Still with [Iceberg](https://github.com/npasserini/iceberg), I took care of some bug... but most important than that, I added an option to create repositories from Iceberg. This is very simple: you click in the "New repository" button :) This way you do not need a remote repository to start working, and you can keep your versions in your local environent if you want. *WARNNING*: When doing your first push, it has to be a clean push (fast-forward), I have had problems trying the otherwise (which triggered a merge that Iceberg still does not knows how to handle). 27 March 2017: -------------- * I just spent sometime fixing stuff on [Iceberg](https://github.com/npasserini/iceberg). * I fixed [issue 313](https://github.com/npasserini/iceberg/issues/313) (now user gets a dialog to set user properties when needed). * Now commit dialog remembers last choice of "push" automatically while commiting. cheers! Esteban

April 3, 2017

Re: [Pharo-dev] Changing a field value with GtInspector

by Tudor Girba

Hi, This was present before we moved to FastTable. With the move some things did not make it in the integration, and editing the value is still on the to do list. Doru > On Apr 2, 2017, at 3:33 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > Hi > > May be I'm blind but I do not see how > we can change a value of an instance variable with gtInspector. > In the old inspector we could just type it and press accept. > When will we get this behavior? > Stef -- www.tudorgirba.com www.feenk.com "Every now and then stop and ask yourself if the war you're fighting is the right one."

April 3, 2017

Re: [Pharo-dev] [gsoc] Advances in Code Quality

by Yuriy Tymchuk

Ah, now I understand. So there are already inline critiques support where I highlight text and provide information on the side bar. Doing the smart suggestions wonât be super hard, because I have some critiques that know the exact node that violates the rule and can have a replacement node. So yes, the would be a nice extension. Uko > On 2 Apr 2017, at 16:50, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > > > On Sat, Apr 1, 2017 at 9:42 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>> wrote: > Hey Guille! > > Now Iâm interested :) Can you explain a bit more? Because there are already some autofix suggestions. What exactly do you suggest? Is selected ast node something a rule detects or is it selected by a user? > > What I mean by suggestions is the "smart suggestions" tool. The one that gives you a contextual menu given the selected AST in the code. Smart suggestions already allow you to show some actions given an AST node. It is used to show so far some meta-links (breakpoints, watchers), refactorings (targetting the specified node), and code navigation (senders, implementors). > > It would be nice because from the text editor you can access the suggestions with (ctrl | cmd) + t. I did not see an already existing integration of renraku with this, but maybe there is. > > Cheers. > Uko > >> On 1 Apr 2017, at 15:07, Guillermo Polito <guillermopolito(a)gmail.com <mailto:guillermopolito@gmail.com>> wrote: >> >> Yes! Actually offering fixes and transformations from renraku based on the selected ast node could be really cool! >> >> On Fri, Mar 31, 2017 at 7:21 PM, Stephane Ducasse <stepharo.self(a)gmail.com <mailto:stepharo.self@gmail.com>> wrote: >> This is a super topic. >> What would be good is to check the smart suggestions because they need more love. >> >> Stef >> >> On Fri, Mar 31, 2017 at 3:14 PM, Myroslava Romaniuk <romaniuk(a)ucu.edu.ua <mailto:romaniuk@ucu.edu.ua>> wrote: >> Hello, >> >> I'm Myroslava and I'm studying Computer Science at the Ukrainian Catholic University in Lviv. As part of my Google Summer of Code project I'm going to work on the quality of code in Pharo. This <https://docs.google.com/document/d/1cX7VJ2QZejq_Cu6Ur28UCiUwzSD-Bu8GgSDqECi…> is my proposal draft, and I would really appreciate some feedback, comments, suggestions and so on. >> >> Thanks! >> >> > >

April 2, 2017