- Pharo-users - lists.pharo.org

Re: [Pharo-users] [ANN] Pharo Chip Designer

by Hilaire

Nice! Hilaire -- Dr. Geo http://drgeo.eu

Aug. 11, 2019

Re: [Pharo-users] Old projects in ss3

by Dale Henrichs

Thanks Carlo ... that will certainly help me solve this problem ... I probably won't be able to get ss3 patched until after ESUG :), but now I know where to look ... Dale On 8/10/19 3:20 PM, sk via Pharo-users wrote: > Hi Dale > > Looks like a NumberParser error due to the chrome Accept request > header including "v=b3". > > Chrome sends something like: " > Accept: > text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3" > which seems to break on SS3. > You could try wget and receive the same error:Â wget --header="Accept: > text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3" > Â "http://ss3.gemtalksystems.com/ss/GTDImplementation" > If you remove v=b3 or modify it to by v=3 then there is no error. > > Somewhat related bug report for a different project: > https://github.com/emicklei/go-restful/issues/400 > > Carlo

Aug. 10, 2019

Re: [Pharo-users] Old projects in ss3

by sk

Hi Dale Looks like a NumberParser error due to the chrome Accept request header including "v=b3". Chrome sends something like: "Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3" which seems to break on SS3. You could try wget and receive the same error: wget --header="Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3" "http://ss3.gemtalksystems.com/ss/GTDImplementation" If you remove v=b3 or modify it to by v=3 then there is no error. Somewhat related bug report for a different project: https://github.com/emicklei/go-restful/issues/400 <https://github.com/emicklei/go-restful/issues/400> Carlo On 10 Aug 2019, at 23:32, Dale Henrichs <dale.henrichs(a)gemtalksystems.com> wrote: Here are some log entries from lighttpd (the first is the successful (200) firefox request and the second is the failed (500) chrome request): 50.xxx ss3.gemtalksystems.com - [10/Aug/2019:14:18:56 -0700] "GET /ss/STON.html HTTP/1.1" 200 6961 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0" 50.xxx ss3.gemtalksystems.com - [10/Aug/2019:14:19:21 -0700] "GET /ss/STON.html HTTP/1.1" 500 512 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/76.0.3809.100 Safari/537.36" Seaside server logs show no errors being logged, since this morning ...) No entries in fastcgi error log since midnight Aug 8th ... The 500 means there is some part of the system on our machine that is choking on the Chrome http request, but at this point it sure isn't obvious (to me)... Dale On 8/10/19 1:51 PM, Dale Henrichs wrote: > Well, here's the html that shows up in firefox ... can anyone spot anything on this page that would cause chrome to do anything different than firefox? > > <html><head><title>GTD Implementation</title></head><body onload="onLoad() <>"><h1>GTD Implementation</h1><a href="http://ss3.gemtalksystems.com/ss/GTDImplementation.html <>">SqueakSource3 project page</a>This project is an implementation of the GTD (Getting Things Done) practice described in David Allen's book.<a href="GTD-SergioFedi.20.mcz <>">GTD-SergioFedi.20.mcz</a> <a href="GTD-SergioFedi.19.mcz <>">GTD-SergioFedi.19.mcz</a> <a href="GTD-SergioFedi.18.mcz <>">GTD-SergioFedi.18.mcz</a> <a href="GTD-SergioFedi.17.mcz <>">GTD-SergioFedi.17.mcz</a> <a href="GTD-SergioFedi.16.mcz <>">GTD-SergioFedi.16.mcz</a> <a href="GTD-SergioFedi.15.mcz <>">GTD-SergioFedi.15.mcz</a> <a href="GTD-FedericoFigueredo.14.mcz <>">GTD-FedericoFigueredo.14.mcz</a> <a href="GTD-SergioFedi.13.mcz <>">GTD-SergioFedi.13.mcz</a> <a href="GTD-SergioFedi.12.mcz <>">GTD-SergioFedi.12.mcz</a> <a href="GTD-SergioFedi.11.mcz <>">GTD-SergioFedi.11.mcz</a> <a href="GTD-FedericoFigueredo.10.mcz <>">GTD-FedericoFigueredo.10.mcz</a> <a href="GTD-SergioFedi.9.mcz <>">GTD-SergioFedi.9.mcz</a> <a href="GTD-FedericoFigueredo.8.mcz <>">GTD-FedericoFigueredo.8.mcz</a> <a href="GTD-FedericoFigueredo.7.mcz <>">GTD-FedericoFigueredo.7.mcz</a> <a href="GTD-SergioFedi.6.mcz <>">GTD-SergioFedi.6.mcz</a> <a href="GTD-SergioFedi.5.mcz <>">GTD-SergioFedi.5.mcz</a> <a href="GTD-SergioFedi.4.mcz <>">GTD-SergioFedi.4.mcz</a> <a href="GTD-SergioFedi.3.mcz <>">GTD-SergioFedi.3.mcz</a> <a href="GTD-FedericoFigueredo.2.mcz <>">GTD-FedericoFigueredo.2.mcz</a> <a href="SUnit-UI-SergioFedi.111.mcz <>">SUnit-UI-SergioFedi.111.mcz</a> <a href="GTD-SergioFedi.1.mcz <>">GTD-SergioFedi.1.mcz</a> <script type="text/javascript <>">/*<![CDATA[*/function onLoad(){};/*]]>*/</script></body></html> > This url (front page) is displayed okay in chrome (http://ss3.gemtalksystems.com/ss <http://ss3.gemtalksystems.com/ss>)... > > FWIW, the following html (from GemSource: http://seaside.gemtalksystems.com/ss/PortablePetitParser/) displays just fine in chrome: <> > <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd" <http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd>><html><head><title></title></head><body><title>PortablePetitParser</title><h1>PortablePetitParser</h1><a href="http://seaside.gemtalksystems.com/ss/PortablePetitParser.html" <http://seaside.gemtalksystems.com/ss/PortablePetitParser.html>>GemSource project page</a><a href="ConfigurationOfPetitParser-EstebanLorenzano.27.mcz">ConfigurationOfPetitParser-EstebanLorenzano.27.mcz</a> <a href="PetitXPath-EstebanLorenzano.5.mcz">PetitXPath-EstebanLorenzano.5.mcz</a> <a href="ConfigurationOfPetitParser-EstebanLorenzano.26.mcz">ConfigurationOfPetitParser-EstebanLorenzano.26.mcz</a> <a href="PetitParserGemstone-EstebanLorenzano.2.mcz">PetitParserGemstone-EstebanLorenzano.2.mcz</a> <a href="ConfigurationOfPetitParser-EstebanLorenzano.25.mcz">ConfigurationOfPetitParser-EstebanLorenzano.25.mcz</a> <a href="PetitParser-EstebanLorenzano.224.mcz">PetitParser-EstebanLorenzano.224.mcz</a> <a href="ConfigurationOfPetitParser-EstebanLorenzano.24.mcz">ConfigurationOfPetitParser-EstebanLorenzano.24.mcz</a> <a href="PetitParser-EstebanLorenzano.223.mcz">PetitParser-EstebanLorenzano.223.mcz</a> <a href="PetitParser-EstebanLorenzano.222.mcz">PetitParser-EstebanLorenzano.222.mcz</a> <a href="PetitXPath-EstebanLorenzano.4.mcz">PetitXPath-EstebanLorenzano.4.mcz</a> <a href="PetitParserGemstone-EstebanLorenzano.1.mcz">PetitParserGemstone-EstebanLorenzano.1.mcz</a> <a href="ConfigurationOfPetitParser-EstebanLorenzano.17.mcz">ConfigurationOfPetitParser-EstebanLorenzano.17.mcz</a> <a href="PetitXml-EstebanLorenzano.32.mcz">PetitXml-EstebanLorenzano.32.mcz</a> <a href="PetitXPath-EstebanLorenzano.2.mcz">PetitXPath-EstebanLorenzano.2.mcz</a> <a href="PetitJson-EstebanLorenzano.7.mcz">PetitJson-EstebanLorenzano.7.mcz</a> <a href="PetitCSV-EstebanLorenzano.8.mcz">PetitCSV-EstebanLorenzano.8.mcz</a> <a href="PetitAnalyzer-EstebanLorenzano.39.mcz">PetitAnalyzer-EstebanLorenzano.39.mcz</a> <a href="PetitTests-EstebanLorenzano.33.mcz">PetitTests-EstebanLorenzano.33.mcz</a> <a href="PetitParser-EstebanLorenzano.218.mcz">PetitParser-EstebanLorenzano.218.mcz</a> <a href="ConfigurationOfPetitParser-EstebanLorenzano.23.mcz">ConfigurationOfPetitParser-EstebanLorenzano.23.mcz</a> <a href="PetitAnalyzer-EstebanLorenzano.44.mcz">PetitAnalyzer-EstebanLorenzano.44.mcz</a> <a href="ConfigurationOfPetitParser-EstebanLorenzano.22.mcz">ConfigurationOfPetitParser-EstebanLorenzano.22.mcz</a> <a href="PetitAnalyzer-EstebanLorenzano.43.mcz">PetitAnalyzer-EstebanLorenzano.43.mcz</a> <a href="ConfigurationOfPetitParser-EstebanLorenzano.21.mcz">ConfigurationOfPetitParser-EstebanLorenzano.21.mcz</a> <a href="PetitAnalyzer-EstebanLorenzano.42.mcz">PetitAnalyzer-EstebanLorenzano.42.mcz</a> <a href="PetitParser-EstebanLorenzano.221.mcz">PetitParser-EstebanLorenzano.221.mcz</a> <a href="ConfigurationOfPetitParser-EstebanLorenzano.20.mcz">ConfigurationOfPetitParser-EstebanLorenzano.20.mcz</a> <a href="PetitAnalyzer-EstebanLorenzano.41.mcz">PetitAnalyzer-EstebanLorenzano.41.mcz</a> <a href="ConfigurationOfPetitParser-EstebanLorenzano.19.mcz">ConfigurationOfPetitParser-EstebanLorenzano.19.mcz</a> <a href="PetitXml-EstebanLorenzano.33.mcz">PetitXml-EstebanLorenzano.33.mcz</a> <a href="PetitXPath-EstebanLorenzano.3.mcz">PetitXPath-EstebanLorenzano.3.mcz</a> <a href="PetitTests-EstebanLorenzano.35.mcz">PetitTests-EstebanLorenzano.35.mcz</a> <a href="PetitParser-EstebanLorenzano.220.mcz">PetitParser-EstebanLorenzano.220.mcz</a> <a href="PetitJson-EstebanLorenzano.8.mcz">PetitJson-EstebanLorenzano.8.mcz</a> <a href="PetitCSV-EstebanLorenzano.9.mcz">PetitCSV-EstebanLorenzano.9.mcz</a> <a href="PetitAnalyzer-EstebanLorenzano.40.mcz">PetitAnalyzer-EstebanLorenzano.40.mcz</a> <a href="PetitParser-EstebanLorenzano.219.mcz">PetitParser-EstebanLorenzano.219.mcz</a> <a href="ConfigurationOfPetitParser-EstebanLorenzano.18.mcz">ConfigurationOfPetitParser-EstebanLorenzano.18.mcz</a> <a href="PetitTests-EstebanLorenzano.34.mcz">PetitTests-EstebanLorenzano.34.mcz</a> > Other than the !DOCTYPE at the front, the two pages of html seem to similarly constructed ... > > The error message that you are seeing looks like an error that _would_ be generated by the seaside server, however there are no error messages showing up in the seaside server logs ... (other errors _are_ showing up, but the last seaside server log is from 11 am this morning (it's 2pm right now) ... I'll need to dig through some logs to see if I can find record of "the system administrator" being notified:) > > Dale > > On 8/10/19 8:40 AM, Sergio Fedi wrote: >> Ok, strangely, when I go to that page in Firefox it doesn't show that error. >> Tried to go with Chrome in incognito (so as to get rid of plug ins) and it still fails. >> >> Gonna try from within Pharo and if it fails I'll post again. >> >> Below are screenshots on how it fails or succeeds on each browser. >> >> In firefox: >> >> <image.png> >> >> In chrome: >> <image.png> >> >> >> On Fri, Aug 9, 2019 at 10:30 PM Paul DeBruicker <pdebruic(a)gmail.com <mailto:pdebruic@gmail.com>> wrote: >> Also did you use the URL of the page your repo is on? Seems like maybe you >> did from the image. You shouldn't. >> >> >> You should use the Monticello Repository specification shown on the repo >> page when you hover over Monticello Repository in the Getting The Code >> section of the project page on ss3. >> >> e.g. >> >> MCHttpRepository >> location: 'http://ss3.gemtalksystems.com/ss/GTDImplementation <http://ss3.gemtalksystems.com/ss/GTDImplementation>' >> user: '' >> password: '' >> >> >> >> >> >> >> >> Paul DeBruicker wrote >> > what is the repo you're having trouble reading? >> > >> > >> > Sergio Fedi wrote >> >> Hello, >> >> >> >> I'm coming back after a few years (Pharo 5.0) and tried to take a look >> >> and >> >> download some projects I have on ss3. >> >> >> >> I'm using a Pharo 7.0 image. >> >> >> >> Going to the ss3 site I find that I can't access my projects, a "Reading >> >> a >> >> number failed: a digit between 0 and 9 expected" error shows in the page. >> >> >> >> Trying to view them from Monticello, after adding the appropriate >> >> repository it shows weird characters for the name and versions and it is >> >> unable to load them. >> >> >> >> [image: image.png] >> >> >> >> What am I missing/doing wrong? >> >> >> >> Thanks! >> >> >> >> >> >> image.png (182K) >> >> <http://forum.world.st/attachment/5102137/0/image.png&gt <http://forum.world.st/attachment/5102137/0/image.png&gt>; >> > >> > >> > >> > >> > >> > -- >> > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html <http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html> >> >> >> >> >> >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html <http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html> >>

