July 2017 - Pharo-dev - lists.pharo.org

Iceberg
by Aliaksei Syrel Sept. 20, 2017

Sept. 20, 2017

Hi, It is amazing to see how fast Pharo progresses and moves closer to release. Therefore it may happen that after a week of absence there is so much new stuff that I just loose track of changes and sometimes old behaviour does not correspond new reality and "nothing works" :) Probably it is my case now. I would like to work on a project hosted on github. I tried iceberg:dev-0.4, iceberg:dev-0.5, iceberg-master but didn't succeed.. Here is what I get when try to clone repository both from Playground or by using "+" clone button in Iceberg both dev-04 and dev-05 [image: Inline images 1] If I try to load Iceberg master in the Image I get this: [image: Inline images 2] I am sure I do something wrong, so I recorded three videos - one for every Iceberg version. â Iceberg-0.4.mov <https://drive.google.com/file/d/0B-bMBVDOi3oTLTZvejdYTkNfaWM/view?usp=drive…> ââ Iceberg-0.5.mov <https://drive.google.com/file/d/0B-bMBVDOi3oTbDJNZnJMeUJEYk0/view?usp=drive…> ââ Iceberg-master.mov <https://drive.google.com/file/d/0B-bMBVDOi3oTVzhGQmJOVzN3akU/view?usp=drive…> â VM: pharo-mac-i386-201705051953-b8db6de Image: 60482 OS: macOS Sierra 10.12.4 P.S. Still getting black screen when open an Image until I click... Cheers, Alex

8 11

Pharo 7 provisional HOWTO
by Pavel Krivanek Aug. 24, 2017

Aug. 24, 2017

Hi, this mail describes how to start to send pull requests to Pharo 7 Github repository from Pharo 7. Preparations ===================== - you need to have a Github account and set SSH keys. See https://help.github.com/articles/connecting-to-github-with-ssh/ - create own pharo-project/pharo repository fork. Go to https://github.com/pharo-project/pharo, click on "Fork" button and follow the instructions Get Pharo 7 image ===================== The CI jobs for the Pharo 7 defelopment are currently not fully set and we still do not publish Pharo 7 image to files.pharo.org so you cannot get it using zero-conf scripts. But we have a provisional CI job that bootstraps the Pharo 7 image. https://ci.inria.fr/pharo/view/7.0/job/70-Bootstrap-32bit/ There download a file named like Pharo7.0-32bit-hash.zip and decompress it. Unlike Pharo 6 images, the archive contains three files. Image, changes and sources. In Pharo 7 you have the sources file for every bootstrapped version. It has a commit hash in the name and it cannot be shared between different Pharo 7 imges, however it can be shared between images that were created as snapshots with the same bootstrapped image as ancestor. Create local clone ===================== You need a local clone of the Pharo repository. Because it contains a lot of small files, it is not a good idea to have own clone for every image. You can have only one and share them between images. But because of some current Monticello constraints you need to have the clone placed in the image directory in a folder with name 'pharo-core'. In this step we will clone the Pharo repository from pharo-project/pharo Github repository and add your fork as default pull target. We will update your fork repository to contain all latest commits from the Pharo repository in the branch named 'development'. For latest stable version (Pharo 6) we use the master branch. In the end we will checkout the repository to a particular commit from which the downloaded Pharo 7 image was bootstrapped. Imagine that you have a Pharo 7 image that is several days old and the development branch has already some commits that change code. If you would take this older image, checkout to the development branch and then do your commit, your would revert all changes done in not-loaded commits. The other option is to update your image to correspond to the repository latest commit which requires packages reloading. If you checkout to a particular commit, you are in detached HEAD state. In this state you cannot do commits directly. You need to firstly create new a new branch which we will do anyway. Evaluate the following code. This functionality will be later direct part of Iceberg UI. Do not forget to change the user name. username := 'YOUR-USER-NAME'. repository := IceRepositoryCreator new url: 'git@github.com:pharo-project/pharo.git'; location: ('pharo-core' asFileReference ensureCreateDirectory); subdirectory:'src'; createRepository. repository checkoutBranch: 'development'. repository register. fork := (IceRemote name: 'myFork' url: ('git@github.com:{1}/pharo.git' format: {username})). repository addRemote: fork. repository pushRemote: fork. repository pullRemote: repository origin. "update fork" repository backend pullFrom: repository origin. "use this low-level form to prevent packages reloading" repository push. "checkout to the commit from which the image was bootstrapped" repository checkoutBranch: (SystemVersion current commitHash). Use already created clone ===================== This is alternative to the previous step. Let's suppose that you already have your local clone. You take some Pharo 7 image and you want to create commits. Then you need to create a symlink or move/copy the repository into your image directory. Remember, it must be named pharo-core (we do not use the name 'pharo' to avoid collision with VM executable). In this step we will register an existing Pharo repository clone, set your fork as the push target, update your fork and then switch to the particular commit. repository := IceRepositoryCreator new location: ('pharo-core' asFileReference); subdirectory:'src'; createRepository. repository register. fork := repository remotes detect: [ :remote | remote remoteName = #myFork ]. repository pushRemote: fork. repository pullRemote: repository origin. repository checkoutBranch: 'development'. repository backend pullFrom: repository origin. repository push. repository checkoutBranch: (SystemVersion current commitHash). Issue processing ===================== - create new case on FogBugz to get the issue number - open Iceberg and from the context menu on the 'pharo' repository do: Pharo - Create new branch from FogBugz issue, enter the issue ID and it will fill the full branch name for you - create your changes (you can do it before the creation of the branch too) - commit and push your changes in Iceberg, this way you will commit your branch to your fork repository. Remember that the Iceberg commit window has two buttons, one for local commit, the second for commit with immediate push. They can be very long because they contain the full branch (issue) name - in Iceberg in the 'pharo' repository context menu do: Pharo - Create pull request, fill your - fill your Github credentials - leave the PR title, comment is not required, check the pull request head and base. The base MUST be pharo-project/pharo development. Create the pull requests - go to https://github.com/pharo-project/pharo/pulls, check your pull requests and put URL of it into the issue record on FogBugz (as a comment). Resolve the issue as Fix review needed Cheers, -- Pavel

