- Pharo-dev - lists.pharo.org

[Pharo 7.0-dev] Build #680: 21531 Fix critiques in in NonInteractiveTranscript and DailyNonInteractiveTranscript
by ci-pharo-ci-jenkins2＠inria.fr March 11, 2018

March 11, 2018

There is a new Pharo build available! The status of the build #680 was: SUCCESS. The Pull Request #1055 was integrated: "21531 Fix critiques in in NonInteractiveTranscript and DailyNonInteractiveTranscript" Pull request url: https://github.com/pharo-project/pharo/pull/1055 Issue Url: https://pharo.fogbugz.com/f/cases/21531 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #679: 21541 Cleanup remaining testFindTokensEscapedByxx methods
by ci-pharo-ci-jenkins2＠inria.fr March 11, 2018

March 11, 2018

There is a new Pharo build available! The status of the build #679 was: SUCCESS. The Pull Request #1066 was integrated: "21541 Cleanup remaining testFindTokensEscapedByxx methods" Pull request url: https://github.com/pharo-project/pharo/pull/1066 Issue Url: https://pharo.fogbugz.com/f/cases/21541 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #678: 21477 Improve #allClassVarNames
by ci-pharo-ci-jenkins2＠inria.fr March 10, 2018

March 10, 2018

There is a new Pharo build available! The status of the build #678 was: SUCCESS. The Pull Request #1012 was integrated: "21477 Improve #allClassVarNames" Pull request url: https://github.com/pharo-project/pharo/pull/1012 Issue Url: https://pharo.fogbugz.com/f/cases/21477 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #677: 21479 Better structure in UnifiedFFI-Tests and add class comments
by ci-pharo-ci-jenkins2＠inria.fr March 10, 2018

March 10, 2018

There is a new Pharo build available! The status of the build #677 was: FAILURE. The Pull Request #1016 was integrated: "21479 Better structure in UnifiedFFI-Tests and add class comments" Pull request url: https://github.com/pharo-project/pharo/pull/1016 Issue Url: https://pharo.fogbugz.com/f/cases/21479 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #676: 21527-move-DynamicMessageImplementorTest-to-Debugger-Tests
by ci-pharo-ci-jenkins2＠inria.fr March 10, 2018

March 10, 2018

There is a new Pharo build available! The status of the build #676 was: FAILURE. The Pull Request #1053 was integrated: "21527-move-DynamicMessageImplementorTest-to-Debugger-Tests" Pull request url: https://github.com/pharo-project/pharo/pull/1053 Issue Url: https://pharo.fogbugz.com/f/cases/21527 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #675: 21526-remove-Nautilus-Tests
by ci-pharo-ci-jenkins2＠inria.fr March 10, 2018

March 10, 2018

There is a new Pharo build available! The status of the build #675 was: SUCCESS. The Pull Request #1052 was integrated: "21526-remove-Nautilus-Tests" Pull request url: https://github.com/pharo-project/pharo/pull/1052 Issue Url: https://pharo.fogbugz.com/f/cases/21526 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Discord server vanished!
by Vincent.Blondeau＠lamresearch.com March 10, 2018

March 10, 2018

Hi, It seems that the Pharo discord server is not available anymore at this address provided on Pharo.org: https://discordapp.com/invite/Sj2rhxn And it vanished from the discord app... Where did it go? Thanks, Vincent

7 11

Please rejoin Discord
by Dimitris Chloupis March 10, 2018

March 10, 2018

Hey guys after my mistake we got "hacked" and someone banned all our members in Discord I have revoked all the bans but you will have to rejoin . Existing join links are still valid , if you dont have one here is one https://discord.gg/gtKeHne My apologies for this inconvenience, I am still exploring all possible threats to make sure this never happens again.

2 1

Pavel's ChangeLog week of 2018-02-26
by Pavel Krivanek March 10, 2018

March 10, 2018

