April 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] [Pharo 1.4] Please test!

by Marcus Denker

On Apr 6, 2012, at 10:16 AM, Marcus Denker wrote: > > On Apr 5, 2012, at 5:42 PM, Hilaire Fernandes wrote: > >> You may want to add these clean-up as well. >> Strangely, 'FileSystem-Tests-Disk' and 'FileSystem-Tests-Memory' are not >> cleaned up. Although there is instance class in memory. May be order >> matter in cleaning and those need to be cleaned first. >> >> >> (MCPackage named: 'Announcements-Help') unload. >> (MCPackage named: 'FileSystem-Tests-Core') unload. >> (MCPackage named: 'FileSystem-Tests-AnsiStreams') unload. >> (MCPackage named: 'FileSystem-Tests-Disk') unload. >> (MCPackage named: 'FileSystem-Tests-Memory') unload. >> (MCPackage named: 'Metacello-Help') unload. >> (MCPackage named: 'Regex-Help') unload. >> > > Yes! I will fix it. http://code.google.com/p/pharo/issues/detail?id=5582 -- Marcus Denker -- http://marcusdenker.de

April 6, 2012

Re: [Pharo-project] CogVM and fn key

by Milan Mimica

On my laptop the entire numpad doesn't respond in Pharo. I don't know if it worked on Squeak VM. On 6 April 2012 10:12, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > Hi, > > I've got a keybord input problem on the Linux CogVM on my laptop. If I > want to write for example the character +, one of the way how to write > it is to press something like fn+/. But CogVM ignores it. It is a long > term problem of this VM, in the old Squeak VM it works well. Does > anyone have the same experience? > > -- Pavel > > -- Milan Mimica http://sparklet.sf.net

April 6, 2012

Re: [Pharo-project] [Pharo 1.4] Please test!

by Marcus Denker

On Apr 5, 2012, at 5:42 PM, Hilaire Fernandes wrote: > You may want to add these clean-up as well. > Strangely, 'FileSystem-Tests-Disk' and 'FileSystem-Tests-Memory' are not > cleaned up. Although there is instance class in memory. May be order > matter in cleaning and those need to be cleaned first. > > > (MCPackage named: 'Announcements-Help') unload. > (MCPackage named: 'FileSystem-Tests-Core') unload. > (MCPackage named: 'FileSystem-Tests-AnsiStreams') unload. > (MCPackage named: 'FileSystem-Tests-Disk') unload. > (MCPackage named: 'FileSystem-Tests-Memory') unload. > (MCPackage named: 'Metacello-Help') unload. > (MCPackage named: 'Regex-Help') unload. > Yes! I will fix it. Marcus -- Marcus Denker -- http://marcusdenker.de

April 6, 2012

[Pharo-project] CogVM and fn key

by Pavel Krivanek

Hi, I've got a keybord input problem on the Linux CogVM on my laptop. If I want to write for example the character +, one of the way how to write it is to press something like fn+/. But CogVM ignores it. It is a long term problem of this VM, in the old Squeak VM it works well. Does anyone have the same experience? -- Pavel

April 6, 2012

[Pharo-project] SmallLint and manifest

by Simon Allier

