- Pharo-dev - lists.pharo.org

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

[Pharo 9.0] Build #626: sendsToSuper-CleanBlockClosure

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

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

Aug. 28, 2020

[Pharo 9.0] Build #625: Cleanup-reflective-pragma

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

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

Aug. 28, 2020

[Pharo 9.0] Build #624: 7196-IconStyler-is-missing-visitEnglobingErrorNode

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

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

Aug. 28, 2020

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

by Christophe Demarey

> 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

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

by Sven Van Caekenberghe

> 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. > Regards, > Christophe > >> Le 28 aoÃ»t 2020 Ã 09:37, Christophe Demarey <christophe.demarey(a)inria.fr> a Ã©crit : >> >> Hi Dale, >> >> I would not call it a bug but an omission ;) >> It is hard to guess that a tool is scraping an html page to get data. >> >> Nevertheless, I will take a look today to find a solution for Glass to work again with smalltalkhub. >> Could you tell me what is the expected output? What is the html structure that is expected? >> >> I think I can find a solution to produce an html page through apache index listing and rewrite rules to catch URLs like http://smalltalkhub.com/mc/Seaside/Seaside30LGPL/main. >> >> Thanks, >> Christophe. >> >>> Le 27 aoÃ»t 2020 Ã 23:50, Dale Henrichs <dale.henrichs(a)gemtalksystems.com> a Ã©crit : >>> >>> That makes sense and confirms that the static site has a bug ... portions of my work are on hold until the SmalltalkHub issue is resolved and at least one other GemStone user is impacted, so far... >>> >>> Dale >>> >>> On 8/27/20 2:41 PM, Sven Van Caekenberghe wrote: >>>> The static version of StHub seems to always assume the client is Pharo, while the dynamic version used format=raw (which non-Pharo implementation did not include in their request for the listing) to send the Pharo specific response only then. >>>> >>>>> On 27 Aug 2020, at 23:34, Dale Henrichs <dale.henrichs(a)gemtalksystems.com> wrote: >>>>> >>>>> Depends upon how old that optimized code is ... as little as a 15 days ago, the last time my travis cron job ran successfully[1], the pharo code presumably was handling html page returns ... I'm pretty certain I haven't touched the Monticello HTTP handling code for nearly a decade:) >>>>> >>>>> Dale >>>>> >>>>> [1] https://travis-ci.org/github/GsDevKit/GsDevKit_home/builds/717364651 >>>>> >>>>> On 8/27/20 1:44 PM, Sven Van Caekenberghe wrote: >>>>>> Hmm, this is going to be a hard one. >>>>>> >>>>>> SmalltalkHub got optimised in Pharo, consider >>>>>> >>>>>> MCHttpRepository>>#parseFileNamesFromStream: aStream >>>>>> | names fullName | >>>>>> names := OrderedCollection new. >>>>>> [aStream atEnd] whileFalse: >>>>>> [[aStream upTo: $<. {$a. $A. nil} includes: aStream next] whileFalse. >>>>>> aStream upTo: $". >>>>>> aStream atEnd ifFalse: [ >>>>>> fullName := aStream upTo: $". >>>>>> names add: fullName urlDecoded ]]. >>>>>> ^ names >>>>>> >>>>>> vs. >>>>>> >>>>>> MCSmalltalkHubRepository>>#parseFileNamesFromStream: aNewLineDelimitedString >>>>>> ^ aNewLineDelimitedString >>>>>> ifNil: [ ^ OrderedCollection new ] >>>>>> ifNotNil: [ aNewLineDelimitedString substrings: String crlf ] >>>>>> >>>>>> In the old server code there was probably a way to detect what kind of client was making the request to determine how to respond. I am not sure a static server can do that (it is the format=raw query parameter, see MCSmalltalkHubRepository>>#loadAllFileNames). I also believe GZIP compressed files were returned in the optimised case. >>>>>> >>>>>> BTW, there exists code to generate the listing in >>>>>> >>>>>> ZnMonticelloRepository>>#repositoryListing >>>>>> ^ ZnHtmlOutputStream streamContents: [ :html | >>>>>> html page: 'Monticello Repository' do: [ >>>>>> html tag: #ul do: [ >>>>>> self mczEntries do: [ :each | >>>>>> html tag: #li do: [ >>>>>> html >>>>>> tag: #a >>>>>> attributes: { #href. each } >>>>>> with: each ] ] ] ] ] >>>>>> >>>>>> Sven >>>>>> >>>>>>> On 27 Aug 2020, at 22:29, Dale Henrichs <dale.henrichs(a)gemtalksystems.com> wrote: >>>>>>> >>>>>>> My guess is lies in the difference in the payload returned. >>>>>>> >>>>>>> http://www.squeaksource.com/MooseSQL/ produces a html page: >>>>>>> >>>>>>> <pnioijaecacnfagp.png> >>>>>>> >>>>>>> and the static smalltalkhub site does not: >>>>>>> >>>>>>> <lepkhlgeiolajoki.png> >>>>>>> >>>>>>> I think that all of the monticello web sites return an html web page listing of packages and presumably the static site should produce html ... I'm sure that the dynamic version of smalltalkhub produced html pages as well and for now we are caught between a rock and a hard place ... the dynamic site is flakey and the static site breaks existing Monticello package list reading code:) >>>>>>> >>>>>>> Dale >>>>>>> >>>>>>> On 8/27/20 1:04 PM, Dale Henrichs wrote: >>>>>>>> As I've started digging around, I have found that this url[1] does produce the correct list of mcz files in the browser, but is currently failing to produce any list at all in GLASS ... so there is a different mystery ... other than the fact that this url[1] was working prior(?) to the switchover (if in fact the DNS has propagated to all the right spots) and has been working for all of the other http Monticello repositories for over a decade:) >>>>>>>> >>>>>>>> I will continue digging ... >>>>>>>> >>>>>>>> Dale >>>>>>>> >>>>>>>> [1] http://smalltalkhub.com/mc/Seaside/Seaside30LGPL/main >>>>>>>> >>>>>>>> On 8/27/20 12:48 PM, Dale Henrichs wrote: >>>>>>>>> Christophe, >>>>>>>>> >>>>>>>>> There is a new(?) problem that we are having that has been reported in this thread on the GLASS list[1] where I am able to successfully download an mcz file [2], but get a `Not Found` error when I try to list the mcz files in a project[3]. The missing mcz list is consistent with the failed builds that I am now seeing on travis [4] and that are being reported by Brodbeck[1]. I have yet to get to a point where I can debug the problems directly and determine what is actually going on and of course I can't tell if these are the results of slow DNS propagation. >>>>>>>>> >>>>>>>>> In this case [2][3], the list of file shows up on the dynamic(?) site: >>>>>>>>> >>>>>>>>> <popmbnhcnehhanno.png> >>>>>>>>> >>>>>>>>> and can be downloaded by pressing the download for the selected mcz file, but the missing list of packages[3] is likely to be the root cause of the problem. >>>>>>>>> >>>>>>>>> Dale >>>>>>>>> >>>>>>>>> [1] http://forum.world.st/SmalltalkHub-packages-not-accessible-tt5120932.html >>>>>>>>> [2] http://smalltalkhub.com/mc/Seaside/Seaside30LGPL/main/Seaside-Swazoo-jf.19.… >>>>>>>>> [3] http://smalltalkhub.com/mc/Seaside/Seaside30LGPL >>>>>>>>> [4] https://travis-ci.org/github/GsDevKit/GsDevKit_home/jobs/721523221#L2411 >>>>>>>>> >>>>>>>>> On 8/27/20 5:36 AM, Christophe Demarey wrote: >>>>>>>>>> Hi Dale, >>>>>>>>>> >>>>>>>>>> Sorry, I did not see your message before. >>>>>>>>>> Yesterday, I switched smalltalkhub to the static version (a bit earlier than announced) to avoid frequent downtimes we had with smalltalkhub. >>>>>>>>>> I did not measure but downloads should now be faster and reliable. >>>>>>>>>> >>>>>>>>>> Do not hesitate to ping if you have any problem. >>>>>>>>>> >>>>>>>>>> Cheers, >>>>>>>>>> Christophe >>>>>>>>>> >>>>>>>>>>> Le 26 aoÃ»t 2020 Ã 18:12, Dale Henrichs <dale.henrichs(a)gemtalksystems.com> a Ã©crit : >>>>>>>>>>> >>>>>>>>>>> Well, I haven't see any email response, but today (after two days of brokenness), http://smalltalkhub.com/mc/dkh/metacello/main/Metacello-Base-dkh.109.mcz is now downloading successfully, so THANK YOU, to whoever fixed the problem! >>>>>>>>>>> >>>>>>>>>>> Dale >>>>>>>>>>> >>>>>>>>>>> On 8/25/20 9:02 AM, Dale Henrichs wrote: >>>>>>>>>>>> SmalltalkHub mcz downloads are broken ... looks like a mongo server has gone down? .... I ran into this problem running production tests yesterday and today I find that while the smalltalkhub site is up, I cannot download an mcz file, using this url: http://smalltalkhub.com/mc/dkh/metacello/main/Metacello-Base-dkh.109.mcz. >>>>>>>>>>>> >>>>>>>>>>>> If you are not going to keep the current smalltalkhub site functional, why don't you switch to the static site and give those of us who DEPEND upon static access to mcz files a reliable site to connect to ... I have plans to move completely away from mcz files, but I didn't plan on doing that this week ... and frankly I don't have the cycles to do that ... right now ... >>>>>>>>>>>> >>>>>>>>>>>> Here's a screenshot of a manual login and navigation to the mcz file that is failing to download: >>>>>>>>>>>> >>>>>>>>>>>> <jchancldefkbdajd.png> >>>>>>>>>>>> >>>>>>>>>>>> And when I press the `Download .mcz` button, I get the following "response" after a delay: >>>>>>>>>>>> >>>>>>>>>>>> <lnonccpgaamnnobg.png> >>>>>>>>>>>> >>>> >>> >> >> > >

Aug. 28, 2020