February 2018 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Problem to save packages

by Nicolas Cellier

2018-02-18 22:01 GMT+01:00 Stephan Eggermont <stephan(a)stack.nl>: > Nicolas Cellier > <nicolas.cellier.aka.nice(a)gmail.com> wrote: > > But whatever the bug, why saving in the package-cache? > > The package-cache is just a cache as the name tells. > > It's less volatile than RAM, but can still be subject to aggressive > cleanup. > > Because it is much more reliable than network, and it depends on simpler > and working infrastructure. The package cache is deliberately not cleaned, > and not shared by default. > > Stephan > > > If it would be me, I would then go for my own MCDirectoryRepository. These are my files, I want to be in control and manage them by myself. Eventually save them on another medium, and not mix them with thousands of other files that generally populate a package-cache. Do you see what I mean?

Feb. 18, 2018

Re: [Pharo-dev] Problem to save packages

by Stephan Eggermont

Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: > But whatever the bug, why saving in the package-cache? > The package-cache is just a cache as the name tells. > It's less volatile than RAM, but can still be subject to aggressive cleanup. Because it is much more reliable than network, and it depends on simpler and working infrastructure. The package cache is deliberately not cleaned, and not shared by default. Stephan

Feb. 18, 2018

Re: [Pharo-dev] Problem to save packages

by Nicolas Cellier

But whatever the bug, why saving in the package-cache? The package-cache is just a cache as the name tells. It's less volatile than RAM, but can still be subject to aggressive cleanup. Le 18 fÃ©vr. 2018 18:15, "Stephane Ducasse" <stepharo.self(a)gmail.com> a Ã©crit : > Hi vincent > > Welcome to Pharo. > - Did you check that you can write in your cache folder? > - Is there any files in your cache? > - Normally just selecting a package and pressing save should save it. > - The exception you report is super strange. > > Stef > > On Sun, Feb 18, 2018 at 4:39 PM, Roca Vincent <vincentroca9(a)gmail.com> > wrote: > > Hi, > > I'm a new Pharo user (Pharo 5.0). I have created a package and now I just > > want to save it in the package-cache folder. But, when I try to do this > > using the Monticello Browser, I get an exception telling me the file I'm > > trying to save does not exist. I already managed to save some packages > but I > > can't anymore. Thanks in advance for your help. > >

Feb. 18, 2018

[Pharo 7.0-dev] Build #573: 21363-coreMethodsForClass-send-but-not-implemented

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

There is a new Pharo build available! The status of the build #573 was: SUCCESS. The Pull Request #913 was integrated: "21363-coreMethodsForClass-send-but-not-implemented" Pull request url: https://github.com/pharo-project/pharo/pull/913 Issue Url: https://pharo.fogbugz.com/f/cases/21363 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 18, 2018

Re: [Pharo-dev] NeoCSV nil-Handling

by Sven Van Caekenberghe

Sean, > On 13 Feb 2018, at 14:39, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > I'd like a hook to specify default values more dynamically. The use case is > that I created a glue layer between Magritte and NeoCSV so one can > meta-describe how to extract CSV fields into objects. > > For example: > ``` > descriptionDate > <magritteDescription> > > ^ MADateDescription new > accessor: #date; > priority: 400; > propertyAt: #csvFieldName put: 'Date'; > propertyAt: #csvReader put: [ :s | (s, '/2017') asDate ]; > default: Date today; > yourself > ``` > > The problem is that there doesn't seem to be a way to plug #default: above > into NeoCSV because other hooks like #addField:converter: seem to be skipped > for nil values, shortcutting to a statically described per-csv-file > emptyFieldValue. The initial idea of the empty value (defaulting to nil) and the short circuiting of further conversion, is precisely to help in the writing of the converter blocks, so that [ :s | s asDate ] will never receive nil or an empty string and consequently does not have to test on it. I suppose I could imagine an option like #passEmptyFieldsToConverters, which would allow (and force you) to write converter blocks like [ :s | s isEmptyOrNil ifTrue: [ Date doomsDay ] ifFalse: [ s asDate ] ] so that you can specify your own custom empty value per field. What do you think ? Sven

Feb. 18, 2018

Re: [Pharo-dev] Problem to save packages

by Stephane Ducasse

Hi vincent Welcome to Pharo. - Did you check that you can write in your cache folder? - Is there any files in your cache? - Normally just selecting a package and pressing save should save it. - The exception you report is super strange. Stef On Sun, Feb 18, 2018 at 4:39 PM, Roca Vincent <vincentroca9(a)gmail.com> wrote: > Hi, > I'm a new Pharo user (Pharo 5.0). I have created a package and now I just > want to save it in the package-cache folder. But, when I try to do this > using the Monticello Browser, I get an exception telling me the file I'm > trying to save does not exist. I already managed to save some packages but I > can't anymore. Thanks in advance for your help.

Feb. 18, 2018

Problem to save packages

by Roca Vincent

Hi, I'm a new Pharo user (Pharo 5.0). I have created a package and now I just want to save it in the package-cache folder. But, when I try to do this using the Monticello Browser, I get an exception telling me the file I'm trying to save does not exist. I already managed to save some packages but I can't anymore. Thanks in advance for your help.

Feb. 18, 2018

[Pharo 7.0-dev] Build #572: 17913-LegacyWeakSubscription-should-be-merged-with-WeakAnnouncementSubscription

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

There is a new Pharo build available! The status of the build #572 was: SUCCESS. The Pull Request #879 was integrated: "17913-LegacyWeakSubscription-should-be-merged-with-WeakAnnouncementSubscription" Pull request url: https://github.com/pharo-project/pharo/pull/879 Issue Url: https://pharo.fogbugz.com/f/cases/17913 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 18, 2018

[Pharo 7.0-dev] Build #571: 21366-Add-a-good-printOn-method-to-SHRange

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

There is a new Pharo build available! The status of the build #571 was: SUCCESS. The Pull Request #910 was integrated: "21366-Add-a-good-printOn-method-to-SHRange" Pull request url: https://github.com/pharo-project/pharo/pull/910 Issue Url: https://pharo.fogbugz.com/f/cases/21366 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 17, 2018

Re: [Pharo-dev] we should include ReferenceFinder as part of Pharo

by Stephane Ducasse

I would add it. And I would also add the tools of Yuriy on matching expressions with RBParseTree. We can manage them with their own baseline. The fact that we do not have to update versions is a game changer. On Sat, Feb 17, 2018 at 2:53 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Hi, > > Recently I was hunting a leak and I found that what we have now (pointers explorer) is not very good, so I dug into ReferenceFinder (in catalog) and everything became a lot easier. > So, I wonder: Shouldnât we include it as part of the standard distribution? > > (also, taking into account we want to remove EyeInspector and related tools and pointer explored is based on it?) > > cheers, > Esteban

Feb. 17, 2018