- Pharo-dev - lists.pharo.org

Re: [Pharo-vm] New VM Release v10.3.2

by Guillermo Polito

>> I've rolled the stable version back to 10.3.1, please test. > > thanks, that means the 10.3.1 is still build with ubuntu and 10.3.2 is debian based? The binary for version 10.3.1 was built on ubuntu 16 or 18 I think, maybe Christophe or Pablo can give more details, I donât recall it right now. 10.3.2 was built on the new linux server infrastructure. $ uname -a Debian 6.1.99-1 (2024-07-15) x86_64 GNU/Linux We are evaluating different alternatives (e.g., downgrading the build server for a while). > Just to be sure. In that case it would be nice to have a way to download precisely 10.3.1 in order to stay safe and we have time to plan countermeasure. If you want to control what you download, right now the safest way is to go to files.pharo.org <http://files.pharo.org/>, more precisely to https://files.pharo.org/vm/pharo-spur64/, and look for your architecture. There you will find the archives with the binaries we built. Details about naming conventions are found here: https://github.com/pharo-project/pharo-vm/wiki/About-Build-and-Artifacts That file server stores both released artifacts and intermediate build results. The released artifact is the first artifact with the corresponding version tag (e.g., 10.3.1, 10.2.0). This is generally the oldest in timestime, but you can confirm with the tags on github. Moreover, the general advice is to avoid zeroconf as much as possible. We donât have the manpower to maintain build farms for each possible linux flavor. Internally, we recently started discussing the deprecation of zeroconf and the migration path to OBS for *nixes. The early sketch is that each released version will have its own package in OBS. Then a virtual package will gather them all together (and help people update or downgrade on need) More of this will come soon. > I think on one of the issues there was a mentioning that Kris add some patch for their CI. Iâm not aware of this, can you post a link here? > Maybe this is a good addition to zeroconf? Or can this be achieved differently Zeroconf worked very well until now, and we have put lot of effort in its modernization lately. However, as it is it has problems to scale: - executing an untrusted script that downloads unverified binaries - we manage only one nix build, which works only as soon as all nixes keep compatibility with the version we built on - it is designed to expose two versions: latest and stable. Much of this is solved by OBS, and we hope this improves our stability and visibility. > > Overall this is quite unfortunate. I hope there will be a better solution then everyone has to build their own vms. I think I need to plan some time to do it. We understand, and believe me, itâs unfortunate for us too. We are working on it and hope to have some news in the following weeks. >> >> @Norbert et al, we identified at least two issues: >> - a glibC incompatibility with Ubuntu 20.04 that arises because recently the build servers changed to a Debian, so all zeroconf users are impacted (except those using stable debian). > > I can confirm that. The segfault was always in ZdcSocketStream when accessing a native glibc function. Sadly the console I cannot see anymore because too many builds in between. Thanks, could you share your OS/setup ? (uname -a probably is enough). Also, anybody having a couple of minutes to test and help, if you see this issue locally, could you - build a VM (https://github.com/pharo-project/pharo-vm/) checking out tag v10.3.2 - run locally the failing tests This information could help us reduce the search space, and identify if itâs just the build environment or there is something else we have to deal with. Cheers, G

Dec. 5, 2024

Re: [Pharo-vm] New VM Release v10.3.2

by Norbert Hartl

