- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] ***important*** cannot remove a class anymore...

by stepharo

How can I see the changes? Our process is not good. Most of us do not get any chance understanding what is changing. > Hi, > > This is a side effect of > > https://pharo.fogbugz.com/f/cases/16475/Nautilus-sends-too-many-announcemen… > > (which was reviewed by two people, so not obvious). > > What happened is that #updatePackageGroupAndClassList calls itself via > #selectedClass: leading to a loop. > > Should be easy to fix for the people involved in case 16475. > > Marcus > > > On Sat, Sep 5, 2015 at 8:51 AM, stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>> wrote: > > Hi > > I do not know if this is linked to recent changes but we cannot > remove classes or move them to another package. > > Stef > > > > > -- > -- > Marcus Denker -- denker(a)acm.org <mailto:denker@acm.org> > http://www.marcusdenker.de

Sept. 5, 2015

Re: [Pharo-dev] ***important*** cannot remove a class anymore...

by Marcus Denker

> On 05 Sep 2015, at 09:29, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hi, > > This is a side effect of > > https://pharo.fogbugz.com/f/cases/16475/Nautilus-sends-too-many-announcemen… <https://pharo.fogbugz.com/f/cases/16475/Nautilus-sends-too-many-announcemen…> > > (which was reviewed by two people, so not obvious). > > What happened is that #updatePackageGroupAndClassList calls itself via #selectedClass: leading to a loop. > > Should be easy to fix for the people involved in case 16475. I added an issue tracker entry: https://pharo.fogbugz.com/f/cases/16484/Endless-loop-on-refresh-after-delet… <https://pharo.fogbugz.com/f/cases/16484/Endless-loop-on-refresh-after-delet…> Marcus

Sept. 5, 2015

Re: [Pharo-dev] ***important*** cannot remove a class anymore...

by Marcus Denker

Hi, This is a side effect of https://pharo.fogbugz.com/f/cases/16475/Nautilus-sends-too-many-announcemen… (which was reviewed by two people, so not obvious). What happened is that #updatePackageGroupAndClassList calls itself via #selectedClass: leading to a loop. Should be easy to fix for the people involved in case 16475. Marcus On Sat, Sep 5, 2015 at 8:51 AM, stepharo <stepharo(a)free.fr> wrote: > Hi > > I do not know if this is linked to recent changes but we cannot remove > classes or move them to another package. > > Stef > > -- -- Marcus Denker -- denker(a)acm.org http://www.marcusdenker.de

Sept. 5, 2015

Re: [Pharo-dev] Voyage Mongo and Serialization anomalies?

by Esteban Lorenzano

Hi Holger, by default, BSON should be decoding a ByteArray (if persisted as is) with data type âbinary dataâ, and you should be receiving a ByteArray as expected when reading. This is how SmalltalkHub works so I suspect there is something else going on (otherwise, there would be many, many people angry :P). Can you confirm the code is being persisted as binary data? (just check in the database). A simple workaround is to define an accessor: MyClass class>>#myByteArray <mongoDescription> ^ VOMongoToOneDescription new attributeName: âbyteArray'; accessor: (MAPluggableAccessor read: [ :anObject | anObject byteArray ] write: [ :anObject :value | anObject byteArray: value asByteArray ]); yourself cheers, Esteban > On 04 Sep 2015, at 19:51, Holger Freyther <holger(a)freyther.de> wrote: > > Hi all, > > it is the first time I notice this and I am not sure that this has been written down somewhere > and if it is known to others (and then what to do about it). > > I had an Object with a ByteArray and then tried to find this object using the ByteArray and > it wasnât found. It looks like the ByteArray will be converted to an âarrayâ. When searching > the ByteArray would not match it, an Array matches it. When using anArray to find the object > and using a âgetterâ to get the value and comparing it will not lead to equality. I understand > that Mongo doesnât have same types (Array, OrderedCollection, ByteArray) as Smalltalk but > I wonder if there can be done something to improve the situation? > > Is this known? Can we improve it? I can of course workaround it by converting it to an > array/orderedcollection before comparing it. > > holger > > > Example: > > | data repository test res | > repository := VOMongoRepository database: 'dbtest'. > data := #[1 2 3 4]. > test := ZEByteArrayVoyage new. > test byteArray: data. > repository save: test. > > res := repository selectOne: ZEByteArrayVoyage where: [:each | each byteArray = data ]. > res. "---> UndefinedObject" > > res := repository selectOne: ZEByteArrayVoyage where: [:each | each byteArray = data asArray]. > res. "---> ZEByteArrayVoyage" > > res byteArray = data. âfalse.. OrderedCollection = ByteArray" > res byteArray = data asArray. âOrderedCollection = Array" > res byteArray = data asOrderedCollection. "true"