10 27

Catalog statistics (Who know this projects?)
by Esteban Lorenzano Aug. 22, 2017

Aug. 22, 2017

Soâ¦ I took a couple of minutes to do a small list of project description status: >From a total of 379 projects currently in the catalog, just 115 have a description and/or keywords associated. Which means 264 are mysterious projects nobody can guess what are they about. I was thinking most of this projects would be in Unsorted (or Pharo 3), but I found that many are also on Pharo 5 and 4â¦. which is frankly unacceptable :) Even very important projects like Seaside or Garage and Glorp are not documented. So, please peopleâ¦ take a look at your projects and PLEASE, provide a description and proper keywordsâ¦ Nobody can guess what is Aconcagua (besides a cool mountain in south america), or Telescope, etc., etc., etc. Here the list of non-documented projects: http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo50/main --- 'A4BP' 'Aconcagua' 'BootstrapMagritte' 'Chalten' 'CommandShell' 'Cormas' 'DependencyAnalyser' 'FamixJS' 'FontAwesome' 'Garage' 'GarageConnectionPool' 'GarageGlorp' 'Glorp' 'Grease' 'IniModules' 'Kendrick' 'Magritte3' 'MagritteMagic' 'MetaBoardBoard' 'MyFirstWebApp' 'NBOpenGL' 'NeoJSON' 'OSProcess' 'PetitParser' 'Phexample' 'Pier3' 'Pier3AddOns' 'ProcessWrapper' 'RewriteTool' 'Seaside3' 'SimplePersistence' 'Ston' 'Telescope' 'Woden' âXtreams' http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo40/main --- 'AconcaguaDeluxe' 'AthensSVG' 'Autotest' 'CPanel' 'CreativeCommonsLive' 'DevFlow' 'EventRecorder' 'ExtendedNumberParser' 'ExternalWebBrowser2' 'FixedDecimal' 'Ghost' 'GraphViz' 'Gravatar' 'Hubcap' 'Infinity' 'Mandrill' 'Mathex' 'MemoryMonitor' 'MinimalConnectors' 'Mocketry' 'MongoTalk' 'NBSQLite3' 'NumericalMethods' 'ODBC' 'OSOSX' 'OSWindows' 'PackageDependenciesAnalysis' 'PharoLauncher' 'PlagueDoctor' 'Pomodoro' 'RemoteAnnouncement' 'SandstoneDb' 'Scheduler' 'ScriptManager' 'Shapes' 'SmallUML' 'Spreadsheet' 'Spy' 'StateSpecs' 'SuffixConditionals' 'Teachable' 'TestMock' 'Trees' 'Twilio' 'Vidi' 'VistaCursors' 'Viva' 'WiringPi' 'WorkingSet' 'XBase' 'sQuick' âsQuick_new' http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo30/main --- 'Actalk' 'Arduino' 'BabyMock2' 'CTranslator' 'DBPedia' 'DigitalOcean' 'Forum' 'Fuel' 'GTDebugger' 'GTInspector' 'GTInspectorCore' 'GTPlayground' 'GTPlaygroundCore' 'GTSpotter' 'GToolkit' 'GlamourCore' 'GlorpDBX' 'GraphET' 'InstanceEncoder' 'Marina' 'Mechanize' 'Memcached' 'Moose' 'Pastell' 'PharoOnlineHelp' 'ProfStef' 'PythonParser' 'RFB' 'Roassal3d' 'SQLite3' 'Smallapack' 'SmalltalkHub' 'Snapshotcello' 'SortFunctions' 'Spotlight' 'Stamp' 'Tide' 'VersionBrowser' âVersionner' http://www.squeaksource.com/MetacelloRepository --- 'AXAnnouncements' 'Adore' 'Aida' 'Ajp' 'Algernon' 'Alien' 'Amers' 'Announcements' 'AutomaticMethodCategorizer' 'BetaNineIPAddress' 'CAnalyzer' 'CairoGraphics' 'CampSmalltalkLondon' 'Cecinestpasunepomme' 'CharacterMap' 'Chronos' 'CloudforkAWS' 'Cog' 'Connectors' 'ContextS' 'Control' 'Country' 'Countryside' 'DBXBrowser' 'DBXTools' 'DependencyBrowser' 'DependencyView' 'EnhancedOmniBrowser' 'ExternalIconFamily' 'ExternalWebBrowser' 'FileMan' 'FileTree' 'Filesystem' 'GemTools' 'Gitocello' 'Glamour' 'Gofer' 'GoferProjectLoader' 'GoogleAnalytics' 'HPDF' 'HealthReportProducer' 'HelpSystem' 'ICal' 'InstancesBrowser' 'JQueryWidgetBox' 'JavaScriptAnalyzer' 'Jejak' 'Keymapping' 'Kozen' 'KyotoTycoonClient' 'MaBase' 'MaClientServer' 'Magma' 'Magmafy' 'Magritte' 'Magritte2' 'Magritte3AddOns' 'MagritteAddOns2' 'Metacello' 'MetacelloBrowser' 'MetacelloPreview' 'MockGemStone' 'Mondrian' 'Money' 'MonticelloRedirect' 'Murmansk' 'Nagare' 'NativeBoost' 'Neo4reSt' 'NewECompletion' 'NewInspector' 'NewOCompletion' 'Nile' 'NotificationsArea' 'O2' 'OCompletion' 'OPAX' 'ObjectMetaTools' 'OmniBrowser' 'OmniBrowserLukas' 'Orca' 'PagedReader' 'Pharo' 'PharoMorphicExtras' 'PharoNonCore' 'Phriak' 'Pier' 'Pier2' 'PierAddOns' 'PierAddOns2' 'PostMark' 'ProcessModel' 'Quaternion' 'REPL' 'Raphael' 'RatPack' 'RefactoringBrowser' 'RefactoringTools' 'RoelTyper' 'SIXX' 'SPort2' 'SandcastleThemes' 'Scamper' 'Scribo' 'Seafox' 'Seaside' 'Seaside28' 'Seaside28Examples' 'Seaside30' 'SeasideJSON' 'SeasideRest' 'SeasideTesting' 'SharedWorkspace' 'Shout' 'SimpleApplescript' 'SoapOpera' 'SpellingServices' 'SpyForO2' 'Sqnappy' 'SqueakCheck' 'SqueakDBX' 'SqueakFS' 'SqueakSource' 'StOMP' 'Stripe' 'SunnysidePlanning2' 'SwaLint' 'Swazoo2' 'TODO' 'TimerDaemon' 'Tuio' 'VMMaker' 'Waterfall' 'WebClient' 'WebTester' 'XMLRPC' 'XMLSupport' 'Zodiac'