> Am 05.12.2024 um 11:20 schrieb Guille Polito <guillermo.polito(a)inria.fr>: > > Hi all, > > I've rolled the stable version back to 10.3.1, please test. thanks, that means the 10.3.1 is still build with ubuntu and 10.3.2 is debian based? Just to be sure. In that case it would be nice to have a way to download precisely 10.3.1 in order to stay safe and we have time to plan countermeasure. I think on one of the issues there was a mentioning that Kris add some patch for their CI. Maybe this is a good addition to zeroconf? Or can this be achieved differently Overall this is quite unfortunate. I hope there will be a better solution then everyone has to build their own vms. I think I need to plan some time to do it. > > @Norbert et al, we identified at least two issues: > - a glibC incompatibility with Ubuntu 20.04 that arises because recently the build servers changed to a Debian, so all zeroconf users are impacted (except those using stable debian). I can confirm that. The segfault was always in ZdcSocketStream when accessing a native glibc function. Sadly the console I cannot see anymore because too many builds in between. Norbert > - a vm crash that we are still investigating > > If you have the second issue, and you have a small reproducible case (like some small test set in your open source project) that we can use to reproduce the issue, that will accelerate our debugging process. > > Thanks all for understanding, > G > >> Le 5 dÃ©c. 2024 Ã 10:45â¯AM, Norbert Hartl <norbert(a)hartl.name> a Ã©crit : >> >> Thanks. >> >> And please tell us what data we can generate in order to help. It happened on our CI and this is a place where I can introduce stuff which generates data if it does not become too slow. >> >> Norbert >> >>> Am 05.12.2024 um 08:42 schrieb Guille Polito <guillermo.polito(a)inria.fr>: >>> >>> Hi all, >>> >>> We had reports of issues observed with this version, we will rollback during the morning and after proceed to study the indicent. >>> >>> G >>> >>>> Le 4 dÃ©c. 2024 Ã 10:56â¯AM, Guille Polito <guillermo.polito(a)inria.fr> a Ã©crit : >>>> >>>> Hi all, >>>> >>>> Weâve published a new VM release (v10.3.2) to be used with Pharo versions 10 through 13. >>>> Please check the change log here: >>>> >>>> https://github.com/pharo-project/pharo-vm/releases/tag/v10.3.2 >>>> >>>> The build is on the oven, new VMs should be available as soon as the build farm finishes. >>>> >>>> Cheers, >>>> G >>>> _______________________________________________ >>>> Pharo-vm mailing list -- pharo-vm(a)lists.pharo.org >>>> To unsubscribe send an email to pharo-vm-leave(a)lists.pharo.org >>> >> >> _______________________________________________ >> Pharo-vm mailing list -- pharo-vm(a)lists.pharo.org >> To unsubscribe send an email to pharo-vm-leave(a)lists.pharo.org >

Dec. 5, 2024

Re: [Pharo-vm] New VM Release v10.3.2

by Guille Polito

Hi all, I've rolled the stable version back to 10.3.1, please test. @Norbert et al, we identified at least two issues: - a glibC incompatibility with Ubuntu 20.04 that arises because recently the build servers changed to a Debian, so all zeroconf users are impacted (except those using stable debian). - a vm crash that we are still investigating If you have the second issue, and you have a small reproducible case (like some small test set in your open source project) that we can use to reproduce the issue, that will accelerate our debugging process. Thanks all for understanding, G > Le 5 dÃ©c. 2024 Ã 10:45â¯AM, Norbert Hartl <norbert(a)hartl.name> a Ã©crit : > > Thanks. > > And please tell us what data we can generate in order to help. It happened on our CI and this is a place where I can introduce stuff which generates data if it does not become too slow. > > Norbert > >> Am 05.12.2024 um 08:42 schrieb Guille Polito <guillermo.polito(a)inria.fr>: >> >> Hi all, >> >> We had reports of issues observed with this version, we will rollback during the morning and after proceed to study the indicent. >> >> G >> >>> Le 4 dÃ©c. 2024 Ã 10:56â¯AM, Guille Polito <guillermo.polito(a)inria.fr> a Ã©crit : >>> >>> Hi all, >>> >>> Weâve published a new VM release (v10.3.2) to be used with Pharo versions 10 through 13. >>> Please check the change log here: >>> >>> https://github.com/pharo-project/pharo-vm/releases/tag/v10.3.2 >>> >>> The build is on the oven, new VMs should be available as soon as the build farm finishes. >>> >>> Cheers, >>> G >>> _______________________________________________ >>> Pharo-vm mailing list -- pharo-vm(a)lists.pharo.org >>> To unsubscribe send an email to pharo-vm-leave(a)lists.pharo.org >> > > _______________________________________________ > Pharo-vm mailing list -- pharo-vm(a)lists.pharo.org > To unsubscribe send an email to pharo-vm-leave(a)lists.pharo.org

Dec. 5, 2024

Re: [Pharo-vm] New VM Release v10.3.2

by Norbert Hartl

