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

Re: [Pharo-dev] evolutions of squeakelib & crypto (Reed Solomon)

by Robert Withers

ReedSolomon updates: https://www.dropbox.com/s/f5unbbdetv4c5xs/Cryptography-rww.41.mcz?dl=0 more refactoring of the pipeline: https://www.dropbox.com/s/g45himklwa66zqb/SqueakElib-rww.205.mcz?dl=0 - Robert On 12/03/2015 06:00 AM, Robert Withers wrote: > Here is an update with some refactorings and extensions. I added > 'domain' to the IWant/IAm messages to support subdomains. > > https://www.dropbox.com/s/tvpxfuixzxrj3op/SqueakElib-rww.204.mcz?dl=0 > > thanks for trying it, > Robert > > On 12/01/2015 02:23 PM, Robert Withers wrote: >> Another version fixing empty payloads... >> >> https://www.dropbox.com/s/wjhbopwabbrszjn/SqueakElib-rww.202.mcz?dl=0 >> >> thank you, >> - Robert >> >> On 12/01/2015 11:44 AM, Robert Withers wrote: >>> Here is a newer version (201) with a protocol change to remove all >>> tcpIds from the rendezvous. >>> >>> https://www.dropbox.com/s/7mgfglwu3e4bf4j/SqueakElib-rww.201.mcz?dl=0 >>> >>> - Robert >>> >>> On 12/01/2015 07:37 AM, Robert Withers wrote: >>>> This version of the Cryptography package has beginnings of >>>> ReedSolomon encoding. >>>> >>>> The rendezvous is separated into an OperationProtocol and a >>>> StartupProtocol and the message pipeline of the session layer of >>>> SqueakElib has been completely rewritten and LayeredProtocols have >>>> been folded in. Please look at ElibVatTPDataTestCase for an example. >>>> >>>> Cryptography: >>>> https://www.dropbox.com/s/z9dux2goimej79e/Cryptography-rww.40.mcz?dl=0 >>>> SqueakElib: >>>> https://www.dropbox.com/s/5yvkl3df89uyjnh/SqueakElib-rww.200.mcz?dl=0 >>>> >>>> In the spirit of #GivingTuesday, >>>> Robert >>> >> >

Dec. 3, 2015

Re: [Pharo-dev] evolutions of squeakelib & crypto (Reed Solomon)

by Robert Withers

Here is an update with some refactorings and extensions. I added 'domain' to the IWant/IAm messages to support subdomains. https://www.dropbox.com/s/tvpxfuixzxrj3op/SqueakElib-rww.204.mcz?dl=0 thanks for trying it, Robert On 12/01/2015 02:23 PM, Robert Withers wrote: > Another version fixing empty payloads... > > https://www.dropbox.com/s/wjhbopwabbrszjn/SqueakElib-rww.202.mcz?dl=0 > > thank you, > - Robert > > On 12/01/2015 11:44 AM, Robert Withers wrote: >> Here is a newer version (201) with a protocol change to remove all >> tcpIds from the rendezvous. >> >> https://www.dropbox.com/s/7mgfglwu3e4bf4j/SqueakElib-rww.201.mcz?dl=0 >> >> - Robert >> >> On 12/01/2015 07:37 AM, Robert Withers wrote: >>> This version of the Cryptography package has beginnings of >>> ReedSolomon encoding. >>> >>> The rendezvous is separated into an OperationProtocol and a >>> StartupProtocol and the message pipeline of the session layer of >>> SqueakElib has been completely rewritten and LayeredProtocols have >>> been folded in. Please look at ElibVatTPDataTestCase for an example. >>> >>> Cryptography: >>> https://www.dropbox.com/s/z9dux2goimej79e/Cryptography-rww.40.mcz?dl=0 >>> SqueakElib: >>> https://www.dropbox.com/s/5yvkl3df89uyjnh/SqueakElib-rww.200.mcz?dl=0 >>> >>> In the spirit of #GivingTuesday, >>> Robert >> >

Dec. 3, 2015

Re: [Pharo-dev] vm crash in SmalltalkImage>garbageCollect

by Max Leske