15 22

[ANN] Pharo 6.1 (summer) released!
by Esteban Lorenzano Aug. 22, 2017

Aug. 22, 2017

Hi, We are releasing Pharo 6.1. Usually, between each major version we just apply bugfixes changing the build number and not announcing new versions but this time is different since the fixes applied required a new VM. The principal reason for the new version is to update Iceberg support, bringing it to macOS 64bits version. So, now Pharo 6.1 comes with Iceberg 0.5.5, which includes: - running on macOS 64bits - adds cherry pick - adds major improvements on performance for big repositories - adds pull request review plugin - repositories browser: group branches by remote - adds bitbucket and gitlab to recognised providers on metacello integration - uses libgit v0.25.1 as backend - several bugfixes Other important change: - linux vm by default is now vm threaded heartbeat. We still miss 64bits Windows (sorry for that), but we are getting there. I hope to have it running right after ESUG. To download 6.1 version, you can go to http://pharo.org/download <http://pharo.org/download> page, or with zeroconf: wget -O- get.pharo.org | bash Enjoy! Esteban

16 36

Pharo behind ALLSTOCKER marketplace
by Masashi UMEZAWA Aug. 17, 2017

Aug. 17, 2017

Hi all, >From Torsten, I've received a request to post about some technical details of ALLSTOCKER (http://pharo.org/success/AllStocker) . I hope these notes will be interesting to Pharo web developers. - Seaside / Teapot We are using Seaside as a main framework for ALLSTOCKER marketplace. Seaside's component architecture is great for extending application in an organized way. ALLSTOCKER prototype was originally composed of only 3 class categories. Now these were gradually grown to 70 categories. But we still feel that they are manageable. We also use Teapot for building Web-based API in a quick way. Recently we've built webhook handlers for integration with other services. - Templating with Mustaside We need a lot of responsive-design web pages for supporting various mobile devices. (It is important especially for Southeast Asian countries, where tablets are popular than PCs). We would like to adopt existing Twitter Bootstrap templates for saving time. So, Mustaside was our choice. http://smalltalkhub.com/#!/~MasashiUmezawa/Mustaside Before Mustaside, there were a lot of noisy #div: sends in our code. Now they are gone. - Localization Our business target is world-wide. So localization is very important topic. Currently ALLSTOCKER supports 4 languages and we will add Chinese languages soon. Translation strings are not only in Smalltalk code, but also in Mustache templates. So we selected Soup for extracting translatable strings in those templates. http://smalltalkhub.com/#!/~PharoExtras/Soup For managing translations, we use Gettext package. http://smalltalkhub.com/#!/~PharoExtras/Gettext - Databases For transactional data, we chose Glorp. Although there are mapping costs, we prefer RDB (Postgres). It is reliable for handling precious order-related data. However, for supporting complex search of machines, we use Neo4j - a graph database. It supports very powerful query language called Cypher. We can avoid complex table joins and get aggregated results faster. http://smalltalkhub.com/#!/~MasashiUmezawa/Neo4reSt - Keyword search ALLSTOCKER supports free keyword search. We selected Elasticsearch for search-engine. Elasticsearch has elaborated searching facilities and those are easily accessible via REST API. We have extended the existing Elasticsearch client for Pharo 5. https://github.com/newapplesho/elasticsearch-smalltalk - Deployment We are using AWS Elastic Load Balancer and running Nginx as a front-end web server. Two back-end Pharo images are running and load-balanced with sticky sessions. It was sort of difficult to find the appropriate simultaneous number of database connections and Pharo processes. We feel ALLSTOCKER is pretty stable for now, but we need to adjust more for expanding our services. Best regards, -- [:masashi | ^umezawa]