Thanks. And please tell us what data we can generate in order to help. It happened on our CI and this is a place where I can introduce stuff which generates data if it does not become too slow. Norbert > Am 05.12.2024 um 08:42 schrieb Guille Polito <guillermo.polito(a)inria.fr>: > > Hi all, > > We had reports of issues observed with this version, we will rollback during the morning and after proceed to study the indicent. > > G > >> Le 4 dÃ©c. 2024 Ã 10:56â¯AM, Guille Polito <guillermo.polito(a)inria.fr> a Ã©crit : >> >> Hi all, >> >> Weâve published a new VM release (v10.3.2) to be used with Pharo versions 10 through 13. >> Please check the change log here: >> >> https://github.com/pharo-project/pharo-vm/releases/tag/v10.3.2 >> >> The build is on the oven, new VMs should be available as soon as the build farm finishes. >> >> Cheers, >> G >> _______________________________________________ >> Pharo-vm mailing list -- pharo-vm(a)lists.pharo.org >> To unsubscribe send an email to pharo-vm-leave(a)lists.pharo.org >

Dec. 5, 2024

Re: [Pharo-vm] New VM Release v10.3.2

by Guille Polito

Hi all, We had reports of issues observed with this version, we will rollback during the morning and after proceed to study the indicent. G > Le 4 dÃ©c. 2024 Ã 10:56â¯AM, Guille Polito <guillermo.polito(a)inria.fr> a Ã©crit : > > Hi all, > > Weâve published a new VM release (v10.3.2) to be used with Pharo versions 10 through 13. > Please check the change log here: > > https://github.com/pharo-project/pharo-vm/releases/tag/v10.3.2 > > The build is on the oven, new VMs should be available as soon as the build farm finishes. > > Cheers, > G > _______________________________________________ > Pharo-vm mailing list -- pharo-vm(a)lists.pharo.org > To unsubscribe send an email to pharo-vm-leave(a)lists.pharo.org

Dec. 5, 2024

New VM Release v10.3.2

by Guille Polito

Hi all, Weâve published a new VM release (v10.3.2) to be used with Pharo versions 10 through 13. Please check the change log here: https://github.com/pharo-project/pharo-vm/releases/tag/v10.3.2 The build is on the oven, new VMs should be available as soon as the build farm finishes. Cheers, G

Dec. 4, 2024

Re: "Evaluation of SUnit" â New blog post on all: objects all: theTime

by Yanni Chiu

The blog post has "Nobody thought about automating that process. Until Kent Beck did." That is not accurate, AFAIK. I believe it was in Kent Beck's original EXtreme Programming book where he says the practices were gathered from various Smalltalk shops he consulted at during the Smalltalk heyday in the early 90's. For what it's worth, here's the history I know. Around 1993, in Toronto, I was working at Footprint Software on VisualBanker (a suite of code to support banking that 4 of the 5 major Canadian banks bought). With my programming buddy (no "pair programming" at the time) our task was to build a persistence framework (supporting Relational, ObjectFiler, and in-memory). My task in a previous job was to convert (the AT&T Unix) C compiler to support the "new" ANSI C standard. Thankfully, I was provided with a test suite of C code, so that if it compiled without errors, then the compiler was standard compliant. So, looking for something similar to the ANSI C test suite I'd encountered, I set up test cases where all methods starting with "test" would be run, and ran the tests against all the backend data stores. The next day, my programming buddy (George), who started at 6am (to have a faster commute) tells me this test thing is great, and shows me the UI he built so we could just push a button. We can check the same behaviour for all backends, and we can coordinate our code changes through the tests (to mitigate our different schedule). A year later, the company's product was deemed slow, so they contracted Kent Beck to review our code base. He eventually comes around to us. We showed him what we did with tests, and then he just paused for about a minute staring out the window. We thought we were doing something really bad. A few months later, George said to me "did you see the SUnit thing posted on comp.lang.smalltalk". The basic "test"-prefixed test cases were there, but with the addition of the setUp and tearDown concept. Every once in a while I think to write this up. The "Nobody thought about automating..." words pushed me over this time. Maybe 15 years ago, I was able to find the original comp.lang.smalltalk SUnit posting, but could not locate it this time when I wanted to verify the dates. Yanni Chiu, Smalltalk oldtimer, Toronto On Fri, Nov 22, 2024 at 8:58â¯AM Koen De Hondt <koen(a)all-objects-all-the-time.st> wrote: > > Dear Pharo users and developers, > > I wrote a blog post in which I evaluate SUnit. > > Enjoy reading it! > > Ciao, > Koen >