Aug. 10, 2019

Re: [Pharo-users] Old projects in ss3

by Dale Henrichs

Here are some log entries from lighttpd (the first is the successful (200) firefox request and the second is the failed (500) chrome request): 50.xxx ss3.gemtalksystems.com - [10/Aug/2019:14:18:56 -0700] "GET /ss/STON.html HTTP/1.1" 200 6961 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0" 50.xxx ss3.gemtalksystems.com - [10/Aug/2019:14:19:21 -0700] "GET /ss/STON.html HTTP/1.1" 500 512 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/76.0.3809.100 Safari/537.36" Seaside server logs show no errors being logged, since this morning ...) No entries in fastcgi error log since midnight Aug 8th ... The 500 means there is some part of the system on our machine that is choking on the Chrome http request, but at this point it sure isn't obvious (to me)... Dale On 8/10/19 1:51 PM, Dale Henrichs wrote: > > Well, here's the html that shows up in firefox ... can anyone spot > anything on this page that would cause chrome to do anything different > than firefox? > > <html><head><title>GTD Implementation</title></head><body > onload="onLoad()"><h1>GTD Implementation</h1><a > href="http://ss3.gemtalksystems.com/ss/GTDImplementation.html">SqueakSource3 > project page</a>This project is an implementation of the GTD > (Getting Things Done) practice described in David Allen's book.<a > href="GTD-SergioFedi.20.mcz">GTD-SergioFedi.20.mcz</a> <a > href="GTD-SergioFedi.19.mcz">GTD-SergioFedi.19.mcz</a> <a > href="GTD-SergioFedi.18.mcz">GTD-SergioFedi.18.mcz</a> <a > href="GTD-SergioFedi.17.mcz">GTD-SergioFedi.17.mcz</a> <a > href="GTD-SergioFedi.16.mcz">GTD-SergioFedi.16.mcz</a> <a > href="GTD-SergioFedi.15.mcz">GTD-SergioFedi.15.mcz</a> <a > href="GTD-FedericoFigueredo.14.mcz">GTD-FedericoFigueredo.14.mcz</a> <a > href="GTD-SergioFedi.13.mcz">GTD-SergioFedi.13.mcz</a> <a > href="GTD-SergioFedi.12.mcz">GTD-SergioFedi.12.mcz</a> <a > href="GTD-SergioFedi.11.mcz">GTD-SergioFedi.11.mcz</a> <a > href="GTD-FedericoFigueredo.10.mcz">GTD-FedericoFigueredo.10.mcz</a> <a > href="GTD-SergioFedi.9.mcz">GTD-SergioFedi.9.mcz</a> <a > href="GTD-FedericoFigueredo.8.mcz">GTD-FedericoFigueredo.8.mcz</a> <a > href="GTD-FedericoFigueredo.7.mcz">GTD-FedericoFigueredo.7.mcz</a> <a > href="GTD-SergioFedi.6.mcz">GTD-SergioFedi.6.mcz</a> <a > href="GTD-SergioFedi.5.mcz">GTD-SergioFedi.5.mcz</a> <a > href="GTD-SergioFedi.4.mcz">GTD-SergioFedi.4.mcz</a> <a > href="GTD-SergioFedi.3.mcz">GTD-SergioFedi.3.mcz</a> <a > href="GTD-FedericoFigueredo.2.mcz">GTD-FedericoFigueredo.2.mcz</a> <a > href="SUnit-UI-SergioFedi.111.mcz">SUnit-UI-SergioFedi.111.mcz</a> <a > href="GTD-SergioFedi.1.mcz">GTD-SergioFedi.1.mcz</a> <script > type="text/javascript">/*<![CDATA[*/function > onLoad(){};/*]]>*/</script></body></html> > This url (front page) is displayed okay in chrome > (http://ss3.gemtalksystems.com/ss) > > FWIW, the following html (from GemSource: > http://seaside.gemtalksystems.com/ss/PortablePetitParser/) displays > just fine in chrome: > <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html><head><title></title></head><body><title>PortablePetitParser</title><h1>PortablePetitParser</h1><a href="http://seaside.gemtalksystems.com/ss/PortablePetitParser.html">GemSource project page</a><a href="ConfigurationOfPetitParser-EstebanLorenzano.27.mcz">ConfigurationOfPetitParser-EstebanLorenzano.27.mcz</a> <a href="PetitXPath-EstebanLorenzano.5.mcz">PetitXPath-EstebanLorenzano.5.mcz</a> <a href="ConfigurationOfPetitParser-EstebanLorenzano.26.mcz">ConfigurationOfPetitParser-EstebanLorenzano.26.mcz</a> <a href="PetitParserGemstone-EstebanLorenzano.2.mcz">PetitParserGemstone-EstebanLorenzano.2.mcz</a> <a href="ConfigurationOfPetitParser-EstebanLorenzano.25.mcz">ConfigurationOfPetitParser-EstebanLorenzano.25.mcz</a> <a href="PetitParser-EstebanLorenzano.224.mcz">PetitParser-EstebanLorenzano.224.mcz</a> <a href="ConfigurationOfPetitParser-EstebanLorenzano.24.mcz">ConfigurationOfPetitParser-EstebanLorenzano.24.mcz</a> <a href="PetitParser-EstebanLorenzano.223.mcz">PetitParser-EstebanLorenzano.223.mcz</a> <a href="PetitParser-EstebanLorenzano.222.mcz">PetitParser-EstebanLorenzano.222.mcz</a> <a href="PetitXPath-EstebanLorenzano.4.mcz">PetitXPath-EstebanLorenzano.4.mcz</a> <a href="PetitParserGemstone-EstebanLorenzano.1.mcz">PetitParserGemstone-EstebanLorenzano.1.mcz</a> <a href="ConfigurationOfPetitParser-EstebanLorenzano.17.mcz">ConfigurationOfPetitParser-EstebanLorenzano.17.mcz</a> <a href="PetitXml-EstebanLorenzano.32.mcz">PetitXml-EstebanLorenzano.32.mcz</a> <a href="PetitXPath-EstebanLorenzano.2.mcz">PetitXPath-EstebanLorenzano.2.mcz</a> <a href="PetitJson-EstebanLorenzano.7.mcz">PetitJson-EstebanLorenzano.7.mcz</a> <a href="PetitCSV-EstebanLorenzano.8.mcz">PetitCSV-EstebanLorenzano.8.mcz</a> <a href="PetitAnalyzer-EstebanLorenzano.39.mcz">PetitAnalyzer-EstebanLorenzano.39.mcz</a> <a href="PetitTests-EstebanLorenzano.33.mcz">PetitTests-EstebanLorenzano.33.mcz</a> <a href="PetitParser-EstebanLorenzano.218.mcz">PetitParser-EstebanLorenzano.218.mcz</a> <a href="ConfigurationOfPetitParser-EstebanLorenzano.23.mcz">ConfigurationOfPetitParser-EstebanLorenzano.23.mcz</a> <a href="PetitAnalyzer-EstebanLorenzano.44.mcz">PetitAnalyzer-EstebanLorenzano.44.mcz</a> <a href="ConfigurationOfPetitParser-EstebanLorenzano.22.mcz">ConfigurationOfPetitParser-EstebanLorenzano.22.mcz</a> <a href="PetitAnalyzer-EstebanLorenzano.43.mcz">PetitAnalyzer-EstebanLorenzano.43.mcz</a> <a href="ConfigurationOfPetitParser-EstebanLorenzano.21.mcz">ConfigurationOfPetitParser-EstebanLorenzano.21.mcz</a> <a href="PetitAnalyzer-EstebanLorenzano.42.mcz">PetitAnalyzer-EstebanLorenzano.42.mcz</a> <a href="PetitParser-EstebanLorenzano.221.mcz">PetitParser-EstebanLorenzano.221.mcz</a> <a href="ConfigurationOfPetitParser-EstebanLorenzano.20.mcz">ConfigurationOfPetitParser-EstebanLorenzano.20.mcz</a> <a href="PetitAnalyzer-EstebanLorenzano.41.mcz">PetitAnalyzer-EstebanLorenzano.41.mcz</a> <a href="ConfigurationOfPetitParser-EstebanLorenzano.19.mcz">ConfigurationOfPetitParser-EstebanLorenzano.19.mcz</a> <a href="PetitXml-EstebanLorenzano.33.mcz">PetitXml-EstebanLorenzano.33.mcz</a> <a href="PetitXPath-EstebanLorenzano.3.mcz">PetitXPath-EstebanLorenzano.3.mcz</a> <a href="PetitTests-EstebanLorenzano.35.mcz">PetitTests-EstebanLorenzano.35.mcz</a> <a href="PetitParser-EstebanLorenzano.220.mcz">PetitParser-EstebanLorenzano.220.mcz</a> <a href="PetitJson-EstebanLorenzano.8.mcz">PetitJson-EstebanLorenzano.8.mcz</a> <a href="PetitCSV-EstebanLorenzano.9.mcz">PetitCSV-EstebanLorenzano.9.mcz</a> <a href="PetitAnalyzer-EstebanLorenzano.40.mcz">PetitAnalyzer-EstebanLorenzano.40.mcz</a> <a href="PetitParser-EstebanLorenzano.219.mcz">PetitParser-EstebanLorenzano.219.mcz</a> <a href="ConfigurationOfPetitParser-EstebanLorenzano.18.mcz">ConfigurationOfPetitParser-EstebanLorenzano.18.mcz</a> <a href="PetitTests-EstebanLorenzano.34.mcz">PetitTests-EstebanLorenzano.34.mcz</a> > Other than the !DOCTYPE at the front, the two pages of html seem to > similarly constructed ... > > The error message that you are seeing looks like an error that _would_ > be generated by the seaside server, however there are no error > messages showing up in the seaside server logs ... (other errors _are_ > showing up, but the last seaside server log is from 11 am this morning > (it's 2pm right now) ... I'll need to dig through some logs to see if > I can find record of "the system administrator" being notified:) > > Dale > > On 8/10/19 8:40 AM, Sergio Fedi wrote: >> Ok, strangely, when I go to that page in Firefox it doesn't show that >> error. >> Tried to go with Chrome in incognito (so as to get rid of plug ins) >> and it still fails. >> >> Gonna try from within Pharo and if it fails I'll post again. >> >> Below are screenshots on how it fails or succeeds on each browser. >> >> In firefox: >> >> image.png >> >> In chrome: >> image.png >> >> >> On Fri, Aug 9, 2019 at 10:30 PM Paul DeBruicker <pdebruic(a)gmail.com >> <mailto:pdebruic@gmail.com>> wrote: >> >> Also did you use the URL of the page your repo is on?Â Seems like >> maybe you >> did from the image. You shouldn't. >> >> >> You should use the Monticello Repository specification shown on >> the repo >> page when you hover over Monticello Repository in the Getting The >> Code >> section of the project page on ss3. >> >> e.g. >> >> MCHttpRepository >> Â Â location: 'http://ss3.gemtalksystems.com/ss/GTDImplementation' >> Â Â user: '' >> Â Â password: '' >> >> >> >> >> >> >> >> Paul DeBruicker wrote >> > what is the repo you're having trouble reading? >> > >> > >> > Sergio Fedi wrote >> >> Hello, >> >> >> >> I'm coming back after a few years (Pharo 5.0) and tried to >> take a look >> >> and >> >> download some projects I have on ss3. >> >> >> >> I'm using a Pharo 7.0 image. >> >> >> >> Going to the ss3 site I find that I can't access my projects, >> a "Reading >> >> a >> >> number failed: a digit between 0 and 9 expected" error shows >> in the page. >> >> >> >> Trying to view them from Monticello, after adding the appropriate >> >> repository it shows weird characters for the name and versions >> and it is >> >> unable to load them. >> >> >> >> [image: image.png] >> >> >> >> What am I missing/doing wrong? >> >> >> >> Thanks! >> >> >> >> >> >> image.png (182K) >> >> <http://forum.world.st/attachment/5102137/0/image.png> >> > >> > >> > >> > >> > >> > -- >> > Sent from: >> http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> >> >> >> >> >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >>

