- Pharo-dev - lists.pharo.org

Issue with ZnMimeType>>#=

by Andy Kellens

Hi, Yesterday, I stumbled across a bug when using the Zinc Seaside adaptor that resulted in that the post fields of a request were not present in the WARequest. I found out that the problem occurred when converting a Zinc request into a WARequest. More particular: ZnZincServerAdaptor>>requestFieldsFor: aZincRequest | fields | fields := WARequestFields new. (aZincRequest method = #POST and: [ aZincRequest hasEntity ]) ifTrue: [ aZincRequest entity contentType = ZnMimeType applicationFormUrlEncoded ifTrue: [ fields addAll: aZincRequest entity fields ]. aZincRequest entity contentType = ZnMimeType multiPartFormData ifTrue: [ fields addAll: (self convertMultipart: aZincRequest entity) ] ]. ^ fields This method checks if the Mime Type is either applicationFormUrlEncoded or multiPartFormData in order to extract the post fields. Recently, ZnMimeType>>= got changed from: ZnMimeType>>= other ^ (self class == other class) and: [ self main = other main and: [ self sub = other sub ] ] to: ZnMimeType>>= other ^ (self class == other class) and: [ self main = other main and: [ self sub = other sub and: [ self hasParameters not & other hasParameters not or: [ self parameters = other parameters ] ] ] ] As my request had an additional parameter charset=utf-8, the equality with ZnMimeType applicationFormUrlEncoded failed and hence the fields were not extract. While I assume that the comparison of the Mime type parameters in #= is there for a good reason, and the best way to fix this problem is to change the #requestFieldsFor: method in order to match the Mime type differently, I wanted to briefly check with the mailing list before opening an issue + submitting a patch. Kind regards, Andy

June 4, 2013

Re: [Pharo-dev] MetacelloRepository

by Tudor Girba

Which is a good thing :) Thanks, Doru On Tue, Jun 4, 2013 at 9:28 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > > On Jun 4, 2013, at 7:18 AM, Hilaire Fernandes <hilaire.fernandes(a)gmail.com> > wrote: > > > Stephane, > > > > The lack for me was the configurationOfXML with the XML-Parser version I > > use (#20, a bit old). > > As this is problably limited to my sistuation I recreate a > > configurationOfXML in my own repo. > > > > Btw, I use XML-Parser for both read and write of XML file. > > Was XML-support splited in two packages recently? > > yes > Normally when loading the parser you would get the writer but damien cut > it apart. > > Stef > > > > > Thanks > > > > Hilaire > > > > Le 03/06/2013 22:08, StÃ©phane Ducasse a Ã©crit : > >> Hilaire > >> > >> Normally this is XMLParser. I extracted just the XML parser and not all > the tools. > >> Now if you want to write you have XMLWriter. > >> > >> Let us know if it works. > >> > >> Stef > >> > >> On Jun 3, 2013, at 10:17 AM, Hilaire Fernandes < > hilaire.fernandes(a)gmail.com> wrote: > >> > >>> Hello, > >>> > >>> To build DrGeo I use the squeaksource MetacelloRepository (example > bellow). > >>> I can not find it in SmalltalkHub? > >>> I can see in PahroExtra/XMLParser ConfigurationOfXMLParser, is it the > >>> same as ConfigurationOfXMLSupport. Can I find equivalent of > >>> ConfigurationOfXMLSupport matching the exact same XML source version? > >>> Unhelpful, I did not find how to browse the source form Smalltalkhub to > >>> explore online the ConfigurationOf... code. > >>> > >>> Thanks > >>> > >>> Hilaire > >>> > >>> > >>> baseline1012: spec > >>> <version: '10.12-baseline'> > >>> spec for: #pharo do: [ > >>> spec blessing: #baseline. > >>> spec project: 'XML Parser' with: [ > >>> spec className: 'ConfigurationOfXMLSupport'; > >>> version: '1.0.1'; > >>> loads: #('default'); > >>> file: 'ConfigurationOfXMLSupport'; > >>> repository: ' > http://www.squeaksource.com/MetacelloRepository']. > >>> spec package: 'DrGeoII-Core' with: [ > >>> spec requires: 'XML Parser']] > >>> > >>> -- > >>> Dr. Geo - http://drgeo.eu > >>> > >>> > >> > > > > > > -- > > Dr. Geo - http://drgeo.eu > > > > > > > -- www.tudorgirba.com "Every thing has its own flow"

June 4, 2013

Re: [Pharo-dev] MetacelloRepository

by StÃ©phane Ducasse

On Jun 4, 2013, at 7:18 AM, Hilaire Fernandes <hilaire.fernandes(a)gmail.com> wrote: > Stephane, > > The lack for me was the configurationOfXML with the XML-Parser version I > use (#20, a bit old). > As this is problably limited to my sistuation I recreate a > configurationOfXML in my own repo. > > Btw, I use XML-Parser for both read and write of XML file. > Was XML-support splited in two packages recently? yes Normally when loading the parser you would get the writer but damien cut it apart. Stef > > Thanks > > Hilaire > > Le 03/06/2013 22:08, StÃ©phane Ducasse a Ã©crit : >> Hilaire >> >> Normally this is XMLParser. I extracted just the XML parser and not all the tools. >> Now if you want to write you have XMLWriter. >> >> Let us know if it works. >> >> Stef >> >> On Jun 3, 2013, at 10:17 AM, Hilaire Fernandes <hilaire.fernandes(a)gmail.com> wrote: >> >>> Hello, >>> >>> To build DrGeo I use the squeaksource MetacelloRepository (example bellow). >>> I can not find it in SmalltalkHub? >>> I can see in PahroExtra/XMLParser ConfigurationOfXMLParser, is it the >>> same as ConfigurationOfXMLSupport. Can I find equivalent of >>> ConfigurationOfXMLSupport matching the exact same XML source version? >>> Unhelpful, I did not find how to browse the source form Smalltalkhub to >>> explore online the ConfigurationOf... code. >>> >>> Thanks >>> >>> Hilaire >>> >>> >>> baseline1012: spec >>> <version: '10.12-baseline'> >>> spec for: #pharo do: [ >>> spec blessing: #baseline. >>> spec project: 'XML Parser' with: [ >>> spec className: 'ConfigurationOfXMLSupport'; >>> version: '1.0.1'; >>> loads: #('default'); >>> file: 'ConfigurationOfXMLSupport'; >>> repository: 'http://www.squeaksource.com/MetacelloRepository']. >>> spec package: 'DrGeoII-Core' with: [ >>> spec requires: 'XML Parser']] >>> >>> -- >>> Dr. Geo - http://drgeo.eu >>> >>> >> > > > -- > Dr. Geo - http://drgeo.eu > >

June 4, 2013

Re: [Pharo-dev] A primitive to create a temporary directory?

by Damien Cassou

On Tue, Jun 4, 2013 at 5:32 AM, David T. Lewis <lewis(a)mail.msen.com> wrote: > I added the primitives to OSProcessPlugin and OSProcess. OSProcess support code > is in the latest OSProcess on SqueakSource: thank you so much David. Is it available for other OSes too? Best -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

June 4, 2013

Re: [Pharo-dev] jenkins running temporarily EC2

by Damien Cassou

On Mon, Jun 3, 2013 at 10:16 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > I added an emergency EC2 instance to our jenkins (and connected the mac slave via the EC2 instance) > that way we have an short term emergency solution up and running. > > I will switch back everything once the network problem at ci.inria.fr are fixed. thank you Camillo. Can I get ssh access to install some missing pieces? (http://rmod.lille.inria.fr/web/pier/private/HowTo/How-to-configure-a-Linux-…) -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

June 4, 2013

Re: [Pharo-dev] WhatsUp from: 2013-06-03 until: 2013-06-16

by Damien Cassou

On Mon, Jun 3, 2013 at 5:03 PM, <btc(a)openinworld.com> wrote: > Cool. You mention in its design specification that it will be cross > platform. Is that the case as this stage? I'm not sure if I follow Jenkins > logs properly but there seems only a Linux job running. it is already cross-platform as it is written in Pharo itself. For now, it has been successfully used in both Linux and MacOSX. > btw, Are there any plans for PharoLauncher to help report VM bugs? Eliot > once mentioned on [vm-dev] that the best VM bug reports provide a launch > script that reproduces the VM crash. The PharoLauncher could monitor VMs > that don't close cleanly, and then lead the user through generating such a > script. Then at the click of a button, the script, VM and image can be > packaged up for submitting to a bug tracker. Much further down the line, > PharoLauncher might even enable a VM flag to log all UI events from which a > crash-script could be generated. I'm not sure such a thing can be done automatically from another image. If you think you can do it, feel free to try: http://www.smalltalkhub.com/#!/~Pharo/PharoLauncher -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

June 4, 2013

Re: [Pharo-dev] [update 3.0] #30179

by Marcus Denker

Hmmâ¦ it seems this will only run after the slaves are back. Git tracker job is failing: https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-0-GitTracker/ As it seems to retry every couple of seconds, I have disable it in addition. So no updates anymoreâ¦ this is now the 4th day in a row. I guess we had not a stretch like that without update for a loooong timeâ¦ Marcus On Jun 4, 2013, at 8:33 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > 30179 > ----- > > 10825 Lots of Obsolete classes related to AST Navigation > https://pharo.fogbugz.com/f/cases/10825 > > 10837 CheckBox glitch fixed! > https://pharo.fogbugz.com/f/cases/10837 > > 10826 ./pharo Pharo.image -e 1 + 2 does not work > https://pharo.fogbugz.com/f/cases/10826 > > > Diff information: > http://smalltalkhub.com/mc/Pharo/Pharo30/main/System-CommandLine-MarcusDenk… > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Polymorph-Widgets-MarcusDenke… >

June 4, 2013

[update 3.0] #30179

by Marcus Denker

30179 ----- 10825 Lots of Obsolete classes related to AST Navigation https://pharo.fogbugz.com/f/cases/10825 10837 CheckBox glitch fixed! https://pharo.fogbugz.com/f/cases/10837 10826 ./pharo Pharo.image -e 1 + 2 does not work https://pharo.fogbugz.com/f/cases/10826 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/System-CommandLine-MarcusDenk… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Polymorph-Widgets-MarcusDenke…

June 4, 2013

Re: [Pharo-dev] get.moosetechnology.org

by Sven Van Caekenberghe

You know, "imitation is the sincerest form of flattery"â¦ On 03 Jun 2013, at 23:22, Camillo Bruni <camillobruni(a)gmail.com> wrote: > nice work :) > > On 2013-06-03, at 23:18, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> Hi, >> >> Andrei joined Camillo and extended a bit the ZeroConf infrastructure to make it easy for other projects to generate install scripts. >> >> As a consequence, we now have: >> http://get.moosetechnology.org >> >> The Moose-specific customization code can be found in the Moose-Development-Tools package from: >> http://www.smalltalkhub.com/mc/Moose/Moose/main >> >> The scripts are generated via the Pharo command line like: >> Pharo/pharo-ui moose-latest-dev-4.8.image moosezeroconf >> >> Cheers, >> Doru >> >> >> -- >> www.tudorgirba.com >> >> "No matter how many recipes we know, we still value a chef." >> >> >> >> >> >> >> > >

June 4, 2013

Re: [Pharo-dev] MetacelloRepository

by Hilaire Fernandes

Stephane, The lack for me was the configurationOfXML with the XML-Parser version I use (#20, a bit old). As this is problably limited to my sistuation I recreate a configurationOfXML in my own repo. Btw, I use XML-Parser for both read and write of XML file. Was XML-support splited in two packages recently? Thanks Hilaire Le 03/06/2013 22:08, StÃ©phane Ducasse a Ã©crit : > Hilaire > > Normally this is XMLParser. I extracted just the XML parser and not all the tools. > Now if you want to write you have XMLWriter. > > Let us know if it works. > > Stef > > On Jun 3, 2013, at 10:17 AM, Hilaire Fernandes <hilaire.fernandes(a)gmail.com> wrote: > >> Hello, >> >> To build DrGeo I use the squeaksource MetacelloRepository (example bellow). >> I can not find it in SmalltalkHub? >> I can see in PahroExtra/XMLParser ConfigurationOfXMLParser, is it the >> same as ConfigurationOfXMLSupport. Can I find equivalent of >> ConfigurationOfXMLSupport matching the exact same XML source version? >> Unhelpful, I did not find how to browse the source form Smalltalkhub to >> explore online the ConfigurationOf... code. >> >> Thanks >> >> Hilaire >> >> >> baseline1012: spec >> <version: '10.12-baseline'> >> spec for: #pharo do: [ >> spec blessing: #baseline. >> spec project: 'XML Parser' with: [ >> spec className: 'ConfigurationOfXMLSupport'; >> version: '1.0.1'; >> loads: #('default'); >> file: 'ConfigurationOfXMLSupport'; >> repository: 'http://www.squeaksource.com/MetacelloRepository']. >> spec package: 'DrGeoII-Core' with: [ >> spec requires: 'XML Parser']] >> >> -- >> Dr. Geo - http://drgeo.eu >> >> > -- Dr. Geo - http://drgeo.eu

June 4, 2013