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

Re: [Pharo-dev] Distributing native libraries with Metacello

by HernÃ¡n Morales Durand

Hi Ronie, Have a look at: https://github.com/hernanmd/MetacelloFileDownload Best regards, HernÃ¡n 2017-12-26 22:43 GMT-03:00 Ronie Salgado <roniesalg(a)gmail.com>: > Hi All, > > During the last month I have been doing a massive refactoring to Woden 2. By > using Lowtalk for the math library, the requirement on the Lowcode VM is now > optional. However, there are still some native library dependencies required > for distributing Woden: > - AbstractGpu, a wrapper for graphics API (Vulkan, Metal and D3D12). > - AbstracPhysicsa wrapper for physics engines (Bullet). > > I saw that when loading Bloc via the Metacello script, it does download the > Moz2D dependency. So, I am wondering how I could do the same for Woden?. > > There is also a dependency on the data present in a repository with some > core assets, mostly the required shaders, and some textures. I am also > wondering wondering on how I could tell Metacello to clone this repository, > or download its zip file from GitHub? > > Best regards, > Ronie

Dec. 27, 2017

Distributing native libraries with Metacello

by Ronie Salgado

Hi All, During the last month I have been doing a massive refactoring to Woden 2. By using Lowtalk for the math library, the requirement on the Lowcode VM is now optional. However, there are still some native library dependencies required for distributing Woden: - AbstractGpu, a wrapper for graphics API (Vulkan, Metal and D3D12). - AbstracPhysicsa wrapper for physics engines (Bullet). I saw that when loading Bloc via the Metacello script, it does download the Moz2D dependency. So, I am wondering how I could do the same for Woden?. There is also a dependency on the data present in a repository with some core assets, mostly the required shaders, and some textures. I am also wondering wondering on how I could tell Metacello to clone this repository, or download its zip file from GitHub? Best regards, Ronie

Dec. 27, 2017

Re: [Pharo-dev] Calendrical capabilities

by Paul DeBruicker

There is a port to Pharo (and gemstone) of Chronos here: http://smalltalkhub.com/#!/~Chronos/Chronos I think I last tested it in Pharo 4. publius789 wrote > This is very helpful. Nice holiday weekend reading! > > Sure, if its not too much trouble you can send it to me. > > Thanks. > > Regards, > Jim > > -----Original Message----- > From: Pharo-dev [mailto: > pharo-dev-bounces@.pharo > ] On Behalf Of Stephane Ducasse > Sent: Saturday, December 23, 2017 5:02 PM > To: Pharo Development List < > pharo-dev@.pharo > > > Subject: Re: [Pharo-dev] Calendrical capabilities > > Aconcagua is available via the catalog. > Here is what I found in my harddisc about chronos. > I can send you the zipped file with old code (probably should be ported to > Pharo). > > > On Sat, Dec 23, 2017 at 10:32 PM, < > publius789@ > > wrote: >> I am new to the Pharo world and looking at capabilities for potential >> applications. >> >> >> >> One of the first things I am interested in is Calendar processing >> capabilities. I havenât had a chance to look at the code yet, but >> specifically how much does Pharoâs Date/Calendar capabilities match >> that in the java.util package for Java 9? Additionally, is there any >> way to give the number of business days between two dates for a >> particular local calendar? If so, whatâs the format for a local >> calendar? >> >> >> >> Iâm going to take a look at the code shortly, but if anyone can shed a >> general light what currently exists it would be greatly appreciated. >> >> >> >> Regards, >> >> Jim -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Dec. 27, 2017

Re: [Pharo-dev] roundUpTo:? truncatedTo:

by Nicolas Cellier

Hi Hilaire, it' not just funny: it's the exact case round: was made for. Note that there is an opened issue suggesting the removal of round: (no time to check the exact ref now). Alternatives if round: is deprecated could be: (c / 255 roundTo: 1/1000) asFloat. (c / 255 roundTo: 0.001s) asFloat. I didn't verify if Pharo did change that, but Squeak RGB color components have 10 bits internally. 10 bits is 1024. So rounding to 1/1000 was not enough to distinguish different colors. Nicolas 2017-12-26 22:26 GMT+01:00 Hilaire <hilaire(a)drgeo.eu>: > It i s funny to note how #round: message seems to have more success for > that: > > 0.9420000000001 round: 3. > "0.942" > > > > Le 26/12/2017 Ã 21:27, Stephane Ducasse a Ã©crit : > >> 0.9420000000001 roundUpTo: 0.001 >> and the same truncatedTo: 0.001 >> do not work >> > > -- > Dr. Geo > http://drgeo.eu > > > >

Dec. 26, 2017

Re: [Pharo-dev] How to restore image upgrade? was New Year Wishlist (2018) ?

by Nicolas Cellier

2017-12-25 23:54 GMT+01:00 Ben Coman <btc(a)openinworld.com>: > As a half-way house, consider that "upgrade" scripts could be a good > mechanism > post-Release when changes should be less-deep/less-arduous on the system. > This might avoid Esteban's time being needed to re-Release for each > upgrade, > with post-Release moving to a more community supported mechanism. > This could scale better as we gain more users interested in long term > support > of their applications on a stable-release than the moving target of the > development-edge. > > cheers -ben > Hi Ben, upgrade scripts is what is used by Squeak trunk (as available via Monticello). it's difficult to write correctly, and difficult to test (clearly a job for a bot). Every intermediate script has to be replayed (or not, but who knows?) and this is done via MonticelloConfigurationMap. Can you imagine that transposed to git? It's not reversible (we don't provide the reverse scripts). It might fail due to specific changes in the image (let's say dirty workspace), and not only code changes. So it's very very far from git smoothness. Fortunately, those scripts are rarely needed (as a percentage of commits). Unfortunately, they are regularly needed (several times a year). Remind that Pharo is supposed to change Kernel classes a bit faster than Squeak ;) > On 25 December 2017 at 23:11, Stephane Ducasse <stepharo.self(a)gmail.com> > wrote: > >> Nicolas >> >> We want to keep the live part of Pharo and incremental loading and it >> is key for us. Now we should not be naive. >> > Hi Steph, Not every provocation deserves an answer ;) I hope everyone here wants a lively thing, otherwise why use Pharo? > Most of the time we do not have the garantee that a change will work >> when loaded. >> >> We have bots passing tests for rejecting broken code. But the problem is that correct code can also be rejected We proposed Pablo to work since two years on a really working dynamic >> code loader and >> Pablo has really nice results. But it takes time to evaluate if/how we >> integrate its changes. >> Pablo has an atomic coder loader and an incremental and modular class >> builder. >> He also designed a modular shutdown/startup list manager (in production). >> >> Glad to ear that. I hope to read publications on this subject one day then. Two years for nice intermediate results just confirms that the problem is very tough as we all know... We want to be able to have a **real** and robust incremental load. >> Right now as you know it and as in ANY smalltalk I can break the >> system super easily. >> There is no magic. I do not see how we can make sure that any piece of >> code will be loaded >> and do not break the system. >> So our objective is to have a new infrastructure that we can updates >> (like method hashes for example without having to >> twists our mind and do five updates). >> >> Now about git, we want and we will have our lovely image as a working >> directory but this requires engineering >> because the image is another artefact that other languages do not have >> to worry. >> We will get there. >> >> Agree with all you said, My point is that git is not going to help you solving the problems others don't have. If we have seemless integration for bootstrap free code, that will already be something... For the rest, it's a bit too much wishful thinking to my taste. As said above, because bootstrap problems happen rarely, but regularly, I can predict that pharo development won't be as smooth as dreamed of for some time. We have to accept that and work hard to find acceptable trade offs. I'm interested in seeing which solution will emerge. Stef >> >> >> On Sun, Dec 24, 2017 at 11:41 PM, Nicolas Cellier >> <nicolas.cellier.aka.nice(a)gmail.com> wrote: >> > >> > >> > 2017-12-24 2:59 GMT+01:00 Alexandre Bergel <alexandre.bergel(a)me.com>: >> >> >> >> My four wishes, in no particular order: >> >> - Better code completion >> >> - Git in Pharo as easy as using Git for other languages >> > >> > The recipe is easy: turn pharo into a file based edit-compile-run >> language >> > and expunge those live object burden ;) >> > Let me explain why it's not just trolling. >> > Currently we have to download an image made by a bot. >> > Pharo has gradually lost the power to upgrade the image (it's not new). >> > >> > If we recognize that an image acts like a workspace, and want to let the >> > pull/branch switch/etc work again... >> > IOW going from one point to any other in source code graph >> > and experience the full power of git like any other language, >> > that means, in a live IDE, at least solving those two problems: >> > - changing the tools that are used to upgrade the image (Compiler, >> > MethodDictionary, Array, etc...) >> > - correctly initialize all the states (including stange loops) >> > If pharo has not managed to solve this with a linear one way history >> (the >> > regularly broken update image option), >> > how do you think this is going to be solved in the more general case? >> > I call this the universal boostrap problem. >> > >> > IMO the logical next step is to separate the IDE >> > (the Inanimate Desintegrated Environment of any other language). >> > >> > Maybe we don't have to bend Pharo too much to git if it does not fit. >> > The goal: as easy might be not that easy. >> > >> > >> >> - Bloc on Steroid >> >> - Being able to interrupt any process and endless loop using >> Cmd-. >> >> >> >> Merry Christmas to all of you! >> >> Alexandre >> >> >> >> >> >> >> >> > On Dec 23, 2017, at 1:58 PM, Esteban Lorenzano <estebanlm(a)gmail.com> >> >> > wrote: >> >> > >> >> > Hi everybody, >> >> > >> >> > This looks like a good moment of the year to ask all of you what >> would >> >> > you want to see in Pharo next year. >> >> > Features, improvements, radical changes, etcâ¦. whatever you want. >> >> > >> >> > Of course, this list will not be a roadmap and it does not means we >> will >> >> > implement all of it (as always, time drives our possibilities), but >> is a >> >> > good moment for us a a community to check where we are and where we >> wan to >> >> > go next :) >> >> > >> >> > So, letâs those wishes come! >> >> > >> >> > cheers, >> >> > Esteban >> >> >> >> >> > >> >> >

Dec. 26, 2017

Re: [Pharo-dev] roundUpTo:? truncatedTo:

by Hilaire

It i s funny to note how #round: message seems to have more success for that: 0.9420000000001 round: 3. Â "0.942" Le 26/12/2017 Ã 21:27, Stephane Ducasse a Ã©critÂ : > 0.9420000000001 roundUpTo: 0.001 > and the same truncatedTo: 0.001 > do not work -- Dr. Geo http://drgeo.eu

Dec. 26, 2017

Re: [Pharo-dev] Simple game framework

by Stephane Ducasse

Hi Hilaire yes you can have multiple approaches. I was focusing on tiles-based ones: sokoban, miners.. SDL2.0 is our plan. For Cairo we asked Bloc guys to make sure that we can use Cairo as back end to avoid to have 20 mb by default with Mozz2d (and mozz2d is not really packaged by their creators so high risk) so Cairo should stay around. Now I would like to use Bloc for tile based games. Stef On Tue, Dec 26, 2017 at 4:19 PM, Hilaire <hilaire(a)drgeo.eu> wrote: > Read. SDL + Cairo is the way you have been. I did not imagine Cairo was good > at manipulating block of bitmap. > > Is Cairo stable over time in Pharo? I wonder will it be wiped out. More > generally, I wonder what is the stable ground to build graphic application > on Pharo? > > > Le 25/12/2017 Ã 19:32, ClÃ©ment Bera a Ã©crit : >> >> See those ReadMe: >> >> https://github.com/clementbera/wizard-battle-arena >> >> https://github.com/clementbera/SpiderInvasion >> >> Audio has always been a problem to me. I successfully run audio files with >> the open AL binding, but I failed to do so cross-platform. Already >> key-bindings coherent cross platform is difficult. >> >> Cheers > > > -- > Dr. Geo > http://drgeo.eu > > >

Dec. 26, 2017

Re: [Pharo-dev] New Year Wishlist (2018) ?

by Stephane Ducasse

Hi Evan yes thierry was discussing with clement and we will see :). Stef On Mon, Dec 25, 2017 at 6:55 PM, Evan Donahue <emdonahu(a)gmail.com> wrote: > Given the recent stirrings of AI-related applications in Pharo, I guess I'm > wishing for vm support for vector operations/fast math. I heard something > about that a while ago on the polymath chanel, so I figure it can't hurt to > wish. > > Evan > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >

Dec. 26, 2017

Re: [Pharo-dev] New Year Wishlist (2018) ?

by Stephane Ducasse

Yes saw and my second answer took that into account. We were discussing about making sure that we can write applications vs. code. We should be able to package an application. The experience accumulated with the launcher and the effort on making Pharo silent (not forcing to write everywhere files) are in that direction too. Stef On Mon, Dec 25, 2017 at 6:25 PM, Hilaire <hilaire(a)drgeo.eu> wrote: > I really don't mean a GUI builder :-) > > > Le 25/12/2017 Ã 15:57, Stephane Ducasse a Ã©crit : >>> >>> 4. application builder. Smalltalk/X has a GUI to build a standalone >>> application, was not able to get it working, but it probably worked at >>> some >>> time in the past (see screenshot). Such a feature in Pharo will be >>> fantastic, and likely a kill feature for the ones developing stand alone >>> application; yes there are still some;-) >> >> We would like the same. Now spec was an increment in that direction >> because behind the UI builder you need to reuse the model. So >> with a pass on spec we will be set to be able to build the builder part >> > > -- > Dr. Geo > http://drgeo.eu > > >

Dec. 26, 2017

roundUpTo:? truncatedTo:

by Stephane Ducasse

Hi I'm working on improving the number of named colors we have. I got this list And I did the following to convert numbers to float and I want to keep only max three decimal Now I do not get 0.9420000000001 roundUpTo: 0.001 and the same truncatedTo: 0.001 do not work list collect: [ :each | | split color name | split := Character tab split: each. color := Character space split: (split at: 1). color := color select: [ :c| c isNotEmpty ]. color := color collect: [ :c | (c asInteger / 255) asFloat roundUpTo: 0.001 ]. name := split at: 3. {name asSymbol. color asArray} ] as: Array (Character cr split: '255 250 250 snow 248 248 255 ghost white 248 248 255 GhostWhite 245 245 245 white smoke 245 245 245 WhiteSmoke 220 220 220 gainsboro 255 250 240 floral white 255 250 240 FloralWhite 253 245 230 old lace 253 245 230 OldLace 250 240 230 linen 250 235 215 antique white 250 235 215 AntiqueWhite 255 239 213 papaya whip 255 239 213 PapayaWhip 255 235 205 blanched almond 255 235 205 BlanchedAlmond 255 228 196 bisque 255 218 185 peach puff 255 218 185 PeachPuff 255 222 173 navajo white 255 222 173 NavajoWhite 255 228 181 moccasin 255 248 220 cornsilk 255 255 240 ivory 255 250 205 lemon chiffon 255 250 205 LemonChiffon 255 245 238 seashell 240 255 240 honeydew 245 255 250 mint cream 245 255 250 MintCream 240 255 255 azure 240 248 255 alice blue 240 248 255 AliceBlue 230 230 250 lavender 255 240 245 lavender blush 255 240 245 LavenderBlush 255 228 225 misty rose 255 228 225 MistyRose 255 255 255 white 0 0 0 black 47 79 79 dark slate gray 47 79 79 DarkSlateGray 47 79 79 dark slate grey 47 79 79 DarkSlateGrey 105 105 105 dim gray 105 105 105 DimGray 105 105 105 dim grey 105 105 105 DimGrey 112 128 144 slate gray 112 128 144 SlateGray 112 128 144 slate grey 112 128 144 SlateGrey 119 136 153 light slate gray 119 136 153 LightSlateGray 119 136 153 light slate grey 119 136 153 LightSlateGrey 190 190 190 gray 190 190 190 grey 211 211 211 light grey 211 211 211 LightGrey 211 211 211 light gray 211 211 211 LightGray 25 25 112 midnight blue 25 25 112 MidnightBlue 0 0 128 navy 0 0 128 navy blue 0 0 128 NavyBlue 100 149 237 cornflower blue 100 149 237 CornflowerBlue 72 61 139 dark slate blue 72 61 139 DarkSlateBlue 106 90 205 slate blue 106 90 205 SlateBlue 123 104 238 medium slate blue 123 104 238 MediumSlateBlue 132 112 255 light slate blue 132 112 255 LightSlateBlue 0 0 205 medium blue 0 0 205 MediumBlue 65 105 225 royal blue 65 105 225 RoyalBlue 0 0 255 blue 30 144 255 dodger blue 30 144 255 DodgerBlue 0 191 255 deep sky blue 0 191 255 DeepSkyBlue 135 206 235 sky blue 135 206 235 SkyBlue 135 206 250 light sky blue 135 206 250 LightSkyBlue 70 130 180 steel blue 70 130 180 SteelBlue 176 196 222 light steel blue 176 196 222 LightSteelBlue 173 216 230 light blue 173 216 230 LightBlue 176 224 230 powder blue 176 224 230 PowderBlue 175 238 238 pale turquoise 175 238 238 PaleTurquoise 0 206 209 dark turquoise 0 206 209 DarkTurquoise 72 209 204 medium turquoise 72 209 204 MediumTurquoise 64 224 208 turquoise 0 255 255 cyan 224 255 255 light cyan 224 255 255 LightCyan 95 158 160 cadet blue 95 158 160 CadetBlue 102 205 170 medium aquamarine 102 205 170 MediumAquamarine 127 255 212 aquamarine 0 100 0 dark green 0 100 0 DarkGreen 85 107 47 dark olive green 85 107 47 DarkOliveGreen 143 188 143 dark sea green 143 188 143 DarkSeaGreen 46 139 87 sea green 46 139 87 SeaGreen 60 179 113 medium sea green 60 179 113 MediumSeaGreen 32 178 170 light sea green 32 178 170 LightSeaGreen 152 251 152 pale green 152 251 152 PaleGreen 0 255 127 spring green 0 255 127 SpringGreen 124 252 0 lawn green 124 252 0 LawnGreen 0 255 0 green 127 255 0 chartreuse 0 250 154 medium spring green 0 250 154 MediumSpringGreen 173 255 47 green yellow 173 255 47 GreenYellow 50 205 50 lime green 50 205 50 LimeGreen 154 205 50 yellow green 154 205 50 YellowGreen 34 139 34 forest green 34 139 34 ForestGreen 107 142 35 olive drab 107 142 35 OliveDrab 189 183 107 dark khaki 189 183 107 DarkKhaki 240 230 140 khaki 238 232 170 pale goldenrod 238 232 170 PaleGoldenrod 250 250 210 light goldenrod yellow 250 250 210 LightGoldenrodYellow 255 255 224 light yellow 255 255 224 LightYellow 255 255 0 yellow 255 215 0 gold 238 221 130 light goldenrod 238 221 130 LightGoldenrod 218 165 32 goldenrod 184 134 11 dark goldenrod 184 134 11 DarkGoldenrod 188 143 143 rosy brown 188 143 143 RosyBrown 205 92 92 indian red 205 92 92 IndianRed 139 69 19 saddle brown 139 69 19 SaddleBrown 160 82 45 sienna 205 133 63 peru 222 184 135 burlywood 245 245 220 beige 245 222 179 wheat 244 164 96 sandy brown 244 164 96 SandyBrown 210 180 140 tan 210 105 30 chocolate 178 34 34 firebrick 165 42 42 brown 233 150 122 dark salmon 233 150 122 DarkSalmon 250 128 114 salmon 255 160 122 light salmon 255 160 122 LightSalmon 255 165 0 orange 255 140 0 dark orange 255 140 0 DarkOrange 255 127 80 coral 240 128 128 light coral 240 128 128 LightCoral 255 99 71 tomato 255 69 0 orange red 255 69 0 OrangeRed 255 0 0 red 255 105 180 hot pink 255 105 180 HotPink 255 20 147 deep pink 255 20 147 DeepPink 255 192 203 pink 255 182 193 light pink 255 182 193 LightPink 219 112 147 pale violet red 219 112 147 PaleVioletRed 176 48 96 maroon 199 21 133 medium violet red 199 21 133 MediumVioletRed 208 32 144 violet red 208 32 144 VioletRed 255 0 255 magenta 238 130 238 violet 221 160 221 plum 218 112 214 orchid 186 85 211 medium orchid 186 85 211 MediumOrchid 153 50 204 dark orchid 153 50 204 DarkOrchid 148 0 211 dark violet 148 0 211 DarkViolet 138 43 226 blue violet 138 43 226 BlueViolet 160 32 240 purple 147 112 219 medium purple 147 112 219 MediumPurple 216 191 216 thistle 255 250 250 snow1 238 233 233 snow2 205 201 201 snow3 139 137 137 snow4 255 245 238 seashell1 238 229 222 seashell2 205 197 191 seashell3 139 134 130 seashell4 255 239 219 AntiqueWhite1 238 223 204 AntiqueWhite2 205 192 176 AntiqueWhite3 139 131 120 AntiqueWhite4 255 228 196 bisque1 238 213 183 bisque2 205 183 158 bisque3 139 125 107 bisque4 255 218 185 PeachPuff1 238 203 173 PeachPuff2 205 175 149 PeachPuff3 139 119 101 PeachPuff4 255 222 173 NavajoWhite1 238 207 161 NavajoWhite2 205 179 139 NavajoWhite3 139 121 94 NavajoWhite4 255 250 205 LemonChiffon1 238 233 191 LemonChiffon2 205 201 165 LemonChiffon3 139 137 112 LemonChiffon4 255 248 220 cornsilk1 238 232 205 cornsilk2 205 200 177 cornsilk3 139 136 120 cornsilk4 255 255 240 ivory1 238 238 224 ivory2 205 205 193 ivory3 139 139 131 ivory4 240 255 240 honeydew1 224 238 224 honeydew2 193 205 193 honeydew3 131 139 131 honeydew4 255 240 245 LavenderBlush1 238 224 229 LavenderBlush2 205 193 197 LavenderBlush3 139 131 134 LavenderBlush4 255 228 225 MistyRose1 238 213 210 MistyRose2 205 183 181 MistyRose3 139 125 123 MistyRose4 240 255 255 azure1 224 238 238 azure2 193 205 205 azure3 131 139 139 azure4 131 111 255 SlateBlue1 122 103 238 SlateBlue2 105 89 205 SlateBlue3 71 60 139 SlateBlue4 72 118 255 RoyalBlue1 67 110 238 RoyalBlue2 58 95 205 RoyalBlue3 39 64 139 RoyalBlue4 0 0 255 blue1 0 0 238 blue2 0 0 205 blue3 0 0 139 blue4 30 144 255 DodgerBlue1 28 134 238 DodgerBlue2 24 116 205 DodgerBlue3 16 78 139 DodgerBlue4 99 184 255 SteelBlue1 92 172 238 SteelBlue2 79 148 205 SteelBlue3 54 100 139 SteelBlue4 0 191 255 DeepSkyBlue1 0 178 238 DeepSkyBlue2 0 154 205 DeepSkyBlue3 0 104 139 DeepSkyBlue4 135 206 255 SkyBlue1 126 192 238 SkyBlue2 108 166 205 SkyBlue3 74 112 139 SkyBlue4 176 226 255 LightSkyBlue1 164 211 238 LightSkyBlue2 141 182 205 LightSkyBlue3 96 123 139 LightSkyBlue4 198 226 255 SlateGray1 185 211 238 SlateGray2 159 182 205 SlateGray3 108 123 139 SlateGray4 202 225 255 LightSteelBlue1 188 210 238 LightSteelBlue2 162 181 205 LightSteelBlue3 110 123 139 LightSteelBlue4 191 239 255 LightBlue1 178 223 238 LightBlue2 154 192 205 LightBlue3 104 131 139 LightBlue4 224 255 255 LightCyan1 209 238 238 LightCyan2 180 205 205 LightCyan3 122 139 139 LightCyan4 187 255 255 PaleTurquoise1 174 238 238 PaleTurquoise2 150 205 205 PaleTurquoise3 102 139 139 PaleTurquoise4 152 245 255 CadetBlue1 142 229 238 CadetBlue2 122 197 205 CadetBlue3 83 134 139 CadetBlue4 0 245 255 turquoise1 0 229 238 turquoise2 0 197 205 turquoise3 0 134 139 turquoise4 0 255 255 cyan1 0 238 238 cyan2 0 205 205 cyan3 0 139 139 cyan4 151 255 255 DarkSlateGray1 141 238 238 DarkSlateGray2 121 205 205 DarkSlateGray3 82 139 139 DarkSlateGray4 127 255 212 aquamarine1 118 238 198 aquamarine2 102 205 170 aquamarine3 69 139 116 aquamarine4 193 255 193 DarkSeaGreen1 180 238 180 DarkSeaGreen2 155 205 155 DarkSeaGreen3 105 139 105 DarkSeaGreen4 84 255 159 SeaGreen1 78 238 148 SeaGreen2 67 205 128 SeaGreen3 46 139 87 SeaGreen4 154 255 154 PaleGreen1 144 238 144 PaleGreen2 124 205 124 PaleGreen3 84 139 84 PaleGreen4 0 255 127 SpringGreen1 0 238 118 SpringGreen2 0 205 102 SpringGreen3 0 139 69 SpringGreen4 0 255 0 green1 0 238 0 green2 0 205 0 green3 0 139 0 green4 127 255 0 chartreuse1 118 238 0 chartreuse2 102 205 0 chartreuse3 69 139 0 chartreuse4 192 255 62 OliveDrab1 179 238 58 OliveDrab2 154 205 50 OliveDrab3 105 139 34 OliveDrab4 202 255 112 DarkOliveGreen1 188 238 104 DarkOliveGreen2 162 205 90 DarkOliveGreen3 110 139 61 DarkOliveGreen4 255 246 143 khaki1 238 230 133 khaki2 205 198 115 khaki3 139 134 78 khaki4 255 236 139 LightGoldenrod1 238 220 130 LightGoldenrod2 205 190 112 LightGoldenrod3 139 129 76 LightGoldenrod4 255 255 224 LightYellow1 238 238 209 LightYellow2 205 205 180 LightYellow3 139 139 122 LightYellow4 255 255 0 yellow1 238 238 0 yellow2 205 205 0 yellow3 139 139 0 yellow4 255 215 0 gold1 238 201 0 gold2 205 173 0 gold3 139 117 0 gold4 255 193 37 goldenrod1 238 180 34 goldenrod2 205 155 29 goldenrod3 139 105 20 goldenrod4 255 185 15 DarkGoldenrod1 238 173 14 DarkGoldenrod2 205 149 12 DarkGoldenrod3 139 101 8 DarkGoldenrod4 255 193 193 RosyBrown1 238 180 180 RosyBrown2 205 155 155 RosyBrown3 139 105 105 RosyBrown4 255 106 106 IndianRed1 238 99 99 IndianRed2 205 85 85 IndianRed3 139 58 58 IndianRed4 255 130 71 sienna1 238 121 66 sienna2 205 104 57 sienna3 139 71 38 sienna4 255 211 155 burlywood1 238 197 145 burlywood2 205 170 125 burlywood3 139 115 85 burlywood4 255 231 186 wheat1 238 216 174 wheat2 205 186 150 wheat3 139 126 102 wheat4 255 165 79 tan1 238 154 73 tan2 205 133 63 tan3 139 90 43 tan4 255 127 36 chocolate1 238 118 33 chocolate2 205 102 29 chocolate3 139 69 19 chocolate4 255 48 48 firebrick1 238 44 44 firebrick2 205 38 38 firebrick3 139 26 26 firebrick4 255 64 64 brown1 238 59 59 brown2 205 51 51 brown3 139 35 35 brown4 255 140 105 salmon1 238 130 98 salmon2 205 112 84 salmon3 139 76 57 salmon4 255 160 122 LightSalmon1 238 149 114 LightSalmon2 205 129 98 LightSalmon3 139 87 66 LightSalmon4 255 165 0 orange1 238 154 0 orange2 205 133 0 orange3 139 90 0 orange4 255 127 0 DarkOrange1 238 118 0 DarkOrange2 205 102 0 DarkOrange3 139 69 0 DarkOrange4 255 114 86 coral1 238 106 80 coral2 205 91 69 coral3 139 62 47 coral4 255 99 71 tomato1 238 92 66 tomato2 205 79 57 tomato3 139 54 38 tomato4 255 69 0 OrangeRed1 238 64 0 OrangeRed2 205 55 0 OrangeRed3 139 37 0 OrangeRed4 255 0 0 red1 238 0 0 red2 205 0 0 red3 139 0 0 red4 255 20 147 DeepPink1 238 18 137 DeepPink2 205 16 118 DeepPink3 139 10 80 DeepPink4 255 110 180 HotPink1 238 106 167 HotPink2 205 96 144 HotPink3 139 58 98 HotPink4 255 181 197 pink1 238 169 184 pink2 205 145 158 pink3 139 99 108 pink4 255 174 185 LightPink1 238 162 173 LightPink2 205 140 149 LightPink3 139 95 101 LightPink4 255 130 171 PaleVioletRed1 238 121 159 PaleVioletRed2 205 104 137 PaleVioletRed3 139 71 93 PaleVioletRed4 255 52 179 maroon1 238 48 167 maroon2 205 41 144 maroon3 139 28 98 maroon4 255 62 150 VioletRed1 238 58 140 VioletRed2 205 50 120 VioletRed3 139 34 82 VioletRed4 255 0 255 magenta1 238 0 238 magenta2 205 0 205 magenta3 139 0 139 magenta4 255 131 250 orchid1 238 122 233 orchid2 205 105 201 orchid3 139 71 137 orchid4 255 187 255 plum1 238 174 238 plum2 205 150 205 plum3 139 102 139 plum4 224 102 255 MediumOrchid1 209 95 238 MediumOrchid2 180 82 205 MediumOrchid3 122 55 139 MediumOrchid4 191 62 255 DarkOrchid1 178 58 238 DarkOrchid2 154 50 205 DarkOrchid3 104 34 139 DarkOrchid4 155 48 255 purple1 145 44 238 purple2 125 38 205 purple3 85 26 139 purple4 171 130 255 MediumPurple1 159 121 238 MediumPurple2 137 104 205 MediumPurple3 93 71 139 MediumPurple4 255 225 255 thistle1 238 210 238 thistle2 205 181 205 thistle3 139 123 139 thistle4 0 0 0 gray0 0 0 0 grey0 3 3 3 gray1 3 3 3 grey1 5 5 5 gray2 5 5 5 grey2 8 8 8 gray3 8 8 8 grey3 10 10 10 gray4 10 10 10 grey4 13 13 13 gray5 13 13 13 grey5 15 15 15 gray6 15 15 15 grey6 18 18 18 gray7 18 18 18 grey7 20 20 20 gray8 20 20 20 grey8 23 23 23 gray9 23 23 23 grey9 26 26 26 gray10 26 26 26 grey10 28 28 28 gray11 28 28 28 grey11 31 31 31 gray12 31 31 31 grey12 33 33 33 gray13 33 33 33 grey13 36 36 36 gray14 36 36 36 grey14 38 38 38 gray15 38 38 38 grey15 41 41 41 gray16 41 41 41 grey16 43 43 43 gray17 43 43 43 grey17 46 46 46 gray18 46 46 46 grey18 48 48 48 gray19 48 48 48 grey19 51 51 51 gray20 51 51 51 grey20 54 54 54 gray21 54 54 54 grey21 56 56 56 gray22 56 56 56 grey22 59 59 59 gray23 59 59 59 grey23 61 61 61 gray24 61 61 61 grey24 64 64 64 gray25 64 64 64 grey25 66 66 66 gray26 66 66 66 grey26 69 69 69 gray27 69 69 69 grey27 71 71 71 gray28 71 71 71 grey28 74 74 74 gray29 74 74 74 grey29 77 77 77 gray30 77 77 77 grey30 79 79 79 gray31 79 79 79 grey31 82 82 82 gray32 82 82 82 grey32 84 84 84 gray33 84 84 84 grey33 87 87 87 gray34 87 87 87 grey34 89 89 89 gray35 89 89 89 grey35 92 92 92 gray36 92 92 92 grey36 94 94 94 gray37 94 94 94 grey37 97 97 97 gray38 97 97 97 grey38 99 99 99 gray39 99 99 99 grey39 102 102 102 gray40 102 102 102 grey40 105 105 105 gray41 105 105 105 grey41 107 107 107 gray42 107 107 107 grey42 110 110 110 gray43 110 110 110 grey43 112 112 112 gray44 112 112 112 grey44 115 115 115 gray45 115 115 115 grey45 117 117 117 gray46 117 117 117 grey46 120 120 120 gray47 120 120 120 grey47 122 122 122 gray48 122 122 122 grey48 125 125 125 gray49 125 125 125 grey49 127 127 127 gray50 127 127 127 grey50 130 130 130 gray51 130 130 130 grey51 133 133 133 gray52 133 133 133 grey52 135 135 135 gray53 135 135 135 grey53 138 138 138 gray54 138 138 138 grey54 140 140 140 gray55 140 140 140 grey55 143 143 143 gray56 143 143 143 grey56 145 145 145 gray57 145 145 145 grey57 148 148 148 gray58 148 148 148 grey58 150 150 150 gray59 150 150 150 grey59 153 153 153 gray60 153 153 153 grey60 156 156 156 gray61 156 156 156 grey61 158 158 158 gray62 158 158 158 grey62 161 161 161 gray63 161 161 161 grey63 163 163 163 gray64 163 163 163 grey64 166 166 166 gray65 166 166 166 grey65 168 168 168 gray66 168 168 168 grey66 171 171 171 gray67 171 171 171 grey67 173 173 173 gray68 173 173 173 grey68 176 176 176 gray69 176 176 176 grey69 179 179 179 gray70 179 179 179 grey70 181 181 181 gray71 181 181 181 grey71 184 184 184 gray72 184 184 184 grey72 186 186 186 gray73 186 186 186 grey73 189 189 189 gray74 189 189 189 grey74 191 191 191 gray75 191 191 191 grey75 194 194 194 gray76 194 194 194 grey76 196 196 196 gray77 196 196 196 grey77 199 199 199 gray78 199 199 199 grey78 201 201 201 gray79 201 201 201 grey79 204 204 204 gray80 204 204 204 grey80 207 207 207 gray81 207 207 207 grey81 209 209 209 gray82 209 209 209 grey82 212 212 212 gray83 212 212 212 grey83 214 214 214 gray84 214 214 214 grey84 217 217 217 gray85 217 217 217 grey85 219 219 219 gray86 219 219 219 grey86 222 222 222 gray87 222 222 222 grey87 224 224 224 gray88 224 224 224 grey88 227 227 227 gray89 227 227 227 grey89 229 229 229 gray90 229 229 229 grey90 232 232 232 gray91 232 232 232 grey91 235 235 235 gray92 235 235 235 grey92 237 237 237 gray93 237 237 237 grey93 240 240 240 gray94 240 240 240 grey94 242 242 242 gray95 242 242 242 grey95 245 245 245 gray96 245 245 245 grey96 247 247 247 gray97 247 247 247 grey97 250 250 250 gray98 250 250 250 grey98 252 252 252 gray99 252 252 252 grey99 255 255 255 gray100 255 255 255 grey100 169 169 169 dark grey 169 169 169 DarkGrey 169 169 169 dark gray 169 169 169 DarkGray 0 0 139 dark blue 0 0 139 DarkBlue 0 139 139 dark cyan 0 139 139 DarkCyan 139 0 139 dark magenta 139 0 139 DarkMagenta 139 0 0 dark red 139 0 0 DarkRed 144 238 144 light green 144 238 144 LightGreen') collect: [ :each | | split color name | split := Character tab split: each. color := Character space split: (split at: 1). color := color select: [ :c| c isNotEmpty ]. color := color collect: [ :c | (c asInteger / 255) asFloat roundUpTo: 0.001 ]. name := split at: 3. {name asSymbol. color asArray} ] as: Array

Dec. 26, 2017

Re: [Pharo-dev] [ANN] Phanide - Pharo Native IDE

by Ronie Salgado

> > Great work, Ronie, it looks very promising! Keep in mind that we already > have an IDE - Pharo, so it would be cool to make the components of your IDE > as much reusable as possible and I think that most of them should be in the > standard image in future. I agree on the reusability part. BTW, I forgot to mention that the Phanide syntax highlighters are also automatically registered with the GT Inspector, so if you do a 'test.cpp' asFileReference inspect , you will also have the syntax highlighting. Best regards, Ronie 2017-12-26 13:12 GMT-03:00 Pavel Krivanek <pavel.krivanek(a)gmail.com>: > Great work, Ronie, it looks very promising! Keep in mind that we already > have an IDE - Pharo, so it would be cool to make the components of your IDE > as much reusable as possible and I think that most of them should be in the > standard image in future. > > Cheers, > -- Pavel > > 2017-12-24 21:05 GMT+01:00 Ronie Salgado <roniesalg(a)gmail.com>: > >> Hi, >> >> I am going to announce a project that I started in November: >> >> Phanide, Pharo Native IDE( currently a File Browser, and a syntax >> highlighting framework): https://github.com/ronsaldo/phanide >> >> [image: ImÃ¡genes integradas 3] >> >> [image: ImÃ¡genes integradas 4] >> >> As for the UI, I am just copying some existing stuff like Atom (the text >> editor that I am currently using). >> >> Now I have a couple of questions to the mailing list: >> - In the fast table (used for the tree view): >> - How do I remove or add single elements without collapsing the whole >> tree? >> - In the Rubric text editor, how do I a put an icon (such as a breakpoint >> for GDB) in a specific line of the text, not in a index of the text? >> >> Merry Christmas, >> Ronie >> > >

Dec. 26, 2017

Re: [Pharo-dev] [ANN] Phanide - Pharo Native IDE

by Pavel Krivanek

Great work, Ronie, it looks very promising! Keep in mind that we already have an IDE - Pharo, so it would be cool to make the components of your IDE as much reusable as possible and I think that most of them should be in the standard image in future. Cheers, -- Pavel 2017-12-24 21:05 GMT+01:00 Ronie Salgado <roniesalg(a)gmail.com>: > Hi, > > I am going to announce a project that I started in November: > > Phanide, Pharo Native IDE( currently a File Browser, and a syntax > highlighting framework): https://github.com/ronsaldo/phanide > > [image: ImÃ¡genes integradas 3] > > [image: ImÃ¡genes integradas 4] > > As for the UI, I am just copying some existing stuff like Atom (the text > editor that I am currently using). > > Now I have a couple of questions to the mailing list: > - In the fast table (used for the tree view): > - How do I remove or add single elements without collapsing the whole > tree? > - In the Rubric text editor, how do I a put an icon (such as a breakpoint > for GDB) in a specific line of the text, not in a index of the text? > > Merry Christmas, > Ronie >

Dec. 26, 2017

Re: [Pharo-dev] Simple game framework

by Hilaire

Read. SDL + Cairo is the way you have been. I did not imagine Cairo was good at manipulating block of bitmap. Is Cairo stable over time in Pharo? I wonder will it be wiped out. More generally, I wonder what is the stable ground to build graphic application on Pharo? Le 25/12/2017 Ã 19:32, ClÃ©ment Bera a Ã©critÂ : > See those ReadMe: > > https://github.com/clementbera/wizard-battle-arena > > https://github.com/clementbera/SpiderInvasion > > Audio has always been a problem to me. I successfully run audio files > with the open AL binding, but I failed to do so cross-platform. > Already key-bindings coherent cross platform is difficult. > > Cheers -- Dr. Geo http://drgeo.eu

Dec. 26, 2017

Re: [Pharo-dev] Building an application with P7

by Hilaire

I meant more tests in DrGeo to expose its features, and to discover where newer Pharo breaks it. Hilaire Le 25/12/2017 Ã 23:59, Ben Coman a Ã©critÂ : > > really took me a long time to get drgeo right on P3 because these > oddities only show up at runtime, under specific scenario. There > are easy to fix, thought. Writing more tests should help too. > > > It would be great to have Issues opened with new tests attached for > these specific cases > that currently fail which we can work on make green. > They make the problem nicely explicit to work on. > -- Dr. Geo http://drgeo.eu

Dec. 26, 2017

Re: [Pharo-dev] Building an application with P7

by Ben Coman

On 26 December 2017 at 01:51, Hilaire <hilaire(a)drgeo.eu> wrote: > Let's discuss it in another thread. > > Until now, I moved slowly to update the drgeo build script to adjust to > Tonel file repository and P7; mostly done now. Will now look for help from > Pavel to build the drgeo image from a tiny core. > > About the other problems to get a user ready drgeo application based on > the forthcoming P7: > > - set up an application 64bits VMs architecture for Linux, OS X and > Windows (aka one-click image). I understand the later may be a problem as > there is not yet 64bits VMs. > > - get over the strange oddities appearing with P7, long and tedious but > mandatory; otherwise this sets back drgeo as an end user (student, > teacher) will immediately run away if drgeo is unpredictable. It really > took me a long time to get drgeo right on P3 because these oddities only > show up at runtime, under specific scenario. There are easy to fix, > thought. Writing more tests should help too. > It would be great to have Issues opened with new tests attached for these specific cases that currently fail which we can work on make green. They make the problem nicely explicit to work on. cheers -ben > > Hilaire > > > Le 25/12/2017 Ã 15:57, Stephane Ducasse a Ã©crit : > >> 5. fulfill the promise of tiny image, aka bootstrap and 4. >>> >> Did you see that pavel produced a smaller image than the first >> bootstrapped version >> >> All these wishes are under construction, so likely to happen \o/ >>> >>> >>> I have personal three wishes (beside good health of course), sharing it >>> in >>> case others are interested to hack on it too: >>> >>> A. get DrGeo working on P7, particularly on the bootstrap process. >>> >> Let us know the problem you face because this is important that you can. >> >> >> > -- > Dr. Geo > http://drgeo.eu > > > >

Dec. 25, 2017

Re: [Pharo-dev] How to restore image upgrade? was New Year Wishlist (2018) ?

by Ben Coman

As a half-way house, consider that "upgrade" scripts could be a good mechanism post-Release when changes should be less-deep/less-arduous on the system. This might avoid Esteban's time being needed to re-Release for each upgrade, with post-Release moving to a more community supported mechanism. This could scale better as we gain more users interested in long term support of their applications on a stable-release than the moving target of the development-edge. cheers -ben On 25 December 2017 at 23:11, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Nicolas > > We want to keep the live part of Pharo and incremental loading and it > is key for us. Now we should not be naive. > Most of the time we do not have the garantee that a change will work > when loaded. > > We proposed Pablo to work since two years on a really working dynamic > code loader and > Pablo has really nice results. But it takes time to evaluate if/how we > integrate its changes. > Pablo has an atomic coder loader and an incremental and modular class > builder. > He also designed a modular shutdown/startup list manager (in production). > > We want to be able to have a **real** and robust incremental load. > Right now as you know it and as in ANY smalltalk I can break the > system super easily. > There is no magic. I do not see how we can make sure that any piece of > code will be loaded > and do not break the system. > So our objective is to have a new infrastructure that we can updates > (like method hashes for example without having to > twists our mind and do five updates). > > Now about git, we want and we will have our lovely image as a working > directory but this requires engineering > because the image is another artefact that other languages do not have > to worry. > We will get there. > > Stef > > > On Sun, Dec 24, 2017 at 11:41 PM, Nicolas Cellier > <nicolas.cellier.aka.nice(a)gmail.com> wrote: > > > > > > 2017-12-24 2:59 GMT+01:00 Alexandre Bergel <alexandre.bergel(a)me.com>: > >> > >> My four wishes, in no particular order: > >> - Better code completion > >> - Git in Pharo as easy as using Git for other languages > > > > The recipe is easy: turn pharo into a file based edit-compile-run > language > > and expunge those live object burden ;) > > Let me explain why it's not just trolling. > > Currently we have to download an image made by a bot. > > Pharo has gradually lost the power to upgrade the image (it's not new). > > > > If we recognize that an image acts like a workspace, and want to let the > > pull/branch switch/etc work again... > > IOW going from one point to any other in source code graph > > and experience the full power of git like any other language, > > that means, in a live IDE, at least solving those two problems: > > - changing the tools that are used to upgrade the image (Compiler, > > MethodDictionary, Array, etc...) > > - correctly initialize all the states (including stange loops) > > If pharo has not managed to solve this with a linear one way history (the > > regularly broken update image option), > > how do you think this is going to be solved in the more general case? > > I call this the universal boostrap problem. > > > > IMO the logical next step is to separate the IDE > > (the Inanimate Desintegrated Environment of any other language). > > > > Maybe we don't have to bend Pharo too much to git if it does not fit. > > The goal: as easy might be not that easy. > > > > > >> - Bloc on Steroid > >> - Being able to interrupt any process and endless loop using > Cmd-. > >> > >> Merry Christmas to all of you! > >> Alexandre > >> > >> > >> > >> > On Dec 23, 2017, at 1:58 PM, Esteban Lorenzano <estebanlm(a)gmail.com> > >> > wrote: > >> > > >> > Hi everybody, > >> > > >> > This looks like a good moment of the year to ask all of you what would > >> > you want to see in Pharo next year. > >> > Features, improvements, radical changes, etcâ¦. whatever you want. > >> > > >> > Of course, this list will not be a roadmap and it does not means we > will > >> > implement all of it (as always, time drives our possibilities), but > is a > >> > good moment for us a a community to check where we are and where we > wan to > >> > go next :) > >> > > >> > So, letâs those wishes come! > >> > > >> > cheers, > >> > Esteban > >> > >> > > > >

Dec. 25, 2017

Re: [Pharo-dev] New Year Wishlist (2018) ?

by Ben Coman

On 25 December 2017 at 22:58, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > On Mon, Dec 25, 2017 at 2:17 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > > A GUI builder is always a nice thing ... and there already was an attempt > > for Pharo: > > > > http://www.squeaksource.com/UIBuilder/ > > > > Now marked as "Failed attempt of develop a UI builder for > Pharo-Smalltalk. That version > > only works in Pharo 1.1. Is opened for any developer.". > > > > Dont know why it failed ... maybe because the UI (especially with > Morphic legacy) > > is still too shaky are in Pharo. > > The developer stopped when he saw that he could not build a excel like > grid. > Oh, then let me add an Excel-like grid as my Christmas wish (or does FastTable already provide much of this?) cheers -ben

Dec. 25, 2017

Re: [Pharo-dev] New Year Wishlist (2018) ?

by serge.stinckwich＠gmail.com

Yes we talk about something like that with ClÃ©ment some months ago. EnvoyÃ© de mon iPhone > Le 25 dÃ©c. 2017 Ã 20:29, Dimitris Chloupis <kilon.alios(a)gmail.com> a Ã©crit : > > >> On Mon, Dec 25, 2017 at 3:18 PM Torsten Bergmann <astares(a)gmx.de> wrote: >> A GUI builder is always a nice thing ... and there already was an attempt >> for Pharo: >> >> http://www.squeaksource.com/UIBuilder/ >> >> Now marked as "Failed attempt of develop a UI builder for Pharo-Smalltalk. That version >> only works in Pharo 1.1. Is opened for any developer.". >> >> Dont know why it failed ... maybe because the UI (especially with Morphic legacy) >> is still too shaky are in Pharo. >> >> But I guess the order will be/needs to be: >> >> - good and stable graphics framework (maybe solved with Bloc) >> - good and stable standardized widget set (maybe solved with Brick) >> - then place a UI builder on top of it >> >> Bye > > Yeap that's the ideology about GUI designers , which is why so few IDE's have them. It's like the man waiting for the perfect woman to marry, ending up all alone and miserable. > > As a designer myself I cannot follow easily this ideology. Actually I cannot follow it at all. > > I see it the exact opposite way, if you don't have a good GUI designer , your ability to provide a stable and powerful GUI API will be limited because less people will use it. > > The most stable and powerful GUI api I ever used was VCL , the standard library of Delphi and surprise, surprise it has a GUI designer. The most powerful I used so far. > > Open source wise QT dominates , surprise , surprise it has a very powerful GUI designer. > > On Windows you have VS studio GUI designer on MacOS and iOS the XCode GUI Designer and so forth. > > There a ton of GUI APIs out there that almost none uses, is it because they are not stable ? > > Well ... *cough* Windows *cough* ... sure. > > Making GUIs via code, is not as much fun, its slower and ends up being also less flexible as you can easily lose track of what you intend to do trying to understand the internals of a GUI API. Not fun at all. Especially if you experienced the horrors of MFC. > > But I am realistic , don't expect a GUI designer any time soon in Pharo. They are very hard to make and coders being allergic to GUIs does not help motivate to make one. > > I am ok with just a modular image format. > > Also I drink my own poison. I have made my own GUI API in Python with OpenGL (used from inside Blender for an application I am developing) very loosely inspired by some things I liked about Morphic. The more complex it becomes the more I feel the need to create a designer that will handle the boring stuff for me. > > For now I use the excellent excuse you provide of stability and inability to promise the structure of the GUI API in the future. But its an excuse with an expiration date. Making the GUI I have in my head using plain code , without a GUI designer, is a nightmare that is highly unlikely I will let myself experience. > > On the other hand when one makes his own GUI API the good news is that he can make it fits well in the workflow of a GUI designer. This way instead of trying to make the Designer according to the API , I make the API according to the designer. > > But the good news is that it has helped me realize the amount work needed to put in GUI API to become really useful. Fortunately making API to find only my needs has made things far easier and far smaller. I cannot imagine making something like Bloc and keeping my sanity. This way the next time I complain about a GUI API, I will have a whole different level of respect for the developers behind it.

Dec. 25, 2017

Re: [Pharo-dev] New Year Wishlist (2018) ?

by Dimitris Chloupis

On Mon, Dec 25, 2017 at 3:18 PM Torsten Bergmann <astares(a)gmx.de> wrote: > A GUI builder is always a nice thing ... and there already was an attempt > for Pharo: > > http://www.squeaksource.com/UIBuilder/ > > Now marked as "Failed attempt of develop a UI builder for Pharo-Smalltalk. > That version > only works in Pharo 1.1. Is opened for any developer.". > > Dont know why it failed ... maybe because the UI (especially with Morphic > legacy) > is still too shaky are in Pharo. > > But I guess the order will be/needs to be: > > - good and stable graphics framework (maybe solved with Bloc) > - good and stable standardized widget set (maybe solved with Brick) > - then place a UI builder on top of it > > Bye > Yeap that's the ideology about GUI designers , which is why so few IDE's have them. It's like the man waiting for the perfect woman to marry, ending up all alone and miserable. As a designer myself I cannot follow easily this ideology. Actually I cannot follow it at all. I see it the exact opposite way, if you don't have a good GUI designer , your ability to provide a stable and powerful GUI API will be limited because less people will use it. The most stable and powerful GUI api I ever used was VCL , the standard library of Delphi and surprise, surprise it has a GUI designer. The most powerful I used so far. Open source wise QT dominates , surprise , surprise it has a very powerful GUI designer. On Windows you have VS studio GUI designer on MacOS and iOS the XCode GUI Designer and so forth. There a ton of GUI APIs out there that almost none uses, is it because they are not stable ? Well ... *cough* Windows *cough* ... sure. Making GUIs via code, is not as much fun, its slower and ends up being also less flexible as you can easily lose track of what you intend to do trying to understand the internals of a GUI API. Not fun at all. Especially if you experienced the horrors of MFC. But I am realistic , don't expect a GUI designer any time soon in Pharo. They are very hard to make and coders being allergic to GUIs does not help motivate to make one. I am ok with just a modular image format. Also I drink my own poison. I have made my own GUI API in Python with OpenGL (used from inside Blender for an application I am developing) very loosely inspired by some things I liked about Morphic. The more complex it becomes the more I feel the need to create a designer that will handle the boring stuff for me. For now I use the excellent excuse you provide of stability and inability to promise the structure of the GUI API in the future. But its an excuse with an expiration date. Making the GUI I have in my head using plain code , without a GUI designer, is a nightmare that is highly unlikely I will let myself experience. On the other hand when one makes his own GUI API the good news is that he can make it fits well in the workflow of a GUI designer. This way instead of trying to make the Designer according to the API , I make the API according to the designer. But the good news is that it has helped me realize the amount work needed to put in GUI API to become really useful. Fortunately making API to find only my needs has made things far easier and far smaller. I cannot imagine making something like Bloc and keeping my sanity. This way the next time I complain about a GUI API, I will have a whole different level of respect for the developers behind it.

Dec. 25, 2017

Re: [Pharo-dev] Simple game framework

by ClÃ©ment Bera

See those ReadMe: https://github.com/clementbera/wizard-battle-arena https://github.com/clementbera/SpiderInvasion Audio has always been a problem to me. I successfully run audio files with the open AL binding, but I failed to do so cross-platform. Already key-bindings coherent cross platform is difficult. Cheers On Mon, Dec 25, 2017 at 6:58 PM, Hilaire <hilaire(a)drgeo.eu> wrote: > You may have different kind of games; for example in 2D games, it could be > fixed frame, side scrolling, up scrolling, isometric, etc. To get it > started easily, it could come with graphic and audio banks. > > I really don't have much idea how such a general system should be > designed. Only wrote once a commercial decades ago on ARM code. > > Will look a the bloc tutorial for game[1] > > [1] https://github.com/pharo-graphics/Tutorials/ > > > Le 25/12/2017 Ã 15:57, Stephane Ducasse a Ã©crit : > >> B. Build an environment in Pharo to develop simple games, targeted for >>> kids. >>> There are some teenagers in my school likely to get interested on such >>> courses. If it could result in standalone games build thanks to wish 4., >>> so >>> good. >>> >> I'm interested into that this is why I proposed to "laura" >> maximilliano to work on such framework. >> Now I never got the time to do a pass over it and to release what I >> learned. >> - direction >> - handling on moves. >> - I created a grid data structure but this is the least interesting >> part. >> >> If you want we can discuss what I learned. >> Also students in Prague are building games on top of Bloc. >> >> >> > -- > Dr. Geo > http://drgeo.eu > > > > -- ClÃ©ment BÃ©ra Pharo consortium engineer https://clementbera.wordpress.com/ BÃ¢timent B 40, avenue Halley 59650 Villeneuve d'Ascq

Dec. 25, 2017

Re: [Pharo-dev] New Year Wishlist (2018) ?

by Hilaire

I don't understand your question Le 25/12/2017 Ã 15:57, Stephane Ducasse a Ã©critÂ : >> C. Develop a white board application, easy to extend to add third party >> features. The OpenBoard[2] we are using in school are merely goods (can't >> get the right tooling to do geometry for example), handwriting is not nice, >> hacking on it is super complicated (C++ code), not to mention the building >> process. A Pharo based one will be fantastic and much easy to hack. > Is Pharo running on this? -- Dr. Geo http://drgeo.eu

Dec. 25, 2017

Simple game framework

by Hilaire

You may have different kind of games; for example in 2D games, it could be fixed frame, side scrolling, up scrolling, isometric, etc. To get it started easily, it could come with graphic and audio banks. I really don't have much idea how such a general system should be designed. Only wrote once a commercial decades ago on ARM code. Will look a the bloc tutorial for game[1] [1] https://github.com/pharo-graphics/Tutorials/ Le 25/12/2017 Ã 15:57, Stephane Ducasse a Ã©critÂ : >> B. Build an environment in Pharo to develop simple games, targeted for kids. >> There are some teenagers in my school likely to get interested on such >> courses. If it could result in standalone games build thanks to wish 4., so >> good. > I'm interested into that this is why I proposed to "laura" > maximilliano to work on such framework. > Now I never got the time to do a pass over it and to release what I learned. > - direction > - handling on moves. > - I created a grid data structure but this is the least interesting part. > > If you want we can discuss what I learned. > Also students in Prague are building games on top of Bloc. > > -- Dr. Geo http://drgeo.eu

Dec. 25, 2017

Re: [Pharo-dev] New Year Wishlist (2018) ?

by Evan Donahue

Given the recent stirrings of AI-related applications in Pharo, I guess I'm wishing for vm support for vector operations/fast math. I heard something about that a while ago on the polymath chanel, so I figure it can't hurt to wish. Evan -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Dec. 25, 2017

Building an application with P7

by Hilaire

Let's discuss it in another thread. Until now, I moved slowly to update the drgeo build script to adjust to Tonel file repository and P7; mostly done now. Will now look for help from Pavel to build the drgeo image from a tiny core. About the other problems to get a user ready drgeo application based on the forthcoming P7: - set up an application 64bits VMs architecture for Linux, OS X and Windows (aka one-click image). I understand the later may be a problem as there is not yet 64bits VMs. - get over the strange oddities appearing with P7, long and tedious but mandatory; otherwise this sets back drgeo as an end user (student, teacher)Â will immediately run away if drgeo is unpredictable. It really took me a long time to get drgeo right on P3 because these oddities only show up at runtime, under specific scenario. There are easy to fix, thought. Writing more tests should help too. Hilaire Le 25/12/2017 Ã 15:57, Stephane Ducasse a Ã©critÂ : >> 5. fulfill the promise of tiny image, aka bootstrap and 4. > Did you see that pavel produced a smaller image than the first > bootstrapped version > >> All these wishes are under construction, so likely to happen \o/ >> >> >> I have personal three wishes (beside good health of course), sharing it in >> case others are interested to hack on it too: >> >> A. get DrGeo working on P7, particularly on the bootstrap process. > Let us know the problem you face because this is important that you can. > > -- Dr. Geo http://drgeo.eu

Dec. 25, 2017

Re: [Pharo-dev] New Year Wishlist (2018) ?

by Hilaire

I really don't mean a GUI builder :-) Le 25/12/2017 Ã 15:57, Stephane Ducasse a Ã©critÂ : >> 4. application builder. Smalltalk/X has a GUI to build a standalone >> application, was not able to get it working, but it probably worked at some >> time in the past (see screenshot). Such a feature in Pharo will be >> fantastic, and likely a kill feature for the ones developing stand alone >> application; yes there are still some;-) > We would like the same. Now spec was an increment in that direction > because behind the UI builder you need to reuse the model. So > with a pass on spec we will be set to be able to build the builder part > -- Dr. Geo http://drgeo.eu

Dec. 25, 2017

Re: [Pharo-dev] New Year Wishlist (2018) ?

by Hilaire

In case of, at wish 4. I did not write a GUI builder but really an application builder: a tool to let you build up the image and the needed VMs, and pack it appropriately for the end user. As it is manually done for Dr.Geo. Le 25/12/2017 Ã 14:17, Torsten Bergmann a Ã©critÂ : > A GUI builder is always a nice thing ... and there already was an attempt > for Pharo: -- Dr. Geo http://drgeo.eu

Dec. 25, 2017

Re: [Pharo-dev] How to restore image upgrade? was New Year Wishlist (2018) ?

by Stephane Ducasse

Nicolas We want to keep the live part of Pharo and incremental loading and it is key for us. Now we should not be naive. Most of the time we do not have the garantee that a change will work when loaded. We proposed Pablo to work since two years on a really working dynamic code loader and Pablo has really nice results. But it takes time to evaluate if/how we integrate its changes. Pablo has an atomic coder loader and an incremental and modular class builder. He also designed a modular shutdown/startup list manager (in production). We want to be able to have a **real** and robust incremental load. Right now as you know it and as in ANY smalltalk I can break the system super easily. There is no magic. I do not see how we can make sure that any piece of code will be loaded and do not break the system. So our objective is to have a new infrastructure that we can updates (like method hashes for example without having to twists our mind and do five updates). Now about git, we want and we will have our lovely image as a working directory but this requires engineering because the image is another artefact that other languages do not have to worry. We will get there. Stef On Sun, Dec 24, 2017 at 11:41 PM, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: > > > 2017-12-24 2:59 GMT+01:00 Alexandre Bergel <alexandre.bergel(a)me.com>: >> >> My four wishes, in no particular order: >> - Better code completion >> - Git in Pharo as easy as using Git for other languages > > The recipe is easy: turn pharo into a file based edit-compile-run language > and expunge those live object burden ;) > Let me explain why it's not just trolling. > Currently we have to download an image made by a bot. > Pharo has gradually lost the power to upgrade the image (it's not new). > > If we recognize that an image acts like a workspace, and want to let the > pull/branch switch/etc work again... > IOW going from one point to any other in source code graph > and experience the full power of git like any other language, > that means, in a live IDE, at least solving those two problems: > - changing the tools that are used to upgrade the image (Compiler, > MethodDictionary, Array, etc...) > - correctly initialize all the states (including stange loops) > If pharo has not managed to solve this with a linear one way history (the > regularly broken update image option), > how do you think this is going to be solved in the more general case? > I call this the universal boostrap problem. > > IMO the logical next step is to separate the IDE > (the Inanimate Desintegrated Environment of any other language). > > Maybe we don't have to bend Pharo too much to git if it does not fit. > The goal: as easy might be not that easy. > > >> - Bloc on Steroid >> - Being able to interrupt any process and endless loop using Cmd-. >> >> Merry Christmas to all of you! >> Alexandre >> >> >> >> > On Dec 23, 2017, at 1:58 PM, Esteban Lorenzano <estebanlm(a)gmail.com> >> > wrote: >> > >> > Hi everybody, >> > >> > This looks like a good moment of the year to ask all of you what would >> > you want to see in Pharo next year. >> > Features, improvements, radical changes, etcâ¦. whatever you want. >> > >> > Of course, this list will not be a roadmap and it does not means we will >> > implement all of it (as always, time drives our possibilities), but is a >> > good moment for us a a community to check where we are and where we wan to >> > go next :) >> > >> > So, letâs those wishes come! >> > >> > cheers, >> > Esteban >> >> >

Dec. 25, 2017

Re: [Pharo-dev] New Year Wishlist (2018) ?

by Stephane Ducasse

About the application builder we will continue to work on the effort and lamrc is interested to show that we can build real applications with Pharo. So I really hope that something will happen this year. Stef On Mon, Dec 25, 2017 at 3:58 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > On Mon, Dec 25, 2017 at 2:17 PM, Torsten Bergmann <astares(a)gmx.de> wrote: >> A GUI builder is always a nice thing ... and there already was an attempt >> for Pharo: >> >> http://www.squeaksource.com/UIBuilder/ >> >> Now marked as "Failed attempt of develop a UI builder for Pharo-Smalltalk. That version >> only works in Pharo 1.1. Is opened for any developer.". >> >> Dont know why it failed ... maybe because the UI (especially with Morphic legacy) >> is still too shaky are in Pharo. > > The developer stopped when he saw that he could not build a excel like grid. > I tried to rescue its effort but it was too large to recover. > > >> But I guess the order will be/needs to be: >> >> - good and stable graphics framework (maybe solved with Bloc) >> - good and stable standardized widget set (maybe solved with Brick) >> - then place a UI builder on top of it >> >> Bye >> T. >> >>> Gesendet: Montag, 25. Dezember 2017 um 12:33 Uhr >>> Von: Hilaire <hilaire(a)drgeo.eu> >>> An: pharo-dev(a)lists.pharo.org >>> Betreff: Re: [Pharo-dev] New Year Wishlist (2018) ? >>> >>> Oh, you asked for that Esteban :) >>> >>> 1. stability >>> >>> 2. Tonel is a nice way to export file (its granularity is just right, >>> bravo Esteban!) and commit to arbitrary repository, experimenting it >>> with DrGeo, and it is nice to commit code[1] along other data files of >>> the project (graphics, doc, translation, etc.). Got some an when non >>> ascii characters were present in the source code, people reported it >>> there. Likely to be fixed :) >>> >>> 3. vectorial interface, oh already on its way >>> >>> 4. application builder. Smalltalk/X has a GUI to build a standalone >>> application, was not able to get it working, but it probably worked at >>> some time in the past (see screenshot). Such a feature in Pharo will be >>> fantastic, and likely a kill feature for the ones developing stand alone >>> application; yes there are still some ;-) >>> >>> 5. fulfill the promise of tiny image, aka bootstrap and 4. >>> >>> All these wishes are under construction, so likely to happen \o/ >>> >>> >>> I have personal three wishes (beside good health of course), sharing it >>> in case others are interested to hack on it too: >>> >>> A. get DrGeo working on P7, particularly on the bootstrap process. >>> >>> B. Build an environment in Pharo to develop simple games, targeted for >>> kids. There are some teenagers in my school likely to get interested on >>> such courses. If it could result in standalone games build thanks to >>> wish 4., so good. >>> >>> C. Develop a white board application, easy to extend to add third party >>> features. The OpenBoard[2] we are using in school are merely goods >>> (can't get the right tooling to do geometry for example), handwriting is >>> not nice, hacking on it is super complicated (C++ code), not to mention >>> the building process. A Pharo based one will be fantastic and much easy >>> to hack. >>> >>> >>> Have a nice Christmas! >>> >>> >>> [1] >>> http://bazaar.launchpad.net/~drgeo-developers/drgeo/trunk/files/head:/src/ >>> [2] http://openboard.ch >>> >>> Le 23/12/2017 Ã 17:58, Esteban Lorenzano a Ã©crit : >>> > So, letâs those wishes come! >>> >>> -- >>> Dr. Geo >>> http://drgeo.eu >>> >>> >>

Dec. 25, 2017

Re: [Pharo-dev] New Year Wishlist (2018) ?

by Stephane Ducasse

On Mon, Dec 25, 2017 at 2:17 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > A GUI builder is always a nice thing ... and there already was an attempt > for Pharo: > > http://www.squeaksource.com/UIBuilder/ > > Now marked as "Failed attempt of develop a UI builder for Pharo-Smalltalk. That version > only works in Pharo 1.1. Is opened for any developer.". > > Dont know why it failed ... maybe because the UI (especially with Morphic legacy) > is still too shaky are in Pharo. The developer stopped when he saw that he could not build a excel like grid. I tried to rescue its effort but it was too large to recover. > But I guess the order will be/needs to be: > > - good and stable graphics framework (maybe solved with Bloc) > - good and stable standardized widget set (maybe solved with Brick) > - then place a UI builder on top of it > > Bye > T. > >> Gesendet: Montag, 25. Dezember 2017 um 12:33 Uhr >> Von: Hilaire <hilaire(a)drgeo.eu> >> An: pharo-dev(a)lists.pharo.org >> Betreff: Re: [Pharo-dev] New Year Wishlist (2018) ? >> >> Oh, you asked for that Esteban :) >> >> 1. stability >> >> 2. Tonel is a nice way to export file (its granularity is just right, >> bravo Esteban!) and commit to arbitrary repository, experimenting it >> with DrGeo, and it is nice to commit code[1] along other data files of >> the project (graphics, doc, translation, etc.). Got some an when non >> ascii characters were present in the source code, people reported it >> there. Likely to be fixed :) >> >> 3. vectorial interface, oh already on its way >> >> 4. application builder. Smalltalk/X has a GUI to build a standalone >> application, was not able to get it working, but it probably worked at >> some time in the past (see screenshot). Such a feature in Pharo will be >> fantastic, and likely a kill feature for the ones developing stand alone >> application; yes there are still some ;-) >> >> 5. fulfill the promise of tiny image, aka bootstrap and 4. >> >> All these wishes are under construction, so likely to happen \o/ >> >> >> I have personal three wishes (beside good health of course), sharing it >> in case others are interested to hack on it too: >> >> A. get DrGeo working on P7, particularly on the bootstrap process. >> >> B. Build an environment in Pharo to develop simple games, targeted for >> kids. There are some teenagers in my school likely to get interested on >> such courses. If it could result in standalone games build thanks to >> wish 4., so good. >> >> C. Develop a white board application, easy to extend to add third party >> features. The OpenBoard[2] we are using in school are merely goods >> (can't get the right tooling to do geometry for example), handwriting is >> not nice, hacking on it is super complicated (C++ code), not to mention >> the building process. A Pharo based one will be fantastic and much easy >> to hack. >> >> >> Have a nice Christmas! >> >> >> [1] >> http://bazaar.launchpad.net/~drgeo-developers/drgeo/trunk/files/head:/src/ >> [2] http://openboard.ch >> >> Le 23/12/2017 Ã 17:58, Esteban Lorenzano a Ã©crit : >> > So, letâs those wishes come! >> >> -- >> Dr. Geo >> http://drgeo.eu >> >> >

Dec. 25, 2017

Re: [Pharo-dev] New Year Wishlist (2018) ?

by Stephane Ducasse

> 1. stability > > 2. Tonel is a nice way to export file (its granularity is just right, bravo > Esteban!) and commit to arbitrary repository, experimenting it with DrGeo, > and it is nice to commit code[1] along other data files of the project > (graphics, doc, translation, etc.). Got some an when non ascii characters > were present in the source code, people reported it there. Likely to be > fixed :) > > 3. vectorial interface, oh already on its way > > 4. application builder. Smalltalk/X has a GUI to build a standalone > application, was not able to get it working, but it probably worked at some > time in the past (see screenshot). Such a feature in Pharo will be > fantastic, and likely a kill feature for the ones developing stand alone > application; yes there are still some ;-) We would like the same. Now spec was an increment in that direction because behind the UI builder you need to reuse the model. So with a pass on spec we will be set to be able to build the builder part > 5. fulfill the promise of tiny image, aka bootstrap and 4. Did you see that pavel produced a smaller image than the first bootstrapped version > > All these wishes are under construction, so likely to happen \o/ > > > I have personal three wishes (beside good health of course), sharing it in > case others are interested to hack on it too: > > A. get DrGeo working on P7, particularly on the bootstrap process. Let us know the problem you face because this is important that you can. > B. Build an environment in Pharo to develop simple games, targeted for kids. > There are some teenagers in my school likely to get interested on such > courses. If it could result in standalone games build thanks to wish 4., so > good. I'm interested into that this is why I proposed to "laura" maximilliano to work on such framework. Now I never got the time to do a pass over it and to release what I learned. - direction - handling on moves. - I created a grid data structure but this is the least interesting part. If you want we can discuss what I learned. Also students in Prague are building games on top of Bloc. > C. Develop a white board application, easy to extend to add third party > features. The OpenBoard[2] we are using in school are merely goods (can't > get the right tooling to do geometry for example), handwriting is not nice, > hacking on it is super complicated (C++ code), not to mention the building > process. A Pharo based one will be fantastic and much easy to hack. Is Pharo running on this? > > > Have a nice Christmas! > > > [1] > http://bazaar.launchpad.net/~drgeo-developers/drgeo/trunk/files/head:/src/ > [2] http://openboard.ch > > > Le 23/12/2017 Ã 17:58, Esteban Lorenzano a Ã©crit : >> >> So, letâs those wishes come! > > > -- > Dr. Geo > http://drgeo.eu >

Dec. 25, 2017

Re: [Pharo-dev] New Year Wishlist (2018) ?

by Stephane Ducasse

Hi hilaire what is nice is that we have most of the same wishes ;) On Mon, Dec 25, 2017 at 12:33 PM, Hilaire <hilaire(a)drgeo.eu> wrote: > Oh, you asked for that Esteban :) > > 1. stability > > 2. Tonel is a nice way to export file (its granularity is just right, bravo > Esteban!) and commit to arbitrary repository, experimenting it with DrGeo, > and it is nice to commit code[1] along other data files of the project > (graphics, doc, translation, etc.). Got some an when non ascii characters > were present in the source code, people reported it there. Likely to be > fixed :) > > 3. vectorial interface, oh already on its way > > 4. application builder. Smalltalk/X has a GUI to build a standalone > application, was not able to get it working, but it probably worked at some > time in the past (see screenshot). Such a feature in Pharo will be > fantastic, and likely a kill feature for the ones developing stand alone > application; yes there are still some ;-) > > 5. fulfill the promise of tiny image, aka bootstrap and 4. > > All these wishes are under construction, so likely to happen \o/ > > > I have personal three wishes (beside good health of course), sharing it in > case others are interested to hack on it too: > > A. get DrGeo working on P7, particularly on the bootstrap process. > > B. Build an environment in Pharo to develop simple games, targeted for kids. > There are some teenagers in my school likely to get interested on such > courses. If it could result in standalone games build thanks to wish 4., so > good. > > C. Develop a white board application, easy to extend to add third party > features. The OpenBoard[2] we are using in school are merely goods (can't > get the right tooling to do geometry for example), handwriting is not nice, > hacking on it is super complicated (C++ code), not to mention the building > process. A Pharo based one will be fantastic and much easy to hack. > > > Have a nice Christmas! > > > [1] > http://bazaar.launchpad.net/~drgeo-developers/drgeo/trunk/files/head:/src/ > [2] http://openboard.ch > > > Le 23/12/2017 Ã 17:58, Esteban Lorenzano a Ã©crit : >> >> So, letâs those wishes come! > > > -- > Dr. Geo > http://drgeo.eu >

Dec. 25, 2017

Re: [Pharo-dev] New Year Wishlist (2018) ?

by Torsten Bergmann

A GUI builder is always a nice thing ... and there already was an attempt for Pharo: http://www.squeaksource.com/UIBuilder/ Now marked as "Failed attempt of develop a UI builder for Pharo-Smalltalk. That version only works in Pharo 1.1. Is opened for any developer.". Dont know why it failed ... maybe because the UI (especially with Morphic legacy) is still too shaky are in Pharo. But I guess the order will be/needs to be: - good and stable graphics framework (maybe solved with Bloc) - good and stable standardized widget set (maybe solved with Brick) - then place a UI builder on top of it Bye T. > Gesendet: Montag, 25. Dezember 2017 um 12:33 Uhr > Von: Hilaire <hilaire(a)drgeo.eu> > An: pharo-dev(a)lists.pharo.org > Betreff: Re: [Pharo-dev] New Year Wishlist (2018) ? > > Oh, you asked for that Esteban :) > > 1. stability > > 2. Tonel is a nice way to export file (its granularity is just right, > bravo Esteban!) and commit to arbitrary repository, experimenting it > with DrGeo, and it is nice to commit code[1] along other data files of > the project (graphics, doc, translation, etc.). Got some an when non > ascii characters were present in the source code, people reported it > there. Likely to be fixed :) > > 3. vectorial interface, oh already on its way > > 4. application builder. Smalltalk/X has a GUI to build a standalone > application, was not able to get it working, but it probably worked at > some time in the past (see screenshot). Such a feature in Pharo will be > fantastic, and likely a kill feature for the ones developing stand alone > application; yes there are still some ;-) > > 5. fulfill the promise of tiny image, aka bootstrap and 4. > > All these wishes are under construction, so likely to happen \o/ > > > I have personal three wishes (beside good health of course), sharing it > in case others are interested to hack on it too: > > A. get DrGeo working on P7, particularly on the bootstrap process. > > B. Build an environment in Pharo to develop simple games, targeted for > kids. There are some teenagers in my school likely to get interested on > such courses. If it could result in standalone games build thanks to > wish 4., so good. > > C. Develop a white board application, easy to extend to add third party > features. The OpenBoard[2] we are using in school are merely goods > (can't get the right tooling to do geometry for example), handwriting is > not nice, hacking on it is super complicated (C++ code), not to mention > the building process. A Pharo based one will be fantastic and much easy > to hack. > > > Have a nice Christmas! > > > [1] > http://bazaar.launchpad.net/~drgeo-developers/drgeo/trunk/files/head:/src/ > [2] http://openboard.ch > > Le 23/12/2017 Ã 17:58, Esteban Lorenzano a Ã©critÂ : > > So, letâs those wishes come! > > -- > Dr. Geo > http://drgeo.eu > >

Dec. 25, 2017

Re: [Pharo-dev] New Year Wishlist (2018) ?

by Hilaire

Oh, you asked for that Esteban :) 1. stability 2. Tonel is a nice way to export file (its granularity is just right, bravo Esteban!) and commit to arbitrary repository, experimenting it with DrGeo, and it is nice to commit code[1] along other data files of the project (graphics, doc, translation, etc.). Got some an when non ascii characters were present in the source code, people reported it there. Likely to be fixed :) 3. vectorial interface, oh already on its way 4. application builder. Smalltalk/X has a GUI to build a standalone application, was not able to get it working, but it probably worked at some time in the past (see screenshot). Such a feature in Pharo will be fantastic, and likely a kill feature for the ones developing stand alone application; yes there are still some ;-) 5. fulfill the promise of tiny image, aka bootstrap and 4. All these wishes are under construction, so likely to happen \o/ I have personal three wishes (beside good health of course), sharing it in case others are interested to hack on it too: A. get DrGeo working on P7, particularly on the bootstrap process. B. Build an environment in Pharo to develop simple games, targeted for kids. There are some teenagers in my school likely to get interested on such courses. If it could result in standalone games build thanks to wish 4., so good. C. Develop a white board application, easy to extend to add third party features. The OpenBoard[2] we are using in school are merely goods (can't get the right tooling to do geometry for example), handwriting is not nice, hacking on it is super complicated (C++ code), not to mention the building process. A Pharo based one will be fantastic and much easy to hack. Have a nice Christmas! [1] http://bazaar.launchpad.net/~drgeo-developers/drgeo/trunk/files/head:/src/ [2] http://openboard.ch Le 23/12/2017 Ã 17:58, Esteban Lorenzano a Ã©critÂ : > So, letâs those wishes come! -- Dr. Geo http://drgeo.eu

Dec. 25, 2017

How to restore image upgrade? was New Year Wishlist (2018) ?

by Nicolas Cellier

2017-12-24 2:59 GMT+01:00 Alexandre Bergel <alexandre.bergel(a)me.com>: > My four wishes, in no particular order: > - Better code completion > - Git in Pharo as easy as using Git for other languages > The recipe is easy: turn pharo into a file based edit-compile-run language and expunge those live object burden ;) Let me explain why it's not just trolling. Currently we have to download an image made by a bot. Pharo has gradually lost the power to upgrade the image (it's not new). If we recognize that an image acts like a workspace, and want to let the pull/branch switch/etc work again... IOW going from one point to any other in source code graph and experience the full power of git like any other language, that means, in a live IDE, at least solving those two problems: - changing the tools that are used to upgrade the image (Compiler, MethodDictionary, Array, etc...) - correctly initialize all the states (including stange loops) If pharo has not managed to solve this with a linear one way history (the regularly broken update image option), how do you think this is going to be solved in the more general case? I call this the universal boostrap problem. IMO the logical next step is to separate the IDE (the Inanimate Desintegrated Environment of any other language). Maybe we don't have to bend Pharo too much to git if it does not fit. The goal: as easy might be not that easy. - Bloc on Steroid > - Being able to interrupt any process and endless loop using Cmd-. > > Merry Christmas to all of you! > Alexandre > > > > > On Dec 23, 2017, at 1:58 PM, Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > > > > Hi everybody, > > > > This looks like a good moment of the year to ask all of you what would > you want to see in Pharo next year. > > Features, improvements, radical changes, etcâ¦. whatever you want. > > > > Of course, this list will not be a roadmap and it does not means we will > implement all of it (as always, time drives our possibilities), but is a > good moment for us a a community to check where we are and where we wan to > go next :) > > > > So, letâs those wishes come! > > > > cheers, > > Esteban > > >

Dec. 24, 2017

[ANN] Phanide - Pharo Native IDE

by Ronie Salgado

Hi, I am going to announce a project that I started in November: Phanide, Pharo Native IDE( currently a File Browser, and a syntax highlighting framework): https://github.com/ronsaldo/phanide [image: ImÃ¡genes integradas 3] [image: ImÃ¡genes integradas 4] As for the UI, I am just copying some existing stuff like Atom (the text editor that I am currently using). Now I have a couple of questions to the mailing list: - In the fast table (used for the tree view): - How do I remove or add single elements without collapsing the whole tree? - In the Rubric text editor, how do I a put an icon (such as a breakpoint for GDB) in a specific line of the text, not in a index of the text? Merry Christmas, Ronie

Dec. 24, 2017

Re: [Pharo-dev] New Year Wishlist (2018) ?

by Dimitris Chloupis

For me 100% bootstrap and anything that helps me minimize the image or completely get rid of it. Second place is a GUI designer. Third place, world peace. Santa hates me :D On Sun, Dec 24, 2017 at 8:14 PM Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > Hi. > > Not blocking FFI, please > > 2017-12-23 17:58 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > >> Hi everybody, >> >> This looks like a good moment of the year to ask all of you what would >> you want to see in Pharo next year. >> Features, improvements, radical changes, etcâ¦. whatever you want. >> >> Of course, this list will not be a roadmap and it does not means we will >> implement all of it (as always, time drives our possibilities), but is a >> good moment for us a a community to check where we are and where we wan to >> go next :) >> >> So, letâs those wishes come! >> >> cheers, >> Esteban >> > >

Dec. 24, 2017

Re: [Pharo-dev] New Year Wishlist (2018) ?

by Denis Kudriashov

Hi. Not blocking FFI, please 2017-12-23 17:58 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > Hi everybody, > > This looks like a good moment of the year to ask all of you what would you > want to see in Pharo next year. > Features, improvements, radical changes, etcâ¦. whatever you want. > > Of course, this list will not be a roadmap and it does not means we will > implement all of it (as always, time drives our possibilities), but is a > good moment for us a a community to check where we are and where we wan to > go next :) > > So, letâs those wishes come! > > cheers, > Esteban >

Dec. 24, 2017

Re: [Pharo-dev] New Year Wishlist (2018) ?

by Alistair Grant

Hi Esteban, - https://github.com/pharo-project/pharo-vm/pull/142 Thanks! Alistair On 23 December 2017 at 17:58, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Hi everybody, > > This looks like a good moment of the year to ask all of you what would you want to see in Pharo next year. > Features, improvements, radical changes, etcâ¦. whatever you want. > > Of course, this list will not be a roadmap and it does not means we will implement all of it (as always, time drives our possibilities), but is a good moment for us a a community to check where we are and where we wan to go next :) > > So, letâs those wishes come! > > cheers, > Esteban

Dec. 24, 2017

Re: [Pharo-dev] New Year Wishlist (2018) ?

by Torsten Bergmann

Hi Esteban, Many things come to mind: vm side ======= - working SSL for all platforms supporting newest TLS - Pharo 64 bit VM for Windows - better and more VM plugins (like the camera plugin which would allow us more collaboration) - threaded vm for non-blocking usage - the VM in a DLL image - cleaning up - Calypso inclusion - Class annotations in the default image - Versionner for editing baselines (instead of manually editing dependencies) - unification of all the quality rules - support for other content types in browser (like highlighted XML, JSON, Js, ...) and managing non-smalltalk project code in git too at the level of projects - better completion - Bloc inclusion of blocs - better widgets and UI - a better catalog ("Index") - a better file browser - filing in/filing out Tonel files also in browser, change sorter, file list (similar to st files) - support for I18N (with tools, maybe binding to lib gettext) general - even more tech talks - more collaboration tools Also: - making a stable but updateable launcher the default install which is working on all platforms so one can use it for Pharo installation and sorting out version or platform specific install issues. If the list is too short then tell me ;) Bye T. > Gesendet: Samstag, 23. Dezember 2017 um 17:58 Uhr > Von: "Esteban Lorenzano" <estebanlm(a)gmail.com> > An: members-consortium(a)pharo.org, "Pharo Development List" <pharo-dev(a)lists.pharo.org> > Betreff: [Pharo-dev] New Year Wishlist (2018) ? > > Hi everybody, > > This looks like a good moment of the year to ask all of you what would you want to see in Pharo next year. > Features, improvements, radical changes, etcâ¦. whatever you want. > > Of course, this list will not be a roadmap and it does not means we will implement all of it (as always, time drives our possibilities), but is a good moment for us a a community to check where we are and where we wan to go next :) > > So, letâs those wishes come! > > cheers, > Esteban >

Dec. 24, 2017

Re: [Pharo-dev] New Year Wishlist (2018) ?

by Alexandre Bergel

My four wishes, in no particular order: - Better code completion - Git in Pharo as easy as using Git for other languages - Bloc on Steroid - Being able to interrupt any process and endless loop using Cmd-. Merry Christmas to all of you! Alexandre > On Dec 23, 2017, at 1:58 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Hi everybody, > > This looks like a good moment of the year to ask all of you what would you want to see in Pharo next year. > Features, improvements, radical changes, etcâ¦. whatever you want. > > Of course, this list will not be a roadmap and it does not means we will implement all of it (as always, time drives our possibilities), but is a good moment for us a a community to check where we are and where we wan to go next :) > > So, letâs those wishes come! > > cheers, > Esteban

Dec. 24, 2017

Re: [Pharo-dev] Calendrical capabilities

by publius789＠gmail.com

This is very helpful. Nice holiday weekend reading! Sure, if its not too much trouble you can send it to me. Thanks. Regards, Jim -----Original Message----- From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of Stephane Ducasse Sent: Saturday, December 23, 2017 5:02 PM To: Pharo Development List <pharo-dev(a)lists.pharo.org> Subject: Re: [Pharo-dev] Calendrical capabilities Aconcagua is available via the catalog. Here is what I found in my harddisc about chronos. I can send you the zipped file with old code (probably should be ported to Pharo). On Sat, Dec 23, 2017 at 10:32 PM, <publius789(a)gmail.com> wrote: > I am new to the Pharo world and looking at capabilities for potential > applications. > > > > One of the first things I am interested in is Calendar processing > capabilities. I havenât had a chance to look at the code yet, but > specifically how much does Pharoâs Date/Calendar capabilities match > that in the java.util package for Java 9? Additionally, is there any > way to give the number of business days between two dates for a > particular local calendar? If so, whatâs the format for a local calendar? > > > > Iâm going to take a look at the code shortly, but if anyone can shed a > general light what currently exists it would be greatly appreciated. > > > > Regards, > > Jim

Dec. 23, 2017

Re: [Pharo-dev] Calendrical capabilities

by Stephane Ducasse

Aconcagua is available via the catalog. Here is what I found in my harddisc about chronos. I can send you the zipped file with old code (probably should be ported to Pharo). On Sat, Dec 23, 2017 at 10:32 PM, <publius789(a)gmail.com> wrote: > I am new to the Pharo world and looking at capabilities for potential > applications. > > > > One of the first things I am interested in is Calendar processing > capabilities. I havenât had a chance to look at the code yet, but > specifically how much does Pharoâs Date/Calendar capabilities match that in > the java.util package for Java 9? Additionally, is there any way to give > the number of business days between two dates for a particular local > calendar? If so, whatâs the format for a local calendar? > > > > Iâm going to take a look at the code shortly, but if anyone can shed a > general light what currently exists it would be greatly appreciated. > > > > Regards, > > Jim

Dec. 23, 2017

Re: [Pharo-dev] Calendrical capabilities

by Stephane Ducasse

Hi Jim you should have a look at the Aconcagua library. It has been designed by people making business in stock management. You can find two pdfs here: http://sdmeta.gforge.inria.fr/Teaching/CoursAnnecy/0506-M1-COO/ And their authors are still around in this mailing-list. Now it may means that you have to extend it to fit your need. I like what they did. There was also a library called chronos but I do not know its status it was supporting many different calendars. Finally I think the core library should deserve some love because sometimes I see it limited but when I compare with the java counterpart I saw, it is good :). Stef On Sat, Dec 23, 2017 at 10:32 PM, <publius789(a)gmail.com> wrote: > I am new to the Pharo world and looking at capabilities for potential > applications. > > > > One of the first things I am interested in is Calendar processing > capabilities. I havenât had a chance to look at the code yet, but > specifically how much does Pharoâs Date/Calendar capabilities match that in > the java.util package for Java 9? Additionally, is there any way to give > the number of business days between two dates for a particular local > calendar? If so, whatâs the format for a local calendar? > > > > Iâm going to take a look at the code shortly, but if anyone can shed a > general light what currently exists it would be greatly appreciated. > > > > Regards, > > Jim

Dec. 23, 2017

Re: [Pharo-dev] New Year Wishlist (2018) ?

by Sean P. DeNigris

CyrilFerlicot wrote > - To be able to depend on a git project from a private server/ * > repo * > in > BaselineOf/ConfigurationOf * > and automatically clone using SSH keys if needed * (Additions to above in bold) > STABILITY Of course! I've been dreaming of most of the rest of my wishlist since 1.1, and it seems we've been creeping closer and closer: - Clean, stable low-level UI framework preserving the liveness and directness of Morphic, which also is infinitely zoomable and supports multiple (potentially simultaneously-running) worlds - 100% customizable (per instance) keybindings - Clean, customizable text editor with intuitive text model (sad to see Tx disappear, but we seem to have a replacement brewing) - Multi OS window support (not sure how close we are here) - Versionner (or its replacement) support for Baselines - hand editing is a draaaag Overall, I'm very thankful for all the progress we've made so far. Many of my wishlist items have been crossed off. Some bigger ones were: - Intuitive file library (FS) - Easy (low-barrier) contribution to other people's projects (via git/GH support) - Image management (Launcher) - Image auto-customization (startup scripts) - Single FFI library with must-have features from different existing (e.g. async callbacks) (almost there?) - Lots of integration with standard formats (NeoCSV/JSON, Pillar for MD) - Massive CI, including issue tracker integration - Cherry pick commits (Iceberg and Komitter before) - Real package model, with meta-data (RPackage and manifests) - In-editor critics with auto-transformations I can't wait to see what 2018 brings! ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Dec. 23, 2017

Calendrical capabilities

by publius789＠gmail.com

I am new to the Pharo world and looking at capabilities for potential applications. One of the first things I am interested in is Calendar processing capabilities. I haven't had a chance to look at the code yet, but specifically how much does Pharo's Date/Calendar capabilities match that in the java.util package for Java 9? Additionally, is there any way to give the number of business days between two dates for a particular local calendar? If so, what's the format for a local calendar? I'm going to take a look at the code shortly, but if anyone can shed a general light what currently exists it would be greatly appreciated. Regards, Jim

Dec. 23, 2017

Re: [Pharo-dev] New Year Wishlist (2018) ?

by StÃ©phane Ducasse

Sounds like a good wish list! > On 23 Dec 2017, at 20:33, Robert Pergl <robert.pergl(a)fit.cvut.cz> wrote: > > Dear Santa, > > this is what I wish for Pharo in 2018: > > - STABILITY > - STABILITY > - STABILITY > - STABILITY > - STABILITY > - STABILITY > - STABILITY > - STABILITY > - STABILITY > - STABILITY > - STABILITY > - STABILITY > - STABILITY > - STABILITY > > Thanks a lot! > > Your Robert > > -- > Ing. Robert Pergl, Ph.D. > Assistant Professor at Department of Software Engineering > Head of Centre for Conceptual Modelling and Implementation > ELIXIR CZ representative in the Interoperability Platform > > Czech Technical University in Prague, Faculty of Information Technology > ThÃ¡kurova 9, 160 00 Praha 6, Czech Republic > room: A-935 > http://ccmi.fit.cvut.cz <http://ccmi.fit.cvut.cz/> > http://www.fit.cvut.cz/en <http://www.fit.cvut.cz/en> > e-mail: robert.pergl(a)fit.cvut.cz <mailto:robert.pergl@fit.cvut.cz> > tel.: +420 777 042 249 > > On 23 December 2017 at 17:58, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: > Hi everybody, > > This looks like a good moment of the year to ask all of you what would you want to see in Pharo next year. > Features, improvements, radical changes, etcâ¦. whatever you want. > > Of course, this list will not be a roadmap and it does not means we will implement all of it (as always, time drives our possibilities), but is a good moment for us a a community to check where we are and where we wan to go next :) > > So, letâs those wishes come! > > cheers, > Esteban > -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr http://www.synectique.eu / http://www.pharo.org 03 59 35 87 52 Assistant: Julie Jonas FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

Dec. 23, 2017

Re: [Pharo-dev] New Year Wishlist (2018) ?

by Cyril Ferlicot D.

On 12/23/2017 05:58 PM, Esteban Lorenzano wrote: > Hi everybody, > Hi :) > This looks like a good moment of the year to ask all of you what would you want to see in Pharo next year. > Features, improvements, radical changes, etcâ¦. whatever you want. > I'll list the things I wanted the most those last months :) - To be able to load a private git project from a private server via Metacello API - To be able to depend on a git project from a private server in BaselineOf/ConfigurationOf - 64bits vm more recent that does not crash 1/4 of the time (It would help to deploy apps for some customers with older linux distributions) - 64bits Windows vm (But as far as I know, there is progress on this side already) - Continue to push Iceberg (I am not really specific because I want a lot on that part. For more details, I open issues on Iceberg repository often :) ) All those points are in the optic to make business with Pharo easier. > Of course, this list will not be a roadmap and it does not means we will implement all of it (as always, time drives our possibilities), but is a good moment for us a a community to check where we are and where we wan to go next :) > Of course :) > So, letâs those wishes come! > Also, I would like to thanks everyone because I really like my Pharo journey and it would not be possible without you! :) > cheers, > Esteban > -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

Dec. 23, 2017

New Year Wishlist (2018) ?

by Esteban Lorenzano

Hi everybody, This looks like a good moment of the year to ask all of you what would you want to see in Pharo next year. Features, improvements, radical changes, etcâ¦. whatever you want. Of course, this list will not be a roadmap and it does not means we will implement all of it (as always, time drives our possibilities), but is a good moment for us a a community to check where we are and where we wan to go next :) So, letâs those wishes come! cheers, Esteban

Dec. 23, 2017

[Pharo 7.0-dev] Build #398: SUCCESS

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #398 was: SUCCESS. Could not extract further issue information from commit message: Looks ok and simple Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Dec. 23, 2017

Re: [Pharo-dev] TLS Version supported by Zinc/Pharo

by Nicolas Cellier

2017-12-22 21:07 GMT+01:00 Stephane Ducasse <stepharo.self(a)gmail.com>: > Hi nicolas > > May be I'm naive and dull but indeed using branches is the way to go. > We used that for Pillar. > I can integrate fixes for the current stable in master and we are > coding in a dedicated branch. > > I imagine that you know it, else you would not wish to use it. > Hi steph, If I had the dictatorship, I would not only wish ;) Git supports branches and usually good processes are > - dev in local branches until it is ready and stable to merge in master > - master is always the stable version > and different builds can trigger and test different branches. > > So do I guess correctly that the VM code is not managed that way? > This is surprising because all complex projects are managed that way with > git. > In fact good branching is one of the best features of git. > > > The problem is partly cultural, but not exclusively. Main specificity to take into account is that most part of development does not happen in github. It happens in VMMaker and VM simulation, ask Clement or Eliot. That explains why the github part can be seen as secondary... and why adoption of better practices is slow. And don't forget that code generation is not yet reproducible. Type inference vary from one invocation to another (due to unordered methodDictionary probably). Until we fix that, we cannot really profit by full github features and increased automation. Branches should be as short as possible, or they get impracticle. We cannot reasonnably use separate branches for sista nor lowcode for example. I mean we could, but would have to merge frequently in trunk (cog). Look how difficult it is to merge classic VMMaker and oscog branches already. Branches are easy to use for modification of platform specific source code, but they are not so much for VMMaker generated code. Concurrent modification of generated code often create many conflicts that cannot reasonnably nor safely be merged. That means that github PR does not really work for VMMaker work (unless non-concurrent). Nevertheless we should use branches and PR for small changes... Before giving lessons, I have to discipline myself. I still commit in trunk too often just because I can. You know, do what I say, not what I do ;) Stef > > > On Fri, Dec 22, 2017 at 5:35 PM, Nicolas Cellier > <nicolas.cellier.aka.nice(a)gmail.com> wrote: > > Hi Norbert, > > having something integrated into the VM is not necessarily hard. > > The pull request of Holger has been accepted fast enough. > > So your point is maybe more about delivery of the binary artefacts. > > > > The pharo builds have been broken for some time but are now fixed, > thanks to > > Fabio/Christophe/Clement/Esteban! > > I wish we can preserve the green status longer this time. > > > > The question is then about the release cycle which is well too > loooonnng... > > Continuous integration require GREEN builds, I wish we start using > feature > > branchs and reject half-ready PR > > Then stability of head revision (cog) also matters. > > Automated tests don't catch all problems. > > Changing the garbage collector for example may trigger rare bugs... > > > > Maybe some essential (and limited) patch could be back-ported to well > known > > stable point. > > But this can't happen with current ressources... > > IOW help is welcome! > > > > Nicolas > > > > > > 2017-12-22 16:31 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > >> > >> the week I return from holidays Iâm planing to get all that done (vm > >> stuff). > >> > >> Esteban > >> > >> > On 22 Dec 2017, at 16:17, Norbert Hartl <norbert(a)hartl.name> wrote: > >> > > >> > I had that problem when openssl 1.1x library was present and SqueakSSL > >> > uses 1.0.2 library. The patch is done by Holger and ready to be > integrated. > >> > But as always it is close to impossible to having something > integrated in > >> > the vm. > >> > > >> > Norbert > >> > > >> > > >> >> Am 22.12.2017 um 16:12 schrieb Torsten Bergmann <astares(a)gmx.de>: > >> >> > >> >> Hi, > >> >> > >> >> I used ZnClient to call an HTTPS URL and while it worked well in the > >> >> past > >> >> I now receive an "SSL Exception: connect failed [code:-5]". > >> >> > >> >> I guess the reason is an update of the URLs site to a server with > newer > >> >> TLS > >> >> protocol (TLS 1.2 instead of TLS 1.0). > >> >> > >> >> Do we support that already in Pharo? > >> >> > >> >> Thx > >> >> T. > >> > > >> > >> > > > >

Dec. 22, 2017

Re: [Pharo-dev] TLS Version supported by Zinc/Pharo

by Stephane Ducasse

Hi nicolas May be I'm naive and dull but indeed using branches is the way to go. We used that for Pillar. I can integrate fixes for the current stable in master and we are coding in a dedicated branch. I imagine that you know it, else you would not wish to use it. Git supports branches and usually good processes are - dev in local branches until it is ready and stable to merge in master - master is always the stable version and different builds can trigger and test different branches. So do I guess correctly that the VM code is not managed that way? This is surprising because all complex projects are managed that way with git. In fact good branching is one of the best features of git. Stef On Fri, Dec 22, 2017 at 5:35 PM, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: > Hi Norbert, > having something integrated into the VM is not necessarily hard. > The pull request of Holger has been accepted fast enough. > So your point is maybe more about delivery of the binary artefacts. > > The pharo builds have been broken for some time but are now fixed, thanks to > Fabio/Christophe/Clement/Esteban! > I wish we can preserve the green status longer this time. > > The question is then about the release cycle which is well too loooonnng... > Continuous integration require GREEN builds, I wish we start using feature > branchs and reject half-ready PR > Then stability of head revision (cog) also matters. > Automated tests don't catch all problems. > Changing the garbage collector for example may trigger rare bugs... > > Maybe some essential (and limited) patch could be back-ported to well known > stable point. > But this can't happen with current ressources... > IOW help is welcome! > > Nicolas > > > 2017-12-22 16:31 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >> >> the week I return from holidays Iâm planing to get all that done (vm >> stuff). >> >> Esteban >> >> > On 22 Dec 2017, at 16:17, Norbert Hartl <norbert(a)hartl.name> wrote: >> > >> > I had that problem when openssl 1.1x library was present and SqueakSSL >> > uses 1.0.2 library. The patch is done by Holger and ready to be integrated. >> > But as always it is close to impossible to having something integrated in >> > the vm. >> > >> > Norbert >> > >> > >> >> Am 22.12.2017 um 16:12 schrieb Torsten Bergmann <astares(a)gmx.de>: >> >> >> >> Hi, >> >> >> >> I used ZnClient to call an HTTPS URL and while it worked well in the >> >> past >> >> I now receive an "SSL Exception: connect failed [code:-5]". >> >> >> >> I guess the reason is an update of the URLs site to a server with newer >> >> TLS >> >> protocol (TLS 1.2 instead of TLS 1.0). >> >> >> >> Do we support that already in Pharo? >> >> >> >> Thx >> >> T. >> > >> >> >

Dec. 22, 2017

Re: [Pharo-dev] TLS Version supported by Zinc/Pharo

by Sean P. DeNigris

Nicolas Cellier wrote > The pharo builds have been broken for some time but are now fixed, thanks > to Fabio/Christophe/Clement/Esteban! THANK YOU ALL!!!!! ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Dec. 22, 2017

Re: [Pharo-dev] TLS Version supported by Zinc/Pharo

by Nicolas Cellier

Hi Norbert, having something integrated into the VM is not necessarily hard. The pull request of Holger has been accepted fast enough. So your point is maybe more about delivery of the binary artefacts. The pharo builds have been broken for some time but are now fixed, thanks to Fabio/Christophe/Clement/Esteban! I wish we can preserve the green status longer this time. The question is then about the release cycle which is well too loooonnng... Continuous integration require GREEN builds, I wish we start using feature branchs and reject half-ready PR Then stability of head revision (cog) also matters. Automated tests don't catch all problems. Changing the garbage collector for example may trigger rare bugs... Maybe some essential (and limited) patch could be back-ported to well known stable point. But this can't happen with current ressources... IOW help is welcome! Nicolas 2017-12-22 16:31 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > the week I return from holidays Iâm planing to get all that done (vm > stuff). > > Esteban > > > On 22 Dec 2017, at 16:17, Norbert Hartl <norbert(a)hartl.name> wrote: > > > > I had that problem when openssl 1.1x library was present and SqueakSSL > uses 1.0.2 library. The patch is done by Holger and ready to be integrated. > But as always it is close to impossible to having something integrated in > the vm. > > > > Norbert > > > > > >> Am 22.12.2017 um 16:12 schrieb Torsten Bergmann <astares(a)gmx.de>: > >> > >> Hi, > >> > >> I used ZnClient to call an HTTPS URL and while it worked well in the > past > >> I now receive an "SSL Exception: connect failed [code:-5]". > >> > >> I guess the reason is an update of the URLs site to a server with newer > TLS > >> protocol (TLS 1.2 instead of TLS 1.0). > >> > >> Do we support that already in Pharo? > >> > >> Thx > >> T. > > > > >

Dec. 22, 2017

Re: [Pharo-dev] TLS Version supported by Zinc/Pharo

by Esteban Lorenzano

the week I return from holidays Iâm planing to get all that done (vm stuff). Esteban > On 22 Dec 2017, at 16:17, Norbert Hartl <norbert(a)hartl.name> wrote: > > I had that problem when openssl 1.1x library was present and SqueakSSL uses 1.0.2 library. The patch is done by Holger and ready to be integrated. But as always it is close to impossible to having something integrated in the vm. > > Norbert > > >> Am 22.12.2017 um 16:12 schrieb Torsten Bergmann <astares(a)gmx.de>: >> >> Hi, >> >> I used ZnClient to call an HTTPS URL and while it worked well in the past >> I now receive an "SSL Exception: connect failed [code:-5]". >> >> I guess the reason is an update of the URLs site to a server with newer TLS >> protocol (TLS 1.2 instead of TLS 1.0). >> >> Do we support that already in Pharo? >> >> Thx >> T. >

Dec. 22, 2017

Re: [Pharo-dev] TLS Version supported by Zinc/Pharo

by Norbert Hartl

I had that problem when openssl 1.1x library was present and SqueakSSL uses 1.0.2 library. The patch is done by Holger and ready to be integrated. But as always it is close to impossible to having something integrated in the vm. Norbert > Am 22.12.2017 um 16:12 schrieb Torsten Bergmann <astares(a)gmx.de>: > > Hi, > > I used ZnClient to call an HTTPS URL and while it worked well in the past > I now receive an "SSL Exception: connect failed [code:-5]". > > I guess the reason is an update of the URLs site to a server with newer TLS > protocol (TLS 1.2 instead of TLS 1.0). > > Do we support that already in Pharo? > > Thx > T.

Dec. 22, 2017

TLS Version supported by Zinc/Pharo

by Torsten Bergmann

Hi, I used ZnClient to call an HTTPS URL and while it worked well in the past I now receive an "SSL Exception: connect failed [code:-5]". I guess the reason is an update of the URLs site to a server with newer TLS protocol (TLS 1.2 instead of TLS 1.0). Do we support that already in Pharo? Thx T.

Dec. 22, 2017

[Pharo 7.0-dev] Build #396: 20886-Undeclared-RBMethodHasNoTimeStampRule-

by ci-pharo-ci-jenkins2＠inria.fr

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

Dec. 22, 2017

[Pharo 7.0-dev] Build #395: 20813-Improve-comments-of-ifNotNil-and-ifNotNilifNil

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #395 was: SUCCESS. The Pull Request #618 was integrated: "20813-Improve-comments-of-ifNotNil-and-ifNotNilifNil" Pull request url: https://github.com/pharo-project/pharo/pull/618 Issue Url: https://pharo.fogbugz.com/f/cases/20813 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Dec. 22, 2017

Re: [Pharo-dev] [ANN] Gemtalk Systems upgraded to Gold Membership

by Esteban Lorenzano

thanks! > On 22 Dec 2017, at 08:32, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > The Pharo Consortium is very happy to announce that Gemtalk Systems > has upgraded to Gold Member status. > > About > - Gemtalk Systems: https://gemtalksystems.com > - Pharo Consortium: http://consortium.pharo.org > > The goal of the Pharo Consortium is to allow companies and institutions to > support the ongoing development and future of Pharo. > > Individuals can support Pharo via the Pharo Association: > > http://association.pharo.org >

Dec. 22, 2017

Re: [Pharo-dev] Updating CI plugins

by Guillermo Polito

Jenkins and slaves are up un running. Let's cross fingers hoping everything is ok :) Keep you updated On Fri, Dec 22, 2017 at 10:14 AM, Guillermo Polito < guillermopolito(a)gmail.com> wrote: > Christophe is also taking benefit of this to update jenkins from 2.32.3 > LTS to 2.89.2 LTS > > On Fri, Dec 22, 2017 at 10:06 AM, Guillermo Polito < > guillermopolito(a)gmail.com> wrote: > >> Hi all, >> >> I'm updating CI plugins. *This will require a CI restart. *The >> corresponding issue is here: >> >> https://pharo.fogbugz.com/f/cases/20884/Update-CI-Plugins >> >> The installed versions are the following: >> >> Workspace Cleanup Plugin 0.34 0.33 >> SCM API Plugin 2.2.6 2.2.1 >> Pipeline Utility Steps 1.5.1 1.4.1 >> Pipeline: API 2.24 2.20 >> Pipeline: Build Step 2.6 2.5.1 >> Pipeline: Declarative 1.2.5 1.1.9 >> Pipeline: Declarative Extension Points API 1.2.5 1.1.9 >> Pipeline: Groovy 2.41 2.40 >> Pipeline: Model API 1.2.5 1.1.9 >> Pipeline: Nodes and Processes 2.16 2.15 >> Pipeline: Shared Groovy Libraries 2.9 2.8 >> Pipeline: Stage Step 2.3 2.2 >> Pipeline: Stage Tags Metadata 1.2.5 1.1.9 >> Pipeline: Step API 2.14 2.12 >> Rebuilder 1.27 1.25 >> JUnit Plugin 1.23 1.21 >> Git client plugin 2.7.0 2.5.0 >> Git plugin 3.6.4 3.5.1 >> GitHub API Plugin 1.90 1.86 >> GitHub Branch Source Plugin 2.3.2 2.2.3 >> GitHub plugin 1.28.1 1.28.0 >> Copy Artifact Plugin 1.39 1.38.1 >> Credentials Plugin 2.1.16 2.1.15 >> Build Timeout 1.19 1.18 >> Conditional BuildStep 1.3.6 1.3.5 >> >> I'll keep you updated as soon as the update is finished. >> Guille >> >> >> -- >> >> >> >> Guille Polito >> >> Research Engineer >> >> Centre de Recherche en Informatique, Signal et Automatique de Lille >> >> CRIStAL - UMR 9189 >> >> French National Center for Scientific Research - *http://www.cnrs.fr >> <http://www.cnrs.fr>* >> >> >> *Web:* *http://guillep.github.io* <http://guillep.github.io> >> >> *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013> >> > > > > -- > > > > Guille Polito > > Research Engineer > > Centre de Recherche en Informatique, Signal et Automatique de Lille > > CRIStAL - UMR 9189 > > French National Center for Scientific Research - *http://www.cnrs.fr > <http://www.cnrs.fr>* > > > *Web:* *http://guillep.github.io* <http://guillep.github.io> > > *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013> > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

Dec. 22, 2017

Re: [Pharo-dev] Updating CI plugins

by Guillermo Polito

Christophe is also taking benefit of this to update jenkins from 2.32.3 LTS to 2.89.2 LTS On Fri, Dec 22, 2017 at 10:06 AM, Guillermo Polito < guillermopolito(a)gmail.com> wrote: > Hi all, > > I'm updating CI plugins. *This will require a CI restart. *The > corresponding issue is here: > > https://pharo.fogbugz.com/f/cases/20884/Update-CI-Plugins > > The installed versions are the following: > > Workspace Cleanup Plugin 0.34 0.33 > SCM API Plugin 2.2.6 2.2.1 > Pipeline Utility Steps 1.5.1 1.4.1 > Pipeline: API 2.24 2.20 > Pipeline: Build Step 2.6 2.5.1 > Pipeline: Declarative 1.2.5 1.1.9 > Pipeline: Declarative Extension Points API 1.2.5 1.1.9 > Pipeline: Groovy 2.41 2.40 > Pipeline: Model API 1.2.5 1.1.9 > Pipeline: Nodes and Processes 2.16 2.15 > Pipeline: Shared Groovy Libraries 2.9 2.8 > Pipeline: Stage Step 2.3 2.2 > Pipeline: Stage Tags Metadata 1.2.5 1.1.9 > Pipeline: Step API 2.14 2.12 > Rebuilder 1.27 1.25 > JUnit Plugin 1.23 1.21 > Git client plugin 2.7.0 2.5.0 > Git plugin 3.6.4 3.5.1 > GitHub API Plugin 1.90 1.86 > GitHub Branch Source Plugin 2.3.2 2.2.3 > GitHub plugin 1.28.1 1.28.0 > Copy Artifact Plugin 1.39 1.38.1 > Credentials Plugin 2.1.16 2.1.15 > Build Timeout 1.19 1.18 > Conditional BuildStep 1.3.6 1.3.5 > > I'll keep you updated as soon as the update is finished. > Guille > > > -- > > > > Guille Polito > > Research Engineer > > Centre de Recherche en Informatique, Signal et Automatique de Lille > > CRIStAL - UMR 9189 > > French National Center for Scientific Research - *http://www.cnrs.fr > <http://www.cnrs.fr>* > > > *Web:* *http://guillep.github.io* <http://guillep.github.io> > > *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013> > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

Dec. 22, 2017

Updating CI plugins

by Guillermo Polito

Hi all, I'm updating CI plugins. *This will require a CI restart. *The corresponding issue is here: https://pharo.fogbugz.com/f/cases/20884/Update-CI-Plugins The installed versions are the following: Workspace Cleanup Plugin 0.34 0.33 SCM API Plugin 2.2.6 2.2.1 Pipeline Utility Steps 1.5.1 1.4.1 Pipeline: API 2.24 2.20 Pipeline: Build Step 2.6 2.5.1 Pipeline: Declarative 1.2.5 1.1.9 Pipeline: Declarative Extension Points API 1.2.5 1.1.9 Pipeline: Groovy 2.41 2.40 Pipeline: Model API 1.2.5 1.1.9 Pipeline: Nodes and Processes 2.16 2.15 Pipeline: Shared Groovy Libraries 2.9 2.8 Pipeline: Stage Step 2.3 2.2 Pipeline: Stage Tags Metadata 1.2.5 1.1.9 Pipeline: Step API 2.14 2.12 Rebuilder 1.27 1.25 JUnit Plugin 1.23 1.21 Git client plugin 2.7.0 2.5.0 Git plugin 3.6.4 3.5.1 GitHub API Plugin 1.90 1.86 GitHub Branch Source Plugin 2.3.2 2.2.3 GitHub plugin 1.28.1 1.28.0 Copy Artifact Plugin 1.39 1.38.1 Credentials Plugin 2.1.16 2.1.15 Build Timeout 1.19 1.18 Conditional BuildStep 1.3.6 1.3.5 I'll keep you updated as soon as the update is finished. Guille -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

Dec. 22, 2017

[ANN] Gemtalk Systems upgraded to Gold Membership

by Marcus Denker

The Pharo Consortium is very happy to announce that Gemtalk Systems has upgraded to Gold Member status. About - Gemtalk Systems: https://gemtalksystems.com - Pharo Consortium: http://consortium.pharo.org The goal of the Pharo Consortium is to allow companies and institutions to support the ongoing development and future of Pharo. Individuals can support Pharo via the Pharo Association: http://association.pharo.org

Dec. 22, 2017

Re: [Pharo-dev] Linux vm packages

by Norbert Hartl

> Am 22.12.2017 um 08:03 schrieb Stephane Ducasse <stepharo.self(a)gmail.com>: > > Let us make clear what I think! > > What I mean is that we are losing OUR/MY time maintaining information > for versions that we > cannot even run and the information is all the time obsolete. Because > let us face it > with the millions different configurations what is the probability > that it will be up to date? > Each time I have students, this information is obsolete or not working > on their specific > version. > There is no need to exaggerate if you have real point. We did this linux move (to opensuse) in order to make the situation better. With this it is easy to install the vm on linux. There is not much magic. The only point is that Holger wrote the initial description which was incomplete. I corrected the version and sent it to the mailing list but it didnât make it to the website for too long. Now there is one or two corrections not much. The installation instruction will change every time a new linux version comes out. > Don't you all think that Marcus could concentrate better on making a > pass on Opal > if he would not have to split his time into many small details? > That is exactly the same for everyone here!! > So if you want to help then perfect. I think that having a travis job > and extracting the information > from the job would be a lot better process. > > Like a test and a method comment. **EXECUTABLE** and **TESTED**. > Ok then you should describe how this process works and where we can use it. If this process does not exist Iâm not sure what you trying to tell... Norbert > Stef > > >> On Fri, Dec 22, 2017 at 7:52 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> I have done all the changes last week. >> >>> On 21 Dec 2017, at 21:17, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >>> >>> Someone install and using Pharo on Linux should maintain this page. >>> I would simply remove it because this is just a pain to maintain a >>> description for system that we cannot even >>> use. >>> >>> >>> >>>> On Sun, Nov 26, 2017 at 1:52 PM, Norbert Hartl <norbert(a)hartl.name> wrote: >>>> Can we change linux installation instructions on the web site? I can't >>>> believe they aren't there, yet. Here is the description. >>>> >>>> http://forum.world.st/Latest-Debian-Ubuntu-and-CentOS-packages-of-the-pharo… >>>> >>>> This describes what to do for some linux distributions not only ubuntu. In >>>> the mail there are opensuse URLs. The all contain the word "latest" which >>>> means the development version. If this is exchanged with "stable" you get >>>> the stable version. The rest stays the same. >>>> >>>> I really should have checked this. Because it is just stupid that people >>>> spend a lot of work into that and it is not used nor published. >>>> >>>> If I can help please say so!!!! >>>> >>>> Norbert >>>> >>> >> >>

Dec. 22, 2017

Re: [Pharo-dev] Linux vm packages

by Stephane Ducasse

> I have done all the changes last week. And then it does not satisfy me because... read the other mail. > >> On 21 Dec 2017, at 21:17, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >> >> Someone install and using Pharo on Linux should maintain this page. >> I would simply remove it because this is just a pain to maintain a >> description for system that we cannot even >> use. >> >> >> >> On Sun, Nov 26, 2017 at 1:52 PM, Norbert Hartl <norbert(a)hartl.name> wrote: >>> Can we change linux installation instructions on the web site? I can't >>> believe they aren't there, yet. Here is the description. >>> >>> http://forum.world.st/Latest-Debian-Ubuntu-and-CentOS-packages-of-the-pharo… >>> >>> This describes what to do for some linux distributions not only ubuntu. In >>> the mail there are opensuse URLs. The all contain the word "latest" which >>> means the development version. If this is exchanged with "stable" you get >>> the stable version. The rest stays the same. >>> >>> I really should have checked this. Because it is just stupid that people >>> spend a lot of work into that and it is not used nor published. >>> >>> If I can help please say so!!!! >>> >>> Norbert >>> >> > >

Dec. 22, 2017

Re: [Pharo-dev] Linux vm packages

by Stephane Ducasse

Let us make clear what I think! What I mean is that we are losing OUR/MY time maintaining information for versions that we cannot even run and the information is all the time obsolete. Because let us face it with the millions different configurations what is the probability that it will be up to date? Each time I have students, this information is obsolete or not working on their specific version. Don't you all think that Marcus could concentrate better on making a pass on Opal if he would not have to split his time into many small details? So if you want to help then perfect. I think that having a travis job and extracting the information from the job would be a lot better process. Like a test and a method comment. **EXECUTABLE** and **TESTED**. Stef On Fri, Dec 22, 2017 at 7:52 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > I have done all the changes last week. > >> On 21 Dec 2017, at 21:17, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >> >> Someone install and using Pharo on Linux should maintain this page. >> I would simply remove it because this is just a pain to maintain a >> description for system that we cannot even >> use. >> >> >> >> On Sun, Nov 26, 2017 at 1:52 PM, Norbert Hartl <norbert(a)hartl.name> wrote: >>> Can we change linux installation instructions on the web site? I can't >>> believe they aren't there, yet. Here is the description. >>> >>> http://forum.world.st/Latest-Debian-Ubuntu-and-CentOS-packages-of-the-pharo… >>> >>> This describes what to do for some linux distributions not only ubuntu. In >>> the mail there are opensuse URLs. The all contain the word "latest" which >>> means the development version. If this is exchanged with "stable" you get >>> the stable version. The rest stays the same. >>> >>> I really should have checked this. Because it is just stupid that people >>> spend a lot of work into that and it is not used nor published. >>> >>> If I can help please say so!!!! >>> >>> Norbert >>> >> > >

Dec. 22, 2017

Re: [Pharo-dev] Linux vm packages

by Marcus Denker

I have done all the changes last week. > On 21 Dec 2017, at 21:17, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > Someone install and using Pharo on Linux should maintain this page. > I would simply remove it because this is just a pain to maintain a > description for system that we cannot even > use. > > > > On Sun, Nov 26, 2017 at 1:52 PM, Norbert Hartl <norbert(a)hartl.name> wrote: >> Can we change linux installation instructions on the web site? I can't >> believe they aren't there, yet. Here is the description. >> >> http://forum.world.st/Latest-Debian-Ubuntu-and-CentOS-packages-of-the-pharo… >> >> This describes what to do for some linux distributions not only ubuntu. In >> the mail there are opensuse URLs. The all contain the word "latest" which >> means the development version. If this is exchanged with "stable" you get >> the stable version. The rest stays the same. >> >> I really should have checked this. Because it is just stupid that people >> spend a lot of work into that and it is not used nor published. >> >> If I can help please say so!!!! >> >> Norbert >> >

Dec. 22, 2017

Re: [Pharo-dev] Linux vm packages

by Cyril Ferlicot D.

Le 21/12/2017 Ã 21:17, Stephane Ducasse a Ã©critÂ : > Someone install and using Pharo on Linux should maintain this page. > I would simply remove it because this is just a pain to maintain a > description for system that we cannot even > use. > > > This is one of the most important page of the website for those using linux but who are not pros. It saved me a lot of time when I installed my debian server and I lost time after installing a Fedora because the instructions were not there. And I was lucky to find a part of the infos on internet. Even if the infos are not always up to date or totally correct, it is still a huge help. -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

Dec. 21, 2017

Re: [Pharo-dev] Linux vm packages

by Norbert Hartl

What do you mean with that? Sounds inadequate to me!! Norbert > Am 21.12.2017 um 21:17 schrieb Stephane Ducasse <stepharo.self(a)gmail.com>: > > Someone install and using Pharo on Linux should maintain this page. > I would simply remove it because this is just a pain to maintain a > description for system that we cannot even > use. > > > >> On Sun, Nov 26, 2017 at 1:52 PM, Norbert Hartl <norbert(a)hartl.name> wrote: >> Can we change linux installation instructions on the web site? I can't >> believe they aren't there, yet. Here is the description. >> >> http://forum.world.st/Latest-Debian-Ubuntu-and-CentOS-packages-of-the-pharo… >> >> This describes what to do for some linux distributions not only ubuntu. In >> the mail there are opensuse URLs. The all contain the word "latest" which >> means the development version. If this is exchanged with "stable" you get >> the stable version. The rest stays the same. >> >> I really should have checked this. Because it is just stupid that people >> spend a lot of work into that and it is not used nor published. >> >> If I can help please say so!!!! >> >> Norbert >>

Dec. 21, 2017

Re: [Pharo-dev] Linux vm packages

by Stephane Ducasse

Someone install and using Pharo on Linux should maintain this page. I would simply remove it because this is just a pain to maintain a description for system that we cannot even use. On Sun, Nov 26, 2017 at 1:52 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > Can we change linux installation instructions on the web site? I can't > believe they aren't there, yet. Here is the description. > > http://forum.world.st/Latest-Debian-Ubuntu-and-CentOS-packages-of-the-pharo… > > This describes what to do for some linux distributions not only ubuntu. In > the mail there are opensuse URLs. The all contain the word "latest" which > means the development version. If this is exchanged with "stable" you get > the stable version. The rest stays the same. > > I really should have checked this. Because it is just stupid that people > spend a lot of work into that and it is not used nor published. > > If I can help please say so!!!! > > Norbert >

Dec. 21, 2017

Dotted selectors?

by Stephane Ducasse

Hi I would like to know if this is a well known iceberg bug because I have many removal of selector with the period at the end and I have no idea what to do? stef

Dec. 21, 2017

Re: [Pharo-dev] Credentials for Metacello

by Sean P. DeNigris

NorbertHartl wrote > - I cannot use filetree:// to load the project because the dependent > projects are loaded as zip via https and there seems to be no way to > specify credentials IIRC I made a patch for this at some point, but then lost interest because I was ultimately unwilling to have plain text credentials floating around in my image, so I moved everything to git with plain filetree:// URLs in my baselines. Of course, I ran into similar problems as you did once I tried to get all the CI working. Although, from your answer in the other thread, it seems that I can now get everything working on GitLab with SmalltalkCI (delta the VM instability issue). If you need HTTPS credentials, maybe Dale remembers something about the fix (I may have sent it to him) or I can look on my machine and see if I still have it. ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Dec. 21, 2017

Re: [Pharo-dev] Download Pharo for GNU/Linux - wrong info on that page

by Marcus Denker

Thanks, I updated the page (and the 64 bit page, too) > On 21 Dec 2017, at 14:30, Petr Fischer <petr.fischer(a)me.com> wrote: > > Hello, this page: > > https://pharo.org/gnu-linux-installation > > 1) in examples, there is a usage of "yum-config-manager" command, add a note that "yum-utils" package must be installed > > 2) correct all paths to the opensuse repos please, at least this is wrong: > > CentOS 7 (only 64bit): > http://download.opensuse.org/repositories/devel:/languages:/pharo:/stable/C… > > Correct URL is probably: > http://download.opensuse.org/repositories/devel:/languages:/pharo:/stable/C… > > pf >

Dec. 21, 2017

Download Pharo for GNU/Linux - wrong info on that page

by Petr Fischer

Hello, this page: https://pharo.org/gnu-linux-installation 1) in examples, there is a usage of "yum-config-manager" command, add a note that "yum-utils" package must be installed 2) correct all paths to the opensuse repos please, at least this is wrong: CentOS 7 (only 64bit): http://download.opensuse.org/repositories/devel:/languages:/pharo:/stable/C… Correct URL is probably: http://download.opensuse.org/repositories/devel:/languages:/pharo:/stable/C… pf

Dec. 21, 2017

Re: [Pharo-dev] Problem with ZipArchive (probably bug due to large file)

by Pavel Krivanek

Pharo does not support Zip64 file format so it cannot work with big files nor files with huge amount of files. -- Pavel 2017-12-21 12:54 GMT+01:00 Mariano Martinez Peck <marianopeck(a)gmail.com>: > Hi guys, > > I discovered a problem with ZipArchive when using Metacello to download a > zipball of a github project. The project in question is HighchartsSt (soon > we will make a new release and ANN) and this repo has *a lot* of > autogenerated code. By a lot, I mean that the ZIP file is about 90MB. > > I do understand the recommended approach with git is to clone (either > externally or with Iceberg), then work with your local clone via filetree > or tonel, and finally lock it. When you do this, ZipArchive is not used and > hence I have no problem. > > However, even if not the recommended path, I know there are people still > getting projects with Metacello from remote urls from github and hence the > zipball download is in play. > > The problem in question is an error reading the zip signature. We believe > it happens only with very big zips (smaller zips do work) and one way to > reproduce it is as simple as this: > > > outputFileName := '/tmp/test.zip'. > ZnClient new > url: 'https://github.com/ba-st/HighchartsSt/zipball/ > highchart6-import'; > downloadTo: outputFileName. > ZipArchive new > readFrom: outputFileName asFileReference > > > Some info I could get is that the zip itself looks good: > > Curl is able to download: > > â¯ curl -L https://github.com/ba-st/HighchartsSt/zipball/highchart6-import > > highcharts.zip > > â¯ ls -lah highcharts.zip > [23:18:06] > -rw-r--r-- 1 mariano staff 79M Dec 18 23:14 highcharts.zip > > and zip seems valid: > > â¯ unzip -q -t highcharts.zip > [23:18:33] > No errors detected in compressed data of highcharts.zip. > > > Anyway, if there is someone with some knowledge in ZipArchive that could > give us a hand.... > > Thank you very much in advance, > > > > -- > Mariano > http://marianopeck.wordpress.com >

Dec. 21, 2017

Problem with ZipArchive (probably bug due to large file)

by Mariano Martinez Peck

Hi guys, I discovered a problem with ZipArchive when using Metacello to download a zipball of a github project. The project in question is HighchartsSt (soon we will make a new release and ANN) and this repo has *a lot* of autogenerated code. By a lot, I mean that the ZIP file is about 90MB. I do understand the recommended approach with git is to clone (either externally or with Iceberg), then work with your local clone via filetree or tonel, and finally lock it. When you do this, ZipArchive is not used and hence I have no problem. However, even if not the recommended path, I know there are people still getting projects with Metacello from remote urls from github and hence the zipball download is in play. The problem in question is an error reading the zip signature. We believe it happens only with very big zips (smaller zips do work) and one way to reproduce it is as simple as this: outputFileName := '/tmp/test.zip'. ZnClient new url: ' https://github.com/ba-st/HighchartsSt/zipball/highchart6-import'; downloadTo: outputFileName. ZipArchive new readFrom: outputFileName asFileReference Some info I could get is that the zip itself looks good: Curl is able to download: â¯ curl -L https://github.com/ba-st/HighchartsSt/zipball/highchart6-import > highcharts.zip â¯ ls -lah highcharts.zip [23:18:06] -rw-r--r-- 1 mariano staff 79M Dec 18 23:14 highcharts.zip and zip seems valid: â¯ unzip -q -t highcharts.zip [23:18:33] No errors detected in compressed data of highcharts.zip. Anyway, if there is someone with some knowledge in ZipArchive that could give us a hand.... Thank you very much in advance, -- Mariano http://marianopeck.wordpress.com

Dec. 21, 2017

Re: [Pharo-dev] Credentials for Metacello

by Thierry Goubier

gitfiletree:// urls support https credentials, but the current 64 bits vm reliably segfaults. Regards, Thierry Le 21 dÃ©c. 2017 11:23 AM, "Norbert Hartl" <norbert(a)hartl.name> a Ã©crit : I have a very annoying problem with projects referenced in metacello that are private. When I try to use that on jenkins â¦ - I cannot use filetree:// to load the project because the dependent projects are loaded as zip via https and there seems to be no way to specify credentials - when using gitlocal:// with the 64bit vm it crashes reliably - when using gitlocal:// with the 32bit vm I have all sorts of no ssh keys found Is there a best practice for that. I even made on repo public so far in order to circumvent the problem. But Iâm not willing to make all our repos public just to be able to load it via metacello Any hints? Norbert

Dec. 21, 2017

Credentials for Metacello

by Norbert Hartl

I have a very annoying problem with projects referenced in metacello that are private. When I try to use that on jenkins â¦ - I cannot use filetree:// to load the project because the dependent projects are loaded as zip via https and there seems to be no way to specify credentials - when using gitlocal:// with the 64bit vm it crashes reliably - when using gitlocal:// with the 32bit vm I have all sorts of no ssh keys found Is there a best practice for that. I even made on repo public so far in order to circumvent the problem. But Iâm not willing to make all our repos public just to be able to load it via metacello Any hints? Norbert

Dec. 21, 2017

Re: [Pharo-dev] [ANN] Pharo Consortium New Bronze Member: Object Profile

by Marcus Denker

I added this to the Pharo news page (http://pharo.org/news <http://pharo.org/news>): [ANN] Pharo Consortium New Bronze Member: Object Profile http://pharo.org/news/consortium-object-profile <http://pharo.org/news/consortium-object-profile> > On 21 Dec 2017, at 08:41, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > The Pharo Consortium is very happy to announce that Object Profile > has joined the Consortium as a Bronze Member. > > About > - Object Profile: http://objectprofile.com > - Pharo Consortium: http://consortium.pharo.org > > The goal of the Pharo Consortium is to allow companies and institutions to > support the ongoing development and future of Pharo. > > Individuals can support Pharo via the Pharo Association: > > - http://association.pharo.org

Dec. 21, 2017

Re: [Pharo-dev] Linux vm packages

by Marcus Denker

Him Thanks to Cyril Ferlicot the 32 bit page now a description for Fedora Linux: https://pharo.org/gnu-linux-installation > On 12 Dec 2017, at 17:15, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > I have added the information to the 64bit download page for now (the other comes next). > > http://pharo.org/web/gnu-linux-installation-64 > > I wonder if we continue to announce a âdefault downloadâ (the zip) if it is much easier to use these? > >> On 27 Nov 2017, at 09:22, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> I can edit the website, I can put al needed infos there. >> >> (but sometimes I am not be able to generate actions out of discussions on the mailing list, >> there is just so much going onâ¦ so if something does not happen this just means I do >> not know that it should happenâ¦) >> >>> On 26 Nov 2017, at 13:52, Norbert Hartl <norbert(a)hartl.name> wrote: >>> >>> Can we change linux installation instructions on the web site? I can't believe they aren't there, yet. Here is the description. >>> >>> http://forum.world.st/Latest-Debian-Ubuntu-and-CentOS-packages-of-the-pharo… >>> >>> This describes what to do for some linux distributions not only ubuntu. In the mail there are opensuse URLs. The all contain the word "latest" which means the development version. If this is exchanged with "stable" you get the stable version. The rest stays the same. >>> >>> I really should have checked this. Because it is just stupid that people spend a lot of work into that and it is not used nor published. >>> >>> If I can help please say so!!!! >>> >>> Norbert >>> >> >

Dec. 21, 2017

Re: [Pharo-dev] :: Separator in class names

by Pavel Krivanek

No, I do not mean changing of the prefix. Class will just say that it has prefix JS and it these letters will be displayed with a different color or something like that. -- Pavel 2017-12-21 10:33 GMT+01:00 Torsten Bergmann <astares(a)gmx.de>: > This is not the same. Lets assume you have a class JSObject with a class > side method: > > toolPrefix > ^'JS' -> 'JavaScript' > > providing such info for the tools and you use that to display it in the > browser as > > JavaScript::Object > > But still in the methods I would have to write JSObject in the code. > Which would be more confusing and useless then ... > > Bye > T. > > > Gesendet: Donnerstag, 21. Dezember 2017 um 08:25 Uhr > Von: "Pavel Krivanek" <pavel.krivanek(a)gmail.com> > An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > Betreff: Re: [Pharo-dev] :: Separator in class names > > Actually I think we do not need any change in the language syntax. Classes > can provide information about their prefix and tools can take it into > account during displaying it in the lists or code. > > -- Pavel > > 2017-12-21 0:35 GMT+01:00 Torsten Bergmann <astares@gmx.de[mailto:astares > @gmx.de]>:Remember this December thread from 2016: > > http://forum.world.st/Separator-in-class-names- > td4926162.html[http://forum.world.st/Separator-in-class- > names-td4926162.html] > > There is no need for a full blown namespace solution with scoping, > imports, .... > > Only for allowing a separator in class names. > > Within this thread I wrote: > > >Not many of you answered this thread in 2016. Maybe > >I have more luck in 2017 ;) > > Looks like one year passed and there was no luck with it. > > Any chance for 2018? ;) > > Bye > T. > > >

Dec. 21, 2017

Re: [Pharo-dev] :: Separator in class names

by Torsten Bergmann

This is not the same. Lets assume you have a class JSObject with a class side method: toolPrefix ^'JS' -> 'JavaScript' providing such info for the tools and you use that to display it in the browser as JavaScript::Object But still in the methods I would have to write JSObject in the code. Which would be more confusing and useless then ... Bye T. Gesendet:Â Donnerstag, 21. Dezember 2017 um 08:25 Uhr Von:Â "Pavel Krivanek" <pavel.krivanek(a)gmail.com> An:Â "Pharo Development List" <pharo-dev(a)lists.pharo.org> Betreff:Â Re: [Pharo-dev] :: Separator in class names Actually I think we do not need any change in the language syntax. Classes can provide information about their prefix and tools can take it into account during displaying it in the lists or code. Â -- Pavel Â 2017-12-21 0:35 GMT+01:00 Torsten Bergmann <astares@gmx.de[mailto:astares@gmx.de]>:Remember this December thread from 2016: Â http://forum.world.st/Separator-in-class-names-td4926162.html[http://forum.… There is no need for a full blown namespace solution with scoping, imports, .... Only for allowing a separator in class names. Within this thread I wrote: >Not many of you answered this thread in 2016. Maybe >I have more luck in 2017 ;) Looks like one year passed and there was no luck with it. Any chance for 2018? ;) Bye T. Â

Dec. 21, 2017

Fwd: [squeak-dev] Maybe we should apply?

by Denis Kudriashov

Interesting possibility for funding ---------- Forwarded message ---------- From: Tobias Pape <Das.Linux(a)gmx.de> Date: 2017-12-21 8:47 GMT+01:00 Subject: [squeak-dev] Maybe we should apply? To: SOB <board(a)squeak.org>, The general-purpose Squeak developers list < squeak-dev(a)lists.squeakfoundation.org> https://pineapplefund.org/ ? -t

Dec. 21, 2017

[ANN] Pharo Consortium New Bronze Member: Object Profile

by Marcus Denker

The Pharo Consortium is very happy to announce that Object Profile has joined the Consortium as a Bronze Member. About - Object Profile: http://objectprofile.com - Pharo Consortium: http://consortium.pharo.org The goal of the Pharo Consortium is to allow companies and institutions to support the ongoing development and future of Pharo. Individuals can support Pharo via the Pharo Association: - http://association.pharo.org

Dec. 21, 2017

Re: [Pharo-dev] :: Separator in class names

by Pavel Krivanek

Actually I think we do not need any change in the language syntax. Classes can provide information about their prefix and tools can take it into account during displaying it in the lists or code. -- Pavel 2017-12-21 0:35 GMT+01:00 Torsten Bergmann <astares(a)gmx.de>: > Remember this December thread from 2016: > > http://forum.world.st/Separator-in-class-names-td4926162.html > > There is no need for a full blown namespace solution with scoping, > imports, .... > > Only for allowing a separator in class names. > > Within this thread I wrote: > > >Not many of you answered this thread in 2016. Maybe > >I have more luck in 2017 ;) > > Looks like one year passed and there was no luck with it. > > Any chance for 2018? ;) > > Bye > T. > >

Dec. 21, 2017

:: Separator in class names

by Torsten Bergmann

Remember this December thread from 2016: http://forum.world.st/Separator-in-class-names-td4926162.html There is no need for a full blown namespace solution with scoping, imports, .... Only for allowing a separator in class names. Within this thread I wrote: >Not many of you answered this thread in 2016. Maybe >I have more luck in 2017 ;) Looks like one year passed and there was no luck with it. Any chance for 2018? ;) Bye T.

Dec. 20, 2017

[Pharo 7.0-dev] Build #394: 20879-ZnCrPortableWriteStreamnextPut-swallows-LFs

by ci-pharo-ci-jenkins2＠inria.fr

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

Dec. 20, 2017

[Pharo 7.0-dev] Build #393: 20861-split-and-friends-should-have-better-comments

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #393 was: FAILURE. The Pull Request #611 was integrated: "20861-split-and-friends-should-have-better-comments" Pull request url: https://github.com/pharo-project/pharo/pull/611 Issue Url: https://pharo.fogbugz.com/f/cases/20861 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Dec. 20, 2017

Re: [Pharo-dev] Is there some progress on the 64bit Metacello loading segfault problem?

by Cyril Ferlicot D.

On 12/20/2017 10:48 AM, Thierry Goubier wrote: > Hi Cyril, > > as said before, those are solved by using a more recent vm, such as the > 201710221351 linux 64bits vm. You're using an older one in the CI > (theÂ 201707201942), and, unless they have been updated, both stable and > latest pharo vms as provided by pharo.org <http://pharo.org> are > subjected to the segfault. > Ok, so we just need to wait for a new vm to be marked as stable? :) Thank you! > Regards, > > Thierry > -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

Dec. 20, 2017

Re: [Pharo-dev] Is there some progress on the 64bit Metacello loading segfault problem?

by Thierry Goubier

Hi Cyril, as said before, those are solved by using a more recent vm, such as the 201710221351 linux 64bits vm. You're using an older one in the CI (the 201707201942), and, unless they have been updated, both stable and latest pharo vms as provided by pharo.org are subjected to the segfault. Regards, Thierry 2017-12-20 10:26 GMT+01:00 Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com>: > Hi, > > There was a bug reported multiple times about segfaults during Metacello > loadings in Pharo. > > This week I setup some Jenkins builds for 64bits products and I still > see a lot of segfault. > > I cannot get a way to reproduce it 100% but it appears pretty often. > Today we got 3 crash out of around 15 builds. This is a pretty high > number of crash. > > I know it is hard to correct random crashes but was there some progress > on this problem since it was reported? > > Here is a stack trace example: > > Segmentation fault Wed Dec 20 02:25:00 2017 > > > /var/lib/jenkins/workspace/path/to/job/pharo-vm/lib/ > pharo/5.0-201707201942/pharo > Pharo VM version: 5.0-201707201942 Thu Jul 20 20:40:54 UTC 2017 gcc > 4.6.3 [Production Spur 64-bit 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-74d10329-bbfd-42e5-8995-b0e3a68c73cb > 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: > /var/lib/jenkins/workspace/path/to/job/pharo-vm/lib/pharo/5.0-201707201942 > [default: > /var/lib/jenkins/workspace/path/to/job/pharo-vm/lib/ > pharo/5.0-201707201942/] > > > C stack backtrace & registers: > rax 0xb654c100 rbx 0xb654bf90 rcx 0xb654c1b8 rdx 0xb654c048 > rdi 0xb654bd68 rsi 0xb654bd68 rbp 0xb654bed8 rsp 0xb654c270 > r8 0xb654b7a8 r9 0xb654b860 r10 0xb654b918 r11 0xb654b9d0 > r12 0xb654ba88 r13 0xb654bb40 r14 0xb654bbf8 r15 0xb654bcb0 > rip 0xb654c328 > *[0x7ffeb654c328] > /var/lib/jenkins/workspace/path/to/job/pharo-vm/lib/ > pharo/5.0-201707201942/pharo[0x41ccd1] > /var/lib/jenkins/workspace/path/to/job/pharo-vm/lib/ > pharo/5.0-201707201942/pharo[0x41d05f] > /lib/x86_64-linux-gnu/libpthread.so.0(+0x11390)[0x7f1d94d5e390] > /var/lib/jenkins/workspace/path/to/job/pharo-vm/lib/ > pharo/5.0-201707201942/pharo[0x4403cc] > /var/lib/jenkins/workspace/path/to/job/pharo-vm/lib/ > pharo/5.0-201707201942/pharo(lookupOrdinaryreceiver+0x67)[0x440777] > /var/lib/jenkins/workspace/path/to/job/pharo-vm/lib/ > pharo/5.0-201707201942/pharo(ceSICMiss+0x58)[0x493d48] > [0x21003ef] > [0x0] > > > Smalltalk stack dump: > 0x7ffeb658f8d0 M INVALID RECEIVER>isInlined 0x24f57b8 is in new space > 0x7ffeb658f900 M > OCASTTranslatorForEffect(OCASTTranslator)>visitMessageNode: 0x235e000: > a(n) OCASTTranslatorForEffect > 0x7ffeb658f938 M INVALID RECEIVER>acceptVisitor: 0x24f57b8 is in new > space > 0x7ffeb658f970 M > OCASTTranslatorForEffect(RBProgramNodeVisitor)>visitNode: 0x235e000: > a(n) OCASTTranslatorForEffect > 0x7ffeb658f9a8 M > OCASTTranslatorForEffect(OCASTTranslator)>visitNode: 0x235e000: a(n) > OCASTTranslatorForEffect > 0x7ffeb658f9e0 M [] in > OCASTTranslatorForValue(OCASTTranslator)>visitCascadeNode: 0x235ea58: > a(n) OCASTTranslatorForValue > 0x7ffeb658fa28 M > OrderedCollection(SequenceableCollection)>allButLastDo: 0x235ea98: a(n) > OrderedCollection > 0x7ffeb658fa60 M > OCASTTranslatorForValue(OCASTTranslator)>visitCascadeNode: 0x235ea58: > a(n) OCASTTranslatorForValue > 0x7ffeb658fa98 M RBCascadeNode>acceptVisitor: 0x235eb70: a(n) > RBCascadeNode > 0x7ffeb658fad0 M > OCASTTranslatorForValue(RBProgramNodeVisitor)>visitNode: 0x235ea58: a(n) > OCASTTranslatorForValue > 0x7ffeb658fb08 M OCASTTranslatorForValue(OCASTTranslator)>visitNode: > 0x235ea58: a(n) OCASTTranslatorForValue > 0x7ffeb658fb48 M OCASTTranslatorForValue>visitSequenceNode: > 0x235ea58: a(n) OCASTTranslatorForValue > 0x7ffeb658fb80 M RBSequenceNode>acceptVisitor: 0x235ec78: a(n) > RBSequenceNode > 0x7ffeb658fbb8 M > OCASTTranslatorForValue(RBProgramNodeVisitor)>visitNode: 0x235ea58: a(n) > OCASTTranslatorForValue > 0x7ffeb658fbf0 M OCASTTranslatorForValue(OCASTTranslator)>visitNode: > 0x235ea58: a(n) OCASTTranslatorForValue > 0x7ffeb658fc40 M > OCASTTranslatorForValue(OCASTTranslator)>visitBlockNode: 0x235ea58: a(n) > OCASTTranslatorForValue > 0x7ffeb658fc78 M RBBlockNode>acceptVisitor: 0x235eda0: a(n) RBBlockNode > 0x7ffeb658fcb0 M > OCASTTranslatorForValue(RBProgramNodeVisitor)>visitNode: 0x235ea58: a(n) > OCASTTranslatorForValue > 0x7ffeb658fce8 M OCASTTranslatorForValue(OCASTTranslator)>visitNode: > 0x235ea58: a(n) OCASTTranslatorForValue > 0x7ffeb658fd20 M [] in > OCASTTranslatorForEffect(OCASTTranslator)>emitMessageNode: 0x235e000: > a(n) OCASTTranslatorForEffect > 0x7ffeb658fd68 M OrderedCollection>do: 0x235ee18: a(n) > OrderedCollection > 0x7ffeb658fda0 M > OCASTTranslatorForEffect(OCASTTranslator)>emitMessageNode: 0x235e000: > a(n) OCASTTranslatorForEffect > 0x7ffeb658fdd8 M OCASTTranslatorForEffect>emitMessageNode: > 0x235e000: a(n) OCASTTranslatorForEffect > 0x7ffeb6581768 M > OCASTTranslatorForEffect(OCASTTranslator)>visitMessageNode: 0x235e000: > a(n) OCASTTranslatorForEffect > 0x7ffeb65817a0 M RBMessageNode>acceptVisitor: 0x235e0d8: a(n) > RBMessageNode > 0x7ffeb65817d8 M > OCASTTranslatorForEffect(RBProgramNodeVisitor)>visitNode: 0x235e000: > a(n) OCASTTranslatorForEffect > 0x7ffeb6581810 M > OCASTTranslatorForEffect(OCASTTranslator)>visitNode: 0x235e000: a(n) > OCASTTranslatorForEffect > 0x7ffeb6581848 M [] in OCASTTranslatorForEffect>visitSequenceNode: > 0x235e000: a(n) OCASTTranslatorForEffect > 0x7ffeb6581890 M OrderedCollection>do: 0x235e138: a(n) > OrderedCollection > 0x7ffeb65818c8 M OCASTTranslatorForEffect>visitSequenceNode: > 0x235e000: a(n) OCASTTranslatorForEffect > 0x7ffeb6581900 M RBSequenceNode>acceptVisitor: 0x235e210: a(n) > RBSequenceNode > 0x7ffeb6581938 M > OCASTTranslatorForEffect(RBProgramNodeVisitor)>visitNode: 0x235e000: > a(n) OCASTTranslatorForEffect > 0x7ffeb6581970 M > OCASTTranslatorForEffect(OCASTTranslator)>visitNode: 0x235e000: a(n) > OCASTTranslatorForEffect > 0x7ffeb65819a8 M OCASTTranslator>visitMethodNode: 0x235e250: a(n) > OCASTTranslator > 0x7ffeb65819e0 M RBMethodNode>acceptVisitor: 0x235e328: a(n) > RBMethodNode > 0x7ffeb6581a18 M OCASTTranslator(RBProgramNodeVisitor)>visitNode: > 0x235e250: a(n) OCASTTranslator > 0x7ffeb6581a50 M OCASTTranslator>visitNode: 0x235e250: a(n) > OCASTTranslator > 0x7ffeb6581a90 M RBMethodNode>generateIR 0x235e328: a(n) RBMethodNode > 0x7ffeb6581ac0 M RBMethodNode>generate: 0x235e328: a(n) RBMethodNode > 0x7ffeb6581b00 M [] in OpalCompiler>compile 0x235e3d0: a(n) > OpalCompiler > 0x7ffeb6581b30 M BlockClosure>on:do: 0x235e4c0: a(n) BlockClosure > 0x7ffeb6581b78 M OpalCompiler>compile 0x235e3d0: a(n) OpalCompiler > 0x7ffeb6581ba8 M MethodAddition>createCompiledMethod 0x235e5c0: a(n) > MethodAddition > 0x7ffeb6581be0 M MCMethodDefinition>addMethodAdditionTo: 0x644f908: > a(n) MCMethodDefinition > 0x7ffeb6581c20 M [] in MCPackageLoader>tryToLoad: 0x64eacb0: a(n) > MCPackageLoader > 0x7ffeb6581c50 M BlockClosure>on:do: 0x235e6d0: a(n) BlockClosure > 0x7ffeb6581c90 M MCPackageLoader>tryToLoad: 0x64eacb0: a(n) > MCPackageLoader > 0x7ffeb6581cc8 M [] in MCPackageLoader>basicLoadDefinitions > 0x64eacb0: a(n) MCPackageLoader > 0x7ffeb6581d30 M [] in > OrderedCollection(Collection)>do:displayingProgress:every: 0x653f700: > a(n) OrderedCollection > 0x7ffeb6581d78 M OrderedCollection>do: 0x653f700: a(n) > OrderedCollection > 0x7ffeb6581dd8 M [] in > OrderedCollection(Collection)>do:displayingProgress:every: 0x653f700: > a(n) OrderedCollection > 0x7ffeb656b818 M BlockClosure>cull: 0x656a310: a(n) BlockClosure > 0x7ffeb656b850 M [] in Job>run 0x6540440: a(n) Job > 0x7ffeb656b898 M [] in CurrentJob(DynamicVariable)>value:during: > 0x36bf880: a(n) CurrentJob > 0x7ffeb656b8d8 M BlockClosure>ensure: 0x6583098: a(n) BlockClosure > 0x7ffeb656b920 M CurrentJob(DynamicVariable)>value:during: > 0x36bf880: a(n) CurrentJob > 0x7ffeb656b960 M CurrentJob class(DynamicVariable > class)>value:during: 0x39a3f30: a(n) CurrentJob class > 0x7ffeb656b9a0 M [] in Job>run 0x6540440: a(n) Job > 0x7ffeb656b9e0 M BlockClosure>ensure: 0x6583270: a(n) BlockClosure > 0x7ffeb656ba18 M Job>run 0x6540440: a(n) Job > 0x7ffeb656ba48 M > NonInteractiveUIManager(UIManager)>displayProgress:from:to:during: > 0x5d3e0a8: a(n) NonInteractiveUIManager > 0x7ffeb656ba98 M ByteString(String)>displayProgressFrom:to:during: > 0x3a84fc8: a(n) ByteString > 0x7ffeb656baf0 M > OrderedCollection(Collection)>do:displayingProgress:every: 0x653f700: > a(n) OrderedCollection > 0x7ffeb656bb38 M > OrderedCollection(Collection)>do:displayingProgress: 0x653f700: a(n) > OrderedCollection > 0x7ffeb656bb78 M MCPackageLoader>basicLoadDefinitions 0x64eacb0: > a(n) MCPackageLoader > 0x7ffeb656bba8 M [] in MCPackageLoader>basicLoad 0x64eacb0: a(n) > MCPackageLoader > 0x7ffeb656bbe0 M [] in SourceFileArray>deferFlushDuring: 0x2f76370: > a(n) SourceFileArray > 0x7ffeb656bc20 M BlockClosure>ensure: 0x6583388: a(n) BlockClosure > 0x7ffeb656bc58 M SourceFileArray>deferFlushDuring: 0x2f76370: a(n) > SourceFileArray > 0x7ffeb656bc90 M MCPackageLoader>basicLoad 0x64eacb0: a(n) > MCPackageLoader > 0x7ffeb656bcc0 M [] in MCPackageLoader>loadWithNameLike: 0x64eacb0: > a(n) MCPackageLoader > 0x7ffeb656bd00 M BlockClosure>ensure: 0x6583540: a(n) BlockClosure > 0x7ffeb656bd48 M MCPackageLoader>useChangeSetNamed:during: > 0x64eacb0: a(n) MCPackageLoader > 0x7ffeb656bd98 I MCPackageLoader>useNewChangeSetNamedLike:during: > 0x64eacb0: a(n) MCPackageLoader > 0x7ffeb656bdd8 M MCPackageLoader>loadWithNameLike: 0x64eacb0: a(n) > MCPackageLoader > 0x7ffeb65637c0 M MCVersionLoader>basicLoadWithNameLike: 0x644be48: > a(n) MCVersionLoader > 0x7ffeb6563800 M [] in MCVersionLoader>loadWithNameLike: 0x644be48: > a(n) MCVersionLoader > 0x7ffeb6563840 M [] in MCVersionLoader>announceLoad:do: 0x644be48: > a(n) MCVersionLoader > 0x7ffeb6563880 M BlockClosure>ensure: 0x64eaec8: a(n) BlockClosure > 0x7ffeb65638d0 M [] in MCVersionLoader>announceLoad:do: 0x644be48: > a(n) MCVersionLoader > 0x7ffeb6563910 M BlockClosure>ensure: 0x64eb010: a(n) BlockClosure > 0x7ffeb6563950 M MCVersionLoader>announceLoad:do: 0x644be48: a(n) > MCVersionLoader > 0x7ffeb6563990 M MCVersionLoader>loadWithNameLike: 0x644be48: a(n) > MCVersionLoader > 0x7ffeb65639d0 M [] in MCVersionLoader>load 0x644be48: a(n) > MCVersionLoader > 0x7ffeb6563a00 M BlockClosure>cull: 0x644df68: a(n) BlockClosure > 0x7ffeb6563a38 M [] in Job>run 0x6446d10: a(n) Job > 0x7ffeb6563a80 M [] in CurrentJob(DynamicVariable)>value:during: > 0x36bf880: a(n) CurrentJob > 0x7ffeb6563ac0 M BlockClosure>ensure: 0x64eb1c8: a(n) BlockClosure > 0x7ffeb6563b08 M CurrentJob(DynamicVariable)>value:during: > 0x36bf880: a(n) CurrentJob > 0x7ffeb6563b48 M CurrentJob class(DynamicVariable > class)>value:during: 0x39a3f30: a(n) CurrentJob class > 0x7ffeb6563b88 M [] in Job>run 0x6446d10: a(n) Job > 0x7ffeb6563bc8 M BlockClosure>ensure: 0x64eb3a0: a(n) BlockClosure > 0x7ffeb6563c00 M Job>run 0x6446d10: a(n) Job > 0x7ffeb6563c38 M [] in MCVersionLoader>load 0x644be48: a(n) > MCVersionLoader > 0x7ffeb6563c78 M BlockClosure>ensure: 0x64eabb8: a(n) BlockClosure > 0x7ffeb6563cb8 M RPackageSet class>withCacheDo: 0x31e8ab8: a(n) > RPackageSet class > 0x7ffeb6563cf0 M MCVersionLoader>load 0x644be48: a(n) MCVersionLoader > 0x7ffeb6563d30 I MetacelloGoferLoad(GoferLoad)>execute 0x6444ed0: > a(n) MetacelloGoferLoad > 0x7ffeb6563d78 M [] in > MetacelloLoadingMCSpecLoader(MetacelloCommonMCSpecLoader)> > loadPackageDirective:gofer: > 0x62fe108: a(n) MetacelloLoadingMCSpecLoader > 0x7ffeb6563de0 M [] in > MetacelloLoadingMCSpecLoader(MetacelloCommonMCSpecLoader)> > loadPackageDirective:gofer: > 0x62fe108: a(n) MetacelloLoadingMCSpecLoader > 0x6184b88 s [] in > IceMetacelloPharoPlatform(MetacelloPharoCommonPlatform)>do:displaying: > 0x6184c50 s BlockClosure>cull: > 0x6184d08 s [] in Job>run > 0x6184dc0 s [] in CurrentJob(DynamicVariable)>value:during: > 0x6184e98 s BlockClosure>ensure: > 0x6185040 s CurrentJob(DynamicVariable)>value:during: > 0x6185200 s CurrentJob class(DynamicVariable class)>value:during: > 0x6184f88 s [] in Job>run > 0x6185128 s BlockClosure>ensure: > 0x61852b8 s Job>run > 0x6185390 s > NonInteractiveUIManager(UIManager)>displayProgress:from:to:during: > 0x6185448 s ByteString(String)>displayProgressFrom:to:during: > 0x62fe210 s > IceMetacelloPharoPlatform(MetacelloPharoCommonPlatform)>do:displaying: > 0x6302c90 s > MetacelloLoadingMCSpecLoader(MetacelloCommonMCSpecLoader)> > loadPackageDirective:gofer: > 0x63086b0 s > MetacelloExplicitLoadDirective(MetacelloVersionLoadDirective) > >loadPackageDirective:gofer: > 0x6310108 s MetacelloPackageLoadDirective>loadUsing:gofer: > 0x6314df0 s [] in > MetacelloExplicitLoadDirective(MetacelloVersionLoadDirective) > >loadLinearLoadDirective:gofer: > 0x63176b0 s OrderedCollection>do: > 0x6318630 s > MetacelloExplicitLoadDirective(MetacelloVersionLoadDirective) > >loadLinearLoadDirective:gofer: > 0x6319b48 s MetacelloExplicitLoadDirective > >explicitLoadUsing:gofer: > 0x631aa78 s MetacelloExplicitLoadDirective > >explicitLoadWithPolicy: > 0x631bc30 s > MetacelloEnsureFetchingMCSpecLoader(MetacelloFetchingMCSpecLoader) > >explicitLoadPackageSpecs:repositories: > 0x631c9e8 s MetacelloPackageSpec>explicitLoadUsing: > 0x631dcf8 s MetacelloPackageSpec>ensureLoadUsing: > 0x631eb60 s > MetacelloMCNamelessProjectSpec(MetacelloMCProjectSpec)>ensureLoadUsing: > 0x631fd00 s > MetacelloMCNamelessProjectSpec(MetacelloMCProjectSpec)> > ensureLoadedForDevelopmentUsing: > 0x6320978 s [] in MetacelloMCVersionSpecLoader>load > 0x63216c8 s Array(SequenceableCollection)>do: > 0x5ea7130 s MetacelloMCVersionSpecLoader>load > 0x606c578 s MetacelloMCVersion>executeLoadFromArray: > 0x6093448 s [] in MetacelloMCVersion>fetchRequiredFromArray: > 0x60ac4f0 s [] in > IceMetacelloPharoPlatform(MetacelloPlatform)>useStackCacheDuring: > defaultDictionary: > 0x5ea7240 s BlockClosure>on:do: > 0x5ea7330 s > IceMetacelloPharoPlatform(MetacelloPlatform)>useStackCacheDuring: > defaultDictionary: > 0x5ea7400 s [] in MetacelloMCVersion>fetchRequiredFromArray: > 0x606c630 s BlockClosure>ensure: > 0x5ea7510 s [] in MetacelloMCVersion>fetchRequiredFromArray: > 0x606c6e8 s [] in > IceMetacelloPharoPlatform(MetacelloPharoCommonPlatform)>do:displaying: > 0x6093500 s BlockClosure>cull: > 0x60ac5a8 s [] in Job>run > 0x62ee0d0 s [] in CurrentJob(DynamicVariable)>value:during: > 0x62fe898 s BlockClosure>ensure: > 0x5ea7650 s CurrentJob(DynamicVariable)>value:during: > 0x606c7a0 s CurrentJob class(DynamicVariable class)>value:during: > 0x5ea7708 s [] in Job>run > 0x606c858 s BlockClosure>ensure: > 0x5ea7800 s Job>run > 0x606c910 s > NonInteractiveUIManager(UIManager)>displayProgress:from:to:during: > 0x5ea78b8 s ByteString(String)>displayProgressFrom:to:during: > 0x5e70fc0 s > IceMetacelloPharoPlatform(MetacelloPharoCommonPlatform)>do:displaying: > 0x5e80a38 s MetacelloMCVersion>fetchRequiredFromArray: > 0x5ea62e0 s [] in > MetacelloMCConfigurationOfProjectSpec(MetacelloMCProjectSpec)>loadVersion: > 0x606c128 s [] in > IceMetacelloPharoPlatform(MetacelloPlatform)>useStackCacheDuring: > defaultDictionary: > 0x5ea6400 s BlockClosure>on:do: > 0x5ea64f0 s > IceMetacelloPharoPlatform(MetacelloPlatform)>useStackCacheDuring: > defaultDictionary: > 0x5ea65c0 s > MetacelloMCConfigurationOfProjectSpec(MetacelloMCProjectSpec)>loadVersion: > 0x606c1e0 s MetacelloProjectSpecForLoad>performLoad > 0x5ea6740 s > MetacelloMCNamelessProjectSpec(MetacelloGenericProjectSpec)>load > 0x606c298 s MetacelloProjectReferenceSpec>loadUsing:gofer: > 0x60932d8 s [] in > MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)> > linearLoadPackageSpecs:repositories: > 0x60ac438 s OrderedCollection>do: > 0x5ea6870 s > MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)> > linearLoadPackageSpecs:repositories: > 0x606c350 s [] in > MetacelloFetchingMCSpecLoader>linearLoadPackageSpecs:repositories: > 0x6093390 s BlockClosure>ensure: > 0x5ea69a0 s MetacelloLoaderPolicy>pushLoadDirective:during: > 0x606c408 s > MetacelloLoaderPolicy>pushLinearLoadDirectivesDuring:for: > 0x5ea6a58 s > MetacelloFetchingMCSpecLoader>linearLoadPackageSpecs:repositories: > 0x606c4c0 s > MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>load > 0x5d8aae8 s MetacelloMCVersionSpecLoader>load > 0x5d88aa8 s MetacelloMCVersion>executeLoadFromArray: > 0x606bc20 s [] in MetacelloMCVersion>fetchRequiredFromArray: > 0x6092ff8 s [] in > IceMetacelloPharoPlatform(MetacelloPlatform)>useStackCacheDuring: > defaultDictionary: > 0x5d88bd0 s BlockClosure>on:do: > 0x5d88cc0 s > IceMetacelloPharoPlatform(MetacelloPlatform)>useStackCacheDuring: > defaultDictionary: > 0x5d88d78 s [] in MetacelloMCVersion>fetchRequiredFromArray: > 0x606bcd8 s BlockClosure>ensure: > 0x5d88e88 s [] in MetacelloMCVersion>fetchRequiredFromArray: > 0x606bd90 s [] in > IceMetacelloPharoPlatform(MetacelloPharoCommonPlatform)>do:displaying: > 0x60930b0 s BlockClosure>cull: > 0x60ac380 s [] in Job>run > 0x62ee018 s [] in CurrentJob(DynamicVariable)>value:during: > 0x62fe7e0 s BlockClosure>ensure: > 0x5d88fc8 s CurrentJob(DynamicVariable)>value:during: > 0x606be48 s CurrentJob class(DynamicVariable class)>value:during: > 0x5d89080 s [] in Job>run > 0x606bf00 s BlockClosure>ensure: > 0x5d89178 s Job>run > 0x606bfb8 s > NonInteractiveUIManager(UIManager)>displayProgress:from:to:during: > 0x6093168 s ByteString(String)>displayProgressFrom:to:during: > 0x5d684f0 s > IceMetacelloPharoPlatform(MetacelloPharoCommonPlatform)>do:displaying: > 0x5d71c88 s MetacelloMCVersion>fetchRequiredFromArray: > 0x606c070 s [] in MetacelloMCVersion>doLoadRequiredFromArray: > 0x6093220 s BlockClosure>ensure: > 0x5d892e8 s MetacelloMCVersion>doLoadRequiredFromArray: > 0x5d893a0 s MetacelloMCVersion>load > 0x5d89458 s [] in > MetacelloScriptEngine>load:onProjectDownGrade:onProjectUpgrade: > 0x5d895b8 s BlockClosure>on:do: > 0x5d896a0 s [] in > MetacelloScriptEngine>handleNotificationsForAction: > 0x5d89780 s BlockClosure>on:do: > 0x5d89868 s [] in > MetacelloScriptEngine>handleNotificationsForAction: > 0x5d89948 s BlockClosure>on:do: > 0x5d89a20 s [] in > MetacelloScriptEngine>handleNotificationsForAction: > 0x5d89b00 s BlockClosure>on:do: > 0x5d89bd8 s MetacelloScriptEngine>handleNotificationsForAction: > 0x5d89c90 s [] in > MetacelloScriptEngine>load:onProjectDownGrade:onProjectUpgrade: > 0x606bab0 s BlockClosure>ensure: > 0x5d89dc0 s MetacelloProjectRegistration > class>copyRegistryRestoreOnErrorWhile: > 0x5d89e78 s > MetacelloScriptEngine>load:onProjectDownGrade:onProjectUpgrade: > 0x5d89f30 s MetacelloScriptEngine>load: > 0x606bb68 s [] in > MetacelloScriptApiExecutor(MetacelloScriptExecutor)>execute: > 0x6092f40 s [] in MetacelloScriptApiExecutor>executeString:do: > 0x60ac2c8 s Array(SequenceableCollection)>do: > 0x5d8a120 s MetacelloScriptApiExecutor>executeString:do: > 0x5d8a1f8 s ByteString(String)>execute:against: > 0x5d87e70 s > MetacelloScriptApiExecutor(MetacelloScriptExecutor)>execute: > 0x606b888 s Metacello>execute:args: > 0x6092d18 s Metacello>load > 0x5d87f60 s [] in UndefinedObject>DoIt > 0x5d88038 s BlockClosure>on:do: > 0x5d88110 s UndefinedObject>DoIt > 0x606b940 s OpalCompiler>evaluate > 0x6092dd0 s OpalCompiler(AbstractCompiler)>evaluate: > 0x60ac210 s [] in EvaluateCommandLineHandler>evaluate: > 0x5d88500 s BlockClosure>on:do: > 0x5d885d8 s EvaluateCommandLineHandler>evaluate: > 0x5d88690 s EvaluateCommandLineHandler>evaluateArguments > 0x5d88748 s EvaluateCommandLineHandler>activate > 0x606b9f8 s EvaluateCommandLineHandler class(CommandLineHandler > class)>activateWith: > 0x6092e88 s [] in > PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: > 0x5d88838 s BlockClosure>on:do: > 0x5d88918 s > PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: > 0x5d889f0 s > PharoCommandLineHandler(BasicCommandLineHandler)>handleSubcommand > 0x5d87070 s > PharoCommandLineHandler(BasicCommandLineHandler)>handleArgument: > 0x5d87138 s [] in > PharoCommandLineHandler(BasicCommandLineHandler)>activate > 0x5d87210 s BlockClosure>on:do: > 0x5d872e8 s > PharoCommandLineHandler(BasicCommandLineHandler)>activate > 0x606b4f0 s PharoCommandLineHandler>activate > 0x6092ba8 s PharoCommandLineHandler class(CommandLineHandler > class)>activateWith: > 0x60ac0a0 s [] in PharoCommandLineHandler class>activateWith: > 0x62edf60 s NonInteractiveUIManager(UIManager)>defer: > 0x5d873d8 s PharoCommandLineHandler class>activateWith: > 0x606b5a8 s [] in BasicCommandLineHandler>activateSubCommand: > 0x5d874e0 s BlockClosure>on:do: > 0x5d875c0 s BasicCommandLineHandler>activateSubCommand: > 0x5d87698 s BasicCommandLineHandler>handleSubcommand > 0x606b660 s BasicCommandLineHandler>handleArgument: > 0x5d87770 s [] in BasicCommandLineHandler>activate > 0x5d87848 s BlockClosure>on:do: > 0x5d87920 s BasicCommandLineHandler>activate > 0x606b718 s [] in BasicCommandLineHandler class>startUp: > 0x6092c60 s BlockClosure>cull: > 0x60ac158 s WorkingSession>executeDeferredStartupActions: > 0x5d879f8 s WorkingSession>runStartup: > 0x606b7d0 s WorkingSession>start: > 0x5aa07a0 s SessionManager>snapshot:andQuit: > 0x5abd988 s [] in SmalltalkImage>snapshot:andQuit: > 0x5abeb68 s CurrentExecutionEnvironment class>activate:for: > 0x5abf148 s > DefaultExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: > 0x5abf730 s DefaultExecutionEnvironment class>beActiveDuring: > 0x5abf200 s SmalltalkImage>snapshot:andQuit: > 0x5abf7e8 s EvaluateCommandLineHandler>activate > 0x5abfaa8 s EvaluateCommandLineHandler class(CommandLineHandler > class)>activateWith: > 0x5abfdb0 s [] in > PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: > 0x5ac01b8 s BlockClosure>on:do: > 0x5ac0450 s > PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: > 0x5ac1648 s > PharoCommandLineHandler(BasicCommandLineHandler)>handleSubcommand > 0x5ac1ce8 s > PharoCommandLineHandler(BasicCommandLineHandler)>handleArgument: > 0x5ac2000 s [] in > PharoCommandLineHandler(BasicCommandLineHandler)>activate > 0x5ac23b0 s BlockClosure>on:do: > 0x5ac2698 s > PharoCommandLineHandler(BasicCommandLineHandler)>activate > 0x5ac2890 s PharoCommandLineHandler>activate > 0x5ac2948 s PharoCommandLineHandler class(CommandLineHandler > class)>activateWith: > 0x5ac2a00 s [] in PharoCommandLineHandler class>activateWith: > 0x5ac2ac8 s NonInteractiveUIManager(UIManager)>defer: > 0x5ac2bc8 s PharoCommandLineHandler class>activateWith: > 0x5ac2cd0 s [] in BasicCommandLineHandler>activateSubCommand: > 0x5ac2da8 s BlockClosure>on:do: > 0x5ac2eb0 s BasicCommandLineHandler>activateSubCommand: > 0x5ac3000 s BasicCommandLineHandler>handleSubcommand > 0x5ac30d8 s BasicCommandLineHandler>handleArgument: > 0x5ac31e0 s [] in BasicCommandLineHandler>activate > 0x5ac3470 s BlockClosure>on:do: > 0x5ac3758 s BasicCommandLineHandler>activate > 0x5ac3950 s [] in BasicCommandLineHandler class>startUp: > 0x5ac3a08 s BlockClosure>cull: > 0x5ac3ae0 s WorkingSession>executeDeferredStartupActions: > 0x5ac3c50 s WorkingSession>runStartup: > 0x5ac3d08 s WorkingSession>start: > 0x5a87f60 s SessionManager>snapshot:andQuit: > 0x5a8b198 s [] in SmalltalkImage>snapshot:andQuit: > 0x5a8ca30 s CurrentExecutionEnvironment class>activate:for: > 0x5a8ea20 s > DefaultExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: > 0x5a90160 s DefaultExecutionEnvironment class>beActiveDuring: > 0x5a8ead8 s SmalltalkImage>snapshot:andQuit: > 0x5a90218 s EvaluateCommandLineHandler>activate > 0x5a91738 s EvaluateCommandLineHandler class(CommandLineHandler > class)>activateWith: > 0x5a95dd0 s [] in > PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: > 0x5a97788 s BlockClosure>on:do: > 0x5a9b230 s > PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: > 0x5a9da20 s > PharoCommandLineHandler(BasicCommandLineHandler)>handleSubcommand > 0x5a9e3c0 s > PharoCommandLineHandler(BasicCommandLineHandler)>handleArgument: > 0x5a9e8a8 s [] in > PharoCommandLineHandler(BasicCommandLineHandler)>activate > 0x5a9ec58 s BlockClosure>on:do: > 0x5a9ef40 s > PharoCommandLineHandler(BasicCommandLineHandler)>activate > 0x5a9f138 s PharoCommandLineHandler>activate > 0x5a9f1f0 s PharoCommandLineHandler class(CommandLineHandler > class)>activateWith: > 0x5a9f2a8 s [] in PharoCommandLineHandler class>activateWith: > 0x5a9f370 s NonInteractiveUIManager(UIManager)>defer: > 0x5a9f470 s PharoCommandLineHandler class>activateWith: > 0x5a9f578 s [] in BasicCommandLineHandler>activateSubCommand: > 0x5a9f650 s BlockClosure>on:do: > 0x5a9f758 s BasicCommandLineHandler>activateSubCommand: > 0x5a9f8a8 s BasicCommandLineHandler>handleSubcommand > 0x5a9f980 s BasicCommandLineHandler>handleArgument: > 0x5a9fa88 s [] in BasicCommandLineHandler>activate > 0x5a9fd18 s BlockClosure>on:do: > 0x5aa0000 s BasicCommandLineHandler>activate > 0x5aa01f8 s [] in BasicCommandLineHandler class>startUp: > 0x5aa02b0 s BlockClosure>cull: > 0x5aa0388 s WorkingSession>executeDeferredStartupActions: > 0x5aa04f8 s WorkingSession>runStartup: > 0x5aa05b0 s WorkingSession>start: > 0x5a32f30 s SessionManager>snapshot:andQuit: > 0x5a333a0 s [] in SmalltalkImage>snapshot:andQuit: > 0x5a350a8 s CurrentExecutionEnvironment class>activate:for: > 0x5a35428 s > DefaultExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: > 0x5a35710 s DefaultExecutionEnvironment class>beActiveDuring: > 0x5a354e0 s SmalltalkImage>snapshot:andQuit: > 0x5a357c8 s SmalltalkImage>saveImageInFileNamed: > 0x5a358d0 s SmalltalkImage>saveAs: > 0x5a35ae0 s SaveCommandLineHandler>saveImage > 0x5a35c30 s SaveCommandLineHandler>activate > 0x5a35e30 s SaveCommandLineHandler class(CommandLineHandler > class)>activateWith: > 0x5a36038 s [] in > PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: > 0x5a36310 s BlockClosure>on:do: > 0x5a36480 s > PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: > 0x5a36788 s > PharoCommandLineHandler(BasicCommandLineHandler)>handleSubcommand > 0x5a36a80 s > PharoCommandLineHandler(BasicCommandLineHandler)>handleArgument: > 0x5a36ca8 s [] in > PharoCommandLineHandler(BasicCommandLineHandler)>activate > 0x5a36f38 s BlockClosure>on:do: > 0x5a37220 s > PharoCommandLineHandler(BasicCommandLineHandler)>activate > 0x5a37418 s PharoCommandLineHandler>activate > 0x5a374d0 s PharoCommandLineHandler class(CommandLineHandler > class)>activateWith: > 0x5a37588 s [] in PharoCommandLineHandler class>activateWith: > 0x5a37650 s NonInteractiveUIManager(UIManager)>defer: > 0x5a37750 s PharoCommandLineHandler class>activateWith: > 0x5a37858 s [] in BasicCommandLineHandler>activateSubCommand: > 0x5a37930 s BlockClosure>on:do: > 0x5a37a38 s BasicCommandLineHandler>activateSubCommand: > 0x5a37b88 s BasicCommandLineHandler>handleSubcommand > 0x5a37c60 s BasicCommandLineHandler>handleArgument: > 0x5a37d68 s [] in BasicCommandLineHandler>activate > 0x5a37ff8 s BlockClosure>on:do: > 0x5a382e0 s BasicCommandLineHandler>activate > 0x5a384d8 s [] in BasicCommandLineHandler class>startUp: > 0x5a38590 s BlockClosure>cull: > 0x5a38668 s WorkingSession>executeDeferredStartupActions: > 0x5a387d8 s WorkingSession>runStartup: > 0x5a38890 s WorkingSession>start: > 0x5a1d7e0 s SessionManager>snapshot:andQuit: > 0x5a1eeb8 s [] in SmalltalkImage>snapshot:andQuit: > 0x5a1f8c0 s CurrentExecutionEnvironment class>activate:for: > 0x5a20020 s > DefaultExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: > 0x5a20568 s DefaultExecutionEnvironment class>beActiveDuring: > 0x5a200d8 s SmalltalkImage>snapshot:andQuit: > 0x5a20620 s ImageCleanerCommandLineHandler>activate > 0x5a20b18 s ImageCleanerCommandLineHandler > class(CommandLineHandler class)>activateWith: > 0x5a20e10 s [] in > PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: > 0x514a970 s BlockClosure>on:do: > 0x514aa50 s > PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: > 0x514a490 s > PharoCommandLineHandler(BasicCommandLineHandler)>handleSubcommand > 0x5a1d8f8 s > PharoCommandLineHandler(BasicCommandLineHandler)>handleArgument: > 0x514a548 s [] in > PharoCommandLineHandler(BasicCommandLineHandler)>activate > 0x514a620 s BlockClosure>on:do: > 0x514a6f8 s > PharoCommandLineHandler(BasicCommandLineHandler)>activate > 0x5a1d9b0 s PharoCommandLineHandler>activate > 0x5a1ef80 s PharoCommandLineHandler class(CommandLineHandler > class)>activateWith: > 0x5a1f9a8 s [] in PharoCommandLineHandler class>activateWith: > 0x5a20190 s NonInteractiveUIManager(UIManager)>defer: > 0x50c8408 s PharoCommandLineHandler class>activateWith: > 0x5a1da68 s [] in BasicCommandLineHandler>activateSubCommand: > 0x514a7b0 s BlockClosure>on:do: > 0x50c8538 s BasicCommandLineHandler>activateSubCommand: > 0x50c8610 s BasicCommandLineHandler>handleSubcommand > 0x5a1db20 s BasicCommandLineHandler>handleArgument: > 0x50c86d8 s [] in BasicCommandLineHandler>activate > 0x514a868 s BlockClosure>on:do: > 0x50c87d0 s BasicCommandLineHandler>activate > 0x5a1dbd8 s [] in BasicCommandLineHandler class>startUp: > 0x5a1f038 s BlockClosure>cull: > 0x5a1fa60 s WorkingSession>executeDeferredStartupActions: > 0x50c88a8 s WorkingSession>runStartup: > 0x5a1dc90 s WorkingSession>start: > 0x50b8758 s SessionManager>snapshot:andQuit: > 0x50bc510 s [] in SmalltalkImage>snapshot:andQuit: > 0x50c6dc8 s CurrentExecutionEnvironment class>activate:for: > 0x50c7610 s > DefaultExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: > 0x50c7aa8 s DefaultExecutionEnvironment class>beActiveDuring: > 0x50c76c8 s SmalltalkImage>snapshot:andQuit: > 0x50af818 s LoadUpdatesCommandLineHandler>activate > 0x50af8d0 s LoadUpdatesCommandLineHandler > class(CommandLineHandler class)>activateWith: > 0x50afb98 s [] in > PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: > 0x50afd70 s BlockClosure>on:do: > 0x50afe50 s > PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: > 0x50aff30 s > PharoCommandLineHandler(BasicCommandLineHandler)>handleSubcommand > 0x50affe8 s > PharoCommandLineHandler(BasicCommandLineHandler)>handleArgument: > 0x50b00c0 s [] in > PharoCommandLineHandler(BasicCommandLineHandler)>activate > 0x50b01d0 s BlockClosure>on:do: > 0x50b02a8 s > PharoCommandLineHandler(BasicCommandLineHandler)>activate > 0x50b0380 s PharoCommandLineHandler>activate > 0x50b0438 s PharoCommandLineHandler class(CommandLineHandler > class)>activateWith: > 0x50b04f0 s [] in PharoCommandLineHandler class>activateWith: > 0x50b05a8 s NonInteractiveUIManager(UIManager)>defer: > 0x50aee08 s PharoCommandLineHandler class>activateWith: > 0x50b0678 s [] in BasicCommandLineHandler>activateSubCommand: > 0x50b0a28 s BlockClosure>on:do: > 0x50aef38 s BasicCommandLineHandler>activateSubCommand: > 0x50af010 s BasicCommandLineHandler>handleSubcommand > 0x50b0730 s BasicCommandLineHandler>handleArgument: > 0x50af0c8 s [] in BasicCommandLineHandler>activate > 0x50b07e8 s BlockClosure>on:do: > 0x50af1c0 s BasicCommandLineHandler>activate > 0x50b08a0 s [] in BasicCommandLineHandler class>startUp: > 0x50b0ae0 s BlockClosure>cull: > 0x50b0b98 s WorkingSession>executeDeferredStartupActions: > 0x50af298 s WorkingSession>runStartup: > 0x50b0958 s WorkingSession>start: > 0x50aba78 s SessionManager>snapshot:andQuit: > 0x50abf80 s [] in SmalltalkImage>snapshot:andQuit: > 0x50ac1a8 s CurrentExecutionEnvironment class>activate:for: > 0x50ac400 s > DefaultExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: > 0x50ac628 s DefaultExecutionEnvironment class>beActiveDuring: > 0x50ac4b8 s SmalltalkImage>snapshot:andQuit: > 0x50ac6e0 s ImageCleanerCommandLineHandler>activate > 0x50ac798 s ImageCleanerCommandLineHandler > class(CommandLineHandler class)>activateWith: > 0x50ac850 s [] in > PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: > 0x50ab148 s BlockClosure>on:do: > 0x50ab228 s > PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: > 0x50aac68 s > PharoCommandLineHandler(BasicCommandLineHandler)>handleSubcommand > 0x50abb30 s > PharoCommandLineHandler(BasicCommandLineHandler)>handleArgument: > 0x50aad20 s [] in > PharoCommandLineHandler(BasicCommandLineHandler)>activate > 0x50aadf8 s BlockClosure>on:do: > 0x50aaed0 s > PharoCommandLineHandler(BasicCommandLineHandler)>activate > 0x50abbe8 s PharoCommandLineHandler>activate > 0x50ac038 s PharoCommandLineHandler class(CommandLineHandler > class)>activateWith: > 0x50ac290 s [] in PharoCommandLineHandler class>activateWith: > 0x50ac570 s NonInteractiveUIManager(UIManager)>defer: > 0x50a8820 s PharoCommandLineHandler class>activateWith: > 0x50abca0 s [] in BasicCommandLineHandler>activateSubCommand: > 0x50aaf88 s BlockClosure>on:do: > 0x50a8950 s BasicCommandLineHandler>activateSubCommand: > 0x50a8a28 s BasicCommandLineHandler>handleSubcommand > 0x50abd58 s BasicCommandLineHandler>handleArgument: > 0x50a8af0 s [] in BasicCommandLineHandler>activate > 0x50ab040 s BlockClosure>on:do: > 0x50a8be8 s BasicCommandLineHandler>activate > 0x50abe10 s [] in BasicCommandLineHandler class>startUp: > 0x50ac0f0 s BlockClosure>cull: > 0x50ac348 s WorkingSession>executeDeferredStartupActions: > 0x50a8cc0 s WorkingSession>runStartup: > 0x50abec8 s WorkingSession>start: > 0x50a7af8 s SessionManager>snapshot:andQuit: > 0x50a7bb0 s [] in SmalltalkImage>snapshot:andQuit: > 0x50a7c68 s CurrentExecutionEnvironment class>activate:for: > 0x50a7d50 s > DefaultExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: > 0x50a7ec0 s DefaultExecutionEnvironment class>beActiveDuring: > 0x50a7e08 s SmalltalkImage>snapshot:andQuit: > 0x50936c8 s LoadUpdatesCommandLineHandler>activate > 0x5093780 s LoadUpdatesCommandLineHandler > class(CommandLineHandler class)>activateWith: > 0x5093a48 s [] in > PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: > 0x5093c20 s BlockClosure>on:do: > 0x5093d00 s > PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: > 0x5093de0 s > PharoCommandLineHandler(BasicCommandLineHandler)>handleSubcommand > 0x5093e98 s > PharoCommandLineHandler(BasicCommandLineHandler)>handleArgument: > 0x5093f70 s [] in > PharoCommandLineHandler(BasicCommandLineHandler)>activate > 0x5094080 s BlockClosure>on:do: > 0x5094158 s > PharoCommandLineHandler(BasicCommandLineHandler)>activate > 0x5094230 s PharoCommandLineHandler>activate > 0x50942e8 s PharoCommandLineHandler class(CommandLineHandler > class)>activateWith: > 0x50943a0 s [] in PharoCommandLineHandler class>activateWith: > 0x5094458 s NonInteractiveUIManager(UIManager)>defer: > 0x5092d68 s PharoCommandLineHandler class>activateWith: > 0x5094510 s [] in BasicCommandLineHandler>activateSubCommand: > 0x50948a8 s BlockClosure>on:do: > 0x5092e98 s BasicCommandLineHandler>activateSubCommand: > 0x5092f70 s BasicCommandLineHandler>handleSubcommand > 0x50945c8 s BasicCommandLineHandler>handleArgument: > 0x5093028 s [] in BasicCommandLineHandler>activate > 0x5094680 s BlockClosure>on:do: > 0x5093120 s BasicCommandLineHandler>activate > 0x5094738 s [] in BasicCommandLineHandler class>startUp: > 0x5094960 s BlockClosure>cull: > 0x5094a18 s WorkingSession>executeDeferredStartupActions: > 0x50931f8 s WorkingSession>runStartup: > 0x50947f0 s WorkingSession>start: > 0x508f9d0 s SessionManager>snapshot:andQuit: > 0x508fed8 s [] in SmalltalkImage>snapshot:andQuit: > 0x5090100 s CurrentExecutionEnvironment class>activate:for: > 0x5090358 s > DefaultExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: > 0x5090580 s DefaultExecutionEnvironment class>beActiveDuring: > 0x5090410 s SmalltalkImage>snapshot:andQuit: > 0x5090638 s ImageCleanerCommandLineHandler>activate > 0x50906f0 s ImageCleanerCommandLineHandler > class(CommandLineHandler class)>activateWith: > 0x50907a8 s [] in > PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: > 0x508f390 s BlockClosure>on:do: > 0x508f470 s > PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: > 0x508eeb0 s > PharoCommandLineHandler(BasicCommandLineHandler)>handleSubcommand > 0x508fa88 s > PharoCommandLineHandler(BasicCommandLineHandler)>handleArgument: > 0x508ef68 s [] in > PharoCommandLineHandler(BasicCommandLineHandler)>activate > 0x508f040 s BlockClosure>on:do: > 0x508f118 s > PharoCommandLineHandler(BasicCommandLineHandler)>activate > 0x508fb40 s PharoCommandLineHandler>activate > 0x508ff90 s PharoCommandLineHandler class(CommandLineHandler > class)>activateWith: > 0x50901e8 s [] in PharoCommandLineHandler class>activateWith: > 0x50904c8 s NonInteractiveUIManager(UIManager)>defer: > 0x508ca48 s PharoCommandLineHandler class>activateWith: > 0x508fbf8 s [] in BasicCommandLineHandler>activateSubCommand: > 0x508f1d0 s BlockClosure>on:do: > 0x508cb78 s BasicCommandLineHandler>activateSubCommand: > 0x508cc50 s BasicCommandLineHandler>handleSubcommand > 0x508fcb0 s BasicCommandLineHandler>handleArgument: > 0x508cd18 s [] in BasicCommandLineHandler>activate > 0x508f288 s BlockClosure>on:do: > 0x508ce10 s BasicCommandLineHandler>activate > 0x508fd68 s [] in BasicCommandLineHandler class>startUp: > 0x5090048 s BlockClosure>cull: > 0x50902a0 s WorkingSession>executeDeferredStartupActions: > 0x508cee8 s WorkingSession>runStartup: > 0x508fe20 s WorkingSession>start: > 0x508bd20 s SessionManager>snapshot:andQuit: > 0x508bdd8 s [] in SmalltalkImage>snapshot:andQuit: > 0x508be90 s CurrentExecutionEnvironment class>activate:for: > 0x508bf78 s > DefaultExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: > 0x508c0e8 s DefaultExecutionEnvironment class>beActiveDuring: > 0x508c030 s SmalltalkImage>snapshot:andQuit: > 0x508a908 s LoadUpdatesCommandLineHandler>activate > 0x508a9c0 s LoadUpdatesCommandLineHandler > class(CommandLineHandler class)>activateWith: > 0x508ac88 s [] in > PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: > 0x508ae60 s BlockClosure>on:do: > 0x508af40 s > PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: > 0x508b020 s > PharoCommandLineHandler(BasicCommandLineHandler)>handleSubcommand > 0x508b0d8 s > PharoCommandLineHandler(BasicCommandLineHandler)>handleArgument: > 0x508b1b0 s [] in > PharoCommandLineHandler(BasicCommandLineHandler)>activate > 0x508b2c0 s BlockClosure>on:do: > 0x508b398 s > PharoCommandLineHandler(BasicCommandLineHandler)>activate > 0x508b470 s PharoCommandLineHandler>activate > 0x508b528 s PharoCommandLineHandler class(CommandLineHandler > class)>activateWith: > 0x508b5e0 s [] in PharoCommandLineHandler class>activateWith: > 0x508b698 s NonInteractiveUIManager(UIManager)>defer: > 0x5089fa8 s PharoCommandLineHandler class>activateWith: > 0x508b750 s [] in BasicCommandLineHandler>activateSubCommand: > 0x508bae8 s BlockClosure>on:do: > 0x508a0d8 s BasicCommandLineHandler>activateSubCommand: > 0x508a1b0 s BasicCommandLineHandler>handleSubcommand > 0x508b808 s BasicCommandLineHandler>handleArgument: > 0x508a268 s [] in BasicCommandLineHandler>activate > 0x508b8c0 s BlockClosure>on:do: > 0x508a360 s BasicCommandLineHandler>activate > 0x508b978 s [] in BasicCommandLineHandler class>startUp: > 0x508bba0 s BlockClosure>cull: > 0x508bc58 s WorkingSession>executeDeferredStartupActions: > 0x508a438 s WorkingSession>runStartup: > 0x508ba30 s WorkingSession>start: > 0x5086c30 s SessionManager>snapshot:andQuit: > 0x5087138 s [] in SmalltalkImage>snapshot:andQuit: > 0x5087360 s CurrentExecutionEnvironment class>activate:for: > 0x50875b8 s > DefaultExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: > 0x50877e0 s DefaultExecutionEnvironment class>beActiveDuring: > 0x5087670 s SmalltalkImage>snapshot:andQuit: > 0x5087898 s ImageCleanerCommandLineHandler>activate > 0x5087950 s ImageCleanerCommandLineHandler > class(CommandLineHandler class)>activateWith: > 0x5087a08 s [] in > PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: > 0x50865f0 s BlockClosure>on:do: > 0x50866d0 s > PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: > 0x5086110 s > PharoCommandLineHandler(BasicCommandLineHandler)>handleSubcommand > 0x5086ce8 s > PharoCommandLineHandler(BasicCommandLineHandler)>handleArgument: > 0x50861c8 s [] in > PharoCommandLineHandler(BasicCommandLineHandler)>activate > 0x50862a0 s BlockClosure>on:do: > 0x5086378 s > PharoCommandLineHandler(BasicCommandLineHandler)>activate > 0x5086da0 s PharoCommandLineHandler>activate > 0x50871f0 s PharoCommandLineHandler class(CommandLineHandler > class)>activateWith: > 0x5087448 s [] in PharoCommandLineHandler class>activateWith: > 0x5087728 s NonInteractiveUIManager(UIManager)>defer: > 0x5083ca8 s PharoCommandLineHandler class>activateWith: > 0x5086e58 s [] in BasicCommandLineHandler>activateSubCommand: > 0x5086430 s BlockClosure>on:do: > 0x5083dd8 s BasicCommandLineHandler>activateSubCommand: > 0x5083eb0 s BasicCommandLineHandler>handleSubcommand > 0x5086f10 s BasicCommandLineHandler>handleArgument: > 0x5083f78 s [] in BasicCommandLineHandler>activate > 0x50864e8 s BlockClosure>on:do: > 0x5084070 s BasicCommandLineHandler>activate > 0x5086fc8 s [] in BasicCommandLineHandler class>startUp: > 0x50872a8 s BlockClosure>cull: > 0x5087500 s WorkingSession>executeDeferredStartupActions: > 0x5084148 s WorkingSession>runStartup: > 0x5087080 s WorkingSession>start: > 0x5082f80 s SessionManager>snapshot:andQuit: > 0x5083038 s [] in SmalltalkImage>snapshot:andQuit: > 0x50830f0 s CurrentExecutionEnvironment class>activate:for: > 0x50831d8 s > DefaultExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: > 0x5083348 s DefaultExecutionEnvironment class>beActiveDuring: > 0x5083290 s SmalltalkImage>snapshot:andQuit: > 0x5080de0 s LoadUpdatesCommandLineHandler>activate > 0x5080e98 s LoadUpdatesCommandLineHandler > class(CommandLineHandler class)>activateWith: > 0x5081160 s [] in > PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: > 0x5081338 s BlockClosure>on:do: > 0x5081418 s > PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: > 0x50814f8 s > PharoCommandLineHandler(BasicCommandLineHandler)>handleSubcommand > 0x50815b0 s > PharoCommandLineHandler(BasicCommandLineHandler)>handleArgument: > 0x5081688 s [] in > PharoCommandLineHandler(BasicCommandLineHandler)>activate > 0x5081798 s BlockClosure>on:do: > 0x5081870 s > PharoCommandLineHandler(BasicCommandLineHandler)>activate > 0x5081948 s PharoCommandLineHandler>activate > 0x5081a00 s PharoCommandLineHandler class(CommandLineHandler > class)>activateWith: > 0x5081ab8 s [] in PharoCommandLineHandler class>activateWith: > 0x5081b70 s NonInteractiveUIManager(UIManager)>defer: > 0x5080480 s PharoCommandLineHandler class>activateWith: > 0x5082100 s [] in BasicCommandLineHandler>activateSubCommand: > 0x5082498 s BlockClosure>on:do: > 0x50805b0 s BasicCommandLineHandler>activateSubCommand: > 0x5080688 s BasicCommandLineHandler>handleSubcommand > 0x50821b8 s BasicCommandLineHandler>handleArgument: > 0x5080740 s [] in BasicCommandLineHandler>activate > 0x5082270 s BlockClosure>on:do: > 0x5080838 s BasicCommandLineHandler>activate > 0x5082328 s [] in BasicCommandLineHandler class>startUp: > 0x5082550 s BlockClosure>cull: > 0x5082608 s WorkingSession>executeDeferredStartupActions: > 0x5080910 s WorkingSession>runStartup: > 0x50823e0 s WorkingSession>start: > 0x507d698 s SessionManager>snapshot:andQuit: > 0x507dae8 s [] in SmalltalkImage>snapshot:andQuit: > 0x507dd10 s CurrentExecutionEnvironment class>activate:for: > 0x507df68 s > DefaultExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: > 0x507e190 s DefaultExecutionEnvironment class>beActiveDuring: > 0x507e020 s SmalltalkImage>snapshot:andQuit: > 0x507e248 s ImageCleanerCommandLineHandler>activate > 0x507e300 s ImageCleanerCommandLineHandler > class(CommandLineHandler class)>activateWith: > 0x507e3b8 s [] in > PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: > 0x507a6a8 s BlockClosure>on:do: > 0x507a090 s > PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: > 0x5079fd8 s > PharoCommandLineHandler(BasicCommandLineHandler)>handleSubcommand > 0x507a1c0 s > PharoCommandLineHandler(BasicCommandLineHandler)>handleArgument: > 0x5079ea8 s [] in > PharoCommandLineHandler(BasicCommandLineHandler)>activate > 0x507a760 s BlockClosure>on:do: > 0x5079db0 s > PharoCommandLineHandler(BasicCommandLineHandler)>activate > 0x507d750 s PharoCommandLineHandler>activate > 0x507dba0 s PharoCommandLineHandler class(CommandLineHandler > class)>activateWith: > 0x507ddf8 s [] in PharoCommandLineHandler class>activateWith: > 0x507e0d8 s NonInteractiveUIManager(UIManager)>defer: > 0x507d1a0 s PharoCommandLineHandler class>activateWith: > 0x507d808 s [] in BasicCommandLineHandler>activateSubCommand: > 0x507a818 s BlockClosure>on:do: > 0x507d098 s BasicCommandLineHandler>activateSubCommand: > 0x507cfe0 s BasicCommandLineHandler>handleSubcommand > 0x507d8c0 s BasicCommandLineHandler>handleArgument: > 0x507ceb0 s [] in BasicCommandLineHandler>activate > 0x507a8d0 s BlockClosure>on:do: > 0x507cdb8 s BasicCommandLineHandler>activate > 0x507d978 s [] in BasicCommandLineHandler class>startUp: > 0x507dc58 s BlockClosure>cull: > 0x507deb0 s WorkingSession>executeDeferredStartupActions: > 0x507aab8 s WorkingSession>runStartup: > 0x507da30 s WorkingSession>start: > 0x5075858 s SessionManager>snapshot:andQuit: > 0x5076370 s [] in SmalltalkImage>snapshot:andQuit: > 0x50765e0 s CurrentExecutionEnvironment class>activate:for: > 0x50766e8 s > DefaultExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: > 0x5076910 s DefaultExecutionEnvironment class>beActiveDuring: > 0x50767a0 s SmalltalkImage>snapshot:andQuit: > 0x50769c8 s LoadUpdatesCommandLineHandler>activate > 0x5076aa0 s LoadUpdatesCommandLineHandler > class(CommandLineHandler class)>activateWith: > 0x5076c38 s [] in > PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: > 0x5076d80 s BlockClosure>on:do: > 0x5076fa8 s > PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: > 0x5078190 s > PharoCommandLineHandler(BasicCommandLineHandler)>handleSubcommand > 0x50782a0 s > PharoCommandLineHandler(BasicCommandLineHandler)>handleArgument: > 0x50785b8 s [] in > PharoCommandLineHandler(BasicCommandLineHandler)>activate > 0x50787e8 s BlockClosure>on:do: > 0x5078ad0 s > PharoCommandLineHandler(BasicCommandLineHandler)>activate > 0x5078ba8 s PharoCommandLineHandler>activate > 0x5078c60 s PharoCommandLineHandler class(CommandLineHandler > class)>activateWith: > 0x5078d18 s [] in PharoCommandLineHandler class>activateWith: > 0x5078dd0 s NonInteractiveUIManager(UIManager)>defer: > 0x5078eb0 s PharoCommandLineHandler class>activateWith: > 0x5078f80 s [] in BasicCommandLineHandler>activateSubCommand: > 0x5079038 s BlockClosure>on:do: > 0x5079140 s BasicCommandLineHandler>activateSubCommand: > 0x5079290 s BasicCommandLineHandler>handleSubcommand > 0x5079368 s BasicCommandLineHandler>handleArgument: > 0x5079470 s [] in BasicCommandLineHandler>activate > 0x5079580 s BlockClosure>on:do: > 0x5079868 s BasicCommandLineHandler>activate > 0x5079940 s [] in BasicCommandLineHandler class>startUp: > 0x50799f8 s BlockClosure>cull: > 0x5079ad0 s WorkingSession>executeDeferredStartupActions: > 0x5079c40 s WorkingSession>runStartup: > 0x5079cf8 s WorkingSession>start: > 0x5074708 s SessionManager>snapshot:andQuit: > 0x5074b58 s [] in SmalltalkImage>snapshot:andQuit: > 0x5074d80 s CurrentExecutionEnvironment class>activate:for: > 0x5074fd8 s > DefaultExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: > 0x5075200 s DefaultExecutionEnvironment class>beActiveDuring: > 0x5075090 s SmalltalkImage>snapshot:andQuit: > 0x50752b8 s ImageCleanerCommandLineHandler>activate > 0x5075370 s ImageCleanerCommandLineHandler > class(CommandLineHandler class)>activateWith: > 0x5075428 s [] in > PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: > 0x5071718 s BlockClosure>on:do: > 0x5071100 s > PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: > 0x5071048 s > PharoCommandLineHandler(BasicCommandLineHandler)>handleSubcommand > 0x5071230 s > PharoCommandLineHandler(BasicCommandLineHandler)>handleArgument: > 0x5070f18 s [] in > PharoCommandLineHandler(BasicCommandLineHandler)>activate > 0x50717d0 s BlockClosure>on:do: > 0x5070e20 s > PharoCommandLineHandler(BasicCommandLineHandler)>activate > 0x50747c0 s PharoCommandLineHandler>activate > 0x5074c10 s PharoCommandLineHandler class(CommandLineHandler > class)>activateWith: > 0x5074e68 s [] in PharoCommandLineHandler class>activateWith: > 0x5075148 s NonInteractiveUIManager(UIManager)>defer: > 0x5074210 s PharoCommandLineHandler class>activateWith: > 0x5074878 s [] in BasicCommandLineHandler>activateSubCommand: > 0x5071888 s BlockClosure>on:do: > 0x5074108 s BasicCommandLineHandler>activateSubCommand: > 0x5074050 s BasicCommandLineHandler>handleSubcommand > 0x5074930 s BasicCommandLineHandler>handleArgument: > 0x5073f20 s [] in BasicCommandLineHandler>activate > 0x5071940 s BlockClosure>on:do: > 0x5073e28 s BasicCommandLineHandler>activate > 0x50749e8 s [] in BasicCommandLineHandler class>startUp: > 0x5074cc8 s BlockClosure>cull: > 0x5074f20 s WorkingSession>executeDeferredStartupActions: > 0x5071b28 s WorkingSession>runStartup: > 0x5074aa0 s WorkingSession>start: > 0x506c8c8 s SessionManager>snapshot:andQuit: > 0x506d3e0 s [] in SmalltalkImage>snapshot:andQuit: > 0x506d650 s CurrentExecutionEnvironment class>activate:for: > 0x506d758 s > DefaultExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: > 0x506d980 s DefaultExecutionEnvironment class>beActiveDuring: > 0x506d810 s SmalltalkImage>snapshot:andQuit: > 0x506da38 s LoadUpdatesCommandLineHandler>activate > 0x506db10 s LoadUpdatesCommandLineHandler > class(CommandLineHandler class)>activateWith: > 0x506dca8 s [] in > PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: > 0x506ddf0 s BlockClosure>on:do: > 0x506e018 s > PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: > 0x506f200 s > PharoCommandLineHandler(BasicCommandLineHandler)>handleSubcommand > 0x506f310 s > PharoCommandLineHandler(BasicCommandLineHandler)>handleArgument: > 0x506f628 s [] in > PharoCommandLineHandler(BasicCommandLineHandler)>activate > 0x506f858 s BlockClosure>on:do: > 0x506fb40 s > PharoCommandLineHandler(BasicCommandLineHandler)>activate > 0x506fc18 s PharoCommandLineHandler>activate > 0x506fcd0 s PharoCommandLineHandler class(CommandLineHandler > class)>activateWith: > 0x506fd88 s [] in PharoCommandLineHandler class>activateWith: > 0x506fe40 s NonInteractiveUIManager(UIManager)>defer: > 0x506ff20 s PharoCommandLineHandler class>activateWith: > 0x506fff0 s [] in BasicCommandLineHandler>activateSubCommand: > 0x50700a8 s BlockClosure>on:do: > 0x50701b0 s BasicCommandLineHandler>activateSubCommand: > 0x5070300 s BasicCommandLineHandler>handleSubcommand > 0x50703d8 s BasicCommandLineHandler>handleArgument: > 0x50704e0 s [] in BasicCommandLineHandler>activate > 0x50705f0 s BlockClosure>on:do: > 0x50708d8 s BasicCommandLineHandler>activate > 0x50709b0 s [] in BasicCommandLineHandler class>startUp: > 0x5070a68 s BlockClosure>cull: > 0x5070b40 s WorkingSession>executeDeferredStartupActions: > 0x5070cb0 s WorkingSession>runStartup: > 0x5070d68 s WorkingSession>start: > 0x506b778 s SessionManager>snapshot:andQuit: > 0x506bbc8 s [] in SmalltalkImage>snapshot:andQuit: > 0x506bdf0 s CurrentExecutionEnvironment class>activate:for: > 0x506c048 s > DefaultExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: > 0x506c270 s DefaultExecutionEnvironment class>beActiveDuring: > 0x506c100 s SmalltalkImage>snapshot:andQuit: > 0x506c328 s ImageCleanerCommandLineHandler>activate > 0x506c3e0 s ImageCleanerCommandLineHandler > class(CommandLineHandler class)>activateWith: > 0x506c498 s [] in > PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: > 0x5068788 s BlockClosure>on:do: > 0x5068170 s > PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: > 0x50680b8 s > PharoCommandLineHandler(BasicCommandLineHandler)>handleSubcommand > 0x50682a0 s > PharoCommandLineHandler(BasicCommandLineHandler)>handleArgument: > 0x5067f88 s [] in > PharoCommandLineHandler(BasicCommandLineHandler)>activate > 0x5068840 s BlockClosure>on:do: > 0x5067e90 s > PharoCommandLineHandler(BasicCommandLineHandler)>activate > 0x506b830 s PharoCommandLineHandler>activate > 0x506bc80 s PharoCommandLineHandler class(CommandLineHandler > class)>activateWith: > 0x506bed8 s [] in PharoCommandLineHandler class>activateWith: > 0x506c1b8 s NonInteractiveUIManager(UIManager)>defer: > 0x506b280 s PharoCommandLineHandler class>activateWith: > 0x506b8e8 s [] in BasicCommandLineHandler>activateSubCommand: > 0x50688f8 s BlockClosure>on:do: > 0x506b178 s BasicCommandLineHandler>activateSubCommand: > 0x506b0c0 s BasicCommandLineHandler>handleSubcommand > 0x506b9a0 s BasicCommandLineHandler>handleArgument: > 0x506af90 s [] in BasicCommandLineHandler>activate > 0x50689b0 s BlockClosure>on:do: > 0x506ae98 s BasicCommandLineHandler>activate > 0x506ba58 s [] in BasicCommandLineHandler class>startUp: > 0x506bd38 s BlockClosure>cull: > 0x506bf90 s WorkingSession>executeDeferredStartupActions: > 0x5068b98 s WorkingSession>runStartup: > 0x506bb10 s WorkingSession>start: > 0x5063e10 s SessionManager>snapshot:andQuit: > 0x5064928 s [] in SmalltalkImage>snapshot:andQuit: > 0x5064b98 s CurrentExecutionEnvironment class>activate:for: > 0x5064ca0 s > DefaultExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: > 0x5064ec8 s DefaultExecutionEnvironment class>beActiveDuring: > 0x5064d58 s SmalltalkImage>snapshot:andQuit: > 0x5064f80 s LoadUpdatesCommandLineHandler>activate > 0x5065058 s LoadUpdatesCommandLineHandler > class(CommandLineHandler class)>activateWith: > 0x5065138 s [] in > PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: > 0x5065280 s BlockClosure>on:do: > 0x50654a8 s > PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: > 0x5066690 s > PharoCommandLineHandler(BasicCommandLineHandler)>handleSubcommand > 0x50667a0 s > PharoCommandLineHandler(BasicCommandLineHandler)>handleArgument: > 0x5066ab8 s [] in > PharoCommandLineHandler(BasicCommandLineHandler)>activate > 0x5066ce8 s BlockClosure>on:do: > 0x5066dc0 s > PharoCommandLineHandler(BasicCommandLineHandler)>activate > 0x5066e98 s PharoCommandLineHandler>activate > 0x5066f50 s PharoCommandLineHandler class(CommandLineHandler > class)>activateWith: > 0x5067008 s [] in PharoCommandLineHandler class>activateWith: > 0x50670c0 s NonInteractiveUIManager(UIManager)>defer: > 0x50671a0 s PharoCommandLineHandler class>activateWith: > 0x5067270 s [] in BasicCommandLineHandler>activateSubCommand: > 0x5067328 s BlockClosure>on:do: > 0x5067430 s BasicCommandLineHandler>activateSubCommand: > 0x5067580 s BasicCommandLineHandler>handleSubcommand > 0x5067658 s BasicCommandLineHandler>handleArgument: > 0x5067760 s [] in BasicCommandLineHandler>activate > 0x5067870 s BlockClosure>on:do: > 0x5067948 s BasicCommandLineHandler>activate > 0x5067a20 s [] in BasicCommandLineHandler class>startUp: > 0x5067ad8 s BlockClosure>cull: > 0x5067bb0 s WorkingSession>executeDeferredStartupActions: > 0x5067d20 s WorkingSession>runStartup: > 0x5067dd8 s WorkingSession>start: > 0x5062730 s SessionManager>snapshot:andQuit: > 0x5062c38 s [] in SmalltalkImage>snapshot:andQuit: > 0x5062e60 s CurrentExecutionEnvironment class>activate:for: > 0x50630b8 s > DefaultExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: > 0x50632e0 s DefaultExecutionEnvironment class>beActiveDuring: > 0x5063170 s SmalltalkImage>snapshot:andQuit: > 0x5063398 s ImageCleanerCommandLineHandler>activate > 0x5063450 s ImageCleanerCommandLineHandler > class(CommandLineHandler class)>activateWith: > 0x5063508 s [] in > PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: > 0x50620f0 s BlockClosure>on:do: > 0x50621d0 s > PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: > 0x5061c10 s > PharoCommandLineHandler(BasicCommandLineHandler)>handleSubcommand > 0x50627e8 s > PharoCommandLineHandler(BasicCommandLineHandler)>handleArgument: > 0x5061cc8 s [] in > PharoCommandLineHandler(BasicCommandLineHandler)>activate > 0x5061da0 s BlockClosure>on:do: > 0x5061e78 s > PharoCommandLineHandler(BasicCommandLineHandler)>activate > 0x50628a0 s PharoCommandLineHandler>activate > 0x5062cf0 s PharoCommandLineHandler class(CommandLineHandler > class)>activateWith: > 0x5062f48 s [] in PharoCommandLineHandler class>activateWith: > 0x5063228 s NonInteractiveUIManager(UIManager)>defer: > 0x505f7a8 s PharoCommandLineHandler class>activateWith: > 0x5062958 s [] in BasicCommandLineHandler>activateSubCommand: > 0x5061f30 s BlockClosure>on:do: > 0x505f8d8 s BasicCommandLineHandler>activateSubCommand: > 0x505f9b0 s BasicCommandLineHandler>handleSubcommand > 0x5062a10 s BasicCommandLineHandler>handleArgument: > 0x505fa78 s [] in BasicCommandLineHandler>activate > 0x5061fe8 s BlockClosure>on:do: > 0x505fb70 s BasicCommandLineHandler>activate > 0x5062ac8 s [] in BasicCommandLineHandler class>startUp: > 0x5062da8 s BlockClosure>cull: > 0x5063000 s WorkingSession>executeDeferredStartupActions: > 0x505fc48 s WorkingSession>runStartup: > 0x5062b80 s WorkingSession>start: > 0x505ea80 s SessionManager>snapshot:andQuit: > 0x505eb38 s [] in SmalltalkImage>snapshot:andQuit: > 0x505ebf0 s CurrentExecutionEnvironment class>activate:for: > 0x505ecd8 s > DefaultExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: > 0x505ee48 s DefaultExecutionEnvironment class>beActiveDuring: > 0x505ed90 s SmalltalkImage>snapshot:andQuit: > 0x505d678 s LoadUpdatesCommandLineHandler>activate > 0x505d730 s LoadUpdatesCommandLineHandler > class(CommandLineHandler class)>activateWith: > 0x505d9f8 s [] in > PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: > 0x505dbd0 s BlockClosure>on:do: > 0x505dcb0 s > PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: > 0x505dd90 s > PharoCommandLineHandler(BasicCommandLineHandler)>handleSubcommand > 0x505de48 s > PharoCommandLineHandler(BasicCommandLineHandler)>handleArgument: > 0x505df20 s [] in > PharoCommandLineHandler(BasicCommandLineHandler)>activate > 0x505e030 s BlockClosure>on:do: > 0x505e108 s > PharoCommandLineHandler(BasicCommandLineHandler)>activate > 0x505e1e0 s PharoCommandLineHandler>activate > 0x505e298 s PharoCommandLineHandler class(CommandLineHandler > class)>activateWith: > 0x505e350 s [] in PharoCommandLineHandler class>activateWith: > 0x505e408 s NonInteractiveUIManager(UIManager)>defer: > 0x505cd18 s PharoCommandLineHandler class>activateWith: > 0x505e4c0 s [] in BasicCommandLineHandler>activateSubCommand: > 0x505e858 s BlockClosure>on:do: > 0x505ce48 s BasicCommandLineHandler>activateSubCommand: > 0x505cf20 s BasicCommandLineHandler>handleSubcommand > 0x505e578 s BasicCommandLineHandler>handleArgument: > 0x505cfd8 s [] in BasicCommandLineHandler>activate > 0x505e630 s BlockClosure>on:do: > 0x505d0d0 s BasicCommandLineHandler>activate > 0x505e6e8 s [] in BasicCommandLineHandler class>startUp: > 0x505e910 s BlockClosure>cull: > 0x505e9c8 s WorkingSession>executeDeferredStartupActions: > 0x505d1a8 s WorkingSession>runStartup: > 0x505e7a0 s WorkingSession>start: > 0x50599a0 s SessionManager>snapshot:andQuit: > 0x5059ea8 s [] in SmalltalkImage>snapshot:andQuit: > 0x505a0d0 s CurrentExecutionEnvironment class>activate:for: > 0x505a328 s > DefaultExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: > 0x505a550 s DefaultExecutionEnvironment class>beActiveDuring: > 0x505a3e0 s SmalltalkImage>snapshot:andQuit: > 0x505a608 s ImageCleanerCommandLineHandler>activate > 0x505a6c0 s ImageCleanerCommandLineHandler > class(CommandLineHandler class)>activateWith: > 0x505a778 s [] in > PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: > 0x5059360 s BlockClosure>on:do: > 0x5059440 s > PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: > 0x5058e80 s > PharoCommandLineHandler(BasicCommandLineHandler)>handleSubcommand > 0x5059a58 s > PharoCommandLineHandler(BasicCommandLineHandler)>handleArgument: > 0x5058f38 s [] in > PharoCommandLineHandler(BasicCommandLineHandler)>activate > 0x5059010 s BlockClosure>on:do: > 0x50590e8 s > PharoCommandLineHandler(BasicCommandLineHandler)>activate > 0x5059b10 s PharoCommandLineHandler>activate > 0x5059f60 s PharoCommandLineHandler class(CommandLineHandler > class)>activateWith: > 0x505a1b8 s [] in PharoCommandLineHandler class>activateWith: > 0x505a498 s NonInteractiveUIManager(UIManager)>defer: > 0x5056a18 s PharoCommandLineHandler class>activateWith: > 0x5059bc8 s [] in BasicCommandLineHandler>activateSubCommand: > 0x50591a0 s BlockClosure>on:do: > 0x5056b48 s BasicCommandLineHandler>activateSubCommand: > 0x5056c20 s BasicCommandLineHandler>handleSubcommand > 0x5059c80 s BasicCommandLineHandler>handleArgument: > 0x5056ce8 s [] in BasicCommandLineHandler>activate > 0x5059258 s BlockClosure>on:do: > 0x5056de0 s BasicCommandLineHandler>activate > 0x5059d38 s [] in BasicCommandLineHandler class>startUp: > 0x505a018 s BlockClosure>cull: > 0x505a270 s WorkingSession>executeDeferredStartupActions: > 0x5056eb8 s WorkingSession>runStartup: > 0x5059df0 s WorkingSession>start: > 0x5055cf0 s SessionManager>snapshot:andQuit: > 0x5055da8 s [] in SmalltalkImage>snapshot:andQuit: > 0x5055e60 s CurrentExecutionEnvironment class>activate:for: > 0x5055f48 s > DefaultExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: > 0x50560b8 s DefaultExecutionEnvironment class>beActiveDuring: > 0x5056000 s SmalltalkImage>snapshot:andQuit: > 0x5054ea8 s LoadUpdatesCommandLineHandler>activate > 0x5054f60 s LoadUpdatesCommandLineHandler > class(CommandLineHandler class)>activateWith: > 0x5055228 s [] in > PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: > 0x5055400 s BlockClosure>on:do: > 0x50554e0 s > PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: > 0x50555c0 s > PharoCommandLineHandler(BasicCommandLineHandler)>handleSubcommand > 0x5055678 s > PharoCommandLineHandler(BasicCommandLineHandler)>handleArgument: > 0x5055750 s [] in > PharoCommandLineHandler(BasicCommandLineHandler)>activate > 0x5055860 s BlockClosure>on:do: > 0x5055938 s > PharoCommandLineHandler(BasicCommandLineHandler)>activate > 0x5055a10 s PharoCommandLineHandler>activate > 0x5055ac8 s PharoCommandLineHandler class(CommandLineHandler > class)>activateWith: > 0x5055b80 s [] in PharoCommandLineHandler class>activateWith: > 0x5055c38 s NonInteractiveUIManager(UIManager)>defer: > 0x5053f88 s PharoCommandLineHandler class>activateWith: > 0x50547c0 s [] in BasicCommandLineHandler>activateSubCommand: > 0x5054b58 s BlockClosure>on:do: > 0x50540b8 s BasicCommandLineHandler>activateSubCommand: > 0x5054190 s BasicCommandLineHandler>handleSubcommand > 0x5054878 s BasicCommandLineHandler>handleArgument: > 0x5054248 s [] in BasicCommandLineHandler>activate > 0x5054930 s BlockClosure>on:do: > 0x5054340 s BasicCommandLineHandler>activate > 0x50549e8 s [] in BasicCommandLineHandler class>startUp: > 0x5054c10 s BlockClosure>cull: > 0x5054cc8 s WorkingSession>executeDeferredStartupActions: > 0x5054418 s WorkingSession>runStartup: > 0x5054aa0 s WorkingSession>start: > 0x5050c10 s SessionManager>snapshot:andQuit: > 0x5051118 s [] in SmalltalkImage>snapshot:andQuit: > 0x5051340 s CurrentExecutionEnvironment class>activate:for: > 0x5051598 s > DefaultExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: > 0x50517c0 s DefaultExecutionEnvironment class>beActiveDuring: > 0x5051650 s SmalltalkImage>snapshot:andQuit: > 0x5051878 s ImageCleanerCommandLineHandler>activate > 0x5051930 s ImageCleanerCommandLineHandler > class(CommandLineHandler class)>activateWith: > 0x50519e8 s [] in > PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: > 0x50505b0 s BlockClosure>on:do: > 0x5050690 s > PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: > 0x50500d0 s > PharoCommandLineHandler(BasicCommandLineHandler)>handleSubcommand > 0x5050cc8 s > PharoCommandLineHandler(BasicCommandLineHandler)>handleArgument: > 0x5050188 s [] in > PharoCommandLineHandler(BasicCommandLineHandler)>activate > 0x5050260 s BlockClosure>on:do: > 0x5050338 s > PharoCommandLineHandler(BasicCommandLineHandler)>activate > 0x5050d80 s PharoCommandLineHandler>activate > 0x50511d0 s PharoCommandLineHandler class(CommandLineHandler > class)>activateWith: > 0x5051428 s [] in PharoCommandLineHandler class>activateWith: > 0x5051708 s NonInteractiveUIManager(UIManager)>defer: > 0x504dc88 s PharoCommandLineHandler class>activateWith: > 0x5050e38 s [] in BasicCommandLineHandler>activateSubCommand: > 0x50503f0 s BlockClosure>on:do: > 0x504ddb8 s BasicCommandLineHandler>activateSubCommand: > 0x504de90 s BasicCommandLineHandler>handleSubcommand > 0x5050ef0 s BasicCommandLineHandler>handleArgument: > 0x504df58 s [] in BasicCommandLineHandler>activate > 0x50504a8 s BlockClosure>on:do: > 0x504e050 s BasicCommandLineHandler>activate > 0x5050fa8 s [] in BasicCommandLineHandler class>startUp: > 0x5051288 s BlockClosure>cull: > 0x50514e0 s WorkingSession>executeDeferredStartupActions: > 0x504e128 s WorkingSession>runStartup: > 0x5051060 s WorkingSession>start: > 0x504cf60 s SessionManager>snapshot:andQuit: > 0x504d018 s [] in SmalltalkImage>snapshot:andQuit: > 0x504d0d0 s CurrentExecutionEnvironment class>activate:for: > 0x504d1b8 s > DefaultExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: > 0x504d328 s DefaultExecutionEnvironment class>beActiveDuring: > 0x504d270 s SmalltalkImage>snapshot:andQuit: > 0x504be10 s LoadUpdatesCommandLineHandler>activate > 0x504bec8 s LoadUpdatesCommandLineHandler > class(CommandLineHandler class)>activateWith: > 0x504c190 s [] in > PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: > 0x504c368 s BlockClosure>on:do: > 0x504c448 s > PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: > 0x504c528 s > PharoCommandLineHandler(BasicCommandLineHandler)>handleSubcommand > 0x504c5e0 s > PharoCommandLineHandler(BasicCommandLineHandler)>handleArgument: > 0x504c6b8 s [] in > PharoCommandLineHandler(BasicCommandLineHandler)>activate > 0x504c7c8 s BlockClosure>on:do: > 0x504c8a0 s > PharoCommandLineHandler(BasicCommandLineHandler)>activate > 0x504c978 s PharoCommandLineHandler>activate > 0x504ca30 s PharoCommandLineHandler class(CommandLineHandler > class)>activateWith: > 0x504cae8 s [] in PharoCommandLineHandler class>activateWith: > 0x504cba0 s NonInteractiveUIManager(UIManager)>defer: > 0x504aef0 s PharoCommandLineHandler class>activateWith: > 0x504b728 s [] in BasicCommandLineHandler>activateSubCommand: > 0x504bac0 s BlockClosure>on:do: > 0x504b020 s BasicCommandLineHandler>activateSubCommand: > 0x504b0f8 s BasicCommandLineHandler>handleSubcommand > 0x504b7e0 s BasicCommandLineHandler>handleArgument: > 0x504b1b0 s [] in BasicCommandLineHandler>activate > 0x504b898 s BlockClosure>on:do: > 0x504b2a8 s BasicCommandLineHandler>activate > 0x504b950 s [] in BasicCommandLineHandler class>startUp: > 0x504bb78 s BlockClosure>cull: > 0x504bc30 s WorkingSession>executeDeferredStartupActions: > 0x504b380 s WorkingSession>runStartup: > 0x504ba08 s WorkingSession>start: > 0x5047b78 s SessionManager>snapshot:andQuit: > 0x5048080 s [] in SmalltalkImage>snapshot:andQuit: > 0x50482a8 s CurrentExecutionEnvironment class>activate:for: > 0x5048500 s > DefaultExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: > 0x5048728 s DefaultExecutionEnvironment class>beActiveDuring: > 0x50485b8 s SmalltalkImage>snapshot:andQuit: > 0x50487e0 s ImageCleanerCommandLineHandler>activate > 0x5048898 s ImageCleanerCommandLineHandler > class(CommandLineHandler class)>activateWith: > 0x5048950 s [] in > PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: > 0x50473f8 s BlockClosure>on:do: > 0x50474d8 s > PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: > 0x5046f18 s > PharoCommandLineHandler(BasicCommandLineHandler)>handleSubcommand > 0x5047c30 s > PharoCommandLineHandler(BasicCommandLineHandler)>handleArgument: > 0x5046fd0 s [] in > PharoCommandLineHandler(BasicCommandLineHandler)>activate > 0x50470a8 s BlockClosure>on:do: > 0x5047180 s > PharoCommandLineHandler(BasicCommandLineHandler)>activate > 0x5047ce8 s PharoCommandLineHandler>activate > 0x5048138 s PharoCommandLineHandler class(CommandLineHandler > class)>activateWith: > 0x5048390 s [] in PharoCommandLineHandler class>activateWith: > 0x5048670 s NonInteractiveUIManager(UIManager)>defer: > 0x5044ab0 s PharoCommandLineHandler class>activateWith: > 0x5047da0 s [] in BasicCommandLineHandler>activateSubCommand: > 0x5047238 s BlockClosure>on:do: > 0x5044be0 s BasicCommandLineHandler>activateSubCommand: > 0x5044cb8 s BasicCommandLineHandler>handleSubcommand > 0x5047e58 s BasicCommandLineHandler>handleArgument: > 0x5044d80 s [] in BasicCommandLineHandler>activate > 0x50472f0 s BlockClosure>on:do: > 0x5044e78 s BasicCommandLineHandler>activate > 0x5047f10 s [] in BasicCommandLineHandler class>startUp: > 0x50481f0 s BlockClosure>cull: > 0x5048448 s WorkingSession>executeDeferredStartupActions: > 0x5044f50 s WorkingSession>runStartup: > 0x5047fc8 s WorkingSession>start: > 0x5043d88 s SessionManager>snapshot:andQuit: > 0x5043e40 s [] in SmalltalkImage>snapshot:andQuit: > 0x5043ef8 s CurrentExecutionEnvironment class>activate:for: > 0x5043fe0 s > DefaultExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: > 0x5044150 s DefaultExecutionEnvironment class>beActiveDuring: > 0x5044098 s SmalltalkImage>snapshot:andQuit: > 0x5042f40 s LoadUpdatesCommandLineHandler>activate > 0x5042ff8 s LoadUpdatesCommandLineHandler > class(CommandLineHandler class)>activateWith: > 0x50432c0 s [] in > PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: > 0x5043498 s BlockClosure>on:do: > 0x5043578 s > PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: > 0x5043658 s > PharoCommandLineHandler(BasicCommandLineHandler)>handleSubcommand > 0x5043710 s > PharoCommandLineHandler(BasicCommandLineHandler)>handleArgument: > 0x50437e8 s [] in > PharoCommandLineHandler(BasicCommandLineHandler)>activate > 0x50438f8 s BlockClosure>on:do: > 0x50439d0 s > PharoCommandLineHandler(BasicCommandLineHandler)>activate > 0x5043aa8 s PharoCommandLineHandler>activate > 0x5043b60 s PharoCommandLineHandler class(CommandLineHandler > class)>activateWith: > 0x5043c18 s [] in PharoCommandLineHandler class>activateWith: > 0x5043cd0 s NonInteractiveUIManager(UIManager)>defer: > 0x5042020 s PharoCommandLineHandler class>activateWith: > 0x5042858 s [] in BasicCommandLineHandler>activateSubCommand: > 0x5042bf0 s BlockClosure>on:do: > 0x5042150 s BasicCommandLineHandler>activateSubCommand: > 0x5042228 s BasicCommandLineHandler>handleSubcommand > 0x5042910 s BasicCommandLineHandler>handleArgument: > 0x50422e0 s [] in BasicCommandLineHandler>activate > 0x50429c8 s BlockClosure>on:do: > 0x50423d8 s BasicCommandLineHandler>activate > 0x5042a80 s [] in BasicCommandLineHandler class>startUp: > 0x5042ca8 s BlockClosure>cull: > 0x5042d60 s WorkingSession>executeDeferredStartupActions: > 0x50424b0 s WorkingSession>runStartup: > 0x5042b38 s WorkingSession>start: > 0x502f970 s SessionManager>snapshot:andQuit: > 0x503d010 s [] in SmalltalkImage>snapshot:andQuit: > 0x503d4d0 s CurrentExecutionEnvironment class>activate:for: > 0x503d688 s > DefaultExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: > 0x503d7f8 s DefaultExecutionEnvironment class>beActiveDuring: > 0x503d740 s SmalltalkImage>snapshot:andQuit: > 0x503d8b0 s [] in WorldState class>saveAndQuit > 0x503d968 s BlockClosure>ensure: > 0x503da40 s CursorWithMask(Cursor)>showWhile: > 0x503db20 s WorldState class>saveAndQuit > 0x503dbd8 s [] in > ToggleMenuItemMorph(MenuItemMorph)>invokeWithEvent: > 0x503dc90 s BlockClosure>ensure: > 0x503ddc0 s CursorWithMask(Cursor)>showWhile: > 0x503dea0 s ToggleMenuItemMorph(MenuItemMorph)>invokeWithEvent: > 0x503df58 s ToggleMenuItemMorph(MenuItemMorph)>mouseUp: > 0x503e010 s ToggleMenuItemMorph(MenuItemMorph)>handleMouseUp: > 0x503e0c8 s MouseButtonEvent>sentTo: > 0x503e180 s ToggleMenuItemMorph(Morph)>handleEvent: > 0x503e238 s MorphicEventDispatcher>dispatchDefault:with: > 0x503e2f0 s MorphicEventDispatcher>handleMouseUp: > 0x503e3a8 s MouseButtonEvent>sentTo: > 0x503e460 s [] in MorphicEventDispatcher>dispatchEvent:with: > 0x503e518 s BlockClosure>ensure: > 0x503e5f8 s MorphicEventDispatcher>dispatchEvent:with: > 0x503e6d0 s ToggleMenuItemMorph(Morph)>processEvent:using: > 0x503e788 s MorphicEventDispatcher>dispatchDefault:with: > 0x503e840 s MorphicEventDispatcher>handleMouseUp: > 0x503e948 s MouseButtonEvent>sentTo: > 0x503ea00 s [] in MorphicEventDispatcher>dispatchEvent:with: > 0x503eab8 s BlockClosure>ensure: > 0x503eb98 s MorphicEventDispatcher>dispatchEvent:with: > 0x503ec70 s MenuMorph(Morph)>processEvent:using: > 0x503ed28 s MenuMorph(Morph)>processEvent: > 0x503ede0 s MenuMorph>handleFocusEvent: > 0x503ee98 s [] in HandMorph>sendFocusEvent:to:clear: > 0x503ef50 s BlockClosure>on:do: > 0x503f050 s WorldMorph(PasteUpMorph)>becomeActiveDuring: > 0x503f140 s HandMorph>sendFocusEvent:to:clear: > 0x503f240 s HandMorph>sendEvent:focus:clear: > 0x503f330 s HandMorph>sendMouseEvent: > 0x503f3e8 s HandMorph>handleEvent: > 0x503f4a0 s HandMorph>processEventsFromQueue: > 0x503f558 s HandMorph>processEvents > 0x503f610 s [] in WorldState>doOneCycleNowFor: > 0x503f6c8 s Array(SequenceableCollection)>do: > 0x503f7a0 s WorldState>handsDo: > 0x503f858 s WorldState>doOneCycleNowFor: > 0x503f910 s WorldState>doOneCycleFor: > 0x503f9c8 s WorldMorph>doOneCycle > 0x503fa80 s WorldMorph class>doOneCycle > 0x4d9acd8 s [] in MorphicUIManager>spawnNewProcess > 0x4d9aa58 s [] in BlockClosure>newProcess > > Most recent primitives > **StackOverflow** > **StackOverflow** > replaceFrom:to:with:startingAt: > **StackOverflow** > **StackOverflow** > stringHash:initialHash: > stringHash:initialHash: > stringHash:initialHash: > stringHash:initialHash: > stringHash:initialHash: > stringHash:initialHash: > stringHash:initialHash: > stringHash:initialHash: > stringHash:initialHash: > **StackOverflow** > **StackOverflow** > **StackOverflow** > **StackOverflow** > stringHash:initialHash: > **StackOverflow** > stringHash:initialHash: > **StackOverflow** > stringHash:initialHash: > stringHash:initialHash: > stringHash:initialHash: > stringHash:initialHash: > stringHash:initialHash: > stringHash:initialHash: > replaceFrom:to:with:startingAt: > 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: > **StackOverflow** > **StackOverflow** > **StackOverflow** > **StackOverflow** > **StackOverflow** > **StackOverflow** > **StackOverflow** > replaceFrom:to:with:startingAt: > **StackOverflow** > **StackOverflow** > replaceFrom:to:with:startingAt: > **StackOverflow** > **StackOverflow** > **StackOverflow** > **StackOverflow** > **StackOverflow** > **StackOverflow** > stringHash:initialHash: > stringHash:initialHash: > stringHash:initialHash: > stringHash:initialHash: > stringHash:initialHash: > stringHash:initialHash: > stringHash:initialHash: > stringHash:initialHash: > stringHash:initialHash: > **StackOverflow** > **StackOverflow** > **StackOverflow** > **StackOverflow** > stringHash:initialHash: > **StackOverflow** > stringHash:initialHash: > **StackOverflow** > stringHash:initialHash: > stringHash:initialHash: > stringHash:initialHash: > stringHash:initialHash: > stringHash:initialHash: > stringHash:initialHash: > replaceFrom:to:with:startingAt: > 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: > **StackOverflow** > **StackOverflow** > **StackOverflow** > **StackOverflow** > **StackOverflow** > **StackOverflow** > **StackOverflow** > replaceFrom:to:with:startingAt: > **StackOverflow** > **StackOverflow** > **StackOverflow** > **StackOverflow** > **StackOverflow** > **StackOverflow** > **StackOverflow** > **StackOverflow** > **StackOverflow** > replaceFrom:to:with:startingAt: > **StackOverflow** > **StackOverflow** > **StackOverflow** > **StackOverflow** > **StackOverflow** > **StackOverflow** > **StackOverflow** > **IncrementalGC** > wait > wait > signal > wait > signal > wait > signal > wait > signal > wait > signal > wait > signal > wait > signal > wait > signal > signal > primitiveFetchMourner > **PrimitiveFailure** > wait > primUTCMicrosecondsClock > digitMultiply:neg: > primOffset > digitCompare: > // > \\ > quo: > quo: > - > with:with:with: > with:with:with: > with:with:with: > with:with:with: > class > basicNew > first > second > second > third > third > julianDayNumberUTC > secondsSinceMidnightUTC > < > at: > at: > bitShift: > class > bitAnd: > bitAnd: > bitAnd: > bitAnd: > basicNew > basicNew > schedulerBeingWaitedOn > primUTCMicrosecondsClock > millisecondDelayDuration > millisecondDelayDuration > primSignal:atUTCMicroseconds: > wait > value > **PrimitiveFailure** > **PrimitiveFailure** > **PrimitiveRetry** > value: > **PrimitiveFailure** > **PrimitiveFailure** > **PrimitiveRetry** > stringHash:initialHash: > stringHash:initialHash: > stringHash:initialHash: > stringHash:initialHash: > stringHash:initialHash: > stringHash:initialHash: > stringHash:initialHash: > stringHash:initialHash: > stringHash:initialHash: > **StackOverflow** > **StackOverflow** > **StackOverflow** > **StackOverflow** > stringHash:initialHash: > **StackOverflow** > stringHash:initialHash: > **StackOverflow** > stringHash:initialHash: > stringHash:initialHash: > stringHash:initialHash: > stringHash:initialHash: > stringHash:initialHash: > stringHash:initialHash: > replaceFrom:to:with:startingAt: > 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: > **StackOverflow** > **StackOverflow** > **StackOverflow** > **StackOverflow** > **StackOverflow** > **StackOverflow** > **StackOverflow** > class > replaceFrom:to:with:startingAt: > **StackOverflow** > **StackOverflow** > **StackOverflow** > **StackOverflow** > **StackOverflow** > **StackOverflow** > **StackOverflow** > **StackOverflow** > **StackOverflow** > replaceFrom:to:with:startingAt: > **StackOverflow** > **StackOverflow** > **StackOverflow** > **StackOverflow** > **StackOverflow** > **StackOverflow** > **StackOverflow** > > stack page bytes 8192 available headroom 5576 minimum unused headroom 4976 > > (Segmentation fault) > > > > -- > Cyril Ferlicot > https://ferlicot.fr > > http://www.synectique.eu > 2 rue Jacques PrÃ©vert 01, > 59650 Villeneuve d'ascq France > >

Dec. 20, 2017

Is there some progress on the 64bit Metacello loading segfault problem?

by Cyril Ferlicot D.

Hi, There was a bug reported multiple times about segfaults during Metacello loadings in Pharo. This week I setup some Jenkins builds for 64bits products and I still see a lot of segfault. I cannot get a way to reproduce it 100% but it appears pretty often. Today we got 3 crash out of around 15 builds. This is a pretty high number of crash. I know it is hard to correct random crashes but was there some progress on this problem since it was reported? Here is a stack trace example: Segmentation fault Wed Dec 20 02:25:00 2017 /var/lib/jenkins/workspace/path/to/job/pharo-vm/lib/pharo/5.0-201707201942/pharo Pharo VM version: 5.0-201707201942 Thu Jul 20 20:40:54 UTC 2017 gcc 4.6.3 [Production Spur 64-bit 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-74d10329-bbfd-42e5-8995-b0e3a68c73cb 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: /var/lib/jenkins/workspace/path/to/job/pharo-vm/lib/pharo/5.0-201707201942 [default: /var/lib/jenkins/workspace/path/to/job/pharo-vm/lib/pharo/5.0-201707201942/] C stack backtrace & registers: rax 0xb654c100 rbx 0xb654bf90 rcx 0xb654c1b8 rdx 0xb654c048 rdi 0xb654bd68 rsi 0xb654bd68 rbp 0xb654bed8 rsp 0xb654c270 r8 0xb654b7a8 r9 0xb654b860 r10 0xb654b918 r11 0xb654b9d0 r12 0xb654ba88 r13 0xb654bb40 r14 0xb654bbf8 r15 0xb654bcb0 rip 0xb654c328 *[0x7ffeb654c328] /var/lib/jenkins/workspace/path/to/job/pharo-vm/lib/pharo/5.0-201707201942/pharo[0x41ccd1] /var/lib/jenkins/workspace/path/to/job/pharo-vm/lib/pharo/5.0-201707201942/pharo[0x41d05f] /lib/x86_64-linux-gnu/libpthread.so.0(+0x11390)[0x7f1d94d5e390] /var/lib/jenkins/workspace/path/to/job/pharo-vm/lib/pharo/5.0-201707201942/pharo[0x4403cc] /var/lib/jenkins/workspace/path/to/job/pharo-vm/lib/pharo/5.0-201707201942/pharo(lookupOrdinaryreceiver+0x67)[0x440777] /var/lib/jenkins/workspace/path/to/job/pharo-vm/lib/pharo/5.0-201707201942/pharo(ceSICMiss+0x58)[0x493d48] [0x21003ef] [0x0] Smalltalk stack dump: 0x7ffeb658f8d0 M INVALID RECEIVER>isInlined 0x24f57b8 is in new space 0x7ffeb658f900 M OCASTTranslatorForEffect(OCASTTranslator)>visitMessageNode: 0x235e000: a(n) OCASTTranslatorForEffect 0x7ffeb658f938 M INVALID RECEIVER>acceptVisitor: 0x24f57b8 is in new space 0x7ffeb658f970 M OCASTTranslatorForEffect(RBProgramNodeVisitor)>visitNode: 0x235e000: a(n) OCASTTranslatorForEffect 0x7ffeb658f9a8 M OCASTTranslatorForEffect(OCASTTranslator)>visitNode: 0x235e000: a(n) OCASTTranslatorForEffect 0x7ffeb658f9e0 M [] in OCASTTranslatorForValue(OCASTTranslator)>visitCascadeNode: 0x235ea58: a(n) OCASTTranslatorForValue 0x7ffeb658fa28 M OrderedCollection(SequenceableCollection)>allButLastDo: 0x235ea98: a(n) OrderedCollection 0x7ffeb658fa60 M OCASTTranslatorForValue(OCASTTranslator)>visitCascadeNode: 0x235ea58: a(n) OCASTTranslatorForValue 0x7ffeb658fa98 M RBCascadeNode>acceptVisitor: 0x235eb70: a(n) RBCascadeNode 0x7ffeb658fad0 M OCASTTranslatorForValue(RBProgramNodeVisitor)>visitNode: 0x235ea58: a(n) OCASTTranslatorForValue 0x7ffeb658fb08 M OCASTTranslatorForValue(OCASTTranslator)>visitNode: 0x235ea58: a(n) OCASTTranslatorForValue 0x7ffeb658fb48 M OCASTTranslatorForValue>visitSequenceNode: 0x235ea58: a(n) OCASTTranslatorForValue 0x7ffeb658fb80 M RBSequenceNode>acceptVisitor: 0x235ec78: a(n) RBSequenceNode 0x7ffeb658fbb8 M OCASTTranslatorForValue(RBProgramNodeVisitor)>visitNode: 0x235ea58: a(n) OCASTTranslatorForValue 0x7ffeb658fbf0 M OCASTTranslatorForValue(OCASTTranslator)>visitNode: 0x235ea58: a(n) OCASTTranslatorForValue 0x7ffeb658fc40 M OCASTTranslatorForValue(OCASTTranslator)>visitBlockNode: 0x235ea58: a(n) OCASTTranslatorForValue 0x7ffeb658fc78 M RBBlockNode>acceptVisitor: 0x235eda0: a(n) RBBlockNode 0x7ffeb658fcb0 M OCASTTranslatorForValue(RBProgramNodeVisitor)>visitNode: 0x235ea58: a(n) OCASTTranslatorForValue 0x7ffeb658fce8 M OCASTTranslatorForValue(OCASTTranslator)>visitNode: 0x235ea58: a(n) OCASTTranslatorForValue 0x7ffeb658fd20 M [] in OCASTTranslatorForEffect(OCASTTranslator)>emitMessageNode: 0x235e000: a(n) OCASTTranslatorForEffect 0x7ffeb658fd68 M OrderedCollection>do: 0x235ee18: a(n) OrderedCollection 0x7ffeb658fda0 M OCASTTranslatorForEffect(OCASTTranslator)>emitMessageNode: 0x235e000: a(n) OCASTTranslatorForEffect 0x7ffeb658fdd8 M OCASTTranslatorForEffect>emitMessageNode: 0x235e000: a(n) OCASTTranslatorForEffect 0x7ffeb6581768 M OCASTTranslatorForEffect(OCASTTranslator)>visitMessageNode: 0x235e000: a(n) OCASTTranslatorForEffect 0x7ffeb65817a0 M RBMessageNode>acceptVisitor: 0x235e0d8: a(n) RBMessageNode 0x7ffeb65817d8 M OCASTTranslatorForEffect(RBProgramNodeVisitor)>visitNode: 0x235e000: a(n) OCASTTranslatorForEffect 0x7ffeb6581810 M OCASTTranslatorForEffect(OCASTTranslator)>visitNode: 0x235e000: a(n) OCASTTranslatorForEffect 0x7ffeb6581848 M [] in OCASTTranslatorForEffect>visitSequenceNode: 0x235e000: a(n) OCASTTranslatorForEffect 0x7ffeb6581890 M OrderedCollection>do: 0x235e138: a(n) OrderedCollection 0x7ffeb65818c8 M OCASTTranslatorForEffect>visitSequenceNode: 0x235e000: a(n) OCASTTranslatorForEffect 0x7ffeb6581900 M RBSequenceNode>acceptVisitor: 0x235e210: a(n) RBSequenceNode 0x7ffeb6581938 M OCASTTranslatorForEffect(RBProgramNodeVisitor)>visitNode: 0x235e000: a(n) OCASTTranslatorForEffect 0x7ffeb6581970 M OCASTTranslatorForEffect(OCASTTranslator)>visitNode: 0x235e000: a(n) OCASTTranslatorForEffect 0x7ffeb65819a8 M OCASTTranslator>visitMethodNode: 0x235e250: a(n) OCASTTranslator 0x7ffeb65819e0 M RBMethodNode>acceptVisitor: 0x235e328: a(n) RBMethodNode 0x7ffeb6581a18 M OCASTTranslator(RBProgramNodeVisitor)>visitNode: 0x235e250: a(n) OCASTTranslator 0x7ffeb6581a50 M OCASTTranslator>visitNode: 0x235e250: a(n) OCASTTranslator 0x7ffeb6581a90 M RBMethodNode>generateIR 0x235e328: a(n) RBMethodNode 0x7ffeb6581ac0 M RBMethodNode>generate: 0x235e328: a(n) RBMethodNode 0x7ffeb6581b00 M [] in OpalCompiler>compile 0x235e3d0: a(n) OpalCompiler 0x7ffeb6581b30 M BlockClosure>on:do: 0x235e4c0: a(n) BlockClosure 0x7ffeb6581b78 M OpalCompiler>compile 0x235e3d0: a(n) OpalCompiler 0x7ffeb6581ba8 M MethodAddition>createCompiledMethod 0x235e5c0: a(n) MethodAddition 0x7ffeb6581be0 M MCMethodDefinition>addMethodAdditionTo: 0x644f908: a(n) MCMethodDefinition 0x7ffeb6581c20 M [] in MCPackageLoader>tryToLoad: 0x64eacb0: a(n) MCPackageLoader 0x7ffeb6581c50 M BlockClosure>on:do: 0x235e6d0: a(n) BlockClosure 0x7ffeb6581c90 M MCPackageLoader>tryToLoad: 0x64eacb0: a(n) MCPackageLoader 0x7ffeb6581cc8 M [] in MCPackageLoader>basicLoadDefinitions 0x64eacb0: a(n) MCPackageLoader 0x7ffeb6581d30 M [] in OrderedCollection(Collection)>do:displayingProgress:every: 0x653f700: a(n) OrderedCollection 0x7ffeb6581d78 M OrderedCollection>do: 0x653f700: a(n) OrderedCollection 0x7ffeb6581dd8 M [] in OrderedCollection(Collection)>do:displayingProgress:every: 0x653f700: a(n) OrderedCollection 0x7ffeb656b818 M BlockClosure>cull: 0x656a310: a(n) BlockClosure 0x7ffeb656b850 M [] in Job>run 0x6540440: a(n) Job 0x7ffeb656b898 M [] in CurrentJob(DynamicVariable)>value:during: 0x36bf880: a(n) CurrentJob 0x7ffeb656b8d8 M BlockClosure>ensure: 0x6583098: a(n) BlockClosure 0x7ffeb656b920 M CurrentJob(DynamicVariable)>value:during: 0x36bf880: a(n) CurrentJob 0x7ffeb656b960 M CurrentJob class(DynamicVariable class)>value:during: 0x39a3f30: a(n) CurrentJob class 0x7ffeb656b9a0 M [] in Job>run 0x6540440: a(n) Job 0x7ffeb656b9e0 M BlockClosure>ensure: 0x6583270: a(n) BlockClosure 0x7ffeb656ba18 M Job>run 0x6540440: a(n) Job 0x7ffeb656ba48 M NonInteractiveUIManager(UIManager)>displayProgress:from:to:during: 0x5d3e0a8: a(n) NonInteractiveUIManager 0x7ffeb656ba98 M ByteString(String)>displayProgressFrom:to:during: 0x3a84fc8: a(n) ByteString 0x7ffeb656baf0 M OrderedCollection(Collection)>do:displayingProgress:every: 0x653f700: a(n) OrderedCollection 0x7ffeb656bb38 M OrderedCollection(Collection)>do:displayingProgress: 0x653f700: a(n) OrderedCollection 0x7ffeb656bb78 M MCPackageLoader>basicLoadDefinitions 0x64eacb0: a(n) MCPackageLoader 0x7ffeb656bba8 M [] in MCPackageLoader>basicLoad 0x64eacb0: a(n) MCPackageLoader 0x7ffeb656bbe0 M [] in SourceFileArray>deferFlushDuring: 0x2f76370: a(n) SourceFileArray 0x7ffeb656bc20 M BlockClosure>ensure: 0x6583388: a(n) BlockClosure 0x7ffeb656bc58 M SourceFileArray>deferFlushDuring: 0x2f76370: a(n) SourceFileArray 0x7ffeb656bc90 M MCPackageLoader>basicLoad 0x64eacb0: a(n) MCPackageLoader 0x7ffeb656bcc0 M [] in MCPackageLoader>loadWithNameLike: 0x64eacb0: a(n) MCPackageLoader 0x7ffeb656bd00 M BlockClosure>ensure: 0x6583540: a(n) BlockClosure 0x7ffeb656bd48 M MCPackageLoader>useChangeSetNamed:during: 0x64eacb0: a(n) MCPackageLoader 0x7ffeb656bd98 I MCPackageLoader>useNewChangeSetNamedLike:during: 0x64eacb0: a(n) MCPackageLoader 0x7ffeb656bdd8 M MCPackageLoader>loadWithNameLike: 0x64eacb0: a(n) MCPackageLoader 0x7ffeb65637c0 M MCVersionLoader>basicLoadWithNameLike: 0x644be48: a(n) MCVersionLoader 0x7ffeb6563800 M [] in MCVersionLoader>loadWithNameLike: 0x644be48: a(n) MCVersionLoader 0x7ffeb6563840 M [] in MCVersionLoader>announceLoad:do: 0x644be48: a(n) MCVersionLoader 0x7ffeb6563880 M BlockClosure>ensure: 0x64eaec8: a(n) BlockClosure 0x7ffeb65638d0 M [] in MCVersionLoader>announceLoad:do: 0x644be48: a(n) MCVersionLoader 0x7ffeb6563910 M BlockClosure>ensure: 0x64eb010: a(n) BlockClosure 0x7ffeb6563950 M MCVersionLoader>announceLoad:do: 0x644be48: a(n) MCVersionLoader 0x7ffeb6563990 M MCVersionLoader>loadWithNameLike: 0x644be48: a(n) MCVersionLoader 0x7ffeb65639d0 M [] in MCVersionLoader>load 0x644be48: a(n) MCVersionLoader 0x7ffeb6563a00 M BlockClosure>cull: 0x644df68: a(n) BlockClosure 0x7ffeb6563a38 M [] in Job>run 0x6446d10: a(n) Job 0x7ffeb6563a80 M [] in CurrentJob(DynamicVariable)>value:during: 0x36bf880: a(n) CurrentJob 0x7ffeb6563ac0 M BlockClosure>ensure: 0x64eb1c8: a(n) BlockClosure 0x7ffeb6563b08 M CurrentJob(DynamicVariable)>value:during: 0x36bf880: a(n) CurrentJob 0x7ffeb6563b48 M CurrentJob class(DynamicVariable class)>value:during: 0x39a3f30: a(n) CurrentJob class 0x7ffeb6563b88 M [] in Job>run 0x6446d10: a(n) Job 0x7ffeb6563bc8 M BlockClosure>ensure: 0x64eb3a0: a(n) BlockClosure 0x7ffeb6563c00 M Job>run 0x6446d10: a(n) Job 0x7ffeb6563c38 M [] in MCVersionLoader>load 0x644be48: a(n) MCVersionLoader 0x7ffeb6563c78 M BlockClosure>ensure: 0x64eabb8: a(n) BlockClosure 0x7ffeb6563cb8 M RPackageSet class>withCacheDo: 0x31e8ab8: a(n) RPackageSet class 0x7ffeb6563cf0 M MCVersionLoader>load 0x644be48: a(n) MCVersionLoader 0x7ffeb6563d30 I MetacelloGoferLoad(GoferLoad)>execute 0x6444ed0: a(n) MetacelloGoferLoad 0x7ffeb6563d78 M [] in MetacelloLoadingMCSpecLoader(MetacelloCommonMCSpecLoader)>loadPackageDirective:gofer: 0x62fe108: a(n) MetacelloLoadingMCSpecLoader 0x7ffeb6563de0 M [] in MetacelloLoadingMCSpecLoader(MetacelloCommonMCSpecLoader)>loadPackageDirective:gofer: 0x62fe108: a(n) MetacelloLoadingMCSpecLoader 0x6184b88 s [] in IceMetacelloPharoPlatform(MetacelloPharoCommonPlatform)>do:displaying: 0x6184c50 s BlockClosure>cull: 0x6184d08 s [] in Job>run 0x6184dc0 s [] in CurrentJob(DynamicVariable)>value:during: 0x6184e98 s BlockClosure>ensure: 0x6185040 s CurrentJob(DynamicVariable)>value:during: 0x6185200 s CurrentJob class(DynamicVariable class)>value:during: 0x6184f88 s [] in Job>run 0x6185128 s BlockClosure>ensure: 0x61852b8 s Job>run 0x6185390 s NonInteractiveUIManager(UIManager)>displayProgress:from:to:during: 0x6185448 s ByteString(String)>displayProgressFrom:to:during: 0x62fe210 s IceMetacelloPharoPlatform(MetacelloPharoCommonPlatform)>do:displaying: 0x6302c90 s MetacelloLoadingMCSpecLoader(MetacelloCommonMCSpecLoader)>loadPackageDirective:gofer: 0x63086b0 s MetacelloExplicitLoadDirective(MetacelloVersionLoadDirective)>loadPackageDirective:gofer: 0x6310108 s MetacelloPackageLoadDirective>loadUsing:gofer: 0x6314df0 s [] in MetacelloExplicitLoadDirective(MetacelloVersionLoadDirective)>loadLinearLoadDirective:gofer: 0x63176b0 s OrderedCollection>do: 0x6318630 s MetacelloExplicitLoadDirective(MetacelloVersionLoadDirective)>loadLinearLoadDirective:gofer: 0x6319b48 s MetacelloExplicitLoadDirective>explicitLoadUsing:gofer: 0x631aa78 s MetacelloExplicitLoadDirective>explicitLoadWithPolicy: 0x631bc30 s MetacelloEnsureFetchingMCSpecLoader(MetacelloFetchingMCSpecLoader)>explicitLoadPackageSpecs:repositories: 0x631c9e8 s MetacelloPackageSpec>explicitLoadUsing: 0x631dcf8 s MetacelloPackageSpec>ensureLoadUsing: 0x631eb60 s MetacelloMCNamelessProjectSpec(MetacelloMCProjectSpec)>ensureLoadUsing: 0x631fd00 s MetacelloMCNamelessProjectSpec(MetacelloMCProjectSpec)>ensureLoadedForDevelopmentUsing: 0x6320978 s [] in MetacelloMCVersionSpecLoader>load 0x63216c8 s Array(SequenceableCollection)>do: 0x5ea7130 s MetacelloMCVersionSpecLoader>load 0x606c578 s MetacelloMCVersion>executeLoadFromArray: 0x6093448 s [] in MetacelloMCVersion>fetchRequiredFromArray: 0x60ac4f0 s [] in IceMetacelloPharoPlatform(MetacelloPlatform)>useStackCacheDuring:defaultDictionary: 0x5ea7240 s BlockClosure>on:do: 0x5ea7330 s IceMetacelloPharoPlatform(MetacelloPlatform)>useStackCacheDuring:defaultDictionary: 0x5ea7400 s [] in MetacelloMCVersion>fetchRequiredFromArray: 0x606c630 s BlockClosure>ensure: 0x5ea7510 s [] in MetacelloMCVersion>fetchRequiredFromArray: 0x606c6e8 s [] in IceMetacelloPharoPlatform(MetacelloPharoCommonPlatform)>do:displaying: 0x6093500 s BlockClosure>cull: 0x60ac5a8 s [] in Job>run 0x62ee0d0 s [] in CurrentJob(DynamicVariable)>value:during: 0x62fe898 s BlockClosure>ensure: 0x5ea7650 s CurrentJob(DynamicVariable)>value:during: 0x606c7a0 s CurrentJob class(DynamicVariable class)>value:during: 0x5ea7708 s [] in Job>run 0x606c858 s BlockClosure>ensure: 0x5ea7800 s Job>run 0x606c910 s NonInteractiveUIManager(UIManager)>displayProgress:from:to:during: 0x5ea78b8 s ByteString(String)>displayProgressFrom:to:during: 0x5e70fc0 s IceMetacelloPharoPlatform(MetacelloPharoCommonPlatform)>do:displaying: 0x5e80a38 s MetacelloMCVersion>fetchRequiredFromArray: 0x5ea62e0 s [] in MetacelloMCConfigurationOfProjectSpec(MetacelloMCProjectSpec)>loadVersion: 0x606c128 s [] in IceMetacelloPharoPlatform(MetacelloPlatform)>useStackCacheDuring:defaultDictionary: 0x5ea6400 s BlockClosure>on:do: 0x5ea64f0 s IceMetacelloPharoPlatform(MetacelloPlatform)>useStackCacheDuring:defaultDictionary: 0x5ea65c0 s MetacelloMCConfigurationOfProjectSpec(MetacelloMCProjectSpec)>loadVersion: 0x606c1e0 s MetacelloProjectSpecForLoad>performLoad 0x5ea6740 s MetacelloMCNamelessProjectSpec(MetacelloGenericProjectSpec)>load 0x606c298 s MetacelloProjectReferenceSpec>loadUsing:gofer: 0x60932d8 s [] in MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>linearLoadPackageSpecs:repositories: 0x60ac438 s OrderedCollection>do: 0x5ea6870 s MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>linearLoadPackageSpecs:repositories: 0x606c350 s [] in MetacelloFetchingMCSpecLoader>linearLoadPackageSpecs:repositories: 0x6093390 s BlockClosure>ensure: 0x5ea69a0 s MetacelloLoaderPolicy>pushLoadDirective:during: 0x606c408 s MetacelloLoaderPolicy>pushLinearLoadDirectivesDuring:for: 0x5ea6a58 s MetacelloFetchingMCSpecLoader>linearLoadPackageSpecs:repositories: 0x606c4c0 s MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>load 0x5d8aae8 s MetacelloMCVersionSpecLoader>load 0x5d88aa8 s MetacelloMCVersion>executeLoadFromArray: 0x606bc20 s [] in MetacelloMCVersion>fetchRequiredFromArray: 0x6092ff8 s [] in IceMetacelloPharoPlatform(MetacelloPlatform)>useStackCacheDuring:defaultDictionary: 0x5d88bd0 s BlockClosure>on:do: 0x5d88cc0 s IceMetacelloPharoPlatform(MetacelloPlatform)>useStackCacheDuring:defaultDictionary: 0x5d88d78 s [] in MetacelloMCVersion>fetchRequiredFromArray: 0x606bcd8 s BlockClosure>ensure: 0x5d88e88 s [] in MetacelloMCVersion>fetchRequiredFromArray: 0x606bd90 s [] in IceMetacelloPharoPlatform(MetacelloPharoCommonPlatform)>do:displaying: 0x60930b0 s BlockClosure>cull: 0x60ac380 s [] in Job>run 0x62ee018 s [] in CurrentJob(DynamicVariable)>value:during: 0x62fe7e0 s BlockClosure>ensure: 0x5d88fc8 s CurrentJob(DynamicVariable)>value:during: 0x606be48 s CurrentJob class(DynamicVariable class)>value:during: 0x5d89080 s [] in Job>run 0x606bf00 s BlockClosure>ensure: 0x5d89178 s Job>run 0x606bfb8 s NonInteractiveUIManager(UIManager)>displayProgress:from:to:during: 0x6093168 s ByteString(String)>displayProgressFrom:to:during: 0x5d684f0 s IceMetacelloPharoPlatform(MetacelloPharoCommonPlatform)>do:displaying: 0x5d71c88 s MetacelloMCVersion>fetchRequiredFromArray: 0x606c070 s [] in MetacelloMCVersion>doLoadRequiredFromArray: 0x6093220 s BlockClosure>ensure: 0x5d892e8 s MetacelloMCVersion>doLoadRequiredFromArray: 0x5d893a0 s MetacelloMCVersion>load 0x5d89458 s [] in MetacelloScriptEngine>load:onProjectDownGrade:onProjectUpgrade: 0x5d895b8 s BlockClosure>on:do: 0x5d896a0 s [] in MetacelloScriptEngine>handleNotificationsForAction: 0x5d89780 s BlockClosure>on:do: 0x5d89868 s [] in MetacelloScriptEngine>handleNotificationsForAction: 0x5d89948 s BlockClosure>on:do: 0x5d89a20 s [] in MetacelloScriptEngine>handleNotificationsForAction: 0x5d89b00 s BlockClosure>on:do: 0x5d89bd8 s MetacelloScriptEngine>handleNotificationsForAction: 0x5d89c90 s [] in MetacelloScriptEngine>load:onProjectDownGrade:onProjectUpgrade: 0x606bab0 s BlockClosure>ensure: 0x5d89dc0 s MetacelloProjectRegistration class>copyRegistryRestoreOnErrorWhile: 0x5d89e78 s MetacelloScriptEngine>load:onProjectDownGrade:onProjectUpgrade: 0x5d89f30 s MetacelloScriptEngine>load: 0x606bb68 s [] in MetacelloScriptApiExecutor(MetacelloScriptExecutor)>execute: 0x6092f40 s [] in MetacelloScriptApiExecutor>executeString:do: 0x60ac2c8 s Array(SequenceableCollection)>do: 0x5d8a120 s MetacelloScriptApiExecutor>executeString:do: 0x5d8a1f8 s ByteString(String)>execute:against: 0x5d87e70 s MetacelloScriptApiExecutor(MetacelloScriptExecutor)>execute: 0x606b888 s Metacello>execute:args: 0x6092d18 s Metacello>load 0x5d87f60 s [] in UndefinedObject>DoIt 0x5d88038 s BlockClosure>on:do: 0x5d88110 s UndefinedObject>DoIt 0x606b940 s OpalCompiler>evaluate 0x6092dd0 s OpalCompiler(AbstractCompiler)>evaluate: 0x60ac210 s [] in EvaluateCommandLineHandler>evaluate: 0x5d88500 s BlockClosure>on:do: 0x5d885d8 s EvaluateCommandLineHandler>evaluate: 0x5d88690 s EvaluateCommandLineHandler>evaluateArguments 0x5d88748 s EvaluateCommandLineHandler>activate 0x606b9f8 s EvaluateCommandLineHandler class(CommandLineHandler class)>activateWith: 0x6092e88 s [] in PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: 0x5d88838 s BlockClosure>on:do: 0x5d88918 s PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: 0x5d889f0 s PharoCommandLineHandler(BasicCommandLineHandler)>handleSubcommand 0x5d87070 s PharoCommandLineHandler(BasicCommandLineHandler)>handleArgument: 0x5d87138 s [] in PharoCommandLineHandler(BasicCommandLineHandler)>activate 0x5d87210 s BlockClosure>on:do: 0x5d872e8 s PharoCommandLineHandler(BasicCommandLineHandler)>activate 0x606b4f0 s PharoCommandLineHandler>activate 0x6092ba8 s PharoCommandLineHandler class(CommandLineHandler class)>activateWith: 0x60ac0a0 s [] in PharoCommandLineHandler class>activateWith: 0x62edf60 s NonInteractiveUIManager(UIManager)>defer: 0x5d873d8 s PharoCommandLineHandler class>activateWith: 0x606b5a8 s [] in BasicCommandLineHandler>activateSubCommand: 0x5d874e0 s BlockClosure>on:do: 0x5d875c0 s BasicCommandLineHandler>activateSubCommand: 0x5d87698 s BasicCommandLineHandler>handleSubcommand 0x606b660 s BasicCommandLineHandler>handleArgument: 0x5d87770 s [] in BasicCommandLineHandler>activate 0x5d87848 s BlockClosure>on:do: 0x5d87920 s BasicCommandLineHandler>activate 0x606b718 s [] in BasicCommandLineHandler class>startUp: 0x6092c60 s BlockClosure>cull: 0x60ac158 s WorkingSession>executeDeferredStartupActions: 0x5d879f8 s WorkingSession>runStartup: 0x606b7d0 s WorkingSession>start: 0x5aa07a0 s SessionManager>snapshot:andQuit: 0x5abd988 s [] in SmalltalkImage>snapshot:andQuit: 0x5abeb68 s CurrentExecutionEnvironment class>activate:for: 0x5abf148 s DefaultExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: 0x5abf730 s DefaultExecutionEnvironment class>beActiveDuring: 0x5abf200 s SmalltalkImage>snapshot:andQuit: 0x5abf7e8 s EvaluateCommandLineHandler>activate 0x5abfaa8 s EvaluateCommandLineHandler class(CommandLineHandler class)>activateWith: 0x5abfdb0 s [] in PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: 0x5ac01b8 s BlockClosure>on:do: 0x5ac0450 s PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: 0x5ac1648 s PharoCommandLineHandler(BasicCommandLineHandler)>handleSubcommand 0x5ac1ce8 s PharoCommandLineHandler(BasicCommandLineHandler)>handleArgument: 0x5ac2000 s [] in PharoCommandLineHandler(BasicCommandLineHandler)>activate 0x5ac23b0 s BlockClosure>on:do: 0x5ac2698 s PharoCommandLineHandler(BasicCommandLineHandler)>activate 0x5ac2890 s PharoCommandLineHandler>activate 0x5ac2948 s PharoCommandLineHandler class(CommandLineHandler class)>activateWith: 0x5ac2a00 s [] in PharoCommandLineHandler class>activateWith: 0x5ac2ac8 s NonInteractiveUIManager(UIManager)>defer: 0x5ac2bc8 s PharoCommandLineHandler class>activateWith: 0x5ac2cd0 s [] in BasicCommandLineHandler>activateSubCommand: 0x5ac2da8 s BlockClosure>on:do: 0x5ac2eb0 s BasicCommandLineHandler>activateSubCommand: 0x5ac3000 s BasicCommandLineHandler>handleSubcommand 0x5ac30d8 s BasicCommandLineHandler>handleArgument: 0x5ac31e0 s [] in BasicCommandLineHandler>activate 0x5ac3470 s BlockClosure>on:do: 0x5ac3758 s BasicCommandLineHandler>activate 0x5ac3950 s [] in BasicCommandLineHandler class>startUp: 0x5ac3a08 s BlockClosure>cull: 0x5ac3ae0 s WorkingSession>executeDeferredStartupActions: 0x5ac3c50 s WorkingSession>runStartup: 0x5ac3d08 s WorkingSession>start: 0x5a87f60 s SessionManager>snapshot:andQuit: 0x5a8b198 s [] in SmalltalkImage>snapshot:andQuit: 0x5a8ca30 s CurrentExecutionEnvironment class>activate:for: 0x5a8ea20 s DefaultExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: 0x5a90160 s DefaultExecutionEnvironment class>beActiveDuring: 0x5a8ead8 s SmalltalkImage>snapshot:andQuit: 0x5a90218 s EvaluateCommandLineHandler>activate 0x5a91738 s EvaluateCommandLineHandler class(CommandLineHandler class)>activateWith: 0x5a95dd0 s [] in PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: 0x5a97788 s BlockClosure>on:do: 0x5a9b230 s PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: 0x5a9da20 s PharoCommandLineHandler(BasicCommandLineHandler)>handleSubcommand 0x5a9e3c0 s PharoCommandLineHandler(BasicCommandLineHandler)>handleArgument: 0x5a9e8a8 s [] in PharoCommandLineHandler(BasicCommandLineHandler)>activate 0x5a9ec58 s BlockClosure>on:do: 0x5a9ef40 s PharoCommandLineHandler(BasicCommandLineHandler)>activate 0x5a9f138 s PharoCommandLineHandler>activate 0x5a9f1f0 s PharoCommandLineHandler class(CommandLineHandler class)>activateWith: 0x5a9f2a8 s [] in PharoCommandLineHandler class>activateWith: 0x5a9f370 s NonInteractiveUIManager(UIManager)>defer: 0x5a9f470 s PharoCommandLineHandler class>activateWith: 0x5a9f578 s [] in BasicCommandLineHandler>activateSubCommand: 0x5a9f650 s BlockClosure>on:do: 0x5a9f758 s BasicCommandLineHandler>activateSubCommand: 0x5a9f8a8 s BasicCommandLineHandler>handleSubcommand 0x5a9f980 s BasicCommandLineHandler>handleArgument: 0x5a9fa88 s [] in BasicCommandLineHandler>activate 0x5a9fd18 s BlockClosure>on:do: 0x5aa0000 s BasicCommandLineHandler>activate 0x5aa01f8 s [] in BasicCommandLineHandler class>startUp: 0x5aa02b0 s BlockClosure>cull: 0x5aa0388 s WorkingSession>executeDeferredStartupActions: 0x5aa04f8 s WorkingSession>runStartup: 0x5aa05b0 s WorkingSession>start: 0x5a32f30 s SessionManager>snapshot:andQuit: 0x5a333a0 s [] in SmalltalkImage>snapshot:andQuit: 0x5a350a8 s CurrentExecutionEnvironment class>activate:for: 0x5a35428 s DefaultExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: 0x5a35710 s DefaultExecutionEnvironment class>beActiveDuring: 0x5a354e0 s SmalltalkImage>snapshot:andQuit: 0x5a357c8 s SmalltalkImage>saveImageInFileNamed: 0x5a358d0 s SmalltalkImage>saveAs: 0x5a35ae0 s SaveCommandLineHandler>saveImage 0x5a35c30 s SaveCommandLineHandler>activate 0x5a35e30 s SaveCommandLineHandler class(CommandLineHandler class)>activateWith: 0x5a36038 s [] in PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: 0x5a36310 s BlockClosure>on:do: 0x5a36480 s PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: 0x5a36788 s PharoCommandLineHandler(BasicCommandLineHandler)>handleSubcommand 0x5a36a80 s PharoCommandLineHandler(BasicCommandLineHandler)>handleArgument: 0x5a36ca8 s [] in PharoCommandLineHandler(BasicCommandLineHandler)>activate 0x5a36f38 s BlockClosure>on:do: 0x5a37220 s PharoCommandLineHandler(BasicCommandLineHandler)>activate 0x5a37418 s PharoCommandLineHandler>activate 0x5a374d0 s PharoCommandLineHandler class(CommandLineHandler class)>activateWith: 0x5a37588 s [] in PharoCommandLineHandler class>activateWith: 0x5a37650 s NonInteractiveUIManager(UIManager)>defer: 0x5a37750 s PharoCommandLineHandler class>activateWith: 0x5a37858 s [] in BasicCommandLineHandler>activateSubCommand: 0x5a37930 s BlockClosure>on:do: 0x5a37a38 s BasicCommandLineHandler>activateSubCommand: 0x5a37b88 s BasicCommandLineHandler>handleSubcommand 0x5a37c60 s BasicCommandLineHandler>handleArgument: 0x5a37d68 s [] in BasicCommandLineHandler>activate 0x5a37ff8 s BlockClosure>on:do: 0x5a382e0 s BasicCommandLineHandler>activate 0x5a384d8 s [] in BasicCommandLineHandler class>startUp: 0x5a38590 s BlockClosure>cull: 0x5a38668 s WorkingSession>executeDeferredStartupActions: 0x5a387d8 s WorkingSession>runStartup: 0x5a38890 s WorkingSession>start: 0x5a1d7e0 s SessionManager>snapshot:andQuit: 0x5a1eeb8 s [] in SmalltalkImage>snapshot:andQuit: 0x5a1f8c0 s CurrentExecutionEnvironment class>activate:for: 0x5a20020 s DefaultExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: 0x5a20568 s DefaultExecutionEnvironment class>beActiveDuring: 0x5a200d8 s SmalltalkImage>snapshot:andQuit: 0x5a20620 s ImageCleanerCommandLineHandler>activate 0x5a20b18 s ImageCleanerCommandLineHandler class(CommandLineHandler class)>activateWith: 0x5a20e10 s [] in PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: 0x514a970 s BlockClosure>on:do: 0x514aa50 s PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: 0x514a490 s PharoCommandLineHandler(BasicCommandLineHandler)>handleSubcommand 0x5a1d8f8 s PharoCommandLineHandler(BasicCommandLineHandler)>handleArgument: 0x514a548 s [] in PharoCommandLineHandler(BasicCommandLineHandler)>activate 0x514a620 s BlockClosure>on:do: 0x514a6f8 s PharoCommandLineHandler(BasicCommandLineHandler)>activate 0x5a1d9b0 s PharoCommandLineHandler>activate 0x5a1ef80 s PharoCommandLineHandler class(CommandLineHandler class)>activateWith: 0x5a1f9a8 s [] in PharoCommandLineHandler class>activateWith: 0x5a20190 s NonInteractiveUIManager(UIManager)>defer: 0x50c8408 s PharoCommandLineHandler class>activateWith: 0x5a1da68 s [] in BasicCommandLineHandler>activateSubCommand: 0x514a7b0 s BlockClosure>on:do: 0x50c8538 s BasicCommandLineHandler>activateSubCommand: 0x50c8610 s BasicCommandLineHandler>handleSubcommand 0x5a1db20 s BasicCommandLineHandler>handleArgument: 0x50c86d8 s [] in BasicCommandLineHandler>activate 0x514a868 s BlockClosure>on:do: 0x50c87d0 s BasicCommandLineHandler>activate 0x5a1dbd8 s [] in BasicCommandLineHandler class>startUp: 0x5a1f038 s BlockClosure>cull: 0x5a1fa60 s WorkingSession>executeDeferredStartupActions: 0x50c88a8 s WorkingSession>runStartup: 0x5a1dc90 s WorkingSession>start: 0x50b8758 s SessionManager>snapshot:andQuit: 0x50bc510 s [] in SmalltalkImage>snapshot:andQuit: 0x50c6dc8 s CurrentExecutionEnvironment class>activate:for: 0x50c7610 s DefaultExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: 0x50c7aa8 s DefaultExecutionEnvironment class>beActiveDuring: 0x50c76c8 s SmalltalkImage>snapshot:andQuit: 0x50af818 s LoadUpdatesCommandLineHandler>activate 0x50af8d0 s LoadUpdatesCommandLineHandler class(CommandLineHandler class)>activateWith: 0x50afb98 s [] in PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: 0x50afd70 s BlockClosure>on:do: 0x50afe50 s PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: 0x50aff30 s PharoCommandLineHandler(BasicCommandLineHandler)>handleSubcommand 0x50affe8 s PharoCommandLineHandler(BasicCommandLineHandler)>handleArgument: 0x50b00c0 s [] in PharoCommandLineHandler(BasicCommandLineHandler)>activate 0x50b01d0 s BlockClosure>on:do: 0x50b02a8 s PharoCommandLineHandler(BasicCommandLineHandler)>activate 0x50b0380 s PharoCommandLineHandler>activate 0x50b0438 s PharoCommandLineHandler class(CommandLineHandler class)>activateWith: 0x50b04f0 s [] in PharoCommandLineHandler class>activateWith: 0x50b05a8 s NonInteractiveUIManager(UIManager)>defer: 0x50aee08 s PharoCommandLineHandler class>activateWith: 0x50b0678 s [] in BasicCommandLineHandler>activateSubCommand: 0x50b0a28 s BlockClosure>on:do: 0x50aef38 s BasicCommandLineHandler>activateSubCommand: 0x50af010 s BasicCommandLineHandler>handleSubcommand 0x50b0730 s BasicCommandLineHandler>handleArgument: 0x50af0c8 s [] in BasicCommandLineHandler>activate 0x50b07e8 s BlockClosure>on:do: 0x50af1c0 s BasicCommandLineHandler>activate 0x50b08a0 s [] in BasicCommandLineHandler class>startUp: 0x50b0ae0 s BlockClosure>cull: 0x50b0b98 s WorkingSession>executeDeferredStartupActions: 0x50af298 s WorkingSession>runStartup: 0x50b0958 s WorkingSession>start: 0x50aba78 s SessionManager>snapshot:andQuit: 0x50abf80 s [] in SmalltalkImage>snapshot:andQuit: 0x50ac1a8 s CurrentExecutionEnvironment class>activate:for: 0x50ac400 s DefaultExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: 0x50ac628 s DefaultExecutionEnvironment class>beActiveDuring: 0x50ac4b8 s SmalltalkImage>snapshot:andQuit: 0x50ac6e0 s ImageCleanerCommandLineHandler>activate 0x50ac798 s ImageCleanerCommandLineHandler class(CommandLineHandler class)>activateWith: 0x50ac850 s [] in PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: 0x50ab148 s BlockClosure>on:do: 0x50ab228 s PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: 0x50aac68 s PharoCommandLineHandler(BasicCommandLineHandler)>handleSubcommand 0x50abb30 s PharoCommandLineHandler(BasicCommandLineHandler)>handleArgument: 0x50aad20 s [] in PharoCommandLineHandler(BasicCommandLineHandler)>activate 0x50aadf8 s BlockClosure>on:do: 0x50aaed0 s PharoCommandLineHandler(BasicCommandLineHandler)>activate 0x50abbe8 s PharoCommandLineHandler>activate 0x50ac038 s PharoCommandLineHandler class(CommandLineHandler class)>activateWith: 0x50ac290 s [] in PharoCommandLineHandler class>activateWith: 0x50ac570 s NonInteractiveUIManager(UIManager)>defer: 0x50a8820 s PharoCommandLineHandler class>activateWith: 0x50abca0 s [] in BasicCommandLineHandler>activateSubCommand: 0x50aaf88 s BlockClosure>on:do: 0x50a8950 s BasicCommandLineHandler>activateSubCommand: 0x50a8a28 s BasicCommandLineHandler>handleSubcommand 0x50abd58 s BasicCommandLineHandler>handleArgument: 0x50a8af0 s [] in BasicCommandLineHandler>activate 0x50ab040 s BlockClosure>on:do: 0x50a8be8 s BasicCommandLineHandler>activate 0x50abe10 s [] in BasicCommandLineHandler class>startUp: 0x50ac0f0 s BlockClosure>cull: 0x50ac348 s WorkingSession>executeDeferredStartupActions: 0x50a8cc0 s WorkingSession>runStartup: 0x50abec8 s WorkingSession>start: 0x50a7af8 s SessionManager>snapshot:andQuit: 0x50a7bb0 s [] in SmalltalkImage>snapshot:andQuit: 0x50a7c68 s CurrentExecutionEnvironment class>activate:for: 0x50a7d50 s DefaultExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: 0x50a7ec0 s DefaultExecutionEnvironment class>beActiveDuring: 0x50a7e08 s SmalltalkImage>snapshot:andQuit: 0x50936c8 s LoadUpdatesCommandLineHandler>activate 0x5093780 s LoadUpdatesCommandLineHandler class(CommandLineHandler class)>activateWith: 0x5093a48 s [] in PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: 0x5093c20 s BlockClosure>on:do: 0x5093d00 s PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: 0x5093de0 s PharoCommandLineHandler(BasicCommandLineHandler)>handleSubcommand 0x5093e98 s PharoCommandLineHandler(BasicCommandLineHandler)>handleArgument: 0x5093f70 s [] in PharoCommandLineHandler(BasicCommandLineHandler)>activate 0x5094080 s BlockClosure>on:do: 0x5094158 s PharoCommandLineHandler(BasicCommandLineHandler)>activate 0x5094230 s PharoCommandLineHandler>activate 0x50942e8 s PharoCommandLineHandler class(CommandLineHandler class)>activateWith: 0x50943a0 s [] in PharoCommandLineHandler class>activateWith: 0x5094458 s NonInteractiveUIManager(UIManager)>defer: 0x5092d68 s PharoCommandLineHandler class>activateWith: 0x5094510 s [] in BasicCommandLineHandler>activateSubCommand: 0x50948a8 s BlockClosure>on:do: 0x5092e98 s BasicCommandLineHandler>activateSubCommand: 0x5092f70 s BasicCommandLineHandler>handleSubcommand 0x50945c8 s BasicCommandLineHandler>handleArgument: 0x5093028 s [] in BasicCommandLineHandler>activate 0x5094680 s BlockClosure>on:do: 0x5093120 s BasicCommandLineHandler>activate 0x5094738 s [] in BasicCommandLineHandler class>startUp: 0x5094960 s BlockClosure>cull: 0x5094a18 s WorkingSession>executeDeferredStartupActions: 0x50931f8 s WorkingSession>runStartup: 0x50947f0 s WorkingSession>start: 0x508f9d0 s SessionManager>snapshot:andQuit: 0x508fed8 s [] in SmalltalkImage>snapshot:andQuit: 0x5090100 s CurrentExecutionEnvironment class>activate:for: 0x5090358 s DefaultExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: 0x5090580 s DefaultExecutionEnvironment class>beActiveDuring: 0x5090410 s SmalltalkImage>snapshot:andQuit: 0x5090638 s ImageCleanerCommandLineHandler>activate 0x50906f0 s ImageCleanerCommandLineHandler class(CommandLineHandler class)>activateWith: 0x50907a8 s [] in PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: 0x508f390 s BlockClosure>on:do: 0x508f470 s PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: 0x508eeb0 s PharoCommandLineHandler(BasicCommandLineHandler)>handleSubcommand 0x508fa88 s PharoCommandLineHandler(BasicCommandLineHandler)>handleArgument: 0x508ef68 s [] in PharoCommandLineHandler(BasicCommandLineHandler)>activate 0x508f040 s BlockClosure>on:do: 0x508f118 s PharoCommandLineHandler(BasicCommandLineHandler)>activate 0x508fb40 s PharoCommandLineHandler>activate 0x508ff90 s PharoCommandLineHandler class(CommandLineHandler class)>activateWith: 0x50901e8 s [] in PharoCommandLineHandler class>activateWith: 0x50904c8 s NonInteractiveUIManager(UIManager)>defer: 0x508ca48 s PharoCommandLineHandler class>activateWith: 0x508fbf8 s [] in BasicCommandLineHandler>activateSubCommand: 0x508f1d0 s BlockClosure>on:do: 0x508cb78 s BasicCommandLineHandler>activateSubCommand: 0x508cc50 s BasicCommandLineHandler>handleSubcommand 0x508fcb0 s BasicCommandLineHandler>handleArgument: 0x508cd18 s [] in BasicCommandLineHandler>activate 0x508f288 s BlockClosure>on:do: 0x508ce10 s BasicCommandLineHandler>activate 0x508fd68 s [] in BasicCommandLineHandler class>startUp: 0x5090048 s BlockClosure>cull: 0x50902a0 s WorkingSession>executeDeferredStartupActions: 0x508cee8 s WorkingSession>runStartup: 0x508fe20 s WorkingSession>start: 0x508bd20 s SessionManager>snapshot:andQuit: 0x508bdd8 s [] in SmalltalkImage>snapshot:andQuit: 0x508be90 s CurrentExecutionEnvironment class>activate:for: 0x508bf78 s DefaultExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: 0x508c0e8 s DefaultExecutionEnvironment class>beActiveDuring: 0x508c030 s SmalltalkImage>snapshot:andQuit: 0x508a908 s LoadUpdatesCommandLineHandler>activate 0x508a9c0 s LoadUpdatesCommandLineHandler class(CommandLineHandler class)>activateWith: 0x508ac88 s [] in PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: 0x508ae60 s BlockClosure>on:do: 0x508af40 s PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: 0x508b020 s PharoCommandLineHandler(BasicCommandLineHandler)>handleSubcommand 0x508b0d8 s PharoCommandLineHandler(BasicCommandLineHandler)>handleArgument: 0x508b1b0 s [] in PharoCommandLineHandler(BasicCommandLineHandler)>activate 0x508b2c0 s BlockClosure>on:do: 0x508b398 s PharoCommandLineHandler(BasicCommandLineHandler)>activate 0x508b470 s PharoCommandLineHandler>activate 0x508b528 s PharoCommandLineHandler class(CommandLineHandler class)>activateWith: 0x508b5e0 s [] in PharoCommandLineHandler class>activateWith: 0x508b698 s NonInteractiveUIManager(UIManager)>defer: 0x5089fa8 s PharoCommandLineHandler class>activateWith: 0x508b750 s [] in BasicCommandLineHandler>activateSubCommand: 0x508bae8 s BlockClosure>on:do: 0x508a0d8 s BasicCommandLineHandler>activateSubCommand: 0x508a1b0 s BasicCommandLineHandler>handleSubcommand 0x508b808 s BasicCommandLineHandler>handleArgument: 0x508a268 s [] in BasicCommandLineHandler>activate 0x508b8c0 s BlockClosure>on:do: 0x508a360 s BasicCommandLineHandler>activate 0x508b978 s [] in BasicCommandLineHandler class>startUp: 0x508bba0 s BlockClosure>cull: 0x508bc58 s WorkingSession>executeDeferredStartupActions: 0x508a438 s WorkingSession>runStartup: 0x508ba30 s WorkingSession>start: 0x5086c30 s SessionManager>snapshot:andQuit: 0x5087138 s [] in SmalltalkImage>snapshot:andQuit: 0x5087360 s CurrentExecutionEnvironment class>activate:for: 0x50875b8 s DefaultExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: 0x50877e0 s DefaultExecutionEnvironment class>beActiveDuring: 0x5087670 s SmalltalkImage>snapshot:andQuit: 0x5087898 s ImageCleanerCommandLineHandler>activate 0x5087950 s ImageCleanerCommandLineHandler class(CommandLineHandler class)>activateWith: 0x5087a08 s [] in PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: 0x50865f0 s BlockClosure>on:do: 0x50866d0 s PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: 0x5086110 s PharoCommandLineHandler(BasicCommandLineHandler)>handleSubcommand 0x5086ce8 s PharoCommandLineHandler(BasicCommandLineHandler)>handleArgument: 0x50861c8 s [] in PharoCommandLineHandler(BasicCommandLineHandler)>activate 0x50862a0 s BlockClosure>on:do: 0x5086378 s PharoCommandLineHandler(BasicCommandLineHandler)>activate 0x5086da0 s PharoCommandLineHandler>activate 0x50871f0 s PharoCommandLineHandler class(CommandLineHandler class)>activateWith: 0x5087448 s [] in PharoCommandLineHandler class>activateWith: 0x5087728 s NonInteractiveUIManager(UIManager)>defer: 0x5083ca8 s PharoCommandLineHandler class>activateWith: 0x5086e58 s [] in BasicCommandLineHandler>activateSubCommand: 0x5086430 s BlockClosure>on:do: 0x5083dd8 s BasicCommandLineHandler>activateSubCommand: 0x5083eb0 s BasicCommandLineHandler>handleSubcommand 0x5086f10 s BasicCommandLineHandler>handleArgument: 0x5083f78 s [] in BasicCommandLineHandler>activate 0x50864e8 s BlockClosure>on:do: 0x5084070 s BasicCommandLineHandler>activate 0x5086fc8 s [] in BasicCommandLineHandler class>startUp: 0x50872a8 s BlockClosure>cull: 0x5087500 s WorkingSession>executeDeferredStartupActions: 0x5084148 s WorkingSession>runStartup: 0x5087080 s WorkingSession>start: 0x5082f80 s SessionManager>snapshot:andQuit: 0x5083038 s [] in SmalltalkImage>snapshot:andQuit: 0x50830f0 s CurrentExecutionEnvironment class>activate:for: 0x50831d8 s DefaultExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: 0x5083348 s DefaultExecutionEnvironment class>beActiveDuring: 0x5083290 s SmalltalkImage>snapshot:andQuit: 0x5080de0 s LoadUpdatesCommandLineHandler>activate 0x5080e98 s LoadUpdatesCommandLineHandler class(CommandLineHandler class)>activateWith: 0x5081160 s [] in PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: 0x5081338 s BlockClosure>on:do: 0x5081418 s PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: 0x50814f8 s PharoCommandLineHandler(BasicCommandLineHandler)>handleSubcommand 0x50815b0 s PharoCommandLineHandler(BasicCommandLineHandler)>handleArgument: 0x5081688 s [] in PharoCommandLineHandler(BasicCommandLineHandler)>activate 0x5081798 s BlockClosure>on:do: 0x5081870 s PharoCommandLineHandler(BasicCommandLineHandler)>activate 0x5081948 s PharoCommandLineHandler>activate 0x5081a00 s PharoCommandLineHandler class(CommandLineHandler class)>activateWith: 0x5081ab8 s [] in PharoCommandLineHandler class>activateWith: 0x5081b70 s NonInteractiveUIManager(UIManager)>defer: 0x5080480 s PharoCommandLineHandler class>activateWith: 0x5082100 s [] in BasicCommandLineHandler>activateSubCommand: 0x5082498 s BlockClosure>on:do: 0x50805b0 s BasicCommandLineHandler>activateSubCommand: 0x5080688 s BasicCommandLineHandler>handleSubcommand 0x50821b8 s BasicCommandLineHandler>handleArgument: 0x5080740 s [] in BasicCommandLineHandler>activate 0x5082270 s BlockClosure>on:do: 0x5080838 s BasicCommandLineHandler>activate 0x5082328 s [] in BasicCommandLineHandler class>startUp: 0x5082550 s BlockClosure>cull: 0x5082608 s WorkingSession>executeDeferredStartupActions: 0x5080910 s WorkingSession>runStartup: 0x50823e0 s WorkingSession>start: 0x507d698 s SessionManager>snapshot:andQuit: 0x507dae8 s [] in SmalltalkImage>snapshot:andQuit: 0x507dd10 s CurrentExecutionEnvironment class>activate:for: 0x507df68 s DefaultExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: 0x507e190 s DefaultExecutionEnvironment class>beActiveDuring: 0x507e020 s SmalltalkImage>snapshot:andQuit: 0x507e248 s ImageCleanerCommandLineHandler>activate 0x507e300 s ImageCleanerCommandLineHandler class(CommandLineHandler class)>activateWith: 0x507e3b8 s [] in PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: 0x507a6a8 s BlockClosure>on:do: 0x507a090 s PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: 0x5079fd8 s PharoCommandLineHandler(BasicCommandLineHandler)>handleSubcommand 0x507a1c0 s PharoCommandLineHandler(BasicCommandLineHandler)>handleArgument: 0x5079ea8 s [] in PharoCommandLineHandler(BasicCommandLineHandler)>activate 0x507a760 s BlockClosure>on:do: 0x5079db0 s PharoCommandLineHandler(BasicCommandLineHandler)>activate 0x507d750 s PharoCommandLineHandler>activate 0x507dba0 s PharoCommandLineHandler class(CommandLineHandler class)>activateWith: 0x507ddf8 s [] in PharoCommandLineHandler class>activateWith: 0x507e0d8 s NonInteractiveUIManager(UIManager)>defer: 0x507d1a0 s PharoCommandLineHandler class>activateWith: 0x507d808 s [] in BasicCommandLineHandler>activateSubCommand: 0x507a818 s BlockClosure>on:do: 0x507d098 s BasicCommandLineHandler>activateSubCommand: 0x507cfe0 s BasicCommandLineHandler>handleSubcommand 0x507d8c0 s BasicCommandLineHandler>handleArgument: 0x507ceb0 s [] in BasicCommandLineHandler>activate 0x507a8d0 s BlockClosure>on:do: 0x507cdb8 s BasicCommandLineHandler>activate 0x507d978 s [] in BasicCommandLineHandler class>startUp: 0x507dc58 s BlockClosure>cull: 0x507deb0 s WorkingSession>executeDeferredStartupActions: 0x507aab8 s WorkingSession>runStartup: 0x507da30 s WorkingSession>start: 0x5075858 s SessionManager>snapshot:andQuit: 0x5076370 s [] in SmalltalkImage>snapshot:andQuit: 0x50765e0 s CurrentExecutionEnvironment class>activate:for: 0x50766e8 s DefaultExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: 0x5076910 s DefaultExecutionEnvironment class>beActiveDuring: 0x50767a0 s SmalltalkImage>snapshot:andQuit: 0x50769c8 s LoadUpdatesCommandLineHandler>activate 0x5076aa0 s LoadUpdatesCommandLineHandler class(CommandLineHandler class)>activateWith: 0x5076c38 s [] in PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: 0x5076d80 s BlockClosure>on:do: 0x5076fa8 s PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: 0x5078190 s PharoCommandLineHandler(BasicCommandLineHandler)>handleSubcommand 0x50782a0 s PharoCommandLineHandler(BasicCommandLineHandler)>handleArgument: 0x50785b8 s [] in PharoCommandLineHandler(BasicCommandLineHandler)>activate 0x50787e8 s BlockClosure>on:do: 0x5078ad0 s PharoCommandLineHandler(BasicCommandLineHandler)>activate 0x5078ba8 s PharoCommandLineHandler>activate 0x5078c60 s PharoCommandLineHandler class(CommandLineHandler class)>activateWith: 0x5078d18 s [] in PharoCommandLineHandler class>activateWith: 0x5078dd0 s NonInteractiveUIManager(UIManager)>defer: 0x5078eb0 s PharoCommandLineHandler class>activateWith: 0x5078f80 s [] in BasicCommandLineHandler>activateSubCommand: 0x5079038 s BlockClosure>on:do: 0x5079140 s BasicCommandLineHandler>activateSubCommand: 0x5079290 s BasicCommandLineHandler>handleSubcommand 0x5079368 s BasicCommandLineHandler>handleArgument: 0x5079470 s [] in BasicCommandLineHandler>activate 0x5079580 s BlockClosure>on:do: 0x5079868 s BasicCommandLineHandler>activate 0x5079940 s [] in BasicCommandLineHandler class>startUp: 0x50799f8 s BlockClosure>cull: 0x5079ad0 s WorkingSession>executeDeferredStartupActions: 0x5079c40 s WorkingSession>runStartup: 0x5079cf8 s WorkingSession>start: 0x5074708 s SessionManager>snapshot:andQuit: 0x5074b58 s [] in SmalltalkImage>snapshot:andQuit: 0x5074d80 s CurrentExecutionEnvironment class>activate:for: 0x5074fd8 s DefaultExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: 0x5075200 s DefaultExecutionEnvironment class>beActiveDuring: 0x5075090 s SmalltalkImage>snapshot:andQuit: 0x50752b8 s ImageCleanerCommandLineHandler>activate 0x5075370 s ImageCleanerCommandLineHandler class(CommandLineHandler class)>activateWith: 0x5075428 s [] in PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: 0x5071718 s BlockClosure>on:do: 0x5071100 s PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: 0x5071048 s PharoCommandLineHandler(BasicCommandLineHandler)>handleSubcommand 0x5071230 s PharoCommandLineHandler(BasicCommandLineHandler)>handleArgument: 0x5070f18 s [] in PharoCommandLineHandler(BasicCommandLineHandler)>activate 0x50717d0 s BlockClosure>on:do: 0x5070e20 s PharoCommandLineHandler(BasicCommandLineHandler)>activate 0x50747c0 s PharoCommandLineHandler>activate 0x5074c10 s PharoCommandLineHandler class(CommandLineHandler class)>activateWith: 0x5074e68 s [] in PharoCommandLineHandler class>activateWith: 0x5075148 s NonInteractiveUIManager(UIManager)>defer: 0x5074210 s PharoCommandLineHandler class>activateWith: 0x5074878 s [] in BasicCommandLineHandler>activateSubCommand: 0x5071888 s BlockClosure>on:do: 0x5074108 s BasicCommandLineHandler>activateSubCommand: 0x5074050 s BasicCommandLineHandler>handleSubcommand 0x5074930 s BasicCommandLineHandler>handleArgument: 0x5073f20 s [] in BasicCommandLineHandler>activate 0x5071940 s BlockClosure>on:do: 0x5073e28 s BasicCommandLineHandler>activate 0x50749e8 s [] in BasicCommandLineHandler class>startUp: 0x5074cc8 s BlockClosure>cull: 0x5074f20 s WorkingSession>executeDeferredStartupActions: 0x5071b28 s WorkingSession>runStartup: 0x5074aa0 s WorkingSession>start: 0x506c8c8 s SessionManager>snapshot:andQuit: 0x506d3e0 s [] in SmalltalkImage>snapshot:andQuit: 0x506d650 s CurrentExecutionEnvironment class>activate:for: 0x506d758 s DefaultExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: 0x506d980 s DefaultExecutionEnvironment class>beActiveDuring: 0x506d810 s SmalltalkImage>snapshot:andQuit: 0x506da38 s LoadUpdatesCommandLineHandler>activate 0x506db10 s LoadUpdatesCommandLineHandler class(CommandLineHandler class)>activateWith: 0x506dca8 s [] in PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: 0x506ddf0 s BlockClosure>on:do: 0x506e018 s PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: 0x506f200 s PharoCommandLineHandler(BasicCommandLineHandler)>handleSubcommand 0x506f310 s PharoCommandLineHandler(BasicCommandLineHandler)>handleArgument: 0x506f628 s [] in PharoCommandLineHandler(BasicCommandLineHandler)>activate 0x506f858 s BlockClosure>on:do: 0x506fb40 s PharoCommandLineHandler(BasicCommandLineHandler)>activate 0x506fc18 s PharoCommandLineHandler>activate 0x506fcd0 s PharoCommandLineHandler class(CommandLineHandler class)>activateWith: 0x506fd88 s [] in PharoCommandLineHandler class>activateWith: 0x506fe40 s NonInteractiveUIManager(UIManager)>defer: 0x506ff20 s PharoCommandLineHandler class>activateWith: 0x506fff0 s [] in BasicCommandLineHandler>activateSubCommand: 0x50700a8 s BlockClosure>on:do: 0x50701b0 s BasicCommandLineHandler>activateSubCommand: 0x5070300 s BasicCommandLineHandler>handleSubcommand 0x50703d8 s BasicCommandLineHandler>handleArgument: 0x50704e0 s [] in BasicCommandLineHandler>activate 0x50705f0 s BlockClosure>on:do: 0x50708d8 s BasicCommandLineHandler>activate 0x50709b0 s [] in BasicCommandLineHandler class>startUp: 0x5070a68 s BlockClosure>cull: 0x5070b40 s WorkingSession>executeDeferredStartupActions: 0x5070cb0 s WorkingSession>runStartup: 0x5070d68 s WorkingSession>start: 0x506b778 s SessionManager>snapshot:andQuit: 0x506bbc8 s [] in SmalltalkImage>snapshot:andQuit: 0x506bdf0 s CurrentExecutionEnvironment class>activate:for: 0x506c048 s DefaultExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: 0x506c270 s DefaultExecutionEnvironment class>beActiveDuring: 0x506c100 s SmalltalkImage>snapshot:andQuit: 0x506c328 s ImageCleanerCommandLineHandler>activate 0x506c3e0 s ImageCleanerCommandLineHandler class(CommandLineHandler class)>activateWith: 0x506c498 s [] in PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: 0x5068788 s BlockClosure>on:do: 0x5068170 s PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: 0x50680b8 s PharoCommandLineHandler(BasicCommandLineHandler)>handleSubcommand 0x50682a0 s PharoCommandLineHandler(BasicCommandLineHandler)>handleArgument: 0x5067f88 s [] in PharoCommandLineHandler(BasicCommandLineHandler)>activate 0x5068840 s BlockClosure>on:do: 0x5067e90 s PharoCommandLineHandler(BasicCommandLineHandler)>activate 0x506b830 s PharoCommandLineHandler>activate 0x506bc80 s PharoCommandLineHandler class(CommandLineHandler class)>activateWith: 0x506bed8 s [] in PharoCommandLineHandler class>activateWith: 0x506c1b8 s NonInteractiveUIManager(UIManager)>defer: 0x506b280 s PharoCommandLineHandler class>activateWith: 0x506b8e8 s [] in BasicCommandLineHandler>activateSubCommand: 0x50688f8 s BlockClosure>on:do: 0x506b178 s BasicCommandLineHandler>activateSubCommand: 0x506b0c0 s BasicCommandLineHandler>handleSubcommand 0x506b9a0 s BasicCommandLineHandler>handleArgument: 0x506af90 s [] in BasicCommandLineHandler>activate 0x50689b0 s BlockClosure>on:do: 0x506ae98 s BasicCommandLineHandler>activate 0x506ba58 s [] in BasicCommandLineHandler class>startUp: 0x506bd38 s BlockClosure>cull: 0x506bf90 s WorkingSession>executeDeferredStartupActions: 0x5068b98 s WorkingSession>runStartup: 0x506bb10 s WorkingSession>start: 0x5063e10 s SessionManager>snapshot:andQuit: 0x5064928 s [] in SmalltalkImage>snapshot:andQuit: 0x5064b98 s CurrentExecutionEnvironment class>activate:for: 0x5064ca0 s DefaultExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: 0x5064ec8 s DefaultExecutionEnvironment class>beActiveDuring: 0x5064d58 s SmalltalkImage>snapshot:andQuit: 0x5064f80 s LoadUpdatesCommandLineHandler>activate 0x5065058 s LoadUpdatesCommandLineHandler class(CommandLineHandler class)>activateWith: 0x5065138 s [] in PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: 0x5065280 s BlockClosure>on:do: 0x50654a8 s PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: 0x5066690 s PharoCommandLineHandler(BasicCommandLineHandler)>handleSubcommand 0x50667a0 s PharoCommandLineHandler(BasicCommandLineHandler)>handleArgument: 0x5066ab8 s [] in PharoCommandLineHandler(BasicCommandLineHandler)>activate 0x5066ce8 s BlockClosure>on:do: 0x5066dc0 s PharoCommandLineHandler(BasicCommandLineHandler)>activate 0x5066e98 s PharoCommandLineHandler>activate 0x5066f50 s PharoCommandLineHandler class(CommandLineHandler class)>activateWith: 0x5067008 s [] in PharoCommandLineHandler class>activateWith: 0x50670c0 s NonInteractiveUIManager(UIManager)>defer: 0x50671a0 s PharoCommandLineHandler class>activateWith: 0x5067270 s [] in BasicCommandLineHandler>activateSubCommand: 0x5067328 s BlockClosure>on:do: 0x5067430 s BasicCommandLineHandler>activateSubCommand: 0x5067580 s BasicCommandLineHandler>handleSubcommand 0x5067658 s BasicCommandLineHandler>handleArgument: 0x5067760 s [] in BasicCommandLineHandler>activate 0x5067870 s BlockClosure>on:do: 0x5067948 s BasicCommandLineHandler>activate 0x5067a20 s [] in BasicCommandLineHandler class>startUp: 0x5067ad8 s BlockClosure>cull: 0x5067bb0 s WorkingSession>executeDeferredStartupActions: 0x5067d20 s WorkingSession>runStartup: 0x5067dd8 s WorkingSession>start: 0x5062730 s SessionManager>snapshot:andQuit: 0x5062c38 s [] in SmalltalkImage>snapshot:andQuit: 0x5062e60 s CurrentExecutionEnvironment class>activate:for: 0x50630b8 s DefaultExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: 0x50632e0 s DefaultExecutionEnvironment class>beActiveDuring: 0x5063170 s SmalltalkImage>snapshot:andQuit: 0x5063398 s ImageCleanerCommandLineHandler>activate 0x5063450 s ImageCleanerCommandLineHandler class(CommandLineHandler class)>activateWith: 0x5063508 s [] in PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: 0x50620f0 s BlockClosure>on:do: 0x50621d0 s PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: 0x5061c10 s PharoCommandLineHandler(BasicCommandLineHandler)>handleSubcommand 0x50627e8 s PharoCommandLineHandler(BasicCommandLineHandler)>handleArgument: 0x5061cc8 s [] in PharoCommandLineHandler(BasicCommandLineHandler)>activate 0x5061da0 s BlockClosure>on:do: 0x5061e78 s PharoCommandLineHandler(BasicCommandLineHandler)>activate 0x50628a0 s PharoCommandLineHandler>activate 0x5062cf0 s PharoCommandLineHandler class(CommandLineHandler class)>activateWith: 0x5062f48 s [] in PharoCommandLineHandler class>activateWith: 0x5063228 s NonInteractiveUIManager(UIManager)>defer: 0x505f7a8 s PharoCommandLineHandler class>activateWith: 0x5062958 s [] in BasicCommandLineHandler>activateSubCommand: 0x5061f30 s BlockClosure>on:do: 0x505f8d8 s BasicCommandLineHandler>activateSubCommand: 0x505f9b0 s BasicCommandLineHandler>handleSubcommand 0x5062a10 s BasicCommandLineHandler>handleArgument: 0x505fa78 s [] in BasicCommandLineHandler>activate 0x5061fe8 s BlockClosure>on:do: 0x505fb70 s BasicCommandLineHandler>activate 0x5062ac8 s [] in BasicCommandLineHandler class>startUp: 0x5062da8 s BlockClosure>cull: 0x5063000 s WorkingSession>executeDeferredStartupActions: 0x505fc48 s WorkingSession>runStartup: 0x5062b80 s WorkingSession>start: 0x505ea80 s SessionManager>snapshot:andQuit: 0x505eb38 s [] in SmalltalkImage>snapshot:andQuit: 0x505ebf0 s CurrentExecutionEnvironment class>activate:for: 0x505ecd8 s DefaultExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: 0x505ee48 s DefaultExecutionEnvironment class>beActiveDuring: 0x505ed90 s SmalltalkImage>snapshot:andQuit: 0x505d678 s LoadUpdatesCommandLineHandler>activate 0x505d730 s LoadUpdatesCommandLineHandler class(CommandLineHandler class)>activateWith: 0x505d9f8 s [] in PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: 0x505dbd0 s BlockClosure>on:do: 0x505dcb0 s PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: 0x505dd90 s PharoCommandLineHandler(BasicCommandLineHandler)>handleSubcommand 0x505de48 s PharoCommandLineHandler(BasicCommandLineHandler)>handleArgument: 0x505df20 s [] in PharoCommandLineHandler(BasicCommandLineHandler)>activate 0x505e030 s BlockClosure>on:do: 0x505e108 s PharoCommandLineHandler(BasicCommandLineHandler)>activate 0x505e1e0 s PharoCommandLineHandler>activate 0x505e298 s PharoCommandLineHandler class(CommandLineHandler class)>activateWith: 0x505e350 s [] in PharoCommandLineHandler class>activateWith: 0x505e408 s NonInteractiveUIManager(UIManager)>defer: 0x505cd18 s PharoCommandLineHandler class>activateWith: 0x505e4c0 s [] in BasicCommandLineHandler>activateSubCommand: 0x505e858 s BlockClosure>on:do: 0x505ce48 s BasicCommandLineHandler>activateSubCommand: 0x505cf20 s BasicCommandLineHandler>handleSubcommand 0x505e578 s BasicCommandLineHandler>handleArgument: 0x505cfd8 s [] in BasicCommandLineHandler>activate 0x505e630 s BlockClosure>on:do: 0x505d0d0 s BasicCommandLineHandler>activate 0x505e6e8 s [] in BasicCommandLineHandler class>startUp: 0x505e910 s BlockClosure>cull: 0x505e9c8 s WorkingSession>executeDeferredStartupActions: 0x505d1a8 s WorkingSession>runStartup: 0x505e7a0 s WorkingSession>start: 0x50599a0 s SessionManager>snapshot:andQuit: 0x5059ea8 s [] in SmalltalkImage>snapshot:andQuit: 0x505a0d0 s CurrentExecutionEnvironment class>activate:for: 0x505a328 s DefaultExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: 0x505a550 s DefaultExecutionEnvironment class>beActiveDuring: 0x505a3e0 s SmalltalkImage>snapshot:andQuit: 0x505a608 s ImageCleanerCommandLineHandler>activate 0x505a6c0 s ImageCleanerCommandLineHandler class(CommandLineHandler class)>activateWith: 0x505a778 s [] in PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: 0x5059360 s BlockClosure>on:do: 0x5059440 s PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: 0x5058e80 s PharoCommandLineHandler(BasicCommandLineHandler)>handleSubcommand 0x5059a58 s PharoCommandLineHandler(BasicCommandLineHandler)>handleArgument: 0x5058f38 s [] in PharoCommandLineHandler(BasicCommandLineHandler)>activate 0x5059010 s BlockClosure>on:do: 0x50590e8 s PharoCommandLineHandler(BasicCommandLineHandler)>activate 0x5059b10 s PharoCommandLineHandler>activate 0x5059f60 s PharoCommandLineHandler class(CommandLineHandler class)>activateWith: 0x505a1b8 s [] in PharoCommandLineHandler class>activateWith: 0x505a498 s NonInteractiveUIManager(UIManager)>defer: 0x5056a18 s PharoCommandLineHandler class>activateWith: 0x5059bc8 s [] in BasicCommandLineHandler>activateSubCommand: 0x50591a0 s BlockClosure>on:do: 0x5056b48 s BasicCommandLineHandler>activateSubCommand: 0x5056c20 s BasicCommandLineHandler>handleSubcommand 0x5059c80 s BasicCommandLineHandler>handleArgument: 0x5056ce8 s [] in BasicCommandLineHandler>activate 0x5059258 s BlockClosure>on:do: 0x5056de0 s BasicCommandLineHandler>activate 0x5059d38 s [] in BasicCommandLineHandler class>startUp: 0x505a018 s BlockClosure>cull: 0x505a270 s WorkingSession>executeDeferredStartupActions: 0x5056eb8 s WorkingSession>runStartup: 0x5059df0 s WorkingSession>start: 0x5055cf0 s SessionManager>snapshot:andQuit: 0x5055da8 s [] in SmalltalkImage>snapshot:andQuit: 0x5055e60 s CurrentExecutionEnvironment class>activate:for: 0x5055f48 s DefaultExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: 0x50560b8 s DefaultExecutionEnvironment class>beActiveDuring: 0x5056000 s SmalltalkImage>snapshot:andQuit: 0x5054ea8 s LoadUpdatesCommandLineHandler>activate 0x5054f60 s LoadUpdatesCommandLineHandler class(CommandLineHandler class)>activateWith: 0x5055228 s [] in PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: 0x5055400 s BlockClosure>on:do: 0x50554e0 s PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: 0x50555c0 s PharoCommandLineHandler(BasicCommandLineHandler)>handleSubcommand 0x5055678 s PharoCommandLineHandler(BasicCommandLineHandler)>handleArgument: 0x5055750 s [] in PharoCommandLineHandler(BasicCommandLineHandler)>activate 0x5055860 s BlockClosure>on:do: 0x5055938 s PharoCommandLineHandler(BasicCommandLineHandler)>activate 0x5055a10 s PharoCommandLineHandler>activate 0x5055ac8 s PharoCommandLineHandler class(CommandLineHandler class)>activateWith: 0x5055b80 s [] in PharoCommandLineHandler class>activateWith: 0x5055c38 s NonInteractiveUIManager(UIManager)>defer: 0x5053f88 s PharoCommandLineHandler class>activateWith: 0x50547c0 s [] in BasicCommandLineHandler>activateSubCommand: 0x5054b58 s BlockClosure>on:do: 0x50540b8 s BasicCommandLineHandler>activateSubCommand: 0x5054190 s BasicCommandLineHandler>handleSubcommand 0x5054878 s BasicCommandLineHandler>handleArgument: 0x5054248 s [] in BasicCommandLineHandler>activate 0x5054930 s BlockClosure>on:do: 0x5054340 s BasicCommandLineHandler>activate 0x50549e8 s [] in BasicCommandLineHandler class>startUp: 0x5054c10 s BlockClosure>cull: 0x5054cc8 s WorkingSession>executeDeferredStartupActions: 0x5054418 s WorkingSession>runStartup: 0x5054aa0 s WorkingSession>start: 0x5050c10 s SessionManager>snapshot:andQuit: 0x5051118 s [] in SmalltalkImage>snapshot:andQuit: 0x5051340 s CurrentExecutionEnvironment class>activate:for: 0x5051598 s DefaultExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: 0x50517c0 s DefaultExecutionEnvironment class>beActiveDuring: 0x5051650 s SmalltalkImage>snapshot:andQuit: 0x5051878 s ImageCleanerCommandLineHandler>activate 0x5051930 s ImageCleanerCommandLineHandler class(CommandLineHandler class)>activateWith: 0x50519e8 s [] in PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: 0x50505b0 s BlockClosure>on:do: 0x5050690 s PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: 0x50500d0 s PharoCommandLineHandler(BasicCommandLineHandler)>handleSubcommand 0x5050cc8 s PharoCommandLineHandler(BasicCommandLineHandler)>handleArgument: 0x5050188 s [] in PharoCommandLineHandler(BasicCommandLineHandler)>activate 0x5050260 s BlockClosure>on:do: 0x5050338 s PharoCommandLineHandler(BasicCommandLineHandler)>activate 0x5050d80 s PharoCommandLineHandler>activate 0x50511d0 s PharoCommandLineHandler class(CommandLineHandler class)>activateWith: 0x5051428 s [] in PharoCommandLineHandler class>activateWith: 0x5051708 s NonInteractiveUIManager(UIManager)>defer: 0x504dc88 s PharoCommandLineHandler class>activateWith: 0x5050e38 s [] in BasicCommandLineHandler>activateSubCommand: 0x50503f0 s BlockClosure>on:do: 0x504ddb8 s BasicCommandLineHandler>activateSubCommand: 0x504de90 s BasicCommandLineHandler>handleSubcommand 0x5050ef0 s BasicCommandLineHandler>handleArgument: 0x504df58 s [] in BasicCommandLineHandler>activate 0x50504a8 s BlockClosure>on:do: 0x504e050 s BasicCommandLineHandler>activate 0x5050fa8 s [] in BasicCommandLineHandler class>startUp: 0x5051288 s BlockClosure>cull: 0x50514e0 s WorkingSession>executeDeferredStartupActions: 0x504e128 s WorkingSession>runStartup: 0x5051060 s WorkingSession>start: 0x504cf60 s SessionManager>snapshot:andQuit: 0x504d018 s [] in SmalltalkImage>snapshot:andQuit: 0x504d0d0 s CurrentExecutionEnvironment class>activate:for: 0x504d1b8 s DefaultExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: 0x504d328 s DefaultExecutionEnvironment class>beActiveDuring: 0x504d270 s SmalltalkImage>snapshot:andQuit: 0x504be10 s LoadUpdatesCommandLineHandler>activate 0x504bec8 s LoadUpdatesCommandLineHandler class(CommandLineHandler class)>activateWith: 0x504c190 s [] in PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: 0x504c368 s BlockClosure>on:do: 0x504c448 s PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: 0x504c528 s PharoCommandLineHandler(BasicCommandLineHandler)>handleSubcommand 0x504c5e0 s PharoCommandLineHandler(BasicCommandLineHandler)>handleArgument: 0x504c6b8 s [] in PharoCommandLineHandler(BasicCommandLineHandler)>activate 0x504c7c8 s BlockClosure>on:do: 0x504c8a0 s PharoCommandLineHandler(BasicCommandLineHandler)>activate 0x504c978 s PharoCommandLineHandler>activate 0x504ca30 s PharoCommandLineHandler class(CommandLineHandler class)>activateWith: 0x504cae8 s [] in PharoCommandLineHandler class>activateWith: 0x504cba0 s NonInteractiveUIManager(UIManager)>defer: 0x504aef0 s PharoCommandLineHandler class>activateWith: 0x504b728 s [] in BasicCommandLineHandler>activateSubCommand: 0x504bac0 s BlockClosure>on:do: 0x504b020 s BasicCommandLineHandler>activateSubCommand: 0x504b0f8 s BasicCommandLineHandler>handleSubcommand 0x504b7e0 s BasicCommandLineHandler>handleArgument: 0x504b1b0 s [] in BasicCommandLineHandler>activate 0x504b898 s BlockClosure>on:do: 0x504b2a8 s BasicCommandLineHandler>activate 0x504b950 s [] in BasicCommandLineHandler class>startUp: 0x504bb78 s BlockClosure>cull: 0x504bc30 s WorkingSession>executeDeferredStartupActions: 0x504b380 s WorkingSession>runStartup: 0x504ba08 s WorkingSession>start: 0x5047b78 s SessionManager>snapshot:andQuit: 0x5048080 s [] in SmalltalkImage>snapshot:andQuit: 0x50482a8 s CurrentExecutionEnvironment class>activate:for: 0x5048500 s DefaultExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: 0x5048728 s DefaultExecutionEnvironment class>beActiveDuring: 0x50485b8 s SmalltalkImage>snapshot:andQuit: 0x50487e0 s ImageCleanerCommandLineHandler>activate 0x5048898 s ImageCleanerCommandLineHandler class(CommandLineHandler class)>activateWith: 0x5048950 s [] in PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: 0x50473f8 s BlockClosure>on:do: 0x50474d8 s PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: 0x5046f18 s PharoCommandLineHandler(BasicCommandLineHandler)>handleSubcommand 0x5047c30 s PharoCommandLineHandler(BasicCommandLineHandler)>handleArgument: 0x5046fd0 s [] in PharoCommandLineHandler(BasicCommandLineHandler)>activate 0x50470a8 s BlockClosure>on:do: 0x5047180 s PharoCommandLineHandler(BasicCommandLineHandler)>activate 0x5047ce8 s PharoCommandLineHandler>activate 0x5048138 s PharoCommandLineHandler class(CommandLineHandler class)>activateWith: 0x5048390 s [] in PharoCommandLineHandler class>activateWith: 0x5048670 s NonInteractiveUIManager(UIManager)>defer: 0x5044ab0 s PharoCommandLineHandler class>activateWith: 0x5047da0 s [] in BasicCommandLineHandler>activateSubCommand: 0x5047238 s BlockClosure>on:do: 0x5044be0 s BasicCommandLineHandler>activateSubCommand: 0x5044cb8 s BasicCommandLineHandler>handleSubcommand 0x5047e58 s BasicCommandLineHandler>handleArgument: 0x5044d80 s [] in BasicCommandLineHandler>activate 0x50472f0 s BlockClosure>on:do: 0x5044e78 s BasicCommandLineHandler>activate 0x5047f10 s [] in BasicCommandLineHandler class>startUp: 0x50481f0 s BlockClosure>cull: 0x5048448 s WorkingSession>executeDeferredStartupActions: 0x5044f50 s WorkingSession>runStartup: 0x5047fc8 s WorkingSession>start: 0x5043d88 s SessionManager>snapshot:andQuit: 0x5043e40 s [] in SmalltalkImage>snapshot:andQuit: 0x5043ef8 s CurrentExecutionEnvironment class>activate:for: 0x5043fe0 s DefaultExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: 0x5044150 s DefaultExecutionEnvironment class>beActiveDuring: 0x5044098 s SmalltalkImage>snapshot:andQuit: 0x5042f40 s LoadUpdatesCommandLineHandler>activate 0x5042ff8 s LoadUpdatesCommandLineHandler class(CommandLineHandler class)>activateWith: 0x50432c0 s [] in PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: 0x5043498 s BlockClosure>on:do: 0x5043578 s PharoCommandLineHandler(BasicCommandLineHandler)>activateSubCommand: 0x5043658 s PharoCommandLineHandler(BasicCommandLineHandler)>handleSubcommand 0x5043710 s PharoCommandLineHandler(BasicCommandLineHandler)>handleArgument: 0x50437e8 s [] in PharoCommandLineHandler(BasicCommandLineHandler)>activate 0x50438f8 s BlockClosure>on:do: 0x50439d0 s PharoCommandLineHandler(BasicCommandLineHandler)>activate 0x5043aa8 s PharoCommandLineHandler>activate 0x5043b60 s PharoCommandLineHandler class(CommandLineHandler class)>activateWith: 0x5043c18 s [] in PharoCommandLineHandler class>activateWith: 0x5043cd0 s NonInteractiveUIManager(UIManager)>defer: 0x5042020 s PharoCommandLineHandler class>activateWith: 0x5042858 s [] in BasicCommandLineHandler>activateSubCommand: 0x5042bf0 s BlockClosure>on:do: 0x5042150 s BasicCommandLineHandler>activateSubCommand: 0x5042228 s BasicCommandLineHandler>handleSubcommand 0x5042910 s BasicCommandLineHandler>handleArgument: 0x50422e0 s [] in BasicCommandLineHandler>activate 0x50429c8 s BlockClosure>on:do: 0x50423d8 s BasicCommandLineHandler>activate 0x5042a80 s [] in BasicCommandLineHandler class>startUp: 0x5042ca8 s BlockClosure>cull: 0x5042d60 s WorkingSession>executeDeferredStartupActions: 0x50424b0 s WorkingSession>runStartup: 0x5042b38 s WorkingSession>start: 0x502f970 s SessionManager>snapshot:andQuit: 0x503d010 s [] in SmalltalkImage>snapshot:andQuit: 0x503d4d0 s CurrentExecutionEnvironment class>activate:for: 0x503d688 s DefaultExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: 0x503d7f8 s DefaultExecutionEnvironment class>beActiveDuring: 0x503d740 s SmalltalkImage>snapshot:andQuit: 0x503d8b0 s [] in WorldState class>saveAndQuit 0x503d968 s BlockClosure>ensure: 0x503da40 s CursorWithMask(Cursor)>showWhile: 0x503db20 s WorldState class>saveAndQuit 0x503dbd8 s [] in ToggleMenuItemMorph(MenuItemMorph)>invokeWithEvent: 0x503dc90 s BlockClosure>ensure: 0x503ddc0 s CursorWithMask(Cursor)>showWhile: 0x503dea0 s ToggleMenuItemMorph(MenuItemMorph)>invokeWithEvent: 0x503df58 s ToggleMenuItemMorph(MenuItemMorph)>mouseUp: 0x503e010 s ToggleMenuItemMorph(MenuItemMorph)>handleMouseUp: 0x503e0c8 s MouseButtonEvent>sentTo: 0x503e180 s ToggleMenuItemMorph(Morph)>handleEvent: 0x503e238 s MorphicEventDispatcher>dispatchDefault:with: 0x503e2f0 s MorphicEventDispatcher>handleMouseUp: 0x503e3a8 s MouseButtonEvent>sentTo: 0x503e460 s [] in MorphicEventDispatcher>dispatchEvent:with: 0x503e518 s BlockClosure>ensure: 0x503e5f8 s MorphicEventDispatcher>dispatchEvent:with: 0x503e6d0 s ToggleMenuItemMorph(Morph)>processEvent:using: 0x503e788 s MorphicEventDispatcher>dispatchDefault:with: 0x503e840 s MorphicEventDispatcher>handleMouseUp: 0x503e948 s MouseButtonEvent>sentTo: 0x503ea00 s [] in MorphicEventDispatcher>dispatchEvent:with: 0x503eab8 s BlockClosure>ensure: 0x503eb98 s MorphicEventDispatcher>dispatchEvent:with: 0x503ec70 s MenuMorph(Morph)>processEvent:using: 0x503ed28 s MenuMorph(Morph)>processEvent: 0x503ede0 s MenuMorph>handleFocusEvent: 0x503ee98 s [] in HandMorph>sendFocusEvent:to:clear: 0x503ef50 s BlockClosure>on:do: 0x503f050 s WorldMorph(PasteUpMorph)>becomeActiveDuring: 0x503f140 s HandMorph>sendFocusEvent:to:clear: 0x503f240 s HandMorph>sendEvent:focus:clear: 0x503f330 s HandMorph>sendMouseEvent: 0x503f3e8 s HandMorph>handleEvent: 0x503f4a0 s HandMorph>processEventsFromQueue: 0x503f558 s HandMorph>processEvents 0x503f610 s [] in WorldState>doOneCycleNowFor: 0x503f6c8 s Array(SequenceableCollection)>do: 0x503f7a0 s WorldState>handsDo: 0x503f858 s WorldState>doOneCycleNowFor: 0x503f910 s WorldState>doOneCycleFor: 0x503f9c8 s WorldMorph>doOneCycle 0x503fa80 s WorldMorph class>doOneCycle 0x4d9acd8 s [] in MorphicUIManager>spawnNewProcess 0x4d9aa58 s [] in BlockClosure>newProcess Most recent primitives **StackOverflow** **StackOverflow** replaceFrom:to:with:startingAt: **StackOverflow** **StackOverflow** stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: **StackOverflow** **StackOverflow** **StackOverflow** **StackOverflow** stringHash:initialHash: **StackOverflow** stringHash:initialHash: **StackOverflow** stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: replaceFrom:to:with:startingAt: 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: **StackOverflow** **StackOverflow** **StackOverflow** **StackOverflow** **StackOverflow** **StackOverflow** **StackOverflow** replaceFrom:to:with:startingAt: **StackOverflow** **StackOverflow** replaceFrom:to:with:startingAt: **StackOverflow** **StackOverflow** **StackOverflow** **StackOverflow** **StackOverflow** **StackOverflow** stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: **StackOverflow** **StackOverflow** **StackOverflow** **StackOverflow** stringHash:initialHash: **StackOverflow** stringHash:initialHash: **StackOverflow** stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: replaceFrom:to:with:startingAt: 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: **StackOverflow** **StackOverflow** **StackOverflow** **StackOverflow** **StackOverflow** **StackOverflow** **StackOverflow** replaceFrom:to:with:startingAt: **StackOverflow** **StackOverflow** **StackOverflow** **StackOverflow** **StackOverflow** **StackOverflow** **StackOverflow** **StackOverflow** **StackOverflow** replaceFrom:to:with:startingAt: **StackOverflow** **StackOverflow** **StackOverflow** **StackOverflow** **StackOverflow** **StackOverflow** **StackOverflow** **IncrementalGC** wait wait signal wait signal wait signal wait signal wait signal wait signal wait signal wait signal signal primitiveFetchMourner **PrimitiveFailure** wait primUTCMicrosecondsClock digitMultiply:neg: primOffset digitCompare: // \\ quo: quo: - with:with:with: with:with:with: with:with:with: with:with:with: class basicNew first second second third third julianDayNumberUTC secondsSinceMidnightUTC < at: at: bitShift: class bitAnd: bitAnd: bitAnd: bitAnd: basicNew basicNew schedulerBeingWaitedOn primUTCMicrosecondsClock millisecondDelayDuration millisecondDelayDuration primSignal:atUTCMicroseconds: wait value **PrimitiveFailure** **PrimitiveFailure** **PrimitiveRetry** value: **PrimitiveFailure** **PrimitiveFailure** **PrimitiveRetry** stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: **StackOverflow** **StackOverflow** **StackOverflow** **StackOverflow** stringHash:initialHash: **StackOverflow** stringHash:initialHash: **StackOverflow** stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: replaceFrom:to:with:startingAt: 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: **StackOverflow** **StackOverflow** **StackOverflow** **StackOverflow** **StackOverflow** **StackOverflow** **StackOverflow** class replaceFrom:to:with:startingAt: **StackOverflow** **StackOverflow** **StackOverflow** **StackOverflow** **StackOverflow** **StackOverflow** **StackOverflow** **StackOverflow** **StackOverflow** replaceFrom:to:with:startingAt: **StackOverflow** **StackOverflow** **StackOverflow** **StackOverflow** **StackOverflow** **StackOverflow** **StackOverflow** stack page bytes 8192 available headroom 5576 minimum unused headroom 4976 (Segmentation fault) -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

Dec. 20, 2017

Re: [Pharo-dev] Failing tests in #development

by Christophe Demarey

> Le 19 dÃ©c. 2017 Ã 10:50, Esteban Lorenzano <estebanlm(a)gmail.com> a Ã©crit : > > but this is because we still need to stabilise the CI: what happens now is that we know some tests are failing randomly then we do not trust the CI to tell us everything is ok. > Then we accept PRs in red state. > Of course, this will fail eventually, and thatâs what we are seeing. > > Most important thing, IMO is to fix the CI: those tests that fails randomly (I think most of them are networking problems) needs to be fixed or removed. I think we should not rely on external services for our tests. We should mock every network service call to have a local version (still using the network). Then, you will not have failing tests because of timeout or network problem. With Zinc or Teapot itâs quite easy to set up a network service on a local port of the machine running tests.

Dec. 20, 2017

Re: [Pharo-dev] Failing tests in #development

by Stephane Ducasse

ahhhhhhhhhhh ok so this is then really nothing. Just blurs any further tests. So in case case we should do two PR on without iceberg and one for iceberg + change the test after... Seems to me a bit over kill. On Tue, Dec 19, 2017 at 6:37 PM, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: > > On mar. 19 dÃ©c. 2017 at 18:27, Stephane Ducasse <stepharo.self(a)gmail.com> > wrote: >> >> Yes sorry I did not think that it could crash. >> I do not really understand why the tooltip can break only for one tool. > > > Hi, > > With the tooltips I added a test to ensure all tools have an explanation. > Currently there is one missing for Iceberg since it will be in its next > release. > >> > -- > Cyril Ferlicot > https://ferlicot.fr > > http://www.synectique.eu > 2 rue Jacques PrÃ©vert 01, > 59650 Villeneuve d'ascq France

Dec. 19, 2017

Re: [Pharo-dev] Does pharo build not retry anymore?

by Stephane Ducasse

agreed :) On Mon, Dec 18, 2017 at 11:43 AM, Guillermo Polito < guillermopolito(a)gmail.com> wrote: > Hi, just to not mistake my intentions :) > > I don't care WHO removed the retry or WHO fixed it. I care about the WHY. > > If the WHY is not clear nor documented, we risk to make the mistake again. > Please, let all of us be strict on the issue reports we do, and even > stricter on ourselves. We need to raise the quality bar, not move it down! > > And regarding this particular issue, I'd like to raise a warning. Let's > not fix symptoms, fix causes. If we fix the symptom, the problem is still > there. And moreover, if we fix the symptom and we lose track of it, we may > forget unless somebody realizes weeks afterwards and it is too late (not > this case fortunately). > > On Sat, Dec 16, 2017 at 9:47 PM, Stephane Ducasse <stepharo.self(a)gmail.com > > wrote: > >> tx them too. >> This is great to be surrounded by all you guys! >> >> >> On Sat, Dec 16, 2017 at 8:22 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com >> > wrote: >> >>> The UI Manager problem was fixed by Pablo and Guille >>> >>> -- Pavel >>> >>> 2017-12-16 13:06 GMT+01:00 Stephane Ducasse <stepharo.self(a)gmail.com>: >>> >>>> tx pavel >>>> >>>> On Sat, Dec 16, 2017 at 9:25 AM, Pavel Krivanek < >>>> pavel.krivanek(a)gmail.com> wrote: >>>> >>>>> The problems were related UIManager initialization and consequences >>>>> of the opening of the Welcome window. >>>>> >>>>> -- Pavel >>>>> >>>>> 2017-12-16 9:12 GMT+01:00 Stephane Ducasse <stepharo.self(a)gmail.com>: >>>>> >>>>>> Pavel what was the problem? >>>>>> >>>>>> Stef >>>>>> >>>>>> >>>>>> On Tue, Dec 12, 2017 at 9:34 PM, Pavel Krivanek < >>>>>> pavel.krivanek(a)gmail.com> wrote: >>>>>> >>>>>>> The variable value was reverted to the original value. Thanks. >>>>>>> >>>>>>> -- Pavel >>>>>>> >>>>>>> 2017-12-12 20:13 GMT+01:00 Pavel Krivanek <pavel.krivanek(a)gmail.com> >>>>>>> : >>>>>>> >>>>>>>> Yes, with Marcus we decreased the retryTimes variable two weeks >>>>>>>> ago to 1 because in that time the validations were in really bad shape and >>>>>>>> literally every validation failed on some random issue and the retries >>>>>>>> caused enormous build times. It was producing more troubles than profit. It >>>>>>>> probably can be reverted now because the main problem of the validation >>>>>>>> instability was suppressed. I will prepare a PR. >>>>>>>> >>>>>>>> -- Pavel >>>>>>>> >>>>>>>> 2017-12-12 18:52 GMT+01:00 Guillermo Polito < >>>>>>>> guillermopolito(a)gmail.com>: >>>>>>>> >>>>>>>>> I see that we are retrying tests only once, which is causing most >>>>>>>>> (if not all) pull requests to fail sporadically... >>>>>>>>> >>>>>>>>> Maybe it got lost because of a mistake? >>>>>>>>> >>>>>>>>> Also, I'd like that changes in the build process are discussed in >>>>>>>>> the mailing list from time to time... I've put a lot of effort into making >>>>>>>>> it work and if we have regressions I'd like to understand them... >>>>>>>>> >>>>>>>>> Guille >>>>>>>>> >>>>>>>>> -- >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Guille Polito >>>>>>>>> >>>>>>>>> Research Engineer >>>>>>>>> >>>>>>>>> Centre de Recherche en Informatique, Signal et Automatique de Lille >>>>>>>>> >>>>>>>>> CRIStAL - UMR 9189 >>>>>>>>> >>>>>>>>> French National Center for Scientific Research - *http://www.cnrs.fr >>>>>>>>> <http://www.cnrs.fr>* >>>>>>>>> >>>>>>>>> >>>>>>>>> *Web:* *http://guillep.github.io* <http://guillep.github.io> >>>>>>>>> >>>>>>>>> *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> > > > -- > > > > Guille Polito > > Research Engineer > > Centre de Recherche en Informatique, Signal et Automatique de Lille > > CRIStAL - UMR 9189 > > French National Center for Scientific Research - *http://www.cnrs.fr > <http://www.cnrs.fr>* > > > *Web:* *http://guillep.github.io* <http://guillep.github.io> > > *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013> >

Dec. 19, 2017

Re: [Pharo-dev] Failing tests in #development

by Cyril Ferlicot

On mar. 19 dÃ©c. 2017 at 18:27, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Yes sorry I did not think that it could crash. > I do not really understand why the tooltip can break only for one tool. > Hi, With the tooltips I added a test to ensure all tools have an explanation. Currently there is one missing for Iceberg since it will be in its next release. > -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

Dec. 19, 2017

Re: [Pharo-dev] Dictionary newFromKeys: andValues:

by Stephane Ducasse

Thanks I will rework my PR because I lost some code and also did not see that SmallDictionary is not a HashedCollection On Mon, Dec 18, 2017 at 11:38 AM, Guillermo Polito < guillermopolito(a)gmail.com> wrote: > Yes I think this is good. > > On Fri, Dec 15, 2017 at 8:32 PM, Stephane Ducasse <stepharo.self(a)gmail.com > > wrote: > >> Hi >> >> I was looking at the Dictionary instance creation API and I would like to >> add >> newFromKeys:andValues: >> Because I do not see why I have to create associations when I have >> already the two collections. >> What do you think? >> >> Stef >> >> > > > -- > > > > Guille Polito > > Research Engineer > > Centre de Recherche en Informatique, Signal et Automatique de Lille > > CRIStAL - UMR 9189 > > French National Center for Scientific Research - *http://www.cnrs.fr > <http://www.cnrs.fr>* > > > *Web:* *http://guillep.github.io* <http://guillep.github.io> > > *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013> >

Dec. 19, 2017

Re: [Pharo-dev] Failing tests in #development

by Stephane Ducasse

Yes sorry I did not think that it could crash. I do not really understand why the tooltip can break only for one tool. On Mon, Dec 18, 2017 at 9:12 AM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > it was a bad idea to integrate PR 606 [1] about the world menu tooltips > before it was green. Now we have failing tests in the development branch and > validations of new pull requests will fail immediately. > > Btw. I do not think this test should be in the ReleaseTest because these > tests should be valid for the minimal image too. > > [1] https://github.com/pharo-project/pharo/pull/606 > > -- Pavel >

Dec. 19, 2017

[Pharo 7.0-dev] Build #392: 20880-failing-test-testIfCompletelyBroken

by ci-pharo-ci-jenkins2＠inria.fr

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

Dec. 19, 2017

[Pharo 7.0-dev] Build #391: 20880-failing-test-testIfCompletelyBroken

by ci-pharo-ci-jenkins2＠inria.fr

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

Dec. 19, 2017

[Pharo 7.0-dev] Build #390: 20876-Drag-and-drop-of-methods-is-broken

by ci-pharo-ci-jenkins2＠inria.fr

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

Dec. 19, 2017