August 2019 - Pharo-users - lists.pharo.org

Re: [Pharo-users] [Pharo-dev] [ANN] Pharo Headless - Beta (Actually what is between Alpha and Beta)

by tesonep＠gmail.com

Hi, The executables are not the same. We have 2 different now: the Stock VM (that is downloaded by the launcher, and it is the default download in Zero-conf), and the headless VM (this is downloaded by zero-conf when using vmLatestHeadless). Those platforms are not representative we currently have: OSX, Windows, and Linux all 64bits. We are working in ARM 32bits. In the near future, I will work on validating different flavors of Unix, but again It depends on the roadmap, and they are not there now. If someone requires some other platform we can talk to see how it can fit in the roadmap. Cheers, Pablo On Mon, Aug 12, 2019 at 10:03 AM Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > Yes. We will be testing these days and we will come back with more details. > > Two more questions: > - Is minheadlessVM now integrated in the regular VM binary or are the two different artifacts? > - Also are the platforms from https://github.com/pharo-project/opensmalltalk-vm/tree/pharo/platforms representative for minheadlessVM? > > Cheers, > Doru > > > > > On Aug 12, 2019, at 9:11 AM, tesonep(a)gmail.com wrote: > > > > Hi Doru, > > can you give us more insight of the errors? Because there should > > not be changes in the behavior of the VM. Maybe there are issues, we > > have used the Pharo tests as a guarantee and we are laking some tests. > > > > Cheers, > > Pablo. > > > > On Sun, Aug 11, 2019 at 9:04 PM Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> > >> Hi, > >> > >> > >> > >>> On Aug 11, 2019, at 5:29 PM, ducasse <stepharo(a)netcourrier.com> wrote: > >>> > >>> > >>> > >>>> On 11 Aug 2019, at 13:19, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >>>> > >>>> Excellent news! > >>>> > >>>> I should say that for GT we are currently using the minheadlessVM (Ronieâs work) out of the opensmalltalk-vm repo (https://bintray.com/opensmalltalk/vm/cog) and it works remarkably well. > >>>> > >>>> We started to play with your minheadlessVM. So far it looks like there are differences, although I am sure they are not large. > >>> > >>> like what? > >> > >> I do not know yet, but running GT in headless opens the window with the one from opensmalltalk-vm, but not with the new one. We did not yet look into details, but we will. > >> > >> Cheers, > >> Doru > >> > >> > >>>> So, what is the difference between the minheadlessVM built by you versus the one from opensmalltalk-vm? > >>>> > >>>> Cheers, > >>>> Doru > >>>> > >>>> > >>>>> On Aug 8, 2019, at 9:53 AM, tesonep(a)gmail.com wrote: > >>>>> > >>>>> TL;DR; > >>>>> ====== > >>>>> > >>>>> For the anxious, you can get real headless vm and image from zero-conf. > >>>>> > >>>>> $ wget get.pharo.org/64/80+vmHeadlessLatest | bash > >>>>> > >>>>> Zero conf scripts remain unchanged for users. > >>>>> > >>>>> However, if you are launching the VM by hand from the executable > >>>>> instead of the launcher scripts (pharo and pharo-ui) as in > >>>>> > >>>>> $ ./pharoexecutable Pharo.image > >>>>> > >>>>> the image will launch in headless mode and will not open a window. > >>>>> To launch it in headfull, you can use the --interactive argument after > >>>>> the image, which will make the image open a window using SDL2. > >>>>> > >>>>> $ ./pharoexecutable Pharo.image --interactive > >>>>> > >>>>> Long version > >>>>> ============ > >>>>> > >>>>> Hi, this mail is the happy intermediate result of the work that us, > >>>>> the Pharo Consortium Team, has been doing in the last couple of > >>>>> months. > >>>>> Our main objective is to have a real headless implementation of Pharo > >>>>> where all the responsibility to open or not a World window (or other) > >>>>> is handled by the image. > >>>>> For doing so we have done a series of modifications in the image and > >>>>> the VM side. > >>>>> We consider this is the path that Pharo 8 and following versions > >>>>> should follow, as it will severely improve server-side and command > >>>>> line Pharo and in building custom desktop applications. > >>>>> > >>>>> These modifications are available only in 64-bits machines (Windows, > >>>>> OSX, and Linux). > >>>>> ARM32 and 64bits headless is in the roadmap, but it is delayed because > >>>>> we have prioritized our three major platforms for this first couple of > >>>>> months. > >>>>> > >>>>> All this work is based in Opensmalltalk-VM and Ronnie's initial work > >>>>> on headless. > >>>>> We are really grateful to all the contributors in the history of this > >>>>> nice product. > >>>>> To achieve a real headless VM we have brought modifications in the > >>>>> source tree because most of the platform code to open and manipulate > >>>>> windows is not required anymore. > >>>>> Instead, we use the SDL2 library that implements a nice layer on top > >>>>> of the OS and allows us to manage on the image side through FFI. > >>>>> > >>>>> So this mail is now an open call for (beta?)testing. > >>>>> The sources of the current VM we are building are in the headless branch in > >>>>> https://github.com/pharo-project/opensmalltalk-vm > >>>>> And we have set up a CI that is both building and testing the VM in > >>>>> https://ci.inria.fr/pharo-ci-jenkins2/job/pharo-vm/job/headless/ > >>>>> > >>>>> For the future we have a lot of ideas, that will wait for another long > >>>>> email or a beer-talk @ESUG. > >>>>> We want to hear your ideas!! > >>>>> > >>>>> Image-Side Improvements > >>>>> ======================= > >>>>> > >>>>> - The image handles the creation or not of the main world window. > >>>>> - We incorporated the idea of World renderer, where different backends > >>>>> are used to render the world. > >>>>> - We have 3 backends: VM support (compatibility with non-headless > >>>>> VMs), and OSWindow with two backends: SDL and GTK3+. > >>>>> - The modifications in the image are fully backward compatible with > >>>>> the non-headless VM and are pushed since weeks in the latest 8.0 > >>>>> image. > >>>>> - We move the handling of events to the image side when using SDL and > >>>>> GTK3+, opening the door to a richer set of events and finer-grained > >>>>> control over them. > >>>>> - SDL and GTK versions are implemented using FFI calls. > >>>>> > >>>>> VM-Side Improvements > >>>>> ==================== > >>>>> > >>>>> - VMMaker code migrated to Tonel thanks to Feenk and included in the > >>>>> repository of the VM. > >>>>> - Making VMMaker execute in Pharo 7 and 8. > >>>>> - Removing GPL code from the VM repository (GDB). > >>>>> > >>>>> - Slowly adding new tests for the JIT / Slang and VMGeneration. > >>>>> - Restructuring of the source code. > >>>>> - A new simpler CMake build. > >>>>> - Generate VM code from Slang on each build. > >>>>> - A CI process to validate (including the run of the tests in Pharo > >>>>> and the ones adding to the VM). > >>>>> - Simplification of the codebase. > >>>>> > >>>>> - Maximize the reuse of code between the platforms (preferring the > >>>>> standard versions over the platform-specific). > >>>>> - Cleaning up duplicated code. > >>>>> - All the plugins are now external plugins. > >>>>> - The VM is now a dynamic library. This is a first step towards > >>>>> embedding Pharo into other applications. > >>>>> - The main executable is a thin frontend (you can change it or > >>>>> implement your own). > >>>>> > >>>>> - Removing unused plugins. > >>>>> - Improved crash dump. Especially the crash dump works now in Windows 64bits. > >>>>> - Dummy implementation of Security plugin (it is going away.... eventually). > >>>>> - Cleanup of SSL, UUID, and Socket plugin. > >>>>> > >>>>> - Cleanup of conditional code (Still to improve). > >>>>> - Improving the types used in the functions (we have to be neat to be > >>>>> multiplatform/multi-arch). > >>>>> - Improving the lookup of modules > >>>>> - Improving the logging of the VM > >>>>> - Improving the handling of VM arguments > >>>>> > >>>>> > >>>>> Thanks a lot for reading so long!! > >>>>> We hope you enjoy the VM and please tell us all the problems you find!! > >>>>> > >>>>> Pablo, Guille, and Esteban > >>>>> > >>>> > >>>> -- > >>>> feenk.com > >>>> > >>>> "Being happy is a matter of choice." > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>> > >>> > >>> > >> > >> -- > >> feenk.com > >> > >> "Speaking louder won't make the point worthier." > >> > >> > > > > > > -- > > Pablo Tesone. > > tesonep(a)gmail.com > > > > -- > feenk.com > > "What is more important: To be happy, or to make happy?" > > -- Pablo Tesone. tesonep(a)gmail.com