Hi, I discovered a similar issue described in this issue https://pharo.fogbugz.com/f/cases/14165/ObsoleteTest-testFixObsoleteSharedP…. Might be related. Cheers, Max > On 24 Nov 2015, at 19:34, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > > > On Mon, Nov 23, 2015 at 4:57 PM, Andrei Chis <chisvasileandrei(a)gmail.com <mailto:chisvasileandrei@gmail.com>> wrote: > Hi Eliot, > > Is an assert vm the same as a vm compiled with debugging support? > > > VMMaker.oscog generates VM sources designed to be compiled in three different ways, Debug, Assert and Production. Debug is designed to enable asserts to check invariants and be compiled with no optimization for maximum debuggability. Assert is designed to enable asserts to check invariants and be compiled with limited optimization for faster assert checking. Production has asserts disabled (actually compiled-out) and be compiled with aggressive optimization, so it has limited debuggability (it should still contain debugging symbols). > > So Assert and Debug are not quite the same and certainly if you're hunting for storage leaks an Assert VM will run much faster than a Debug VM. If you have a look at the Cog svn sources you'll find that the build scripts build all three kinds of VMs for all platforms. > > > > Also can you point me to any documentation about the leak checker. > > > It's not well documented because it may change over time, but the -help flag on the VM should include this: > > -leakcheck num check for leaks in the heap > > and the meaning of num is a set of flags: > > setCheckForLeaks: integerFlags > " 0 = do nothing. > 1 = check for leaks on fullGC (GCModeFull). > 2 = check for leaks on scavenger (GCModeNewSpace). > 4 = check for leaks on incremental (GCModeIncremental) > 8 = check for leaks on become > 16 = check for leaks on image segments" > checkForLeaks := integerFlags > > So once you have your assert VM try running your test case using > > myvm -leakcheck 5 myimage.image > > on the command line. You'll want to use a debugger to put breakpoints in the leak checker and you may need to learn about the VM's debug routines to try and figure out the cause of the leak once the leak checker finds it. > Cheers, > Andrei > > On Nov 24, 2015 1:45 AM, "Eliot Miranda" <eliot.miranda(a)gmail.com <mailto:eliot.miranda@gmail.com>> wrote: > > > > Hi Andrei, > > > > On Mon, Nov 23, 2015 at 7:59 AM, Andrei Chis <chisvasileandrei(a)gmail.com <mailto:chisvasileandrei@gmail.com>> wrote: > >> > >> Hi, > >> > >> With both the latest and stable vm I have an use case in which the vm crashed in SmalltalkImage>>garbageCollect. > >> > >> To set up an image that exhibits the failure , execute this with the latest pharo version: > >> > >> /pharo Pharo.image eval --save "{ { 'ConfigurationOfRubric'. 'Pharo'. 'Rubric' }. { 'ConfigurationOfGlamourCore'. 'Moose'. 'Glamour' }. { 'ConfigurationOfGTInspectorCore'. 'Moose'. 'GToolkit' }. { 'ConfigurationOfGTPlaygroundCore'. 'Moose'. 'GToolkit' }. { 'ConfigurationOfGTEventRecorder'. 'Moose'. 'GToolkit' }. { 'ConfigurationOfGTSpotter'. 'Moose'. 'GToolkit' }. } do: [ :spec | Gofer new smalltalkhubUser: spec second project: spec third; package: spec first; load ]." > >> > >> ./pharo Pharo.image config http://www.smalltalkhub.com/mc/Pharo/Pharo50Inbox/main <http://www.smalltalkhub.com/mc/Pharo/Pharo50Inbox/main> ConfigurationOfGToolkitCore --install=3.2 > >> > >> Then attempting to run the following code triggers the failure: > >> > >> ./pharo Pharo.image eval --save "TestRunner open model packageSearchUpdate: 'gt-tests-inspector'; classSearchUpdate: 'GTInspectorExamplesTest'; runAll" > >> > >> Based on the trace below the failure happens when the test GTInspectorExamplesTest calls 'Smalltalk>>garbageCollect' in the setUp method. > >> > >> That call can be removed, however, in other runs the failure happens in other methods calling Smalltalk>>garbageCollect. > >> > >> Is it possible that this is a bug with the image (some broken object) or is it a vm bug? > > > > > > The way to test this is to build an assert VM and then use the leak checker. The leak checker will allow you to narrow down the cause. If the leak checker shows no corruption then its definitely a GC bug. If there leak checker does show corruption before GC then one still has to find out what caused the heap corruption, but you can use the leak checker to narrow the search. > > > > HTH > > Eliot > > > >> Cheers, > >> > >> Andrei > >> > >> > >> > >> andrei$ ./pharo Pharo.image eval --save "{ { 'ConfigurationOfRubric'. 'Pharo'. 'Rubric' }. { 'ConfigurationOfGlamourCore'. 'Moose'. 'Glamour' }. { 'ConfigurationOfGTInspectorCore'. 'Moose'. 'GToolkit' }. { 'ConfigurationOfGTPlaygroundCore'. 'Moose'. 'GToolkit' }. { 'ConfigurationOfGTEventRecorder'. 'Moose'. 'GToolkit' }. { 'ConfigurationOfGTSpotter'. 'Moose'. 'GToolkit' }. } do: [ :spec | Gofer new smalltalkhubUser: spec second project: spec third; package: spec first; load ]." > >> > >> andrei$ ./pharo Pharo.image config http://www.smalltalkhub.com/mc/Pharo/Pharo50Inbox/main <http://www.smalltalkhub.com/mc/Pharo/Pharo50Inbox/main> ConfigurationOfGToolkitCore --install=3.2 > >> > >> andrei$ ./pharo Pharo.image eval --save "TestRunner open model packageSearchUpdate: 'gt-tests-inspector'; classSearchUpdate: 'GTInspectorExamplesTest'; runAll" > >> > >> > >> Segmentation fault Mon Nov 23 16:48:36 2015 > >> > >> > >> > >> https://github.com/pharo-project/pharo-vm.git <https://github.com/pharo-project/pharo-vm.git> Commit: 28d077d8df494ce050ca42c97c892471e8b8740c Date: 2015-10-16 12:02:43 +0200 By: Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> Jenkins build #15016 > >> > >> > >> C stack backtrace: > >> > >> 0 Pharo 0x0004cacf reportStackState + 159 > >> > >> > >> > >> Smalltalk stack dump: > >> > >> 0xbffbf1a0 M SmalltalkImage>garbageCollect 0x1fd49e30: a(n) SmalltalkImage > >> > >> 0xbffbf1c0 I GTInspectorExamplesTest>setUp 0x2126bc80: a(n) GTInspectorExamplesTest > >> > >> 0x2126cb90 is not a context > >> > >> > >> Most recent primitives > >> > >> @ > >> > >> basicNew > >> > >> @ > >> > >> @ > >> > >> @ > >> > >> @ > >> > >> @ > >> > >> @ > >> > >> @ > >> > >> @ > >> > >> @ > >> > >> basicNew > >> > >> basicNew > >> > >> basicNew > >> > >> @ > >> > >> @ > >> > >> @ > >> > >> @ > >> > >> shallowCopy > >> > >> new > >> > >> new: > >> > >> new: > >> > >> basicNew > >> > >> basicNew > >> > >> new: > >> > >> basicNew > >> > >> new: > >> > >> replaceFrom:to:with:startingAt: > >> > >> new: > >> > >> basicNew > >> > >> new: > >> > >> replaceFrom:to:with:startingAt: > >> > >> new: > >> > >> basicNew > >> > >> @ > >> > >> new: > >> > >> at:put: > >> > >> at:put: > >> > >> perform:with: > >> > >> perform:with: > >> > >> perform: > >> > >> @ > >> > >> @ > >> > >> basicNew > >> > >> @ > >> > >> @ > >> > >> @ > >> > >> @ > >> > >> @ > >> > >> @ > >> > >> basicNew > >> > >> @ > >> > >> new: > >> > >> at:put: > >> > >> at:put: > >> > >> perform:with: > >> > >> perform:with: > >> > >> perform: > >> > >> @ > >> > >> @ > >> > >> basicNew > >> > >> @ > >> > >> @ > >> > >> @ > >> > >> @ > >> > >> @ > >> > >> @ > >> > >> new > >> > >> @ > >> > >> @ > >> > >> @ > >> > >> @ > >> > >> @ > >> > >> basicNew > >> > >> @ > >> > >> @ > >> > >> new: > >> > >> at:put: > >> > >> @ > >> > >> @ > >> > >> basicNew > >> > >> @ > >> > >> @ > >> > >> @ > >> > >> @ > >> > >> new: > >> > >> at:put: > >> > >> at:put: > >> > >> at:put: > >> > >> at:put: > >> > >> new: > >> > >> @ > >> > >> at:put: > >> > >> @ > >> > >> at:put: > >> > >> @ > >> > >> at:put: > >> > >> @ > >> > >> at:put: > >> > >> @ > >> > >> @ > >> > >> @ > >> > >> @ > >> > >> @ > >> > >> @ > >> > >> basicNew > >> > >> @ > >> > >> @ > >> > >> basicNew > >> > >> @ > >> > >> @ > >> > >> basicNew > >> > >> @ > >> > >> @ > >> > >> @ > >> > >> @ > >> > >> @ > >> > >> shallowCopy > >> > >> shallowCopy > >> > >> @ > >> > >> @ > >> > >> new: > >> > >> at:put: > >> > >> at:put: > >> > >> at:put: > >> > >> at:put: > >> > >> new: > >> > >> @ > >> > >> at:put: > >> > >> @ > >> > >> at:put: > >> > >> @ > >> > >> at:put: > >> > >> @ > >> > >> at:put: > >> > >> @ > >> > >> @ > >> > >> @ > >> > >> @ > >> > >> @ > >> > >> @ > >> > >> basicNew > >> > >> @ > >> > >> @ > >> > >> basicNew > >> > >> @ > >> > >> @ > >> > >> basicNew > >> > >> @ > >> > >> @ > >> > >> @ > >> > >> @ > >> > >> @ > >> > >> basicNew > >> > >> @ > >> > >> @ > >> > >> @ > >> > >> @ > >> > >> basicNew > >> > >> @ > >> > >> @ > >> > >> basicNew > >> > >> @ > >> > >> @ > >> > >> basicNew > >> > >> @ > >> > >> @ > >> > >> @ > >> > >> @ > >> > >> @ > >> > >> basicNew > >> > >> @ > >> > >> @ > >> > >> @ > >> > >> @ > >> > >> basicNew > >> > >> @ > >> > >> @ > >> > >> perform: > >> > >> basicNew > >> > >> new: > >> > >> basicNew > >> > >> new: > >> > >> basicNew > >> > >> new: > >> > >> shallowCopy > >> > >> shallowCopy > >> > >> primUTCMicrosecondsClock > >> > >> // > >> > >> basicNew > >> > >> basicNew > >> > >> new: > >> > >> at:put: > >> > >> at:put: > >> > >> at:put: > >> > >> at:put: > >> > >> value > >> > >> valueNoContextSwitch > >> > >> basicNew > >> > >> new: > >> > >> basicNew > >> > >> new: > >> > >> new: > >> > >> basicNew > >> > >> new: > >> > >> replaceFrom:to:with:startingAt: > >> > >> primitiveGarbageCollect > >> > >> **IncrementalGC** > >> > >> **FullGC** > >> > >> garbageCollectMost > >> > >> **IncrementalGC** > >> > >> basicNew > >> > >> new: > >> > >> someInstance > >> > >> basicNew > >> > >> new: > >> > >> someInstance > >> > >> basicNew > >> > >> new: > >> > >> someInstance > >> > >> new: > >> > >> basicNew > >> > >> new: > >> > >> replaceFrom:to:with:startingAt: > >> > >> primitiveGarbageCollect > >> > >> **IncrementalGC** > >> > >> **FullGC** > >> > >> garbageCollectMost > >> > >> **IncrementalGC** > >> > >> wait > >> > >> shallowCopy > >> > >> shallowCopy > >> > >> signal > >> > >> wait > >> > >> shallowCopy > >> > >> shallowCopy > >> > >> at:put: > >> > >> at:put: > >> > >> at:put: > >> > >> at:put: > >> > >> at:put: > >> > >> at:put: > >> > >> signal > >> > >> wait > >> > >> shallowCopy > >> > >> shallowCopy > >> > >> at:put: > >> > >> at:put: > >> > >> signal > >> > >> new: > >> > >> basicNew > >> > >> new: > >> > >> replaceFrom:to:with:startingAt: > >> > >> primitiveGarbageCollect > >> > >> **IncrementalGC** > >> > >> **FullGC** > >> > >> > >> (Segmentation fault) > >> > >> ./pharo: line 11: 5224 Abort trap: 6 "$DIR"/"pharo-vm/Pharo.app/Contents/MacOS/Pharo" --headless "$@" > > > > > > > > > > -- > > _,,,^..^,,,_ > > best, Eliot > > > > > -- > _,,,^..^,,,_ > best, Eliot