Hi pharoers Since a couple of months the Pharo team has been working on improving the support for rules checking and in particular the handling of false positives (there is nothing more boring that to get all the time the same warnings that we know are not adequate). We added a manifest mechanism to manage the false/true positive of SmallLint, the rule checker of Pharo. A manifest is a class that contains meta data. In the future we may add package license and package documentation. This data is stored in methods on the meta side of the class. So, manifest can be versioned in Monticello and not lost. There is one manifest per package. It possible to use SmallLint with Manifest using the Critics Browser (menuWorld > Tool > CriticBrowser). With the Critics browser you can inspect violations of rules and mark them as false positive or true positive (ToDo) and see previous warnings flagged as false positives or toDo. In addition all the logic of the browser has been developed so that the manifest can be saved within the package without adding dependencies. We will continue to improve the Browser. In addition we will run SmallLint rules to all the Pharo packages and the rules checking will be part of the package validation. We want the community to use rule checking for real so that we all improve. Simon and Stef Gofer new url: 'http://www.squeaksource.com/PharoTaskForces'; package: 'ConfigurationOfManifest'; load. ((Smalltalk at: #ConfigurationOfManifest) project version: #stable) load

April 6, 2012

Re: [Pharo-project] Pharo 1.4: unable to load packages from webdav http repository

by Johan Brichau

Hey Sven, Thanks for the response! By tracing, I also just noticed that our webserver returned 'text/plain' mimetype instead of a binary one. It was our fault. Zinc is cool, just too bad it exposed our errors now ;-) Cheers! Johan On 06 Apr 2012, at 09:41, Sven Van Caekenberghe wrote: > Dag Johan, > > On 06 Apr 2012, at 08:58, Johan Brichau wrote: > >> Hi everyone, >> >> I'm test-driving Pharo 1.4 beta and I'm getting an error loading any package from our webdav-based monticello repository. >> The error surfaces in the reading of the zipfile by monticello, but it seems the source of the problems is the replacement of sockets by Zinc sockets: >> >> It seems that Zinc's "get" returns a ByteString instance when getting the file (in method MCHttpRepository>>#readStreamForFileNamed:do:) from the webdav volume. In contrast, when I'm loading a package from squeaksource, it returns a ByteArray. >> >> The reading of the zip goes wrong because the stream is returning characters instead of bytes. So I guess the difference between the ByteString and the ByteArray is the source of that problem. >> >> Maybe anyone knows why this happens? >> In the meantime... I'm digging deeper >> >> Johan > > Yes, this sounds familiar: Zn is much more strict at the HTTP level, most probably your server returns a text mime-type. Hence Zn interprets this as a string. Take one of your packages' URLs and do: > > ZnEasy get: 'http://my-web-dav/repo/Code.123.mcz'. > > and inspect the results, you'll see the mime type there. Compare it to, for example: > > ZnEasy get: 'http://mc.stfx.eu/ZincHTTPComponents/Zinc-HTTP-SvenVanCaekenberghe.254.mcz' > > The solution is to fix your server to use any binary mime-type for .mcz files (application/octet-stream or even application/x-monticello). > > Sven > > PS: Zinc does not 'replace sockets', it is an HTTP client using regular socket[streams].

April 6, 2012

Re: [Pharo-project] Pharo 1.4: unable to load packages from webdav http repository

by Sven Van Caekenberghe

Dag Johan, On 06 Apr 2012, at 08:58, Johan Brichau wrote: > Hi everyone, > > I'm test-driving Pharo 1.4 beta and I'm getting an error loading any package from our webdav-based monticello repository. > The error surfaces in the reading of the zipfile by monticello, but it seems the source of the problems is the replacement of sockets by Zinc sockets: > > It seems that Zinc's "get" returns a ByteString instance when getting the file (in method MCHttpRepository>>#readStreamForFileNamed:do:) from the webdav volume. In contrast, when I'm loading a package from squeaksource, it returns a ByteArray. > > The reading of the zip goes wrong because the stream is returning characters instead of bytes. So I guess the difference between the ByteString and the ByteArray is the source of that problem. > > Maybe anyone knows why this happens? > In the meantime... I'm digging deeper > > Johan Yes, this sounds familiar: Zn is much more strict at the HTTP level, most probably your server returns a text mime-type. Hence Zn interprets this as a string. Take one of your packages' URLs and do: ZnEasy get: 'http://my-web-dav/repo/Code.123.mcz'. and inspect the results, you'll see the mime type there. Compare it to, for example: ZnEasy get: 'http://mc.stfx.eu/ZincHTTPComponents/Zinc-HTTP-SvenVanCaekenberghe.254.mcz' The solution is to fix your server to use any binary mime-type for .mcz files (application/octet-stream or even application/x-monticello). Sven PS: Zinc does not 'replace sockets', it is an HTTP client using regular socket[streams].

April 6, 2012

Re: [Pharo-project] tail-like

by Igor Stasenko

On 5 April 2012 22:07, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > I am looking for a way to implement a logic like in the linux tail command: watch a file and react whenever a new line appears at the end of that file. > > Can anyone point me to some resources that I might use for something like this? > well, best would be the source code of tail command itself. it opens a file for reading and then polls periodically for more data. but i don't know details > Cheers, > Doru > > > -- > www.tudorgirba.com > > "When people care, great things can happen." > > > > -- Best regards, Igor Stasenko.

April 6, 2012

Re: [Pharo-project] CogVM segmentation fault (on linux) when running headless

by Igor Stasenko

hmm.. looks like FS makes VM nuts.. Cannot say that i seen FS code to know what exactly happens. On 6 April 2012 04:30, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > and with one of my VMs? > > > On Thu, Apr 5, 2012 at 7:06 PM, Sebastian Sastre > <sebastian(a)flowingconcept.com> wrote: >> >> Hi guys, >> >> I'm testing CogVM for one airflowing worker we have in stage and it looks >> quite promising when we start the image with UI but when we start it >> headless it immediately segfaults >> >> Below is the log >> >> sebastian >> >> o/ >> >> >> :~$ sudo invoke-rc.d airflowing0 start >> :~$ >> Segmentation fault Thu Apr Â 5 21:00:09 2012 >> >> >> Squeak VM version: 3.9-7 #1 Thu Apr Â 5 14:40:40 CEST 2012 gcc 4.1.2 >> Built from: CoInterpreter VMMaker-oscog-EstebanLorenzano.139 uuid: >> 5aa53979-d7d8-4ca3-91fe-cfc3b4109c33 Apr Â 5 2012 >> With: StackToRegisterMappingCogit VMMaker-oscog-EstebanLorenzano.139 uuid: >> 5aa53979-d7d8-4ca3-91fe-cfc3b4109c33 Apr Â 5 2012 >> Revision: https://git.gitorious.org/cogvm/blessed.git Commit: >> 846551630c3c10df1f59588a6e7131d602f00b45 Date: Thu Apr 5 14:13:41 2012 +0200 >> By: Esteban Lorenzano <estebanlm(a)gmail.com> >> Build host: Linux pharo-build.lille.inria.fr 2.6.18-194.26.1.el5xen #1 SMP >> Tue Nov 9 14:13:46 EST 2010 i686 i686 i386 GNU/Linux >> plugin path: /home/prod/pharo/cog/ [default: /home/prod/pharo/cog/] >> >> >> C stack backtrace: >> /home/prod/pharo/cog/CogVM[0x80968b1] >> /home/prod/pharo/cog/CogVM[0x8096a52] >> [0xb77a8440] >> /lib/tls/i686/cmov/libc.so.6(iconv+0x6e)[0xb761e4ee] >> /home/prod/pharo/cog/CogVM(convertChars+0xb4)[0x8094384] >> /home/prod/pharo/cog/CogVM(sq2uxPath+0x47)[0x80945d7] >> /home/prod/pharo/cog/CogVM(dir_Lookup+0x73)[0x80b8703] >> /home/prod/pharo/cog/CogVM[0x80b7180] >> /home/prod/pharo/cog/CogVM(interpret+0x3f68)[0x808dcc8] >> /home/prod/pharo/cog/CogVM[0x808fc97] >> /home/prod/pharo/cog/CogVM[0x8090664] >> /home/prod/pharo/cog/CogVM(main+0x38a)[0x809774a] >> /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0)[0xb761d460] >> /home/prod/pharo/cog/CogVM[0x805acc1] >> >> >> Smalltalk stack dump: >> 0xbfdc45d8 I FSUnixStore(FSDiskStore)>directoryAt:ifAbsent:nodesDo: >> -1431671128: a(n) FSUnixStore >> 0xbfdc4608 I FSUnixStore(FSDiskStore)>nodeAt:ifPresent:ifAbsent: >> -1431671128: a(n) FSUnixStore >> 0xbfdc4634 I FSUnixStore(FSStore)>exists: -1431671128: a(n) FSUnixStore >> 0xbfdc4658 I FSFilesystem>exists: -1431671120: a(n) FSFilesystem >> 0xbfdc467c I FSReference>exists -1431667420: a(n) FSReference >> 0xbfdc469c I FSLocator>exists -1431671980: a(n) FSLocator >> 0xbfdc46bc I FLHelper>hasConfDirectory -1431672032: a(n) FLHelper >> 0xbfdc46dc I FLHelper>start -1431672032: a(n) FLHelper >> 0xbfdc46fc I FLHelper class>start -1446907784: a(n) FLHelper class >> 0xbfdc471c I FLHelper class>startUp -1446907784: a(n) FLHelper class >> 0xbfdc4734 M FLHelper class(Behavior)>startUp: -1446907784: a(n) FLHelper >> class >> 0xbfdc4760 M [] in SmalltalkImage>send:toClassesNamedIn:with: -1478292160: >> a(n) SmalltalkImage >> 0xbfdc4788 I OrderedCollection>do: -1480202612: a(n) OrderedCollection >> 0xbfdc47b0 I SmalltalkImage>send:toClassesNamedIn:with: -1478292160: a(n) >> SmalltalkImage >> 0xbfdc47dc I SmalltalkImage>processStartUpList: -1478292160: a(n) >> SmalltalkImage >> 0xbfdc4804 I [] in SmalltalkImage>snapshot:andQuit: -1478292160: a(n) >> SmalltalkImage >> 0xbfdc4824 M BlockClosure>ensure: -1436539624: a(n) BlockClosure >> 0xbfdc4848 I MorphicUIManager(UIManager)>boot:during: -1441995864: a(n) >> MorphicUIManager >> 0xbfdc4878 I SmalltalkImage>snapshot:andQuit: -1478292160: a(n) >> SmalltalkImage >> -1436547788 s SmalltalkImage>saveSession >> -1436547696 s [] in ToggleMenuItemMorph(MenuItemMorph)>invokeWithEvent: >> -1436547604 s BlockClosure>ensure: >> -1437443620 s CursorWithMask(Cursor)>showWhile: >> -1437443732 s ToggleMenuItemMorph(MenuItemMorph)>invokeWithEvent: >> -1436547512 s ToggleMenuItemMorph(MenuItemMorph)>mouseUp: >> -1436547420 s ToggleMenuItemMorph(MenuItemMorph)>handleMouseUp: >> -1436547328 s MouseButtonEvent>sentTo: >> -1436547236 s ToggleMenuItemMorph(Morph)>handleEvent: >> -1436547144 s MorphicEventDispatcher>dispatchDefault:with: >> -1436547052 s MorphicEventDispatcher>dispatchEvent:with: >> -1436546960 s ToggleMenuItemMorph(Morph)>processEvent:using: >> -1436546868 s MorphicEventDispatcher>dispatchDefault:with: >> -1436546776 s MorphicEventDispatcher>dispatchEvent:with: >> -1436546684 s MenuMorph(Morph)>processEvent:using: >> -1436546592 s MenuMorph(Morph)>processEvent: >> -1436546500 s MenuMorph>handleFocusEvent: >> -1436546408 s [] in HandMorph>sendFocusEvent:to:clear: >> -1436546316 s [] in PasteUpMorph>becomeActiveDuring: >> -1437443244 s BlockClosure>on:do: >> -1437444096 s PasteUpMorph>becomeActiveDuring: >> -1437444216 s HandMorph>sendFocusEvent:to:clear: >> -1436546224 s HandMorph>sendEvent:focus:clear: >> -1437444332 s HandMorph>sendMouseEvent: >> -1437444424 s HandMorph>handleEvent: >> -1436546132 s HandMorph>processEvents >> -1436546040 s [] in WorldState>doOneCycleNowFor: >> -1436545948 s Array(SequenceableCollection)>do: >> -1436545856 s WorldState>handsDo: >> -1437444768 s WorldState>doOneCycleNowFor: >> -1436545764 s WorldState>doOneCycleFor: >> -1436545672 s PasteUpMorph>doOneCycle >> -1441147720 s [] in Project class>spawnNewProcess >> -1441147868 s [] in BlockClosure>newProcess >> >> Most recent primitives >> value: >> compare:with:collated: >> compare:with:collated: >> value: >> compare:with:collated: >> compare:with:collated: >> compare:with:collated: >> at:put: >> compare:with:collated: >> compare:with:collated: >> compare:with:collated: >> at:put: >> compare:with:collated: >> compare:with:collated: >> compare:with:collated: >> at:put: >> compare:with:collated: >> compare:with:collated: >> compare:with:collated: >> at:put: >> compare:with:collated: >> compare:with:collated: >> compare:with:collated: >> at:put: >> compare:with:collated: >> compare:with:collated: >> compare:with:collated: >> at:put: >> compare:with:collated: >> compare:with:collated: >> compare:with:collated: >> at:put: >> basicNew: >> value:value: >> at:put: >> value:value: >> at:put: >> value:value: >> at:put: >> value:value: >> at:put: >> value:value: >> at:put: >> value:value: >> at:put: >> value:value: >> at:put: >> size >> size >> at: >> compare:with:collated: >> size >> basicNew: >> compare:with:collated: >> new: >> at:put: >> basicNew >> new: >> basicNew: >> species >> basicNew: >> replaceFrom:to:with:startingAt: >> at:put: >> size >> + >> basicNew: >> species >> basicNew: >> replaceFrom:to:with:startingAt: >> at:put: >> basicNew: >> species >> basicNew: >> replaceFrom:to:with:startingAt: >> at:put: >> basicNew: >> species >> basicNew: >> replaceFrom:to:with:startingAt: >> at:put: >> basicNew: >> species >> basicNew: >> replaceFrom:to:with:startingAt: >> at:put: >> basicNew: >> species >> basicNew: >> replaceFrom:to:with:startingAt: >> at:put: >> basicNew: >> species >> basicNew: >> replaceFrom:to:with:startingAt: >> at:put: >> basicNew: >> size >> species >> basicNew: >> replaceFrom:to:with:startingAt: >> at:put: >> basicNew >> new: >> compare:with:collated: >> compare:with:collated: >> compare:with:collated: >> compare:with:collated: >> compare:with:collated: >> at:put: >> compare:with:collated: >> compare:with:collated: >> compare:with:collated: >> at:put: >> compare:with:collated: >> compare:with:collated: >> compare:with:collated: >> at:put: >> compare:with:collated: >> compare:with:collated: >> compare:with:collated: >> at:put: >> compare:with:collated: >> compare:with:collated: >> compare:with:collated: >> at:put: >> compare:with:collated: >> compare:with:collated: >> compare:with:collated: >> at:put: >> compare:with:collated: >> compare:with:collated: >> compare:with:collated: >> at:put: >> basicNew: >> value:value: >> at:put: >> at:put: >> at:put: >> at:put: >> at:put: >> at:put: >> at:put: >> basicNew >> size >> = >> size >> at: >> compare:with:collated: >> size >> basicNew: >> at: >> at:put: >> at:put: >> at:put: >> at:put: >> at:put: >> at:put: >> basicNew >> size >> size >> new: >> size >> at:put: >> size >> size >> at: >> basicNew >> new: >> compare:with:collated: >> compare:with:collated: >> compare:with:collated: >> at:put: >> compare:with:collated: >> compare:with:collated: >> compare:with:collated: >> at:put: >> compare:with:collated: >> compare:with:collated: >> compare:with:collated: >> at:put: >> compare:with:collated: >> compare:with:collated: >> compare:with:collated: >> at:put: >> compare:with:collated: >> compare:with:collated: >> compare:with:collated: >> at:put: >> compare:with:collated: >> compare:with:collated: >> compare:with:collated: >> at:put: >> compare:with:collated: >> compare:with:collated: >> compare:with:collated: >> at:put: >> basicNew: >> at:put: >> at:put: >> at:put: >> at:put: >> at:put: >> at:put: >> at:put: >> basicNew >> size >> size >> compare:with:collated: >> basicNew: >> at:put: >> at:put: >> at:put: >> at:put: >> at:put: >> at:put: >> basicNew: >> basicNew >> value: >> at:put: >> size >> new >> value: >> replaceFrom:to:with:startingAt: >> value >> at:put: >> <= >> * >> + >> value: >> at: >> replaceFrom:to:with:startingAt: >> value >> at:put: >> value: >> replaceFrom:to:with:startingAt: >> value >> at:put: >> value: >> replaceFrom:to:with:startingAt: >> value >> at:put: >> value: >> replaceFrom:to:with:startingAt: >> value >> at:put: >> value: >> replaceFrom:to:with:startingAt: >> species >> basicNew: >> replaceFrom:to:with:startingAt: >> basicNew >> basicNew: >> basicNew >> findFirstInString:inSet:startingAt: >> replaceFrom:to:with:startingAt: >> lookupEntryIn:index: >> >> (Segmentation fault) >> > > > > -- > best, > Eliot > -- Best regards, Igor Stasenko.

April 6, 2012

[Pharo-project] Pharo 1.4: unable to load packages from webdav http repository

by Johan Brichau

Hi everyone, I'm test-driving Pharo 1.4 beta and I'm getting an error loading any package from our webdav-based monticello repository. The error surfaces in the reading of the zipfile by monticello, but it seems the source of the problems is the replacement of sockets by Zinc sockets: It seems that Zinc's "get" returns a ByteString instance when getting the file (in method MCHttpRepository>>#readStreamForFileNamed:do:) from the webdav volume. In contrast, when I'm loading a package from squeaksource, it returns a ByteArray. The reading of the zip goes wrong because the stream is returning characters instead of bytes. So I guess the difference between the ByteString and the ByteArray is the source of that problem. Maybe anyone knows why this happens? In the meantime... I'm digging deeper Johan

April 6, 2012