- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Some bugs

by Lukas Renggli

Wow, this is a very good collection. In the same vein there are similar bugs that slow down my development: 4514: Resumable assertions and expected failures do not work together http://code.google.com/p/pharo/issues/detail?id=4514 4609: Syntax highlighting broken http://code.google.com/p/pharo/issues/detail?id=4609 4611: Implementors browser broken http://code.google.com/p/pharo/issues/detail?id=4611 4615: Text selection makes colors disappear http://code.google.com/p/pharo/issues/detail?id=4615 4642: FinderUI>>compileSource: aString notifying: aController http://code.google.com/p/pharo/issues/detail?id=4642 4643: Inspector>>fieldListMenu: aMenu http://code.google.com/p/pharo/issues/detail?id=4643 2404: Monticello and Subclasses of ProtoObject http://code.google.com/p/pharo/issues/detail?id=2404 2194: MCSnapshotBrowser and Traits http://code.google.com/p/pharo/issues/detail?id=2194 Now I think the subliminal message of this thread is that the Pharo community should focus on making the existing images really stable before hacking away on Pharo 1.4 and beyond ... :-) Lukas On 23 August 2011 09:54, Andrea BrÃ¼hlmann <a.bruehlmann(a)netstyle.ch> wrote: > Hello, > > I reported some bugs on the issue tracker and hope you can help me with > them! > > > 4681: Accepting with the enter key does not work > Â Â Â Â http://code.google.com/p/pharo/issues/detail?id=4681 > > 4682: Code completion makes strange cursor placements and too many spaces > Â Â Â Â http://code.google.com/p/pharo/issues/detail?id=4682 > > 4683: Code completion breaks some search fields (errors during typing) > Â Â Â Â http://code.google.com/p/pharo/issues/detail?id=4683 > > 4684: Missing ctrl+w (methodNamesContainingIt:) > Â Â Â Â http://code.google.com/p/pharo/issues/detail?id=4684 > > 4685: Merge dialog: cannot resolve conflict with removed method > Â Â Â Â http://code.google.com/p/pharo/issues/detail?id=4685 > > 4686: Method category change creates no new version > Â Â Â Â http://code.google.com/p/pharo/issues/detail?id=4686 > > 4687: Errors during coding (MessageNotUnderstood: receiver of "morph" is > nil) > Â Â Â Â http://code.google.com/p/pharo/issues/detail?id=4687 > > 4688: Progress bar disappears on image save > Â Â Â Â http://code.google.com/p/pharo/issues/detail?id=4688 > > 4689: MessageTally bug > Â Â Â Â http://code.google.com/p/pharo/issues/detail?id=4689 > > 4690: Progress bar position > Â Â Â Â http://code.google.com/p/pharo/issues/detail?id=4690 > > 4691: Bad line breaks in code until window is resized (because of bold > text?) > Â Â Â Â http://code.google.com/p/pharo/issues/detail?id=4691 > > 4692: Drop downs should select the default entry (topmost) instead of a > middle one > Â Â Â Â http://code.google.com/p/pharo/issues/detail?id=4692 > > 4693: Line breaks in tooltips are wrong > Â Â Â Â http://code.google.com/p/pharo/issues/detail?id=4693 > > 4694: Debugger: stepping over an error can not open a new debugger until I > hit cmd+. > Â Â Â Â http://code.google.com/p/pharo/issues/detail?id=4694 > > 4695: Time asString prints nanos unrounded > Â Â Â Â http://code.google.com/p/pharo/issues/detail?id=4695 > > > -- > Andrea BrÃ¼hlmann > > -- Lukas Renggli www.lukas-renggli.ch

Aug. 23, 2011

[Pharo-project] Some bugs

by Andrea BrÃ¼hlmann

Hello, I reported some bugs on the issue tracker and hope you can help me with them! 4681: Accepting with the enter key does not work http://code.google.com/p/pharo/issues/detail?id=4681 4682: Code completion makes strange cursor placements and too many spaces http://code.google.com/p/pharo/issues/detail?id=4682 4683: Code completion breaks some search fields (errors during typing) http://code.google.com/p/pharo/issues/detail?id=4683 4684: Missing ctrl+w (methodNamesContainingIt:) http://code.google.com/p/pharo/issues/detail?id=4684 4685: Merge dialog: cannot resolve conflict with removed method http://code.google.com/p/pharo/issues/detail?id=4685 4686: Method category change creates no new version http://code.google.com/p/pharo/issues/detail?id=4686 4687: Errors during coding (MessageNotUnderstood: receiver of "morph" is nil) http://code.google.com/p/pharo/issues/detail?id=4687 4688: Progress bar disappears on image save http://code.google.com/p/pharo/issues/detail?id=4688 4689: MessageTally bug http://code.google.com/p/pharo/issues/detail?id=4689 4690: Progress bar position http://code.google.com/p/pharo/issues/detail?id=4690 4691: Bad line breaks in code until window is resized (because of bold text?) http://code.google.com/p/pharo/issues/detail?id=4691 4692: Drop downs should select the default entry (topmost) instead of a middle one http://code.google.com/p/pharo/issues/detail?id=4692 4693: Line breaks in tooltips are wrong http://code.google.com/p/pharo/issues/detail?id=4693 4694: Debugger: stepping over an error can not open a new debugger until I hit cmd+. http://code.google.com/p/pharo/issues/detail?id=4694 4695: Time asString prints nanos unrounded http://code.google.com/p/pharo/issues/detail?id=4695 -- Andrea BrÃ¼hlmann