Nov. 22, 2024

"Evaluation of SUnit" â New blog post on all: objects all: theTime

by Koen De Hondt

Dear Pharo users and developers, I wrote a blog post in which I evaluate SUnit <https://all-objects-all-the-time.st/#/blog/posts/10>. Enjoy reading it! Ciao, Koen

Nov. 22, 2024

Pharo News of the Week 47/2024

by Marcus Denker

# Pharo News of the Week 47/2024 - The Soil Database has now an entry in HAL https://hal.science/hal-04726251 and is archived by https://www.softwareheritage.org/ # The week on the Pharo Issue Tracker # Features - Introduce New Finder #17420 https://github.com/pharo-project/pharo/pull/17420 - Add Load/Export feature to the New Settings Browser #899 https://github.com/pharo-spec/NewTools/pull/899 # Fixes - Multiple FileBrowser directory handling fixes for Windows #882 https://github.com/pharo-spec/NewTools/pull/882 - UnixResolverTest should check for platform #17387 https://github.com/pharo-project/pharo/pull/17387 # Improvements - 17409-Improving-FFI-Marshalling-of-Constants #17410 https://github.com/pharo-project/pharo/pull/17410 - Use default instead of StartupPreferencesLoader new #17404 https://github.com/pharo-project/pharo/pull/17404 - Better API for tools unregistration. remove: was lame. #17390 https://github.com/pharo-project/pharo/pull/17390\ # VM - Enhancement(versionning): Extract full semantic version from git #870 https://github.com/pharo-project/pharo-vm/pull/870 # GIT / Iceberg - Branch: CommandRepoBrowser1841, Fixes # 1841 #1855 https://github.com/pharo-vcs/iceberg/pull/1855 - Fixes #1851 Update RemoteChangingIssue #1859 https://github.com/pharo-vcs/iceberg/pull/1859 # NewTools - Remove undefined file double-click action. #907 https://github.com/pharo-spec/NewTools/pull/907 - Removing Smalltalk tools! #905 https://github.com/pharo-spec/NewTools/pull/905 - New Finder integration #909 https://github.com/pharo-spec/NewTools/pull/909 - Add a registration API for tool: for now delegate to ToolsRegistry #903 https://github.com/pharo-spec/NewTools/pull/903 - Make playgrounds refresh styling after removing bindings #902 https://github.com/pharo-spec/NewTools/pull/902 - Configure Setting Browser initialization properties #901 https://github.com/pharo-spec/NewTools/pull/901 - Add package âNewTools-DebugPointsBrowser-Testsâ with a subclass of SpSmokeTest for DebugPointBrowserPresenter #900 https://github.com/pharo-spec/NewTools/pull/900 - fix pharo issue 17323 #893 https://github.com/pharo-spec/NewTools/pull/893 # Spec - Adapt whenNumberChangedDo: to use two argument block #1662 https://github.com/pharo-spec/Spec/pull/1662 - Fix the 17373 issue on Pharo (initial focus on text in refactor rename protocol) #1660 https://github.com/pharo-spec/Spec/pull/1660 - less extension. #1656 https://github.com/pharo-spec/Spec/pull/1656 - Factor out #refreshStyling from #evaluate:onCompileError:onError: on SpCodePresenter #1655 https://github.com/pharo-spec/Spec/pull/1655 - Add tests in SpSliderAdapterTest #1652 https://github.com/pharo-spec/Spec/pull/1652 - fixes https://github.com/pharo-spec/NewTools/issues/879 #1643 https://github.com/pharo-spec/Spec/pull/1643 # Cleanups - Cleaning spurious reference to Smalltalk #17407 https://github.com/pharo-project/pharo/pull/17407 - Simplify Calypso environment #17412 https://github.com/pharo-project/pharo/pull/17412 - Remove ClyClassChange #17411 https://github.com/pharo-project/pharo/pull/17411

Nov. 22, 2024

Pharo News of the Week 46

by Marcus Denker

