August 2020 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] 'VOMongoConnectionError' when dowloading mcz from smalltalkhub.com

by Christophe Demarey

I hope this time it will be fine. I removed the newline characters. I will also check if I can keep the original url in the browser rather than the redirected one. Regards, Christophe. > Le 29 aoÃ»t 2020 Ã 18:41, Dale Henrichs <dale.henrichs(a)gemtalksystems.com> a Ã©crit : > > Christophe, > > Again, I appreciate your effort, but you are not quite there. > > If you look at SqueakSource or GemSource html (attached), the html uses <br /> to create newlines on the page and in the Smalltalkhub page, you've inserted a newline as part of the href filename, while SqueakSource and GemSource (and the other monticello sites) do not include a newline in the href, so for better or worse, in GemStone the method MCReader>>canReadFileNamed: expects the filename to end with `.mcz` not a newline and all of the filenames parsed from the SmalltalkHub page are discarded as non-Monticello files. > > So if you eliminate the trailing newline in the href, the GemStone code should finally be happy. > > Thanks for your effort! > > Dale > > > On 8/28/20 3:05 PM, Christophe Demarey wrote: >> I understand that he new site is unusable if tools do not get the expected input. Sorry for the inconvenience. I was just not aware of this as Pharo uses the raw format. >> I had to set up a CGI to produce an html listing from the raw file. >> It should now be ok. Could you tell me if it works in GemStone now? >> >> Christophe >> >>> Le 28 aoÃ»t 2020 Ã 19:21, Dale Henrichs <dale.henrichs(a)gemtalksystems.com <mailto:dale.henrichs@gemtalksystems.com>> a Ã©crit : >>> >>> Christophe, >>> >>> I appreciate your effort, but I assume that you aren't finished yet? >>> >>> When I use the url from your message I get a `Not Found` error (note that I explicitly included a trailing slash in the url): >>> >>> <dkbjiegjmlbelgio.png> >>> >>> This is a bug (or omission) as well, since other Monticello sites produce the expected HTML output with or without a trailing slash. >>> >>> Without the trailing slash I get the same (non-html) response that was causing a problem before ... although something must have changed, because the GemStone command is now producing an error instead of an empty list ... Once you get the static site to produce the expected output, I'm confident that the GemStone errors will go away (this code has been running for about a decade on all Monticello html repositories). >>> >>> I suggest that you look at what is produced on SqueakSource (http://www.squeaksource.com/MooseSQL/ <http://www.squeaksource.com/MooseSQL/>) as an example of expected output of the mcz file listing ... this html page format has been used since 2003 for ALL (valid) monticello repositories. >>> >>> If it is not clear, the `?format=raw` option is a recent Pharo only option and when the dynamic site was running and the `?format-raw` option was OMITTED it produced output compatible with (http://www.squeaksource.com/MooseSQL/ <http://www.squeaksource.com/MooseSQL/>) ... >>> >>> Restoring HTML is *REQUIRED* for the static site to be a faithful replacement of the dynamic site... the format that is produced today is only compatible with the Pharo only `?format=raw` option. >>> >>> Bug or omission ... the static site is currently in worse shape than the dynamic site before the swap ... >>> >>> Dale >>> >>> On 8/28/20 2:12 AM, Christophe Demarey wrote: >>>>> Le 28 aoÃ»t 2020 Ã 10:15, Sven Van Caekenberghe <sven(a)stfx.eu> <mailto:sven@stfx.eu> a Ã©crit : >>>>> >>>>> >>>>> >>>>>> On 28 Aug 2020, at 10:13, Christophe Demarey <christophe.demarey(a)inria.fr> <mailto:christophe.demarey@inria.fr> wrote: >>>>>> >>>>>> Smalltalkhub is now to able to distinguish between raw and not raw mcz listing requests. >>>>>> Ex: >>>>>> http://smalltalkhub.com/mc/Seaside/Seaside30LGPL/main?format=raw <http://smalltalkhub.com/mc/Seaside/Seaside30LGPL/main?format=raw> >>>>>> http://smalltalkhub.com/mc/Seaside/Seaside30LGPL/main/ <http://smalltalkhub.com/mc/Seaside/Seaside30LGPL/main/> >>>>>> >>>>>> I already use the apache directory index for another page so I will not be able to modify this one. I guess the current index will Â« not work Â» because glass expect some HTML structure. >>>>>> Could you confirm and tell me what is the expected structure? >>>>> See my earlier mail with code. >>>> Thanks Sven >>>> >>>> >> > <squeaksource.html><gemsource.html>

