- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Catalog down

by Torsten Bergmann

Thanks! Â Gesendet:Â Dienstag, 01. August 2017 um 10:48 Uhr Von:Â "Christophe Demarey" <christophe.demarey(a)inria.fr> An:Â "Pharo Development List" <pharo-dev(a)lists.pharo.org> Betreff:Â Re: [Pharo-dev] Catalog down It is nows back on line! Â Christophe Â Le 1 aoÃ»t 2017 Ã 08:40, Torsten Bergmann <astares@gmx.de[mailto:astares@gmx.de]> a Ã©crit :Â It is still down. Am 31.07.2017, 19:55, Esteban Lorenzano <estebanlm@gmail.com[mailto:estebanlm@gmail.com]> schrieb:It will be restarted at midnight > On 31 Jul 2017, at 19:51, Torsten Bergmann <astares@gmx.de[mailto:astares@gmx.de]> wrote: > > http://catalog.pharo.org/catalog/json[http://catalog.pharo.org/catalog/json] responds with "Service Temporarily Unavailable". > Sabine already reported it this morning on Discord. > > Any idea? > > Â

Aug. 1, 2017

Re: [Pharo-dev] Creating the smallest server runtime footprint

by Pavel Krivanek

2017-07-31 22:51 GMT+02:00 Tim Mackinnon <tim(a)testit.works>: > I wasnât clear on which image to retry - the https://ci.inria.fr/pharo/ > job/Pharo-6.0-Update-Step-3.2-Minimal/lastSuccessfulBuild/ > artifact/Pharo-minimal-64.zip one still shows as being last updated 7 > days ago. > > The https://ci.inria.fr/pharo/view/6.0-SysConf/job/Pharo-6.0-Step-04-01- > ConfigurationOfMinimalPharo/ one gives me a mismatch error: This > interpreter (vers. 68021) cannot read image file (vers. 6521). > > The https://ci.inria.fr/pharo/view/7.0/job/70-Bootstrap-32bit-Conversion/ > lastSuccessfulBuild/artifact/latest-minimal-64.zip one gives me a > walkback when trying to run my install script : > > 25 UndefinedObject(Object)>>*doesNotUnderstand: #addTo:* > 26 MCRepositoryGroup>>addRepository: > 27 createRepository > | repo | > repo := self project createRepository: self. > ^ MCRepositoryGroup default repositories > detect: [ :each | each = repo ] > ifNone: [ > MCRepositoryGroup default addRepository: repo. > repo ] in MetacelloRepositorySpec>>createRepository > > I think this is because the image doesnât support Metacello? As in: > > Metacello new > repository: 'filetree://../src'; > baseline: 'Lambda'; > load. > > > How do you guys load things into the minimal images (I thought you used > Metacello - but maybe you do it some other way?) > > I can use a big 6.1 image fine (as it has Metacello loaded) but Iâd really > like a minimal solution - that can load in libraries like AWS S3, or XML > parsing etc. and it seems like I should be a good customer for kicking the > tires on all of this. > > Tim > > I checked the 64-bit Pharo 7 minimal image and loading of baseline (of SUnit from pharo-project/pharo) works: ./pharo Pharo7.0-minimal-64bit-b1625bf.image eval --save "Metacello new baseline: 'SUnit'; repository: 'filetree://./pharo-core/src'; load." ./pharo Pharo7.0-minimal-64bit-b1625bf.image eval "TestCase suite run" Can you test it too? -- Pavel

Aug. 1, 2017

Re: [Pharo-dev] Catalog down

by Christophe Demarey

It is nows back on line! Christophe > Le 1 aoÃ»t 2017 Ã 08:40, Torsten Bergmann <astares(a)gmx.de> a Ã©crit : > > It is still down. > Am 31.07.2017, 19:55, Esteban Lorenzano <estebanlm(a)gmail.com> schrieb: > It will be restarted at midnight > > > On 31 Jul 2017, at 19:51, Torsten Bergmann <astares(a)gmx.de> wrote: > > > > http://catalog.pharo.org/catalog/json <http://catalog.pharo.org/catalog/json> responds with "Service Temporarily Unavailable". > > Sabine already reported it this morning on Discord. > > > > Any idea? > > > > >

Aug. 1, 2017

Re: [Pharo-dev] Catalog down

by Torsten Bergmann

Aug. 1, 2017

Re: [Pharo-dev] Launcher and Pharo 6.1