8 7

Is there a portable way to check if a string is a block?
by Mariano Martinez Peck Aug. 13, 2017

Aug. 13, 2017

Hi guys, Is there a portable (that would work in GemStone too) and safe way to know if a String would be a block? I must support this kind of strings: 'singleString' -> false 'multi string' -> false ' [:a | 42]' -> true ' '' '' [:a | 42]' -> true '[:a | 42]' -> true ' "a commet" [:a | 42]' -> true ' WhateverClass someVeryBadHackishMethod. [:a | 42]' -> true I need to identify whether the string is a closure or not. And ideally, I don't want to do an #evaluate: because I don't want any left hand code to be executed. I tried with #parse: why I am having problems. Any ideas? Thanks in advance -- Mariano http://marianopeck.wordpress.com

4 3

Re: [Pharo-dev] Pharo 7 provisional HOWTO
by Nicolai Hess Aug. 9, 2017

Aug. 9, 2017

And if I only want to contribute by reviewing a fix. Do I have to go the git-path ? Or is there a way to just start up an image and load and review the change? Am 28.06.2017 5:26 nachm. schrieb "Pavel Krivanek" <pavel.krivanek(a)gmail.com >: 2017-06-28 17:06 GMT+02:00 ClÃ©ment Bera <bera.clement(a)gmail.com>: > Hi all, > > Just to be clear, in Pharo 7, if I want to get some code integrated: > - I *have to* use the pull request process described by Pavel > OR > - I *can* use the pull request process, but I can also use the old slice > monticello process > ? > > What is the answer to the first question now, and what will be the answer > of this question in 6 months from now ? > You should use the pull request process. It is possible to create a standard slice BUT it must be done from Pharo 6 and then sent into Pharo60Inbox. And then you need to wait until somebody converts this slice to pull request. That means that it will be harder and harder to contribute this way because the code-base is moving. No slice will be integrated into Pharo 7 with the old process directly. Cheers, -- Pavel > > Thanks > > > On Wed, Jun 28, 2017 at 3:42 PM, Ben Coman <btc(a)openinworld.com> wrote: > >> >> >> On Wed, Jun 28, 2017 at 3:46 PM, Juraj Kubelka <juraj.kubelka(a)icloud.com> >> wrote: >> >>> >>> El 28-06-2017, a las 02:57, Ben Coman <btc(a)openinworld.com> escribiÃ³: >>> >>> >>> >>> On Tue, Jun 27, 2017 at 10:35 PM, Pavel Krivanek < >>> pavel.krivanek(a)gmail.com> wrote: >>> >>>> >>>> >>>> 2017-06-27 16:17 GMT+02:00 Serge Stinckwich <serge.stinckwich(a)gmail.com >>>> >: >>>> >>>>> On Tue, Jun 27, 2017 at 3:10 PM, Pavel Krivanek >>>>> <pavel.krivanek(a)gmail.com> wrote: >>>>> > >>>>> > >>>>> > 2017-06-27 15:57 GMT+02:00 Serge Stinckwich < >>>>> serge.stinckwich(a)gmail.com>: >>>>> >> >>>>> >> On Mon, Jun 26, 2017 at 12:14 PM, Pavel Krivanek >>>>> >> <pavel.krivanek(a)gmail.com> wrote: >>>>> >> > Hi, >>>>> >> > >>>>> >> > this mail describes how to start to send pull requests to Pharo 7 >>>>> Github >>>>> >> > repository from Pharo 7. >>>>> >> >>>>> >> Thank you for the great explanation Pavel. >>>>> >> >>>>> >> > Preparations >>>>> >> > ===================== >>>>> >> > >>>>> >> > - you need to have a Github account and set SSH keys. See >>>>> >> > https://help.github.com/articles/connecting-to-github-with-ssh/ >>>>> >> > - create own pharo-project/pharo repository fork. Go to >>>>> >> > https://github.com/pharo-project/pharo, click on "Fork" button >>>>> and >>>>> >> > follow >>>>> >> > the instructions >>>>> >> >>>>> >> [ ... ] >>>>> >> >>>>> >> > Issue processing >>>>> >> > ===================== >>>>> >> > >>>>> >> > - create new case on FogBugz to get the issue number >>>>> >> > - open Iceberg and from the context menu on the 'pharo' >>>>> repository do: >>>>> >> > Pharo >>>>> >> > - Create new branch from FogBugz issue, enter the issue ID and it >>>>> will >>>>> >> > fill >>>>> >> > the full branch name for you >>>>> >> > - create your changes (you can do it before the creation of the >>>>> branch >>>>> >> > too) >>>>> >> > - commit and push your changes in Iceberg, this way you will >>>>> commit your >>>>> >> > branch to your fork repository. Remember that the Iceberg commit >>>>> window >>>>> >> > has >>>>> >> > two buttons, one for local commit, the second for commit with >>>>> immediate >>>>> >> > push. They can be very long because they contain the full branch >>>>> (issue) >>>>> >> > name >>>>> >> > - in Iceberg in the 'pharo' repository context menu do: Pharo - >>>>> Create >>>>> >> > pull >>>>> >> > request, fill your >>>>> >> > - fill your Github credentials >>>>> >> > - leave the PR title, comment is not required, check the pull >>>>> request >>>>> >> > head >>>>> >> > and base. The base MUST be pharo-project/pharo development. >>>>> Create the >>>>> >> > pull >>>>> >> > requests >>>>> >> > - go to https://github.com/pharo-project/pharo/pulls, check your >>>>> pull >>>>> >> > requests and put URL of it into the issue record on FogBugz (as a >>>>> >> > comment). >>>>> >> > Resolve the issue as Fix review needed >>>>> >> >>>>> >> It means, there is no PR without a corresponding FogBugz issue ? >>>>> > >>>>> > >>>>> > Yes, at least for code changes we would like to keep this relation. >>>>> If it is >>>>> > a really trivial change in readme or something like that, we can >>>>> accept no >>>>> > related issue record. >>>>> > Please prefer to comment the issues instead of PRs directly to have >>>>> all >>>>> > information at one place. >>>>> >>>>> Thank you Pavel for the explanation. >>>>> >>>>> Maybe in the future, it will make sense to put everything in the PR >>>>> and use github issues. >>>>> You will use CI travis builds for all PR ? >>>>> >>>> >>>> For now we will use FogBugz because it has a lot of nice features and >>>> good API. Maybe we will switch it in future but now we should not change >>>> too many things at once :-) >>>> For several reasons we now prefer to use own infrastructure for >>>> checking of PRs (mainly because of MacOS issues on Travis). But again, it >>>> can be changed in future. >>>> >>>> >>> It would be interesting to see how this might fit in with our workflow... >>> https://blog.fogcreek.com/fogbugz-github-integration/ >>> >>> >>> >>> What is the benefit of the integration? I do not understand it from the >>> given link. >>> >>> >> When you submit a PR on github, Fogbugz is automatically updated with a >> link to the PR. >> Presumably this makes it easier for people reviewing cases in Fogbugz to >> identify the slice to test. >> This is a better link... >> https://blog.fogcreek.com/improved-github-integration-automa >> tically-create-bug-events-with-commits/ >> >> cheers -ben >> > >

