- Pharo-dev - lists.pharo.org

Fogbugz login to issue
by Sean P. DeNigris Aug. 2, 2014

Aug. 2, 2014

Neither the login link or button on the default page preserves the query, so https://pharo.fogbugz.com/default.asp?2489 gets transformed into ...default.asp?pg=pgLogon&dest=, but should be ...default.asp?pg=pgLogon&dest=2489 Is that something we can fix or is it a fogbugz bug? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Fogbugz-login-to-issue-tp4771555.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

1 0

SmalltalkHub is down ?
by stepharo Aug. 2, 2014

Aug. 2, 2014

3 5

Strange behavior of Rectangle is done :)
by stepharo Aug. 2, 2014

Aug. 2, 2014

After another pair programming session with igor.... Strange behavior of Rectangle https://pharo.fogbugz.com/default.asp?2489 is finally done. Stef

1 0

Re: [Pharo-dev] [Vm-dev] Delay machinery (was Re: Suspending a Process)
by Nicolai Hess Aug. 2, 2014

Aug. 2, 2014

So, we are going to change it in Pharo. What about Squeak ? 2014-07-28 21:39 GMT+02:00 Eliot Miranda <eliot.miranda(a)gmail.com>: > > Hi Nicolai, > > On Jul 27, 2014, at 10:59 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: > > >> >> Then you're not reading it properly. It clearly shows you have a >> deadlock: >> >> Process 0xb9148c20 priority 40 >> 0xff7907b8 M [] in Semaphore>critical: 0xb82f8ef4: a(n) Semaphore >> 0xff7907d8 M BlockClosure>ensure: 0xb91502e0: a(n) BlockClosure >> 0xff7907f8 M Semaphore>critical: 0xb82f8ef4: a(n) Semaphore >> 0xff790814 M Delay>schedule 0xb91501e4: a(n) Delay >> 0xff79082c M Delay>wait 0xb91501e4: a(n) Delay >> 0xff790850 I [] in BackgroundWorkDisplayMorph>initialize 0xb91488b0: >> a(n) BackgroundWorkDisplayMorph >> 0xff790870 I [] in BlockClosure>newProcess 0xb9148b40: a(n) BlockClosure >> >> Process 0xb7902630 priority 40 >> 0xff764784 M [] in Semaphore>critical: 0xb82f8ef4: a(n) Semaphore >> 0xff7647a4 M BlockClosure>ensure: 0xb916b7a4: a(n) BlockClosure >> 0xff7647c4 M Semaphore>critical: 0xb82f8ef4: a(n) Semaphore >> 0xff7647e0 M Delay>schedule 0xb916b6a8: a(n) Delay >> 0xff7647f8 M Delay>wait 0xb916b6a8: a(n) Delay >> 0xff764818 M WorldState>interCyclePause: 0xb75e8fd8: a(n) WorldState >> 0xff764834 M WorldState>doOneCycleFor: 0xb75e8fd8: a(n) WorldState >> 0xff764850 M WorldMorph>doOneCycle 0xb75e8fa4: a(n) WorldMorph >> 0xff764870 I [] in MorphicUIManager()>? 0xb770ac38: a(n) MorphicUIManager >> 0xb78cb554 s [] in BlockClosure()>? >> >> >> > Ah, Ok. > So, it is not my "misuse" of delays but a bug in Delay>>#schedule, like > ben already guessed? > Two processes in the same critical section should not happen, right? > > > Right, and fortunately Ben already provided a solution. > > Nicolai > > > Aloha, > Eliot (phone) > >

1 0

Test Coverage easy to use in Pharo
by Alexandre Bergel Aug. 1, 2014

Aug. 1, 2014

Hi! We are actively working on S2py, the nice successor of Spy1. S2py is a profiler framework: it allows one to easily build dynamic analysis. Hapao, shipped with S2py, is a test coverage tool. Here is how to use it: First, you need free type font: http://bit.ly/installingFreeTypeFont Then, you need Roassal2 and S2py -=-=-=-=-=-=-=-=-=-= Gofer new smalltalkhubUser: 'ObjectProfile' project: 'Roassal2'; package: 'ConfigurationOfRoassal2'; load. (Smalltalk at: #ConfigurationOfRoassal2) loadBleedingEdge. Gofer new smalltalkhubUser: 'ObjectProfile' project: 'S2py'; package: 'S2py'; load. -=-=-=-=-=-=-=-=-=-= Here is a screenshot of the coverage of Nautilus: Run "Hapao @ Class" and "Hapao @ Class â¦â from the World menu. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

