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

Re: [Pharo-dev] Text Indentation in Pharo editor

by Sean P. DeNigris

Pavel Krivanek-3 wrote > Ctrl + Shift + L or Ctrl + Shift + R Mac: Cmd + â¦ ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Dec. 7, 2017

Re: [Pharo-dev] Crash Dump - GT loaded into 6.1

by Sean P. DeNigris

Different image, another crash dump while quitting the image. Lost a bunch of data this time. Ouch. Segmentation fault Wed Dec 6 22:30:12 2017 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 $ C stack backtrace & registers: eax 0x8bfffee0 ebx 0x00000000 ecx 0x0000000c edx 0x00000007 edi 0x0000000c esi 0x0000000c ebp 0xbff3fad8 esp 0xbff3fad8 eip 0x000b2651 0 Pharo 0x000b2651 fetchByteofObject + 9 1 Pharo 0x00113460 reportStackState + 819 2 Pharo 0x001137e6 sigsegv + 163 3 libsystem_platform.dylib 0xa778202b _sigtramp + 43 4 ??? 0xffffffff 0x0 + 4294967295 5 Pharo 0x000dbb9a bytecodePCForstartBcpcin + 273 6 Pharo 0x0009fed8 mustMapMachineCodePCcontext + 328 7 Pharo 0x000a0333 ensureContextHasBytecodePC + 26 8 Pharo 0x000cbb17 makeContextSnapshotSafe + 46 9 Pharo 0x000ab11d voidVMStateForSnapshotFlushingExternalPrimitivesIf + 518 10 Pharo 0x000da477 snapshot + 79 11 Pharo 0x000d019d primitiveSnapshot + 20 12 Pharo 0x000946e8 interpret + 26051 13 Pharo 0x0009db9a enterSmalltalkExecutiveImplementation + 135 14 Pharo 0x0008e3ab interpret + 646 15 Pharo 0x001149d9 -[sqSqueakMainApplication runSqueak] + 476 16 Foundation 0x953897ec __NSFirePerformWithOrder + 432 17 CoreFoundation 0x9392a216 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 22 18 CoreFoundation 0x9392a132 __CFRunLoopDoObservers + 498 19 CoreFoundation 0x9390d5ed __CFRunLoopRun + 1661 20 CoreFoundation 0x9390cc41 CFRunLoopRunSpecific + 641 21 CoreFoundation 0x9390c9aa CFRunLoopRunInMode + 122 22 HIToolbox 0x92f0dd3b RunCurrentEventLoopInMode + 321 23 HIToolbox 0x92f0d91f ReceiveNextEventCommon + 454 24 HIToolbox 0x92f0d73b _BlockUntilNextEventMatchingListInModeWithFilter + 71 25 AppKit 0x9136538d _DPSNextEvent + 2101 26 AppKit 0x91ad6c74 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 2859 27 AppKit 0x91ad6141 -[NSApplication(NSEvent) nextEventMatchingMask:untilDate:inMode:dequeue:] + 134 28 AppKit 0x9135a2e1 -[NSApplication run] + 763 29 AppKit 0x9132c2f2 NSApplicationMain + 1228 30 libdyld.dylib 0xa7502711 start + 1 31 ??? 0x00000002 0x0 + 2 Smalltalk stack dump: 0xbff6ac60 I SessionManager>snapshot:andQuit: 0x8489350: a(n) SessionManager 0xbff6ac90 I [] in SmalltalkImage>snapshot:andQuit: 0x6ea1c50: a(n) SmalltalkImage 0x1f943be0 s CurrentExecutionEnvironment class>activate:for: 0x6806028 s DefaultExecutionEnvironment(ExecutionEnvironment)>beActiveDuring: 0x6806088 s DefaultExecutionEnvironment class>beActiveDuring: 0x1f943c60 s SmalltalkImage>snapshot:andQuit: ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Dec. 7, 2017

Re: [Pharo-dev] Text Indentation in Pharo editor

by Pavel Krivanek

2017-12-07 16:19 GMT+01:00 Torsten Bergmann <astares(a)gmx.de>: > Hi, > > in most code editors I know one can select a (multiline) block of > code/text and then hit > TAB to indent and move it from the position to the right side. > > Using SHIFT+TAB one can move it back to the left. In Pharo the selected > text unfortunately > is always deleted instead of moved/indented when hitting TAB. > > Is such an editor mode or special key combination available? If not could > this easily be > brought into the current text/code editor(s) in Pharo 7? Or will a > possible upcoming Bloc > text/code editor support such behavior? > Ctrl + Shift + L or Ctrl + Shift + R -- Pavel > > This would be really nice to have and move Pharo editor away from being > like Notepad. Because > editors in Eclipse, NetBeans, VS, Brackets, Atom, Notepad++ all support > this TAB Indentation > out of the box. ;) > > Thanks > T. > > > >

Dec. 7, 2017

Text Indentation in Pharo editor

by Torsten Bergmann

Hi, in most code editors I know one can select a (multiline) block of code/text and then hit TAB to indent and move it from the position to the right side. Using SHIFT+TAB one can move it back to the left. In Pharo the selected text unfortunately is always deleted instead of moved/indented when hitting TAB. Is such an editor mode or special key combination available? If not could this easily be brought into the current text/code editor(s) in Pharo 7? Or will a possible upcoming Bloc text/code editor support such behavior? This would be really nice to have and move Pharo editor away from being like Notepad. Because editors in Eclipse, NetBeans, VS, Brackets, Atom, Notepad++ all support this TAB Indentation out of the box. ;) Thanks T.