# News of the Week 46 - [Ann] v10.4.0 pillar https://pharo.org/news/2024-11-15-Pillar.html - ESUG2024 day 4 Videos (and thus all talks of the main track) are now in the playlist: https://www.youtube.com/playlist?list=PLJ5nSnWzQXi-uyYOZIVgXg1up_bclQc7e - Phausto (https://github.com/lucretiomsp/phausto) Presentation at the Audio Developer Conference 2024 (3 daily poster sessions in the virtual venue, and at the open-mic session (https://youtu.be/fVw80P_8RMs) # This week (46/2024) on the Pharo Issue Tracker # Fixes - Fixes CI to have it green again on unix #17377 https://github.com/pharo-project/pharo/pull/17377 - Super call missing in initialization #17353 #17354 https://github.com/pharo-project/pharo/pull/17354 - Add ~/.local/share/fonts/ to the unix font directories #17326 https://github.com/pharo-project/pharo/pull/17326 - Changing "add method" to "create method" in the debugger method creator #892 https://github.com/pharo-spec/NewTools/pull/892 - fix: #884 Renamed TStPresenter into StTPresener #887 https://github.com/pharo-spec/NewTools/pull/887 - Fixed linux terminal command, unified method for Windows #876' https://github.com/pharo-spec/NewTools/pull/876 - Fix MetaBrowserPresenter filtering #868 https://github.com/pharo-spec/NewTools/pull/868 - fix pharo issue 17323 (spec side) #1651 https://github.com/pharo-spec/Spec/pull/1651 - Fix RegexSyntaxError: no terminating "]" in SpSearchInputFieldOptionsâ¦ #1635 https://github.com/pharo-spec/Spec/pull/1635 # Settings - Use StPharoApplication instead of custom settings application #877 https://github.com/pharo-spec/NewTools/pull/877 - Restore Settings Browser missing custom styles #897 https://github.com/pharo-spec/NewTools/pull/897 - Prevent settings reset to their defaults upon new Setting Browser tab selection #895 https://github.com/pharo-spec/NewTools/pull/895 # VM - Improving Forwarders in the PermSpace #861 https://github.com/pharo-project/pharo-vm/pull/861 - use pharo file server @ inria #868 https://github.com/pharo-project/pharo-vm/pull/868 - use pharo file server @ inria #867 https://github.com/pharo-project/pharo-vm/pull/867 - compatible with FreeBSD mmap() #863 https://github.com/pharo-project/pharo-vm/pull/863 # Improvements - Add helper method to setup the filtering list header title #1639 https://github.com/pharo-spec/Spec/pull/1639 - Register new File Browser in tools registry #885 https://github.com/pharo-spec/NewTools/pull/885 - Add a new SettingUpdated event for Epicea Monitor. #17350 https://github.com/pharo-project/pharo/pull/17350 - Use a setting declaration's typeClass to get default values #17342 https://github.com/pharo-project/pharo/pull/17342 - Deprecate explicitRequirement #17276 https://github.com/pharo-project/pharo/pull/17276 # files.pharo.org - use file server @ inria #17375 https://github.com/pharo-project/pharo/pull/17375 - use pharo file server @ inria #17336 https://github.com/pharo-project/pharo/pull/17336 - use files.pharo.org for upload #17371 https://github.com/pharo-project/pharo/pull/17371 # Refactoring Engine - Refactoring of rename temp and extract method while mutation testing #17340 https://github.com/pharo-project/pharo/pull/17340 # Documentation - Better class comments for refactorings #17357 https://github.com/pharo-project/pharo/pull/17357 - add news server #81 https://github.com/pharo-project/pharo-website/pull/81 # Cleanup - Make sure that StFinder uses application for inform: #883 https://github.com/pharo-spec/NewTools/pull/883 - A little clean #889 https://github.com/pharo-spec/NewTools/pull/889 - Repackage #asFileName #17351 https://github.com/pharo-project/pharo/pull/17351 - Clean tools registration #17365 https://github.com/pharo-project/pharo/pull/17365 - Adding some helpers in BaselineOf so that we can clean baselines #17363 https://github.com/pharo-project/pharo/pull/17363 - Cleaning initialize protocol #17359 https://github.com/pharo-project/pharo/pull/17359 - Fedup to have around this initialize-release? Let us get rid of it! #17358 https://github.com/pharo-project/pharo/pull/17358

Nov. 18, 2024