Sept. 5, 2015

how do I get the git commit diff

by stepharo

Hi I still think that I would like in the squeak mailing-list to see the diff of every commit by mail. How can we enable that? Marcus you complain that not enough people are active but we do not engage people by showing changes. oh yes they can - by reading git commit.... oh boy if we believe that people systematically have a look at that then we are pretty naive. Now do not tell me that I can browse git commit I know it and this is not what I need. I need SYSTEMATIC awareness of a change. I NEED everybody to be able to have look before deleting a mail. It is working in Squeak. I can in my mail look at the changes. Or of course nobody cares in Pharo about changes and we can get regression. Another question: how can I get the list of links to git with the commit logs like https://github.com/pharo-project/pharo-core/commit/8a1f79b44b14f8eafaf6d91a… below? How can I get the list? so that I can browse (I'm probably one of the two few interested in fixing bugs after they got introduced). Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 8a1f79b44b14f8eafaf6d91a8bab3c28e673114c https://github.com/pharo-project/pharo-core/commit/8a1f79b44b14f8eafaf6d91a… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-09-04 (Fri, 04 Sep 2015)

Sept. 5, 2015

Re: [Pharo-dev] System announcements fixed?

by stepharo

Since when? Where is the bug entry? Where is a reproducible case? Stephan how can we take action if we do not know it? > What is the planning for getting updates again? > Nautilus and Monticello don't update anymore > in lots of cases. > > Stephan > > >

Sept. 5, 2015

***important*** cannot remove a class anymore...

by stepharo

Hi I do not know if this is linked to recent changes but we cannot remove classes or move them to another package. Stef

Sept. 5, 2015

[searchQuick] Seeking suggestions and contributors

by Jigyasa Grover

Hello All ! This summer I had tried my hand at building *searchQuick* - an offline text search utility in Pharo 4.0 which enables a user to browse and search within the text files present in the current Pharo image. The project has reached a certain milestone where it can do the basic intended tasks. I aspire to add on more features to it and enhance its functionality. It would be great if you all could have a look, suggest and contribute. Check out the GitHub repo <https://github.com/jig08/sQuick_new> and Project web page <http://jig08.github.io/sQuick_new/>. Looking forward to a great response. Kindly contact for further details and queries. Thanks and Regards Jigyasa Grover

Sept. 5, 2015

Re: [Pharo-dev] Image and bootstrap dependencies

by stepharo

Le 4/9/15 21:54, Christophe Demarey a Ã©crit : >> Are examples the only (or majority) kind of ignoredDependencies ? If >> >there is a significant number of other kinds, it might be useful to >> >split the examples out > At this time, not a lot. > It is mostly when you know that a code will not be executed. but in general we would prefer to avoid to tag them as ignored and addresse the dependencies. So ignored is just here to make sure that we can bootstrap fast and then we will have to revise the ignored. >

Sept. 5, 2015

Re: [Pharo-dev] rb highlighting is not up to the task yet

by Tudor Girba

Hi, Here is an example. Type this in a playground in a Pharo 5 image, and all statements before the parentheses become black: | a b c d | a := 42. b := a + 1. c := b + 1. d := c + 1. a . b . c . d } [image: Inline image 2] Here is how this looks in a Pharo 4: [image: Inline image 1] Cheers, Doru On Sat, Sep 5, 2015 at 12:16 AM, Nicolai Hess <nicolaihess(a)web.de> wrote: > This depends on the kind of error. For example, a missing open or closed > parenthesis will most > likely mark the whole (following) code. > > But it should still highlight the preceding code. > Can you give an example. > > > nicolai > > > 2015-09-04 23:10 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com>: > >> Hi, >> >> I think it's nice that we are going towards consolidating our tools >> around RB. >> >> However, the highlighting logic is not quite enough because if I have an >> error anywhere in the code, the whole highlighting disappears. In contrast, >> Shout manages to limit the problem only to the surrounding code. >> >> Is anyone working on this part of the highlighting? >> >> Cheers, >> Doru >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> > > -- www.tudorgirba.com "Every thing has its own flow"

Sept. 5, 2015