Aug. 23, 2011

Re: [Pharo-project] About squeaksource

by Frank Shearar

On 22 August 2011 22:54, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: > 2011/8/22 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >>>> Nicolas >>>> >>>> From I understood this is a fix to fix another problem that conflicted with some hidden logic. >>>> Apparently Squeaksource could save anempty file and you could not upload a new version. >>>> So a fix "appeared" but it broke another aspect. >>>> >>>> Now clearly using an old image with an old vm with an old version of Seaside and thousands >>>> of files and lukas leaving for google led to the fact that indeed the process is not good. >>>> Shit happen. Now this is why we want SmalltalkHub and I hope that we will have process to upgrade. >>>> >>>> Stef >>>> >>> >>> Sure, we have the right to make mistakes. That's just the way to >>> announce it that would raise more questions than answers in the mind >>> of an annoying client like me ;) (to be polite) >>> >>> Nicolas >> >> I understand but this was reality and we should improve and structure our processes. >> Squeaksource is born before pharo and the current tools we use. So I know that we will >> be far more picky on SmalltalkHub :) >> > > Sure, having the right to make mistakes implies the obligation to > guard against mistakes. > How do you write tests for all the edge cases (like simulating network > load/failures, etc...) ? In my previous day job I wrote a SIP stack, so I had to worry about some of these things. Some kinds of failure _are_ testable: mock out the network layer, and inject fake errors. This allows you to immediately test a whole range of errors: an unreachable server, a server that disappears mid-connection, broken DNS, intermittent failures, ... By "mock" I mean one of two things: a classic objects-only layer with an API to which all network stuff talks, or a server that allows you to "supply" misbehaviour. Obviously the former is a lot faster, and allows you to create unit tests for your bottom-most, network-facing layer of your application. Michael Nygaard's "Release It!" describes a test harness on pp 125-128: a server intentionally designed to do all manner of nasty things - accept connections but not return data, return data extremely slowly, refuse connections, fail to ACK, ... Each kind of bad behaviour runs on a separate port, allowing you to just place the test harness in your QA environment and potentially have multiple services under test talk to it. frank > Nicolas > >> >> Stef >> > >

Aug. 23, 2011

Re: [Pharo-project] SmalltalkImage>>garbageCollectAndReport

by Noury Bouraqadi