Dec. 3, 2015

VoyageMongo and cache compaction

by Holger Freyther

Hi guys, I started to run a production load with VoyageMongo and every day the maximum latency of it goes up a bit. Today I looked at the production system and the VOMongoRepository and the VOMongoCache and saw that the cache had around 90 entries in the "objects" WeakValueDictionary all pointing to nil 34k entries in the timestamp dictionary This is a write "heavy" workload but at no point in time more than a couple of objects will be in the cache. So somehow the VOMongoCache>>#compactIfNeeded check does not trigger and/or given the difference in the sizes of the dictionary it is possible that some of the dead objects are not removed from the timestamp cache. I have accidentally restarted one image and flushed the cache on the other but if it is of any help I can wait a day or two and then look at the compactLimit again. But even right now in one image the compactLimit is 3277, the objects dictionary has 142 entries and the timestamp one 272. Is this a known issue? Does this look like "normal"/"good" operation? kind regards holger

Dec. 3, 2015

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/50482 Home: https://github.com/pharo-project/pharo-core

Dec. 3, 2015

[pharo-project/pharo-core] e5a9d5: 50482

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: e5a9d5fb62466db4fa8eeb32b048bba460adfaeb https://github.com/pharo-project/pharo-core/commit/e5a9d5fb62466db4fa8eeb32… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-12-03 (Thu, 03 Dec 2015) Changed paths: M NECompletion-Tests.package/NECContextTest.class/instance/tests/testCreateModel.st M NECompletion.package/NECContext.class/instance/accessing/createModel.st R Refactoring-Core.package/RBDeprecateMethodRefactoring.class/class/as yet unclassified/model_deprecateMethod_in_using_.st A Refactoring-Core.package/RBDeprecateMethodRefactoring.class/class/intance creation/model_deprecateMethod_in_using_.st R Refactoring-Core.package/RBDeprecateMethodRefactoring.class/instance/transforming/formDeprecatedMethod.st R Refactoring-Core.package/RBDeprecateMethodRefactoring.class/instance/transforming/formRewriteRule.st M Refactoring-Core.package/RBDeprecateMethodRefactoring.class/instance/transforming/transform.st R Refactoring-Tests-Core.package/RBDeprecateMethodTest.class/README.md R Refactoring-Tests-Core.package/RBDeprecateMethodTest.class/definition.st R Refactoring-Tests-Core.package/RBDeprecateMethodTest.class/instance/failure tests/testTooManyArguments.st R Refactoring-Tests-Core.package/RBDeprecateMethodTest.class/instance/failure tests/testWrongNumberOfArguments.st R Refactoring-Tests-Core.package/RBDeprecateMethodTest.class/instance/tests/testDeprecateMethod.st R Refactoring-Tests-Core.package/RBDeprecateMethodTest.class/instance/tests/testDeprecateMethodOnClassSide.st R Refactoring-Tests-Core.package/RBDeprecateMethodTest.class/instance/tests/testDeprecateMethodWithLotsOfArguments.st R Refactoring-Tests-Core.package/RBDeprecateMethodTest.class/instance/tests/testDeprecateMethodWithSenders.st R Refactoring-Tests-Core.package/RBDeprecateMethodTest.class/instance/tests/testDeprecateMethodWithSendersInSubclass.st R Refactoring-Tests-Core.package/RBDeprecateMethodTest.class/instance/tests/testSenderNotSelf.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50481.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50482.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50481.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50482.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Slot-Tests.package/SlotTest.class/instance/as yet unclassified/testAsSlotCollection.st M Slot.package/extension/String/instance/asSlotCollection.st A Slot.package/extension/String/instance/asValidInstVarName.st Log Message: ----------- 50482 17176 Simplify Deprecation refactoring https://pharo.fogbugz.com/f/cases/17176 17171 String>>#asSlotCollection parsing does not handle non valid characters https://pharo.fogbugz.com/f/cases/17171 17166 bad completion suggestions on method definitions https://pharo.fogbugz.com/f/cases/17166 http://files.pharo.org/image/50/50482.zip