by Sean P. DeNigris

EstebanLM wrote > it is safe. 6.1 Great. Thanks, guys. I downloaded a new vm via `curl get.pharo.org/vm61 | bash` and it seems to be working fine with 6.0 images. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Launcher-and-Pharo-6-1-tp4957770p4958036.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Aug. 1, 2017

Segmentation fault Pharo 6.1 64bit vm - Ubuntu Linux - loading Metacello dependency

by Tim Mackinnon

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

July 31, 2017

Re: [Pharo-dev] Calypso browser and categories?

by Mariano Martinez Peck

On Mon, Jul 31, 2017 at 6:15 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > Hi Mariano. > > You right. Method for this was implemented but I forgot to use it in > #selectClass: logic. > I committed fix to dev branch. I will realze new version soon. > > OK, great. Let me know when you want me to test it. I am glad it was a "bug". I thought it might have been some "decision". > But I am not sure that it is only issue you are talking about. > Yeah, I figured I can see it elsewhere. But I will find them if there are other places... BTW, I also found some other small issues which I comment below. Do you want me to open issues on github for them? * "Windows" -> "Delete all windows discarding edits" -> does not close Calypso windows with none saved edits * When I have a class opened, with a method opened, then I go to the class comment tab and I save the class comment, calypso automatically gives me focus back to the "method tab" rather than staying in the class comment. This is annoying as i like to save my class comment frequently and not they flip to another tab. * I wish the "new protocol" offers me the existing ones as I type...as I normally re-use existing protocols (on purpose) and its easy to make small typos or differences with the original ones. Thoughts? Thanks! > > 2017-07-31 18:25 GMT+02:00 Mariano Martinez Peck <marianopeck(a)gmail.com>: > >> Hi Denis, >> >> I wanted to give a serious test to Calypso, that is, start using it all >> day long. However, there is a critical thing I am missing, which is the >> grouping of categories (inside packages). >> >> I do not want to start discussing again packages vs categories and what >> are good and bad practices. I do have a few packages and each package may >> have several categories inside. So... seeing all classes together inside a >> package is not nice for me. >> >> Is there a way in calypso to auto-escope to category level? I mean... say >> my package is XXX and I have categories XXX-A and XXX-B. I know I can go to >> left side column and with the tree, I can go to XXX-A and I get what I >> want. But, for example, when I browse a class of XXX-A, the "focus" of the >> left side column is XXX and not XXX-A. So I am wondering if we can make it >> auto-scope to the category everywhere in Calypso. >> >> Thanks in advance, >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> > > -- Mariano http://marianopeck.wordpress.com

July 31, 2017

Re: [Pharo-dev] Calypso browser and categories?

by Denis Kudriashov

Hi Mariano. You right. Method for this was implemented but I forgot to use it in #selectClass: logic. I committed fix to dev branch. I will realze new version soon. But I am not sure that it is only issue you are talking about. 2017-07-31 18:25 GMT+02:00 Mariano Martinez Peck <marianopeck(a)gmail.com>: > Hi Denis, > > I wanted to give a serious test to Calypso, that is, start using it all > day long. However, there is a critical thing I am missing, which is the > grouping of categories (inside packages). > > I do not want to start discussing again packages vs categories and what > are good and bad practices. I do have a few packages and each package may > have several categories inside. So... seeing all classes together inside a > package is not nice for me. > > Is there a way in calypso to auto-escope to category level? I mean... say > my package is XXX and I have categories XXX-A and XXX-B. I know I can go to > left side column and with the tree, I can go to XXX-A and I get what I > want. But, for example, when I browse a class of XXX-A, the "focus" of the > left side column is XXX and not XXX-A. So I am wondering if we can make it > auto-scope to the category everywhere in Calypso. > > Thanks in advance, > > -- > Mariano > http://marianopeck.wordpress.com >

July 31, 2017

Re: [Pharo-dev] Catalog down

by Esteban Lorenzano

It will be restarted at midnight > On 31 Jul 2017, at 19:51, Torsten Bergmann <astares(a)gmx.de> wrote: > > http://catalog.pharo.org/catalog/json responds with "Service Temporarily Unavailable". > Sabine already reported it this morning on Discord. > > Any idea? > >

July 31, 2017

Catalog down

by Torsten Bergmann

http://catalog.pharo.org/catalog/json responds with "Service Temporarily Unavailable". Sabine already reported it this morning on Discord. Any idea?

July 31, 2017