Dec. 7, 2017

[Pharo 7.0-dev] Build #366: 20826 Super setup need to be called in DependencyAnalyser tests

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

There is a new Pharo build available! The status of the build #366 was: SUCCESS. The Pull Request #579 was integrated: "20826 Super setup need to be called in DependencyAnalyser tests" Pull request url: https://github.com/pharo-project/pharo/pull/579 Issue Url: https://pharo.fogbugz.com/f/cases/20826 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Dec. 7, 2017

Re: [Pharo-dev] [Pharo-users] [TechTalk] Topics Wanted for 2018!

by Marcus Denker

What about Tuesday 30th Jan? > On 7 Dec 2017, at 02:06, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > Hi Marcus! > > Thanks for pushing the community! > If there is a free slot at the end of January, I can do another tech talk on AI technique. I am thinking about a lecture on Genetic Algorithm and Genetic Programming. > > Let me know... > > Alexandre > > >> On Dec 1, 2017, at 7:58 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> Hi, >> >> As you know, we are trying to have one Pharo tech-talk per month. >> >> The idea is to use this for >> -> mini âLecturesâ >> -> Demos of interesting Projects >> -> Just some interesting topic to discuss with audio chat on Discord >> >> You can see the past topics here: >> >> http://pharo.org/TechTalk >> >> We will soon define the dates for the first half of 2018. If you want to do a techtalk >> yourself (give a presentation / Demo or moderate a discussion), feel free to contact >> me! You are able to pick a date that works best for you. >> >> >> Marcus > >

Dec. 7, 2017

[Pharo 7.0-dev] Build #365: 20830 Super setup need to be called in Monticello tests and other cleanups (comments, tags)

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

There is a new Pharo build available! The status of the build #365 was: SUCCESS. The Pull Request #583 was integrated: "20830 Super setup need to be called in Monticello tests and other cleanups (comments, tags)" Pull request url: https://github.com/pharo-project/pharo/pull/583 Issue Url: https://pharo.fogbugz.com/f/cases/20830 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Dec. 7, 2017

[Pharo 7.0-dev] Build #364: 20816 Typo in DateAndTimeEpochTest and DateAndTimeUnixEpochTest tearDown

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

There is a new Pharo build available! The status of the build #364 was: FAILURE. The Pull Request #572 was integrated: "20816 Typo in DateAndTimeEpochTest and DateAndTimeUnixEpochTest tearDown" Pull request url: https://github.com/pharo-project/pharo/pull/572 Issue Url: https://pharo.fogbugz.com/f/cases/20816 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Dec. 7, 2017

Re: [Pharo-dev] Running tests in MCMethodDefinitionTest

by Nicolas Cellier

Thanks, very good find! I reviewed the PR yesterday, all good to my eyes. I backported the fix to Squeak where I just experienced the random failure when debugging opensmalltalk-vm test failures https://github.com/hpi-swa/smalltalkCI/issues/350 2017-12-07 13:53 GMT+01:00 Marcus Denker <marcus.denker(a)inria.fr>: > Very nice! I am reviewing the change now. > > Thanks, > > Marcus > > > On 6 Dec 2017, at 23:42, Torsten Bergmann <astares(a)gmx.de> wrote: > > > > Hi, > > > > a little story: while working on cleaning up MCMethodDefinitionTest (see > https://pharo.fogbugz.com/f/cases/20830) > > I noticed that from time to time you have trouble when running the test > methods in this class one after the other > > several times. So sometimes it worked and sometimes not. > > > > I wondered since the latest Pharo 7 build #70360 is definitely green on > CI, so the tests seem to work. > > > > After investigating I've noticed that in MCMethodDefinitionTest>>tearDown > a package "FooBarBaz" which > > is used during the tests is unregistered and (when you run another test > from this suite right afterwards) > > is not found anymore. Because in the test initialization it is not. > > > > This is easily fixed with setting the package up in the #setUp method > which is unregistered in #tearDown > > and one can easily run the tests several times independently. > > > > So if one had trouble in Pharo 6 and Pharo 7 with sporadic fails in > Monticello tests this might have been > > the cause. > > > > The fix is part of PR https://github.com/pharo-project/pharo/pull/583 > > > > Bye > > T. > > > > > > >

Dec. 7, 2017

Re: [Pharo-dev] Running tests in MCMethodDefinitionTest

by Marcus Denker

Very nice! I am reviewing the change now. Thanks, Marcus > On 6 Dec 2017, at 23:42, Torsten Bergmann <astares(a)gmx.de> wrote: > > Hi, > > a little story: while working on cleaning up MCMethodDefinitionTest (see https://pharo.fogbugz.com/f/cases/20830) > I noticed that from time to time you have trouble when running the test methods in this class one after the other > several times. So sometimes it worked and sometimes not. > > I wondered since the latest Pharo 7 build #70360 is definitely green on CI, so the tests seem to work. > > After investigating I've noticed that in MCMethodDefinitionTest>>tearDown a package "FooBarBaz" which > is used during the tests is unregistered and (when you run another test from this suite right afterwards) > is not found anymore. Because in the test initialization it is not. > > This is easily fixed with setting the package up in the #setUp method which is unregistered in #tearDown > and one can easily run the tests several times independently. > > So if one had trouble in Pharo 6 and Pharo 7 with sporadic fails in Monticello tests this might have been > the cause. > > The fix is part of PR https://github.com/pharo-project/pharo/pull/583 > > Bye > T. > >

Dec. 7, 2017