1 0

Todo: Athens (Pharo image corruption and fatal VM error with Roassal)
by Nicolai Hess Aug. 1, 2014

Aug. 1, 2014

2014-08-01 13:09 GMT+02:00 stepharo <stepharo(a)free.fr>: > > > Someone working on this? > > > igor but he got burned out on that. > > > What are the next steps to make the system fully athens based? > > we need > - to update all the drawon: methods (arghhhhh) > No, this can make fun! What is needed? For all drawOn: implement a drawOnAthensCanvas: and test if they work on an AthensWrapMorph? > - get a texteditor working (so far it is working but no tab support) > where? I this in any way related to the work done for Rubric and/or TxText? > > > We can organize a skype meetings with people willing to help. > > > Stef > >

1 0

Re: [Pharo-dev] Pharo image corruption and fatal VM error with Roassal
by Blondeau Vincent Aug. 1, 2014

Aug. 1, 2014

Yes it is. But I will not do TRMorph allInstances do: #delete In command line every dayâ¦ Vincent De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de Usman Bhatti EnvoyÃ© : jeudi 31 juillet 2014 10:59 Ã : Pharo Development List Cc : Moose-related development Objet : Re: [Pharo-dev] Pharo image corruption and fatal VM error with Roassal This may be related to this known issue reported a few days back. https://code.google.com/p/moose-technology/issues/detail?id=1084 And there is a possible solution to recover your image. usman On Thu, Jul 31, 2014 at 10:50 AM, Blondeau Vincent <vincent.blondeau(a)worldline.com<mailto:vincent.blondeau@worldline.com>> wrote: Hi, Yesterday, I was using GraphET (a part of Roassal) to do some charts and, today, when I wanted to reopen the image. And I got that : [cid:image001.png@01CFACAF.C4370C70] It is *very* unpleasantâ¦ To reproduce the bug: 1 - You can do either: | builder | builder := GET2Line data: (0 to: 100) . builder y: [ :x | x*x ]. builder open. Or WorldMenu -> Roassal examples -> choose an item -> click on a graph . A TRMorph should be opened. 2 - donât close the graph and save the pharo image. 3 â Close the pharo image 4 - Reopen it I am under W7 x64 with the latest moose image and the VM available on the pharo.org<http://pharo.org> website (http://files.pharo.org/platform/Pharo3.0-win.zip) from the 10 july. You will find the crash dump attached. Thankfully, I managed to open the image with a latest VM (http://www.mirandabanda.org/files/Cog/VM/VM.r3056/cogwin-14.29.3056.zip) Thanks a lot Eliot ! :) And I got this: [cid:image002.png@01CFACAF.C4370C70] Thanks in advance Cheers, Vincent BLONDEAU ________________________________ Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. ________________________________ Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

9 14

[pharo-project/pharo-core]
by GitHub Aug. 1, 2014

Aug. 1, 2014

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

1 0

[pharo-project/pharo-core] 785095: 40148
by GitHub Aug. 1, 2014

Aug. 1, 2014

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 78509505e1b59550db96856d564034e7b5659e3b https://github.com/pharo-project/pharo-core/commit/78509505e1b59550db96856d… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-08-01 (Fri, 01 Aug 2014) Changed paths: M OpalDecompiler.package/OCDecompiler.class/instance/private/quickMethod.st M OpalDecompiler.package/OCDecompilerConstructor.class/instance/constructor/codeMethod_block_tempVars_primitive_class_.st A OpalDecompiler.package/OCDecompilerConstructor.class/instance/private/pragmasForMethod_.st M OpalDecompiler.package/extension/RBMessageNode/instance/toDoFromWhileWithInit_.st M OpalDecompiler.package/extension/RBMessageNode/instance/toDoLimit_.st M OpalDecompiler.package/extension/RBMethodNode/instance/primitiveErrorVariableName.st M OpalDecompiler.package/extension/RBMethodNode/instance/removeAndRenameLastTempIfErrorCode.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script148.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40148.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40148 13751 OpalDecompiler missdecompile named primitives https://pharo.fogbugz.com/f/cases/13751 13750 OpalDecompiler raises errors in rare cases when decompiling to:do: and to:by:do: https://pharo.fogbugz.com/f/cases/13750 http://files.pharo.org/image/40/40148.zip

1 0

[pharo-project/pharo-core]
by GitHub Aug. 1, 2014

Aug. 1, 2014

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

1 0