Aug. 10, 2019

Re: [Pharo-users] Old projects in ss3

by Dale Henrichs

Well, here's the html that shows up in firefox ... can anyone spot anything on this page that would cause chrome to do anything different than firefox? <html><head><title>GTD Implementation</title></head><body onload="onLoad()"><h1>GTD Implementation</h1><a href="http://ss3.gemtalksystems.com/ss/GTDImplementation.html">SqueakSource3 project page</a>This project is an implementation of the GTD (Getting Things Done) practice described in David Allen's book.<a href="GTD-SergioFedi.20.mcz">GTD-SergioFedi.20.mcz</a> <a href="GTD-SergioFedi.19.mcz">GTD-SergioFedi.19.mcz</a> <a href="GTD-SergioFedi.18.mcz">GTD-SergioFedi.18.mcz</a> <a href="GTD-SergioFedi.17.mcz">GTD-SergioFedi.17.mcz</a> <a href="GTD-SergioFedi.16.mcz">GTD-SergioFedi.16.mcz</a> <a href="GTD-SergioFedi.15.mcz">GTD-SergioFedi.15.mcz</a> <a href="GTD-FedericoFigueredo.14.mcz">GTD-FedericoFigueredo.14.mcz</a> <a href="GTD-SergioFedi.13.mcz">GTD-SergioFedi.13.mcz</a> <a href="GTD-SergioFedi.12.mcz">GTD-SergioFedi.12.mcz</a> <a href="GTD-SergioFedi.11.mcz">GTD-SergioFedi.11.mcz</a> <a href="GTD-FedericoFigueredo.10.mcz">GTD-FedericoFigueredo.10.mcz</a> <a href="GTD-SergioFedi.9.mcz">GTD-SergioFedi.9.mcz</a> <a href="GTD-FedericoFigueredo.8.mcz">GTD-FedericoFigueredo.8.mcz</a> <a href="GTD-FedericoFigueredo.7.mcz">GTD-FedericoFigueredo.7.mcz</a> <a href="GTD-SergioFedi.6.mcz">GTD-SergioFedi.6.mcz</a> <a href="GTD-SergioFedi.5.mcz">GTD-SergioFedi.5.mcz</a> <a href="GTD-SergioFedi.4.mcz">GTD-SergioFedi.4.mcz</a> <a href="GTD-SergioFedi.3.mcz">GTD-SergioFedi.3.mcz</a> <a href="GTD-FedericoFigueredo.2.mcz">GTD-FedericoFigueredo.2.mcz</a> <a href="SUnit-UI-SergioFedi.111.mcz">SUnit-UI-SergioFedi.111.mcz</a> <a href="GTD-SergioFedi.1.mcz">GTD-SergioFedi.1.mcz</a> <script type="text/javascript">/*<![CDATA[*/function onLoad(){};/*]]>*/</script></body></html> This url (front page) is displayed okay in chrome (http://ss3.gemtalksystems.com/ss) FWIW, the following html (from GemSource: http://seaside.gemtalksystems.com/ss/PortablePetitParser/) displays just fine in chrome: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html><head><title></title></head><body><title>PortablePetitParser</title><h1>PortablePetitParser</h1><a href="http://seaside.gemtalksystems.com/ss/PortablePetitParser.html">GemSource project page</a><a href="ConfigurationOfPetitParser-EstebanLorenzano.27.mcz">ConfigurationOfPetitParser-EstebanLorenzano.27.mcz</a> <a href="PetitXPath-EstebanLorenzano.5.mcz">PetitXPath-EstebanLorenzano.5.mcz</a> <a href="ConfigurationOfPetitParser-EstebanLorenzano.26.mcz">ConfigurationOfPetitParser-EstebanLorenzano.26.mcz</a> <a href="PetitParserGemstone-EstebanLorenzano.2.mcz">PetitParserGemstone-EstebanLorenzano.2.mcz</a> <a href="ConfigurationOfPetitParser-EstebanLorenzano.25.mcz">ConfigurationOfPetitParser-EstebanLorenzano.25.mcz</a> <a href="PetitParser-EstebanLorenzano.224.mcz">PetitParser-EstebanLorenzano.224.mcz</a> <a href="ConfigurationOfPetitParser-EstebanLorenzano.24.mcz">ConfigurationOfPetitParser-EstebanLorenzano.24.mcz</a> <a href="PetitParser-EstebanLorenzano.223.mcz">PetitParser-EstebanLorenzano.223.mcz</a> <a href="PetitParser-EstebanLorenzano.222.mcz">PetitParser-EstebanLorenzano.222.mcz</a> <a href="PetitXPath-EstebanLorenzano.4.mcz">PetitXPath-EstebanLorenzano.4.mcz</a> <a href="PetitParserGemstone-EstebanLorenzano.1.mcz">PetitParserGemstone-EstebanLorenzano.1.mcz</a> <a href="ConfigurationOfPetitParser-EstebanLorenzano.17.mcz">ConfigurationOfPetitParser-EstebanLorenzano.17.mcz</a> <a href="PetitXml-EstebanLorenzano.32.mcz">PetitXml-EstebanLorenzano.32.mcz</a> <a href="PetitXPath-EstebanLorenzano.2.mcz">PetitXPath-EstebanLorenzano.2.mcz</a> <a href="PetitJson-EstebanLorenzano.7.mcz">PetitJson-EstebanLorenzano.7.mcz</a> <a href="PetitCSV-EstebanLorenzano.8.mcz">PetitCSV-EstebanLorenzano.8.mcz</a> <a href="PetitAnalyzer-EstebanLorenzano.39.mcz">PetitAnalyzer-EstebanLorenzano.39.mcz</a> <a href="PetitTests-EstebanLorenzano.33.mcz">PetitTests-EstebanLorenzano.33.mcz</a> <a href="PetitParser-EstebanLorenzano.218.mcz">PetitParser-EstebanLorenzano.218.mcz</a> <a href="ConfigurationOfPetitParser-EstebanLorenzano.23.mcz">ConfigurationOfPetitParser-EstebanLorenzano.23.mcz</a> <a href="PetitAnalyzer-EstebanLorenzano.44.mcz">PetitAnalyzer-EstebanLorenzano.44.mcz</a> <a href="ConfigurationOfPetitParser-EstebanLorenzano.22.mcz">ConfigurationOfPetitParser-EstebanLorenzano.22.mcz</a> <a href="PetitAnalyzer-EstebanLorenzano.43.mcz">PetitAnalyzer-EstebanLorenzano.43.mcz</a> <a href="ConfigurationOfPetitParser-EstebanLorenzano.21.mcz">ConfigurationOfPetitParser-EstebanLorenzano.21.mcz</a> <a href="PetitAnalyzer-EstebanLorenzano.42.mcz">PetitAnalyzer-EstebanLorenzano.42.mcz</a> <a href="PetitParser-EstebanLorenzano.221.mcz">PetitParser-EstebanLorenzano.221.mcz</a> <a href="ConfigurationOfPetitParser-EstebanLorenzano.20.mcz">ConfigurationOfPetitParser-EstebanLorenzano.20.mcz</a> <a href="PetitAnalyzer-EstebanLorenzano.41.mcz">PetitAnalyzer-EstebanLorenzano.41.mcz</a> <a href="ConfigurationOfPetitParser-EstebanLorenzano.19.mcz">ConfigurationOfPetitParser-EstebanLorenzano.19.mcz</a> <a href="PetitXml-EstebanLorenzano.33.mcz">PetitXml-EstebanLorenzano.33.mcz</a> <a href="PetitXPath-EstebanLorenzano.3.mcz">PetitXPath-EstebanLorenzano.3.mcz</a> <a href="PetitTests-EstebanLorenzano.35.mcz">PetitTests-EstebanLorenzano.35.mcz</a> <a href="PetitParser-EstebanLorenzano.220.mcz">PetitParser-EstebanLorenzano.220.mcz</a> <a href="PetitJson-EstebanLorenzano.8.mcz">PetitJson-EstebanLorenzano.8.mcz</a> <a href="PetitCSV-EstebanLorenzano.9.mcz">PetitCSV-EstebanLorenzano.9.mcz</a> <a href="PetitAnalyzer-EstebanLorenzano.40.mcz">PetitAnalyzer-EstebanLorenzano.40.mcz</a> <a href="PetitParser-EstebanLorenzano.219.mcz">PetitParser-EstebanLorenzano.219.mcz</a> <a href="ConfigurationOfPetitParser-EstebanLorenzano.18.mcz">ConfigurationOfPetitParser-EstebanLorenzano.18.mcz</a> <a href="PetitTests-EstebanLorenzano.34.mcz">PetitTests-EstebanLorenzano.34.mcz</a> Other than the !DOCTYPE at the front, the two pages of html seem to similarly constructed ... The error message that you are seeing looks like an error that _would_ be generated by the seaside server, however there are no error messages showing up in the seaside server logs ... (other errors _are_ showing up, but the last seaside server log is from 11 am this morning (it's 2pm right now) ... I'll need to dig through some logs to see if I can find record of "the system administrator" being notified:) Dale On 8/10/19 8:40 AM, Sergio Fedi wrote: > Ok, strangely, when I go to that page in Firefox it doesn't show that > error. > Tried to go with Chrome in incognito (so as to get rid of plug ins) > and it still fails. > > Gonna try from within Pharo and if it fails I'll post again. > > Below are screenshots on how it fails or succeeds on each browser. > > In firefox: > > image.png > > In chrome: > image.png > > > On Fri, Aug 9, 2019 at 10:30 PM Paul DeBruicker <pdebruic(a)gmail.com > <mailto:pdebruic@gmail.com>> wrote: > > Also did you use the URL of the page your repo is on?Â Seems like > maybe you > did from the image. You shouldn't. > > > You should use the Monticello Repository specification shown on > the repo > page when you hover over Monticello Repository in the Getting The Code > section of the project page on ss3. > > e.g. > > MCHttpRepository > Â Â location: 'http://ss3.gemtalksystems.com/ss/GTDImplementation' > Â Â user: '' > Â Â password: '' > > > > > > > > Paul DeBruicker wrote > > what is the repo you're having trouble reading? > > > > > > Sergio Fedi wrote > >> Hello, > >> > >> I'm coming back after a few years (Pharo 5.0) and tried to take > a look > >> and > >> download some projects I have on ss3. > >> > >> I'm using a Pharo 7.0 image. > >> > >> Going to the ss3 site I find that I can't access my projects, a > "Reading > >> a > >> number failed: a digit between 0 and 9 expected" error shows in > the page. > >> > >> Trying to view them from Monticello, after adding the appropriate > >> repository it shows weird characters for the name and versions > and it is > >> unable to load them. > >> > >> [image: image.png] > >> > >> What am I missing/doing wrong? > >> > >> Thanks! > >> > >> > >> image.png (182K) > >> <http://forum.world.st/attachment/5102137/0/image.png> > > > > > > > > > > > > -- > > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

Aug. 10, 2019

Re: [Pharo-users] [ANN] Pharo Chip Designer

by Santiago Bragagnolo

woaaaa so nice. El sÃ¡b., 10 ago. 2019 a las 13:16, Pavel Krivanek (<pavel.krivanek(a)gmail.com>) escribiÃ³: > Hi, > > I have created a little program based on an old educational game by > Zachtronics (KOHCTPYKTOP: Engineer of the People[1]) named Pharo Chip > Designer. > > It is an inaccurate and highly simplified tool for the design of silicon > chip layouts. Unlike common tools for logic circuits designs, in Pharo Chip > Designer, you need to face the real-life problems like propagation delays > or limited amount of layers and available substrate area. > > https://github.com/pavel-krivanek/PharoChipDesigner > <https://github.com/pavel-krivanek/PharoChipDesigner/blob/master/README.md> > > It contains levels from the original game, but you can play with your > custom designs on larger surfaces. And of course, use all the Pharo power > to control the I/O signals. > > The Pharo Chip Designer required Pharo 8.0 and Spec2. > > Cheers, > -- Pavel > > [1] http://www.zachtronics.com/kohctpyktop-engineer-of-the-people/ >

Aug. 10, 2019

Re: [Pharo-users] [ANN] Pharo Chip Designer

by Sven Van Caekenberghe

Great hack, really nice demo of what is possible (if you are an exceptional programmer ;-) > On 10 Aug 2019, at 13:15, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > Hi, > > I have created a little program based on an old educational game by Zachtronics (KOHCTPYKTOP: Engineer of the People[1]) named Pharo Chip Designer. > > It is an inaccurate and highly simplified tool for the design of silicon chip layouts. Unlike common tools for logic circuits designs, in Pharo Chip Designer, you need to face the real-life problems like propagation delays or limited amount of layers and available substrate area. > > https://github.com/pavel-krivanek/PharoChipDesigner > > It contains levels from the original game, but you can play with your custom designs on larger surfaces. And of course, use all the Pharo power to control the I/O signals. > > The Pharo Chip Designer required Pharo 8.0 and Spec2. > > Cheers, > -- Pavel > > [1] http://www.zachtronics.com/kohctpyktop-engineer-of-the-people/

Aug. 10, 2019

Re: [Pharo-users] Possible Spam(11.174):Re: Old projects in ss3

by David Shaffer

If itâs any help, I have the same problem: http://ss3.gemtalksystems.com/ss/GOODS.html/Overview?_s=ZrZWgaJfvGoNIvPS&_k… <http://ss3.gemtalksystems.com/ss/GOODS.html/Overview?_s=ZrZWgaJfvGoNIvPS&_k…> Gives: > On Aug 9, 2019, at 9:30 PM, Paul DeBruicker <pdebruic(a)gmail.com> wrote: > > Also did you use the URL of the page your repo is on? Seems like maybe you > did from the image. You shouldn't. > > > You should use the Monticello Repository specification shown on the repo > page when you hover over Monticello Repository in the Getting The Code > section of the project page on ss3. > > e.g. > > MCHttpRepository > location: 'http://ss3.gemtalksystems.com/ss/GTDImplementation' > user: '' > password: '' > > > > > > > > Paul DeBruicker wrote >> what is the repo you're having trouble reading? >> >> >> Sergio Fedi wrote >>> Hello, >>> >>> I'm coming back after a few years (Pharo 5.0) and tried to take a look >>> and >>> download some projects I have on ss3. >>> >>> I'm using a Pharo 7.0 image. >>> >>> Going to the ss3 site I find that I can't access my projects, a "Reading >>> a >>> number failed: a digit between 0 and 9 expected" error shows in the page. >>> >>> Trying to view them from Monticello, after adding the appropriate >>> repository it shows weird characters for the name and versions and it is >>> unable to load them. >>> >>> [image: image.png] >>> >>> What am I missing/doing wrong? >>> >>> Thanks! >>> >>> >>> image.png (182K) >>> <http://forum.world.st/attachment/5102137/0/image.png> >> >> >> >> >> >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

Aug. 10, 2019

Re: [Pharo-users] Old projects in ss3

by Sergio Fedi

Ok, strangely, when I go to that page in Firefox it doesn't show that error. Tried to go with Chrome in incognito (so as to get rid of plug ins) and it still fails. Gonna try from within Pharo and if it fails I'll post again. Below are screenshots on how it fails or succeeds on each browser. In firefox: [image: image.png] In chrome: [image: image.png] On Fri, Aug 9, 2019 at 10:30 PM Paul DeBruicker <pdebruic(a)gmail.com> wrote: > Also did you use the URL of the page your repo is on? Seems like maybe you > did from the image. You shouldn't. > > > You should use the Monticello Repository specification shown on the repo > page when you hover over Monticello Repository in the Getting The Code > section of the project page on ss3. > > e.g. > > MCHttpRepository > location: 'http://ss3.gemtalksystems.com/ss/GTDImplementation' > user: '' > password: '' > > > > > > > > Paul DeBruicker wrote > > what is the repo you're having trouble reading? > > > > > > Sergio Fedi wrote > >> Hello, > >> > >> I'm coming back after a few years (Pharo 5.0) and tried to take a look > >> and > >> download some projects I have on ss3. > >> > >> I'm using a Pharo 7.0 image. > >> > >> Going to the ss3 site I find that I can't access my projects, a "Reading > >> a > >> number failed: a digit between 0 and 9 expected" error shows in the > page. > >> > >> Trying to view them from Monticello, after adding the appropriate > >> repository it shows weird characters for the name and versions and it is > >> unable to load them. > >> > >> [image: image.png] > >> > >> What am I missing/doing wrong? > >> > >> Thanks! > >> > >> > >> image.png (182K) > >> <http://forum.world.st/attachment/5102137/0/image.png> > > > > > > > > > > > > -- > > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > >

Aug. 10, 2019

Re: [Pharo-users] [ANN] Pharo Chip Designer

by Guillermo Polito

haha looks fun :) > El 10 ago 2019, a las 13:15, Pavel Krivanek <pavel.krivanek(a)gmail.com> escribiÃ³: > > Hi, > > I have created a little program based on an old educational game by Zachtronics (KOHCTPYKTOP: Engineer of the People[1]) named Pharo Chip Designer. > > It is an inaccurate and highly simplified tool for the design of silicon chip layouts. Unlike common tools for logic circuits designs, in Pharo Chip Designer, you need to face the real-life problems like propagation delays or limited amount of layers and available substrate area. > > https://github.com/pavel-krivanek/PharoChipDesigner <https://github.com/pavel-krivanek/PharoChipDesigner/blob/master/README.md> > > It contains levels from the original game, but you can play with your custom designs on larger surfaces. And of course, use all the Pharo power to control the I/O signals. > > The Pharo Chip Designer required Pharo 8.0 and Spec2. > > Cheers, > -- Pavel > > [1] http://www.zachtronics.com/kohctpyktop-engineer-of-the-people/ <http://www.zachtronics.com/kohctpyktop-engineer-of-the-people/>

Aug. 10, 2019