Hi, Guille is working on the Iceberg improvements and he wanted to be able to open a terminal window on top of the repository and interact with it via the command line. So we looked at this issue because I already in December made some experiments with the terminal emulation in Pharo. In past, the Squeak had a working terminal emulation that used PseudoTTYPlugin. The VM is not built with this code for a long time but I tried to replace it with a small C library and then wrote an FFI interface to it. Together with that, I ported most of the old code Squeak code to Pharo. With Guille we tried to avoid usage of such external library and wrote an FFI interface to all the required LibC functions. We were successful but we realized that there are several issues that are limiting us. When you want to execute a separate process for the program that you want to open in terminal (typically the Bash), you need to redirect the standard IO files, create a fork of your process, do some additional initialization in it and call 'exec' on it. In the parent process, you change redirected IO files back to the original values. But the problem is that between the FFI calls from Smalltalk the VM can do a lot of things including garbage collection etc. On OS X the fork() function has the following limitation described in man: "There are limits to what you can do in the child process. To be totally safe you should restrict your yourself to only executing async-signal safe operations until such time as one of the exec functions is called. All APIs, including global data symbols, in any framework or library should be assumed to be unsafe after a fork() unless explicitly documented to be safe or async-signal safe. If you need to use these frameworks in the child process, you must exec. In this situation it is reasonable to exec your-self. yourself." As the result in most cases (but not all) the fork() and exec() pair from the Smalltalk side fails on OS X. Linux does not have this limitation however even there we found an issue. It is bound to the fact that fork() makes a fork of all the parent process that uses the same resources. As soon as Pharo is opened in a window and X11 is involved (the window wants to be repainted), it can lead to the VM crash. So we learned that unfortunately we currently cannot use image-only FFI code for this task. We need a C library or VM plugin. The repository of the terminal emulator is here: https://github.com/pavel-krivanek/terminal and can be loaded using the following code: Metacello new baseline: 'TerminalEmulator'; repository: 'github://pavel-krivanek/terminal/src'; load. #TerminalEmulator asClass compileLibrary. â It compiles and links the small library with only one function using the GCC so the machine needs to have a proper development environment. The terminal emulator is in very early stage and has a lot of issues like processes cleanup, drawing, keyboard input etc. etc. If you are interested in it, feel free to contribute. Cheers, -- Pavel

4 7

Re: [Pharo-dev] [Pharo-users] Bootstrap how to
by Alistair Grant March 10, 2018

March 10, 2018

Hi Hilaire, Moving this to pharo-dev... On Thu, Mar 08, 2018 at 11:34:55AM +0100, Hilaire wrote: > I give again a try to bootstrap (after my last summer fail). Here how far I > went: > > Do people really like git or pretend to because > everyone is using it. Maybe there's a better source management system out there, but for me git is much better than any of the alternatives I've used (rcs, svn, vcs and a couple I've forgotten (cms?)). > 1. Fetched the repo https://github.com/pharo-project/pharo. I have to fetch > a fresh one as updating my repo failed with the git command > pull/fetch/merge/reset hard does not work. Incredible how simple thinks does > not work simply with git. I consider myself far from a git expert, so take the following with a grain of salt... You haven't given much detail, but when you have a clone think of the branches that are upstream as being "read only" (typically master and development). They should only ever be modified by merging in the branch from upstream. If you're writing (committing) to your clone, it should always be in a separate branch. When updating, e.g. master, from upstream, get in to the habit of enforcing fast-foward only e.g.: git checkout master git fetch --prune upstream git merge --ff-only upstream/master git push It's more steps, but will ensure you don't get in to the problem you describe above. git pull will do a merge if necessary, making future updates hard / impossible. > 2. Followed instructions to build a bootstrap. > > BUILD_NUMBER=42 BOOTSTRAP_ARCH=32 sh ./bootstrap/scripts/bootstrap.sh The script I've been using is: #!/bin/bash export JOB=bootstrap export BOOTSTRAP_ARCH=32 export PHARO_VERSION=60 export BUILD_NUMBER=$(date "+%m%d") ./bootstrap/scripts/bootstrap.sh It would be good to have a readme in the bootstrap directory that provides basic instructions on what the key variables are and how to run the bootstrap. > The resulting image bootstrap-cache/bootstrap.image is built after 1 or 2 > hours. Its size is 3,4MB, when started there is only blank screen, I guess > it is the expected outcome. My 4 year old Dell XPS-13 (i7) takes about 30-40 minutes to do the build. > 3. Followed instructions to load pharo environment: > > ??BUILD_NUMBER=42 BOOTSTRAP_ARCH=32 ./bootstrap/scripts/build.sh This is called by bootstrap.sh, so it shouldn't be necessary for you to call it directly. > Several attempts were needed and the build.sh script is fragile and fail > when at the repeated attempts, some cleaning were needed. > > I suggest two things : > > 1. you add -p to your mkdir commands (in build.sh and get-vm.sh > scripts) as it make your script less fragile ! > 2. Also checking for the existence of the Pharo.source will avoid to > have duplicted uncessary downloaded source file version. > (Pharo.source1, Pharo.source2): > > if test ! -e PharoV60.sources > ???? then > ???????????? wget http://files.pharo.org/sources/PharoV60.sources > fi > > Now the image is building, will see next. I agree that it would be nice if it was possible to avoid downloading the files each time, and also possible separate the process in to a number of stages, and restart from a nominated stage. Maybe the stages could be: 1. Download all requirements (stable vm (6.0), target vm (7.0), bootstrapImage.zip and anything else I've forgotten). 2. The build steps in bootstrap.sh. 3. The build steps in build.sh There could be a "clean" option that would be called as part of the CI process to ensure that everything is always up to date. Esteban and co.: How open are you to refactoring the scripts to support this? Or is there something I don't understand that means it doesn't make sense? Cheers, Alistair

2 1