Dec. 3, 2015

Re: [Pharo-dev] fixing our tools

by Marcus Denker

Hi, Yes, I think we really need to unify both the editor (get really rid of the old one) and the toolsâ¦ e.g. it is strange that all the changes we did for breakpoint visuals now have to be redone 3 times to get them in all toolsâ¦ I will have a look at these, many seem to be related to the suggestions-menu. > On 03 Dec 2015, at 08:47, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > please take a look at this errors: > > (I don't want to open 20 bug entries, and I think those issues are related > to two changes for Suggestions menu and one problem on rubric (the current menu builder > does not work for all tools where rubric is used) > So, maybe there are only 2 or 3 "real" issues. > > Help appreciate, especially for the rubric issue. Every time I tried to fix one > tool, there is at least one other tool with a broken menu. > > Open Nautilus on a method: > (Morph>>#drawOn:) browse > without any other interaction, right click on the code pane > -> a menu appears with embedded "why you see this menu/debug" debug menu > caused by empty selection interval > as soon as you select once one method entry, the right click menu works again. > > Open VersionBrowser (or any other tool (MC-changes / merge) with diff morph > right click in one of the diff code panes > -> error contextFor: 'Not defined context for a RubEditingArea' > > Open Transcript > right click > -> error contextFor: 'Not defined context for a RubEditingArea' > > Open Finder > right click in the lower code pane > -> 'Not defined context for a RubEditingArea' > > Open ProcessBrowser > right click in the lower code pane > -> 'Not defined context for a RubEditingArea(808452096)' > > Open TimeProfiler > select an entry from the time-"tree" > right click in the code pane > deprecation warning -> The method SmalltalkEditor class>>smalltalkEditorMenuOn: has been deprecated. > > Open a basic inspector (EyeInspector) > right click in the workspace pane > -> EyeIntegerInspector(Object)>>doesNotUnderstand: #selectedMessage > > Open ChangesBrowser > right click in the lower code pane (regardless whether you select a changed class and method > or not you'll get always) > -> ChangeSorterApplication(Object)>>doesNotUnderstand: #selectedMessage > > Open CriticsBrowser > right click on the code pane > -> SingleCodeCriticResultList(Object)>>doesNotUnderstand: #selectedMessage > > Open recover lost changes > right click on the lower code pane > -> ExternalChangesBrowser(Object)>>doesNotUnderstand: #selectedMessage > > The same in external browser > ExternalBrowser(Object)>>doesNotUnderstand: #selectedMessage > > Open debugger > select a inst var or context var > right click in the var "value"-pane > -> MorphicTextAdapter(Object)>>doesNotUnderstand: #acceptAllowed > > Open VersoinBrowser > change from "Side-by-Side" to "Source" view > right click in the code pane > -> UndefinedObject(Object)>>doesNotUnderstand: #ast >