Aug. 29, 2020

Re: [Pharo-dev] 'VOMongoConnectionError' when dowloading mcz from smalltalkhub.com

by Dale Henrichs

Christophe, Again, I appreciate your effort, but you are not quite there. If you look at SqueakSource or GemSource html (attached), the html uses <br /> to create newlines on the page and in the Smalltalkhub page, you've inserted a newline as part of the href filename, while SqueakSource and GemSource (and the other monticello sites) do not include a newline in the href, so for better or worse, in GemStone the method MCReader>>canReadFileNamed: expects the filename to end with `.mcz` not a newline and all of the filenames parsed from the SmalltalkHub page are discarded as non-Monticello files. So if you eliminate the trailing newline in the href, the GemStone code should finally be happy. Thanks for your effort! Dale On 8/28/20 3:05 PM, Christophe Demarey wrote: > I understand that he new site is unusable if tools do not get the > expected input. Sorry for the inconvenience. I was just not aware of > this as Pharo uses the raw format. > I had to set up a CGI to produce an html listing from the raw file. > It should now be ok. Could you tell me if it works in GemStone now? > > Christophe > >> Le 28 aoÃ»t 2020 Ã 19:21, Dale Henrichs >> <dale.henrichs(a)gemtalksystems.com >> <mailto:dale.henrichs@gemtalksystems.com>> a Ã©crit : >> >> Christophe, >> >> I appreciate your effort, but I assume that you aren't finished yet? >> >> When I use the url from your message I get a `Not Found` error (note >> that I explicitly included a trailing slash in the url): >> >> <dkbjiegjmlbelgio.png> >> >> This is a bug (or omission) as well, since other Monticello sites >> produce the expected HTML output with or without a trailing slash. >> >> Without the trailing slash I get the same (non-html) response that >> was causing a problem before ... although something must have >> changed, because the GemStone command is now producing an error >> instead of an empty list ... Once you get the static site to produce >> the expected output, I'm confident that the GemStone errors will go >> away (this code has been running for about a decade on all Monticello >> html repositories). >> >> I suggest that you look at what is produced on SqueakSource >> (http://www.squeaksource.com/MooseSQL/) as an example of expected >> output of the mcz file listing ... this html page format has been >> used since 2003 for ALL (valid) monticello repositories. >> >> If it is not clear, the `?format=raw` option is a recent Pharo only >> option and when the dynamic site was running and the `?format-raw` >> option was OMITTED it produced output compatible with >> (http://www.squeaksource.com/MooseSQL/) ... >> >> Restoring HTML is *REQUIRED* for the static site to be a faithful >> replacement of the dynamic site... the format that is produced today >> is only compatible with the Pharo only `?format=raw` option. >> >> Bug or omission ... the static site is currently in worse shape than >> the dynamic site before the swap ... >> >> Dale >> >> On 8/28/20 2:12 AM, Christophe Demarey wrote: >>>> Le 28 aoÃ»t 2020 Ã 10:15, Sven Van Caekenberghe<sven(a)stfx.eu> a Ã©crit : >>>> >>>> >>>> >>>>> On 28 Aug 2020, at 10:13, Christophe Demarey<christophe.demarey(a)inria.fr> wrote: >>>>> >>>>> Smalltalkhub is now to able to distinguish between raw and not raw mcz listing requests. >>>>> Ex: >>>>> http://smalltalkhub.com/mc/Seaside/Seaside30LGPL/main?format=raw >>>>> http://smalltalkhub.com/mc/Seaside/Seaside30LGPL/main/ >>>>> >>>>> I already use the apache directory index for another page so I will not be able to modify this one. I guess the current index will Â« not work Â» because glass expect some HTML structure. >>>>> Could you confirm and tell me what is the expected structure? >>>> See my earlier mail with code. >>> Thanks Sven >>> >>> >