8 25

Segmentation fault Pharo 6.1 64bit vm - Ubuntu Linux - loading Metacello dependency
by Tim Mackinnon Aug. 7, 2017

Aug. 7, 2017

Hi - I just got a seg fault on my Gitlab CI server when trying to load a metacello baseline via the st command line hander. $ ./pharo Pharo.image --no-default-preferences --save --quit st loadLocal.st config.st "{'$AWS_ACCESS_KEY_ID'. '$AWS_SECRET_ACCESS_KEY'. '$AWS_DEFAULT_REGION'. '$S3_BUCKET'}" |& tee LoadLocal.log Fetched -> BaselineOfLambda-cypress.1 --- filetree:///builds/macta/PharoLambda/src [:] --- filetree:///builds/macta/PharoLambda/src Loaded -> BaselineOfLambda-cypress.1 --- filetree:///builds/macta/PharoLambda/src [:] --- filetree:///builds/macta/PharoLambda/src Loading baseline of BaselineOfLambda... Fetched -> BaselineOfAWS-ShoYoshida.12 --- github://newapplesho/aws-sdk-smalltalk:v1.10/pharo-repository [9149805:v1.10] --- github://newapplesho/aws-sdk-smalltalk:v1.10/pharo-repository Loaded -> BaselineOfAWS-ShoYoshida.12 --- github://newapplesho/aws-sdk-smalltalk:v1.10/pharo-repository [9149805:v1.10] --- github://newapplesho/aws-sdk-smalltalk:v1.10/pharo-repository Fetched -> ConfigurationOfZTimestamp-SvenVanCaekenberghe.25 --- http://mc.stfx.eu/Neo --- http://mc.stfx.eu/Neo Loaded -> ConfigurationOfZTimestamp-SvenVanCaekenberghe.25 --- http://mc.stfx.eu/Neo --- http://mc.stfx.eu/Neo Project: ZTimestamp stable [20] Fetched -> ZTimestamp-SvenVanCaekenberghe.57 --- http://mc.stfx.eu/Neo --- http://mc.stfx.eu/Neo Project: AWS baseline Segmentation fault Mon Jul 31 22:18:27 2017 /builds/macta/PharoLambda/build/pharo-vm/lib/pharo/5.0-201707201942/pharo Pharo VM version: 5.0-201707201942 Thu Jul 20 20:42:13 UTC 2017 gcc 4.6.3 [Production Spur 64-bit ITHB VM] Built from: CoInterpreter VMMaker.oscog-eem.2254 uuid: 4f2c2cce-f4a2-469a-93f1-97ed941df0ad Jul 20 2017 With: StackToRegisterMappingCogit VMMaker.oscog-eem.2252 uuid: 2f3e9b0e-ecd3-4adf-b092-cce2e2587a5c Jul 20 2017 Revision: VM: 201707201942 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Date: Thu Jul 20 12:42:21 2017 -0700 $ Plugins: 201707201942 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Build host: Linux testing-gce-2c303f4c-2b90-4f17-b8b9-ec690d977073 3.13.0-115-generic #162~precise1-Ubuntu SMP Fri Mar 24 16:47:06 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux plugin path: /builds/macta/PharoLambda/build/pharo-vm/lib/pharo/5.0-201707201942 [default: /builds/macta/PharoLambda/build/pharo-vm/lib/pharo/5.0-201707201942/] C stack backtrace & registers: rax 0xa41278c0 rbx 0xa4127750 rcx 0xa4127978 rdx 0xa4127808 rdi 0xa4127528 rsi 0xa4127528 rbp 0xa4127698 rsp 0xa4127a30 r8 0xa4126f68 r9 0xa4127020 r10 0xa41270d8 r11 0xa4127190 r12 0xa4127248 r13 0xa4127300 r14 0xa41273b8 r15 0xa4127470 rip 0xa4127ae8 *[0x7fffa4127ae8] /builds/macta/PharoLambda/build/pharo-vm/lib/pharo/5.0-201707201942/pharo[0x41cd91] /builds/macta/PharoLambda/build/pharo-vm/lib/pharo/5.0-201707201942/pharo[0x41d11f] /lib/x86_64-linux-gnu/libpthread.so.0(+0x11670)[0x7efe11ad9670] /builds/macta/PharoLambda/build/pharo-vm/lib/pharo/5.0-201707201942/pharo[0x43645f] /builds/macta/PharoLambda/build/pharo-vm/lib/pharo/5.0-201707201942/pharo(ceBaseFrameReturn+0xc1)[0x45bec1] [0x260124e] [0x0] Smalltalk stack dump: Most recent primitives stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: compare:with:collated: stringHash:initialHash: stringHash:initialHash: basicAtLeast: basicAtLeast: new: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: compare:with:collated: stringHash:initialHash: compare:with:collated: compare:with:collated: stringHash:initialHash: stringHash:initialHash: compare:with:collated: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: compare:with:collated: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: compare:with:collated: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: compare:with:collated: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: compare:with:collated: stringHash:initialHash: compare:with:collated: stringHash:initialHash: compare:with:collated: stringHash:initialHash: stringHash:initialHash: compare:with:collated: stringHash:initialHash: compare:with:collated: stringHash:initialHash: compare:with:collated: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: compare:with:collated: stringHash:initialHash: compare:with:collated: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: compare:with:collated: compare:with:collated: stringHash:initialHash: stringHash:initialHash: compare:with:collated: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: compare:with:collated: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: compare:with:collated: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: compare:with:collated: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: compare:with:collated: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: compare:with:collated: compare:with:collated: stringHash:initialHash: compare:with:collated: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: compare:with:collated: compare:with:collated: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: compare:with:collated: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: compare:with:collated: compare:with:collated: compare:with:collated: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: compare:with:collated: compare:with:collated: stringHash:initialHash: compare:with:collated: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: compare:with:collated: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: compare:with:collated: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stack page bytes 8192 available headroom 5576 minimum unused headroom 5976 The script being run was - and it segâd on the first Metacello invocation when reading in a dependent spec. "CmdLine script to load project" | stdout | stdout := FileStream stdout wantsLineEndConversion: true; converter; yourself. "Add missing STON dependency in minimal image" Smalltalk at: #STON ifAbsent: [ stdout nextPutAll: 'Loading missing STON'; cr. Gofer new url: 'http://ss3.gemstone.com/ss/STON'; package: 'STON-Core'; load. "Fix-up issue with Undeclared not firing a change in minimal image" { MCFileTreeRepository. MCFileTreeStCypressReader. MCFileTreeAbstractReader } do: [:c | c compileAll ] ]. "Create a stub TestCase (if needed) for packages not minimally defined" Smalltalk at: #TestCase ifAbsent: [ stdout nextPutAll: 'Creating missing TestCase'; cr. Object subclass: #TestCase ]. Metacello new repository: 'filetree://../src'; baseline: 'Lambda'; load. Metacello new repository: 'filetree://../src'; baseline: 'LambdaRuntime'; load. Smalltalk at: #IceRepositoriesBrowser ifPresent: [ :i | stdout nextPutAll: 'Removing rogue ', i name; cr. i allInstances do: [:b | b become: String new ]]. Smalltalk at: #OmSessionStore ifPresent: [ :i | stdout nextPutAll: 'Unregistering ', i name; cr. SessionManager default unregisterClassNamed: i name ]. SmalltalkImage current garbageCollect.

2 2

Epicea: Revert the removal of a class
by Cyril Ferlicot D. Aug. 2, 2017

Aug. 2, 2017

Hi, Today I tried to remove a class, go in Epicea and revert the removal of the class. At the end the class was here but with no methods. Is that the normal behaviour? I think it is a bug but since I don't really use Epicea a lot for know I am not sure. Have a nice day. -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

3 2

Calypso browser and categories?
by Mariano Martinez Peck Aug. 2, 2017

Aug. 2, 2017

Hi Denis, I wanted to give a serious test to Calypso, that is, start using it all day long. However, there is a critical thing I am missing, which is the grouping of categories (inside packages). I do not want to start discussing again packages vs categories and what are good and bad practices. I do have a few packages and each package may have several categories inside. So... seeing all classes together inside a package is not nice for me. Is there a way in calypso to auto-escope to category level? I mean... say my package is XXX and I have categories XXX-A and XXX-B. I know I can go to left side column and with the tree, I can go to XXX-A and I get what I want. But, for example, when I browse a class of XXX-A, the "focus" of the left side column is XXX and not XXX-A. So I am wondering if we can make it auto-scope to the category everywhere in Calypso. Thanks in advance, -- Mariano http://marianopeck.wordpress.com

2 8