Thanx. bytesLeftString is a misleading name :-( Same as for bytesLeft. We should rename them. Noury On 21 aoÃ»t 2011, at 18:16, Alexandre Bergel wrote: > The garbage collection is done in #bytesLeftString > #bytesLeftString is not really a good name in that respect. > > Alexandre > > On 21 Aug 2011, at 17:56, Noury Bouraqadi wrote: > >> Hi, >> >> Is this method should be renamed or is the GC call missing? >> >> garbageCollectAndReport >> "Do a garbage collection, and report results to the user." >> >> "SmalltalkImage current garbageCollectAndReport" >> >> self inform: self bytesLeftString >> >> >> Noury from ESUG @ Edinburgh :-) >> http://car.mines-douai.fr/noury >> -- >> -19Ã¨mes JournÃ©es Francophones sur les SystÃ¨mes Multi-Agents (JFSMAâ11) >> http://www.univ-valenciennes.fr/congres/jfsma2011/ >> 17-19 Octobre 2011, Valenciennes, France >> >> -5th International Conference on Smalltalk Technologies >> http://www.fast.org.ar >> November 3th - 5th, 2011 Universidad Nacional de Quilmes (Argentina) >> >> >> >> >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > Noury Bouraqadi http://car.mines-douai.fr/noury -- -19Ã¨mes JournÃ©es Francophones sur les SystÃ¨mes Multi-Agents (JFSMAâ11) http://www.univ-valenciennes.fr/congres/jfsma2011/ 17-19 Octobre 2011, Valenciennes, France -5th International Conference on Smalltalk Technologies http://www.fast.org.ar November 3th - 5th, 2011 Universidad Nacional de Quilmes (Argentina)

Aug. 23, 2011

Re: [Pharo-project] while waiting for SmalltalkHub...

by StÃ©phane Ducasse

Thanks lukas. We will see if your fixes if ss gets stable again. Stef On Aug 23, 2011, at 5:53 AM, Lukas Renggli wrote: >> Pharo1.4 migrated its repository to ss3 at ss3.gemstone.com. We migrated the inbox there too, because we want to remove the stress on Squeaksource (related to the automatic build process). We put the SqueakSource/PharoInbox. > > Typically (with the original scripts) the stress of the build-server > is (designed to be) really low, because everything is cached locally. > So there is one request to check what versions are available, and one > request for each new version available. > > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch >

Aug. 23, 2011

Re: [Pharo-project] [ANN] glamorous inspector

by Tudor Girba

I think there is much to reinvent in this space. I also think this is an opportunity for Smalltalk. We need to see it as an important area, and then allocate resources and work steadily in this direction. Cheers, Doru On 22 Aug 2011, at 23:01, StÃ©phane Ducasse wrote: > > I like the flow and the no popping behavior :) > > Stef > > On Aug 22, 2011, at 7:59 PM, Tudor Girba wrote: > >> Hi, >> >> I am happy to announce the first release of the Glamorous Inspector, a new browser for inspecting objects based on Glamour. >> >> More information, including a demo and screenshots, can be found here: >> http://www.humane-assessment.com/blog/glamorous-inspector-for-smalltalk >> >> To download it follow the instructions from: >> http://www.moosetechnology.org/tools/glamoroustoolkit >> >> You can use it by: >> 1. "GTInspector openOn: someObject", or >> 2. "GTInspector registerToolsOn: Smalltalk tools" and then use CMD+I (explore) >> >> Please let your opinion be heard :) >> >> Cheers, >> Doru >> >> p.s. Have fun at ESUG :) >> >> -- >> www.tudorgirba.com >> >> "Every successful trip needs a suitable vehicle." >> >> > -- www.tudorgirba.com "From an abstract enough point of view, any two things are similar."

Aug. 23, 2011

Re: [Pharo-project] while waiting for SmalltalkHub...

by Lukas Renggli

> Pharo1.4 migrated its repository to ss3 at ss3.gemstone.com. We migrated the inbox there too, because we want to remove the stress on Squeaksource (related to the automatic build process). We put the SqueakSource/PharoInbox. Typically (with the original scripts) the stress of the build-server is (designed to be) really low, because everything is cached locally. So there is one request to check what versions are available, and one request for each new version available. Lukas -- Lukas Renggli www.lukas-renggli.ch

Aug. 23, 2011

[Pharo-project] New CogVMs available...

by Eliot Miranda

...in http://www.mirandabanda.org/files/Cog/VM/VM.r2489/. These fix bugs in the machine-code at: primitive (that it didn't return primitive fail codes and that it could answer wrong information for contexts). Enjoy. -- best, Eliot

Aug. 23, 2011

Re: [Pharo-project] About squeaksource

by Nicolas Cellier

2011/8/22 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >>> Nicolas >>> >>> From I understood this is a fix to fix another problem that conflicted with some hidden logic. >>> Apparently Squeaksource could save anempty file and you could not upload a new version. >>> So a fix "appeared" but it broke another aspect. >>> >>> Now clearly using an old image with an old vm with an old version of Seaside and thousands >>> of files and lukas leaving for google led to the fact that indeed the process is not good. >>> Shit happen. Now this is why we want SmalltalkHub and I hope that we will have process to upgrade. >>> >>> Stef >>> >> >> Sure, we have the right to make mistakes. That's just the way to >> announce it that would raise more questions than answers in the mind >> of an annoying client like me ;) (to be polite) >> >> Nicolas > > I understand but this was reality and we should improve and structure our processes. > Squeaksource is born before pharo and the current tools we use. So I know that we will > be far more picky on SmalltalkHub :) > Sure, having the right to make mistakes implies the obligation to guard against mistakes. How do you write tests for all the edge cases (like simulating network load/failures, etc...) ? Nicolas > > Stef >

Aug. 22, 2011

[Pharo-project] Moving SqueakDBX mailing list to a new DBXTalk one

by Mariano Martinez Peck

Hi guys. We are moving the mailing list of squeakdbx(a)lists.squeakfoundation.org to a new google group: http://groups.google.com/group/dbxtalk We welcome you in the new mailing list and please deprecate as soon as possible the old one. Cheers -- Mariano http://marianopeck.wordpress.com

Aug. 22, 2011