Aug. 29, 2020

[Pharo 9.0] Build #630: hasLiteralSuchThat-do-not-look-into-Pragmas

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

There is a new Pharo build available! The status of the build #630 was: FAILURE. The Pull Request #7183 was integrated: "hasLiteralSuchThat-do-not-look-into-Pragmas" Pull request url: https://github.com/pharo-project/pharo/pull/7183 Issue Url: https://github.com/pharo-project/pharo/issues/hasLiteralSuchThat Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Aug. 29, 2020

[Pharo 9.0] Build #629: TestCase-use-classCommentBlank

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

There is a new Pharo build available! The status of the build #629 was: FAILURE. The Pull Request #7205 was integrated: "TestCase-use-classCommentBlank" Pull request url: https://github.com/pharo-project/pharo/pull/7205 Issue Url: https://github.com/pharo-project/pharo/issues/TestCase Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Aug. 29, 2020

Re: [Pharo-dev] 'VOMongoConnectionError' when dowloading mcz from smalltalkhub.com

by Sven Van Caekenberghe

Thanks looks fine to me, Christophe, thank you for the great work. The non format=raw case results in a redirect but that should be acceptable, both URL works both and without trailing / > On 29 Aug 2020, at 00:05, Christophe Demarey <christophe.demarey(a)inria.fr> wrote: > > I understand that he new site is unusable if tools do not get the expected input. Sorry for the inconvenience. I was just not aware of this as Pharo uses the raw format. > I had to set up a CGI to produce an html listing from the raw file. > It should now be ok. Could you tell me if it works in GemStone now? > > Christophe > >> Le 28 aoÃ»t 2020 Ã 19:21, Dale Henrichs <dale.henrichs(a)gemtalksystems.com> a Ã©crit : >> >> Christophe, >> >> I appreciate your effort, but I assume that you aren't finished yet? >> >> When I use the url from your message I get a `Not Found` error (note that I explicitly included a trailing slash in the url): >> >> <dkbjiegjmlbelgio.png> >> >> This is a bug (or omission) as well, since other Monticello sites produce the expected HTML output with or without a trailing slash. >> >> Without the trailing slash I get the same (non-html) response that was causing a problem before ... although something must have changed, because the GemStone command is now producing an error instead of an empty list ... Once you get the static site to produce the expected output, I'm confident that the GemStone errors will go away (this code has been running for about a decade on all Monticello html repositories). >> >> I suggest that you look at what is produced on SqueakSource (http://www.squeaksource.com/MooseSQL/) as an example of expected output of the mcz file listing ... this html page format has been used since 2003 for ALL (valid) monticello repositories. >> >> If it is not clear, the `?format=raw` option is a recent Pharo only option and when the dynamic site was running and the `?format-raw` option was OMITTED it produced output compatible with (http://www.squeaksource.com/MooseSQL/) ... >> >> Restoring HTML is *REQUIRED* for the static site to be a faithful replacement of the dynamic site... the format that is produced today is only compatible with the Pharo only `?format=raw` option. >> >> Bug or omission ... the static site is currently in worse shape than the dynamic site before the swap ... >> >> Dale >> >> On 8/28/20 2:12 AM, Christophe Demarey wrote: >>>> Le 28 aoÃ»t 2020 Ã 10:15, Sven Van Caekenberghe <sven(a)stfx.eu> >>>> a Ã©crit : >>>> >>>> >>>> >>>> >>>>> On 28 Aug 2020, at 10:13, Christophe Demarey <christophe.demarey(a)inria.fr> >>>>> wrote: >>>>> >>>>> Smalltalkhub is now to able to distinguish between raw and not raw mcz listing requests. >>>>> Ex: >>>>> >>>>> http://smalltalkhub.com/mc/Seaside/Seaside30LGPL/main?format=raw >>>>> >>>>> >>>>> http://smalltalkhub.com/mc/Seaside/Seaside30LGPL/main/ >>>>> >>>>> >>>>> I already use the apache directory index for another page so I will not be able to modify this one. I guess the current index will Â« not work Â» because glass expect some HTML structure. >>>>> Could you confirm and tell me what is the expected structure? >>>>> >>>> See my earlier mail with code. >>>> >>> Thanks Sven >>> >>> >>> >

Aug. 29, 2020

Re: [Pharo-dev] 'VOMongoConnectionError' when dowloading mcz from smalltalkhub.com

by Christophe Demarey

I understand that he new site is unusable if tools do not get the expected input. Sorry for the inconvenience. I was just not aware of this as Pharo uses the raw format. I had to set up a CGI to produce an html listing from the raw file. It should now be ok. Could you tell me if it works in GemStone now? Christophe > Le 28 aoÃ»t 2020 Ã 19:21, Dale Henrichs <dale.henrichs(a)gemtalksystems.com> a Ã©crit : > > Christophe, > > I appreciate your effort, but I assume that you aren't finished yet? > > When I use the url from your message I get a `Not Found` error (note that I explicitly included a trailing slash in the url): > > <dkbjiegjmlbelgio.png> > > This is a bug (or omission) as well, since other Monticello sites produce the expected HTML output with or without a trailing slash. > > Without the trailing slash I get the same (non-html) response that was causing a problem before ... although something must have changed, because the GemStone command is now producing an error instead of an empty list ... Once you get the static site to produce the expected output, I'm confident that the GemStone errors will go away (this code has been running for about a decade on all Monticello html repositories). > > I suggest that you look at what is produced on SqueakSource (http://www.squeaksource.com/MooseSQL/ <http://www.squeaksource.com/MooseSQL/>) as an example of expected output of the mcz file listing ... this html page format has been used since 2003 for ALL (valid) monticello repositories. > > If it is not clear, the `?format=raw` option is a recent Pharo only option and when the dynamic site was running and the `?format-raw` option was OMITTED it produced output compatible with (http://www.squeaksource.com/MooseSQL/ <http://www.squeaksource.com/MooseSQL/>) ... > > Restoring HTML is *REQUIRED* for the static site to be a faithful replacement of the dynamic site... the format that is produced today is only compatible with the Pharo only `?format=raw` option. > > Bug or omission ... the static site is currently in worse shape than the dynamic site before the swap ... > > Dale > > On 8/28/20 2:12 AM, Christophe Demarey wrote: >> >>> Le 28 aoÃ»t 2020 Ã 10:15, Sven Van Caekenberghe <sven(a)stfx.eu> <mailto:sven@stfx.eu> a Ã©crit : >>> >>> >>> >>>> On 28 Aug 2020, at 10:13, Christophe Demarey <christophe.demarey(a)inria.fr> <mailto:christophe.demarey@inria.fr> wrote: >>>> >>>> Smalltalkhub is now to able to distinguish between raw and not raw mcz listing requests. >>>> Ex: >>>> http://smalltalkhub.com/mc/Seaside/Seaside30LGPL/main?format=raw <http://smalltalkhub.com/mc/Seaside/Seaside30LGPL/main?format=raw> >>>> http://smalltalkhub.com/mc/Seaside/Seaside30LGPL/main/ <http://smalltalkhub.com/mc/Seaside/Seaside30LGPL/main/> >>>> >>>> I already use the apache directory index for another page so I will not be able to modify this one. I guess the current index will Â« not work Â» because glass expect some HTML structure. >>>> Could you confirm and tell me what is the expected structure? >>> See my earlier mail with code. >> Thanks Sven >> >>

Aug. 28, 2020

Re: [Pharo-dev] 'VOMongoConnectionError' when dowloading mcz from smalltalkhub.com

by Dale Henrichs

Christophe, I appreciate your effort, but I assume that you aren't finished yet? When I use the url from your message I get a `Not Found` error (note that I explicitly included a trailing slash in the url): This is a bug (or omission) as well, since other Monticello sites produce the expected HTML output with or without a trailing slash. Without the trailing slash I get the same (non-html) response that was causing a problem before ... although something must have changed, because the GemStone command is now producing an error instead of an empty list ... Once you get the static site to produce the expected output, I'm confident that the GemStone errors will go away (this code has been running for about a decade on all Monticello html repositories). I suggest that you look at what is produced on SqueakSource (http://www.squeaksource.com/MooseSQL/) as an example of expected output of the mcz file listing ... this html page format has been used since 2003 for ALL (valid) monticello repositories. If it is not clear, the `?format=raw` option is a recent Pharo only option and when the dynamic site was running and the `?format-raw` option was OMITTED it produced output compatible with (http://www.squeaksource.com/MooseSQL/) ... Restoring HTML is *REQUIRED* for the static site to be a faithful replacement of the dynamic site... the format that is produced today is only compatible with the Pharo only `?format=raw` option. Bug or omission ... the static site is currently in worse shape than the dynamic site before the swap ... Dale On 8/28/20 2:12 AM, Christophe Demarey wrote: > >> Le 28 aoÃ»t 2020 Ã 10:15, Sven Van Caekenberghe <sven(a)stfx.eu> a Ã©crit : >> >> >> >>> On 28 Aug 2020, at 10:13, Christophe Demarey <christophe.demarey(a)inria.fr> wrote: >>> >>> Smalltalkhub is now to able to distinguish between raw and not raw mcz listing requests. >>> Ex: >>> http://smalltalkhub.com/mc/Seaside/Seaside30LGPL/main?format=raw >>> http://smalltalkhub.com/mc/Seaside/Seaside30LGPL/main/ >>> >>> I already use the apache directory index for another page so I will not be able to modify this one. I guess the current index will Â« not work Â» because glass expect some HTML structure. >>> Could you confirm and tell me what is the expected structure? >> See my earlier mail with code. > Thanks Sven > >

Aug. 28, 2020

[Pharo 9.0] Build #628: CompiledMethod-isFaulty

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

There is a new Pharo build available! The status of the build #628 was: SUCCESS. The Pull Request #7192 was integrated: "CompiledMethod-isFaulty" Pull request url: https://github.com/pharo-project/pharo/pull/7192 Issue Url: https://github.com/pharo-project/pharo/issues/CompiledMethod Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Aug. 28, 2020

Re: [Pharo-dev] Why copy and pasting class definition invokes the class parser?

by StÃ©phane Ducasse

I got it. To determine the range of the selection the tools now use the AST. So this is fair. S > On 27 Aug 2020, at 20:51, Martin McClure <martin(a)hand2mouse.com> wrote: > > This is not definite knowledge, but some code I was digging through yesterday suggests that it *might* be for syntax highlighting of the class definition. > > Regards, > -Martin > > On 8/27/20 11:16 AM, StÃ©phane Ducasse wrote: >> Hi >> >> Iâm working on a nice class definition and Iâm exploringâ¦. >> And I wonder why copy and pasting class definition invokes the class parser? >> >> S >> -------------------------------------------- >> StÃ©phane Ducasse >> http://stephane.ducasse.free.fr <http://stephane.ducasse.free.fr/> / http://www.pharo.org <http://www.pharo.org/> >> 03 59 35 87 52 >> Assistant: Aurore Dalle >> FAX 03 59 57 78 50 >> TEL 03 59 35 86 16 >> S. Ducasse - Inria >> 40, avenue Halley, >> Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza >> Villeneuve d'Ascq 59650 >> France >> > -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Aurore Dalle FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

Aug. 28, 2020

[Pharo 9.0] Build #627: Missing offsets when mapping ast<->bytecode and when the first node is a fullblock

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

There is a new Pharo build available! The status of the build #627 was: FAILURE. The Pull Request #7120 was integrated: "Missing offsets when mapping ast<->bytecode and when the first node is a fullblock" Pull request url: https://github.com/pharo-project/pharo/pull/7120 Issue Url: https://github.com/pharo-project/pharo/issues/7087 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Aug. 28, 2020