Aug. 12, 2019

Re: [Pharo-users] [Pharo-dev] [ANN] Pharo Headless - Beta (Actually what is between Alpha and Beta)

by tesonep＠gmail.com

Hi Doru, can you give us more insight of the errors? Because there should not be changes in the behavior of the VM. Maybe there are issues, we have used the Pharo tests as a guarantee and we are laking some tests. Cheers, Pablo. On Sun, Aug 11, 2019 at 9:04 PM Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > > > > On Aug 11, 2019, at 5:29 PM, ducasse <stepharo(a)netcourrier.com> wrote: > > > > > > > >> On 11 Aug 2019, at 13:19, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> > >> Excellent news! > >> > >> I should say that for GT we are currently using the minheadlessVM (Ronieâs work) out of the opensmalltalk-vm repo (https://bintray.com/opensmalltalk/vm/cog) and it works remarkably well. > >> > >> We started to play with your minheadlessVM. So far it looks like there are differences, although I am sure they are not large. > > > > like what? > > I do not know yet, but running GT in headless opens the window with the one from opensmalltalk-vm, but not with the new one. We did not yet look into details, but we will. > > Cheers, > Doru > > > >> So, what is the difference between the minheadlessVM built by you versus the one from opensmalltalk-vm? > >> > >> Cheers, > >> Doru > >> > >> > >>> On Aug 8, 2019, at 9:53 AM, tesonep(a)gmail.com wrote: > >>> > >>> TL;DR; > >>> ====== > >>> > >>> For the anxious, you can get real headless vm and image from zero-conf. > >>> > >>> $ wget get.pharo.org/64/80+vmHeadlessLatest | bash > >>> > >>> Zero conf scripts remain unchanged for users. > >>> > >>> However, if you are launching the VM by hand from the executable > >>> instead of the launcher scripts (pharo and pharo-ui) as in > >>> > >>> $ ./pharoexecutable Pharo.image > >>> > >>> the image will launch in headless mode and will not open a window. > >>> To launch it in headfull, you can use the --interactive argument after > >>> the image, which will make the image open a window using SDL2. > >>> > >>> $ ./pharoexecutable Pharo.image --interactive > >>> > >>> Long version > >>> ============ > >>> > >>> Hi, this mail is the happy intermediate result of the work that us, > >>> the Pharo Consortium Team, has been doing in the last couple of > >>> months. > >>> Our main objective is to have a real headless implementation of Pharo > >>> where all the responsibility to open or not a World window (or other) > >>> is handled by the image. > >>> For doing so we have done a series of modifications in the image and > >>> the VM side. > >>> We consider this is the path that Pharo 8 and following versions > >>> should follow, as it will severely improve server-side and command > >>> line Pharo and in building custom desktop applications. > >>> > >>> These modifications are available only in 64-bits machines (Windows, > >>> OSX, and Linux). > >>> ARM32 and 64bits headless is in the roadmap, but it is delayed because > >>> we have prioritized our three major platforms for this first couple of > >>> months. > >>> > >>> All this work is based in Opensmalltalk-VM and Ronnie's initial work > >>> on headless. > >>> We are really grateful to all the contributors in the history of this > >>> nice product. > >>> To achieve a real headless VM we have brought modifications in the > >>> source tree because most of the platform code to open and manipulate > >>> windows is not required anymore. > >>> Instead, we use the SDL2 library that implements a nice layer on top > >>> of the OS and allows us to manage on the image side through FFI. > >>> > >>> So this mail is now an open call for (beta?)testing. > >>> The sources of the current VM we are building are in the headless branch in > >>> https://github.com/pharo-project/opensmalltalk-vm > >>> And we have set up a CI that is both building and testing the VM in > >>> https://ci.inria.fr/pharo-ci-jenkins2/job/pharo-vm/job/headless/ > >>> > >>> For the future we have a lot of ideas, that will wait for another long > >>> email or a beer-talk @ESUG. > >>> We want to hear your ideas!! > >>> > >>> Image-Side Improvements > >>> ======================= > >>> > >>> - The image handles the creation or not of the main world window. > >>> - We incorporated the idea of World renderer, where different backends > >>> are used to render the world. > >>> - We have 3 backends: VM support (compatibility with non-headless > >>> VMs), and OSWindow with two backends: SDL and GTK3+. > >>> - The modifications in the image are fully backward compatible with > >>> the non-headless VM and are pushed since weeks in the latest 8.0 > >>> image. > >>> - We move the handling of events to the image side when using SDL and > >>> GTK3+, opening the door to a richer set of events and finer-grained > >>> control over them. > >>> - SDL and GTK versions are implemented using FFI calls. > >>> > >>> VM-Side Improvements > >>> ==================== > >>> > >>> - VMMaker code migrated to Tonel thanks to Feenk and included in the > >>> repository of the VM. > >>> - Making VMMaker execute in Pharo 7 and 8. > >>> - Removing GPL code from the VM repository (GDB). > >>> > >>> - Slowly adding new tests for the JIT / Slang and VMGeneration. > >>> - Restructuring of the source code. > >>> - A new simpler CMake build. > >>> - Generate VM code from Slang on each build. > >>> - A CI process to validate (including the run of the tests in Pharo > >>> and the ones adding to the VM). > >>> - Simplification of the codebase. > >>> > >>> - Maximize the reuse of code between the platforms (preferring the > >>> standard versions over the platform-specific). > >>> - Cleaning up duplicated code. > >>> - All the plugins are now external plugins. > >>> - The VM is now a dynamic library. This is a first step towards > >>> embedding Pharo into other applications. > >>> - The main executable is a thin frontend (you can change it or > >>> implement your own). > >>> > >>> - Removing unused plugins. > >>> - Improved crash dump. Especially the crash dump works now in Windows 64bits. > >>> - Dummy implementation of Security plugin (it is going away.... eventually). > >>> - Cleanup of SSL, UUID, and Socket plugin. > >>> > >>> - Cleanup of conditional code (Still to improve). > >>> - Improving the types used in the functions (we have to be neat to be > >>> multiplatform/multi-arch). > >>> - Improving the lookup of modules > >>> - Improving the logging of the VM > >>> - Improving the handling of VM arguments > >>> > >>> > >>> Thanks a lot for reading so long!! > >>> We hope you enjoy the VM and please tell us all the problems you find!! > >>> > >>> Pablo, Guille, and Esteban > >>> > >> > >> -- > >> feenk.com > >> > >> "Being happy is a matter of choice." > >> > >> > >> > >> > >> > >> > >> > > > > > > > > -- > feenk.com > > "Speaking louder won't make the point worthier." > > -- Pablo Tesone. tesonep(a)gmail.com

Aug. 12, 2019

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

by Offray Vladimir Luna CÃ¡rdenas

Really cool. Thanks for this excellent showcase of what is possible. It's is pretty inspiring. Cheers, Offray On 10/08/19 6:15 a.Â m., Pavel Krivanek 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 > <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. 11, 2019

Re: [Pharo-users] [Pharo-dev] [ANN] Pharo Headless - Beta (Actually what is between Alpha and Beta)

by ducasse

> On 11 Aug 2019, at 13:19, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Excellent news! > > I should say that for GT we are currently using the minheadlessVM (Ronieâs work) out of the opensmalltalk-vm repo (https://bintray.com/opensmalltalk/vm/cog) and it works remarkably well. > > We started to play with your minheadlessVM. So far it looks like there are differences, although I am sure they are not large. like what? > > So, what is the difference between the minheadlessVM built by you versus the one from opensmalltalk-vm? > > Cheers, > Doru > > >> On Aug 8, 2019, at 9:53 AM, tesonep(a)gmail.com wrote: >> >> TL;DR; >> ====== >> >> For the anxious, you can get real headless vm and image from zero-conf. >> >> $ wget get.pharo.org/64/80+vmHeadlessLatest | bash >> >> Zero conf scripts remain unchanged for users. >> >> However, if you are launching the VM by hand from the executable >> instead of the launcher scripts (pharo and pharo-ui) as in >> >> $ ./pharoexecutable Pharo.image >> >> the image will launch in headless mode and will not open a window. >> To launch it in headfull, you can use the --interactive argument after >> the image, which will make the image open a window using SDL2. >> >> $ ./pharoexecutable Pharo.image --interactive >> >> Long version >> ============ >> >> Hi, this mail is the happy intermediate result of the work that us, >> the Pharo Consortium Team, has been doing in the last couple of >> months. >> Our main objective is to have a real headless implementation of Pharo >> where all the responsibility to open or not a World window (or other) >> is handled by the image. >> For doing so we have done a series of modifications in the image and >> the VM side. >> We consider this is the path that Pharo 8 and following versions >> should follow, as it will severely improve server-side and command >> line Pharo and in building custom desktop applications. >> >> These modifications are available only in 64-bits machines (Windows, >> OSX, and Linux). >> ARM32 and 64bits headless is in the roadmap, but it is delayed because >> we have prioritized our three major platforms for this first couple of >> months. >> >> All this work is based in Opensmalltalk-VM and Ronnie's initial work >> on headless. >> We are really grateful to all the contributors in the history of this >> nice product. >> To achieve a real headless VM we have brought modifications in the >> source tree because most of the platform code to open and manipulate >> windows is not required anymore. >> Instead, we use the SDL2 library that implements a nice layer on top >> of the OS and allows us to manage on the image side through FFI. >> >> So this mail is now an open call for (beta?)testing. >> The sources of the current VM we are building are in the headless branch in >> https://github.com/pharo-project/opensmalltalk-vm >> And we have set up a CI that is both building and testing the VM in >> https://ci.inria.fr/pharo-ci-jenkins2/job/pharo-vm/job/headless/ >> >> For the future we have a lot of ideas, that will wait for another long >> email or a beer-talk @ESUG. >> We want to hear your ideas!! >> >> Image-Side Improvements >> ======================= >> >> - The image handles the creation or not of the main world window. >> - We incorporated the idea of World renderer, where different backends >> are used to render the world. >> - We have 3 backends: VM support (compatibility with non-headless >> VMs), and OSWindow with two backends: SDL and GTK3+. >> - The modifications in the image are fully backward compatible with >> the non-headless VM and are pushed since weeks in the latest 8.0 >> image. >> - We move the handling of events to the image side when using SDL and >> GTK3+, opening the door to a richer set of events and finer-grained >> control over them. >> - SDL and GTK versions are implemented using FFI calls. >> >> VM-Side Improvements >> ==================== >> >> - VMMaker code migrated to Tonel thanks to Feenk and included in the >> repository of the VM. >> - Making VMMaker execute in Pharo 7 and 8. >> - Removing GPL code from the VM repository (GDB). >> >> - Slowly adding new tests for the JIT / Slang and VMGeneration. >> - Restructuring of the source code. >> - A new simpler CMake build. >> - Generate VM code from Slang on each build. >> - A CI process to validate (including the run of the tests in Pharo >> and the ones adding to the VM). >> - Simplification of the codebase. >> >> - Maximize the reuse of code between the platforms (preferring the >> standard versions over the platform-specific). >> - Cleaning up duplicated code. >> - All the plugins are now external plugins. >> - The VM is now a dynamic library. This is a first step towards >> embedding Pharo into other applications. >> - The main executable is a thin frontend (you can change it or >> implement your own). >> >> - Removing unused plugins. >> - Improved crash dump. Especially the crash dump works now in Windows 64bits. >> - Dummy implementation of Security plugin (it is going away.... eventually). >> - Cleanup of SSL, UUID, and Socket plugin. >> >> - Cleanup of conditional code (Still to improve). >> - Improving the types used in the functions (we have to be neat to be >> multiplatform/multi-arch). >> - Improving the lookup of modules >> - Improving the logging of the VM >> - Improving the handling of VM arguments >> >> >> Thanks a lot for reading so long!! >> We hope you enjoy the VM and please tell us all the problems you find!! >> >> Pablo, Guille, and Esteban >> > > -- > feenk.com > > "Being happy is a matter of choice." > > > > > > >

Aug. 11, 2019

Re: [Pharo-users] [Pharo-dev] [ANN] Pharo Headless - Beta (Actually what is between Alpha and Beta)

by Santiago Bragagnolo

Hey! I just see this email! This is exciting! <3 <3 <3 <3 El jue., 8 ago. 2019 a las 9:54, tesonep(a)gmail.com (<tesonep(a)gmail.com>) escribiÃ³: > TL;DR; > ====== > > For the anxious, you can get real headless vm and image from zero-conf. > > $ wget get.pharo.org/64/80+vmHeadlessLatest | bash > > Zero conf scripts remain unchanged for users. > > However, if you are launching the VM by hand from the executable > instead of the launcher scripts (pharo and pharo-ui) as in > > $ ./pharoexecutable Pharo.image > > the image will launch in headless mode and will not open a window. > To launch it in headfull, you can use the --interactive argument after > the image, which will make the image open a window using SDL2. > > $ ./pharoexecutable Pharo.image --interactive > > Long version > ============ > > Hi, this mail is the happy intermediate result of the work that us, > the Pharo Consortium Team, has been doing in the last couple of > months. > Our main objective is to have a real headless implementation of Pharo > where all the responsibility to open or not a World window (or other) > is handled by the image. > For doing so we have done a series of modifications in the image and > the VM side. > We consider this is the path that Pharo 8 and following versions > should follow, as it will severely improve server-side and command > line Pharo and in building custom desktop applications. > > These modifications are available only in 64-bits machines (Windows, > OSX, and Linux). > ARM32 and 64bits headless is in the roadmap, but it is delayed because > we have prioritized our three major platforms for this first couple of > months. > > All this work is based in Opensmalltalk-VM and Ronnie's initial work > on headless. > We are really grateful to all the contributors in the history of this > nice product. > To achieve a real headless VM we have brought modifications in the > source tree because most of the platform code to open and manipulate > windows is not required anymore. > Instead, we use the SDL2 library that implements a nice layer on top > of the OS and allows us to manage on the image side through FFI. > > So this mail is now an open call for (beta?)testing. > The sources of the current VM we are building are in the headless branch in > https://github.com/pharo-project/opensmalltalk-vm > And we have set up a CI that is both building and testing the VM in > https://ci.inria.fr/pharo-ci-jenkins2/job/pharo-vm/job/headless/ > > For the future we have a lot of ideas, that will wait for another long > email or a beer-talk @ESUG. > We want to hear your ideas!! > > Image-Side Improvements > ======================= > > - The image handles the creation or not of the main world window. > - We incorporated the idea of World renderer, where different backends > are used to render the world. > - We have 3 backends: VM support (compatibility with non-headless > VMs), and OSWindow with two backends: SDL and GTK3+. > - The modifications in the image are fully backward compatible with > the non-headless VM and are pushed since weeks in the latest 8.0 > image. > - We move the handling of events to the image side when using SDL and > GTK3+, opening the door to a richer set of events and finer-grained > control over them. > - SDL and GTK versions are implemented using FFI calls. > > VM-Side Improvements > ==================== > > - VMMaker code migrated to Tonel thanks to Feenk and included in the > repository of the VM. > - Making VMMaker execute in Pharo 7 and 8. > - Removing GPL code from the VM repository (GDB). > > - Slowly adding new tests for the JIT / Slang and VMGeneration. > - Restructuring of the source code. > - A new simpler CMake build. > - Generate VM code from Slang on each build. > - A CI process to validate (including the run of the tests in Pharo > and the ones adding to the VM). > - Simplification of the codebase. > > - Maximize the reuse of code between the platforms (preferring the > standard versions over the platform-specific). > - Cleaning up duplicated code. > - All the plugins are now external plugins. > - The VM is now a dynamic library. This is a first step towards > embedding Pharo into other applications. > - The main executable is a thin frontend (you can change it or > implement your own). > > - Removing unused plugins. > - Improved crash dump. Especially the crash dump works now in Windows > 64bits. > - Dummy implementation of Security plugin (it is going away.... > eventually). > - Cleanup of SSL, UUID, and Socket plugin. > > - Cleanup of conditional code (Still to improve). > - Improving the types used in the functions (we have to be neat to be > multiplatform/multi-arch). > - Improving the lookup of modules > - Improving the logging of the VM > - Improving the handling of VM arguments > > > Thanks a lot for reading so long!! > We hope you enjoy the VM and please tell us all the problems you find!! > > Pablo, Guille, and Esteban > >

Aug. 11, 2019

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