Dec. 3, 2015

fixing our tools

by Nicolai Hess

please take a look at this errors: (I don't want to open 20 bug entries, and I think those issues are related to two changes for Suggestions menu and one problem on rubric (the current menu builder does not work for all tools where rubric is used) So, maybe there are only 2 or 3 "real" issues. Help appreciate, especially for the rubric issue. Every time I tried to fix one tool, there is at least one other tool with a broken menu. Open Nautilus on a method: (Morph>>#drawOn:) browse without any other interaction, right click on the code pane -> a menu appears with embedded "why you see this menu/debug" debug menu caused by empty selection interval as soon as you select once one method entry, the right click menu works again. Open VersionBrowser (or any other tool (MC-changes / merge) with diff morph right click in one of the diff code panes -> error contextFor: 'Not defined context for a RubEditingArea' Open Transcript right click -> error contextFor: 'Not defined context for a RubEditingArea' Open Finder right click in the lower code pane -> 'Not defined context for a RubEditingArea' Open ProcessBrowser right click in the lower code pane -> 'Not defined context for a RubEditingArea(808452096)' Open TimeProfiler select an entry from the time-"tree" right click in the code pane deprecation warning -> The method SmalltalkEditor class>>smalltalkEditorMenuOn: has been deprecated. Open a basic inspector (EyeInspector) right click in the workspace pane -> EyeIntegerInspector(Object)>>doesNotUnderstand: #selectedMessage Open ChangesBrowser right click in the lower code pane (regardless whether you select a changed class and method or not you'll get always) -> ChangeSorterApplication(Object)>>doesNotUnderstand: #selectedMessage Open CriticsBrowser right click on the code pane -> SingleCodeCriticResultList(Object)>>doesNotUnderstand: #selectedMessage Open recover lost changes right click on the lower code pane -> ExternalChangesBrowser(Object)>>doesNotUnderstand: #selectedMessage The same in external browser ExternalBrowser(Object)>>doesNotUnderstand: #selectedMessage Open debugger select a inst var or context var right click in the var "value"-pane -> MorphicTextAdapter(Object)>>doesNotUnderstand: #acceptAllowed Open VersoinBrowser change from "Side-by-Side" to "Source" view right click in the code pane -> UndefinedObject(Object)>>doesNotUnderstand: #ast

Dec. 3, 2015

Re: [Pharo-dev] Help needed: old issues issue tracker entries

by Nicolai Hess

Am 03.12.2015 1:08 vorm. schrieb "EuanM" <euanmee(a)gmail.com>: > > I had an issue assigned against me, which I have not the time nor the > knowledge to fix. > > (Inconstant aspect ratio of Desktop background image). > > Can I suggest it is given to someone who knows the Desktop GUI codebase? > > (If I was in a position to fix it, I would have just submitted a fix, > not a bug report) It was assigned to "everyone". And just assigned to you after a fix was provided. That issue is already closed. > > On 2 December 2015 at 13:42, webwarrior <reg(a)webwarrior.ws> wrote: > > Case 16725 - Merge changes from spec github repository. > > 2 subcases are resolved, 2 other need decision. Nothing time-consuming - > > just decide if we integrate them or mark as wontfix. > > > > > > Case 15927 - Menu is broken when contained in a list. > > This is much more complicated, it's even not clear which class > > (TransfromMorph or MenuItemMorph) is bugged. > > I tried to fix it myself, but had no success. > > > > > > > > -- > > View this message in context: http://forum.world.st/Help-needed-old-issues-issue-tracker-entries-tp486426… > > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > > >

Dec. 3, 2015

Re: [Pharo-dev] Help needed: old issues issue tracker entries

by EuanM

I had an issue assigned against me, which I have not the time nor the knowledge to fix. (Inconstant aspect ratio of Desktop background image). Can I suggest it is given to someone who knows the Desktop GUI codebase? (If I was in a position to fix it, I would have just submitted a fix, not a bug report) On 2 December 2015 at 13:42, webwarrior <reg(a)webwarrior.ws> wrote: > Case 16725 - Merge changes from spec github repository. > 2 subcases are resolved, 2 other need decision. Nothing time-consuming - > just decide if we integrate them or mark as wontfix. > > > Case 15927 - Menu is broken when contained in a list. > This is much more complicated, it's even not clear which class > (TransfromMorph or MenuItemMorph) is bugged. > I tried to fix it myself, but had no success. > > > > -- > View this message in context: http://forum.world.st/Help-needed-old-issues-issue-tracker-entries-tp486426… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Dec. 3, 2015