- Pharo-dev - lists.pharo.org

introducing my GSoC project - Improving Code Completion

by Myroslava Romaniuk

Hi everyone, My name is Myroslava, I'm a 3rd year CS student in Ukraine, and my project Improving Code Completion has been selected for this year's GSoC. Some of you might know me from the 2 ESUGs I was at or maybe remember me previously doing GSoC in 2017, in any case I'm very happy to have been given this opportunity and I look forward to working with you! I started working on code completion last year during my internship at RMoD with Marcus and Stef, and I really want to make even more progress with code completion this summer and properly implement it inside Pharo as one of the options to use. You can read more about what has been done last summer and what is yet to be done this summer in my proposal (see attached). If you have any feedback or questions, don't hesitate to email me. Help and suggestions throughout my work on the project will be incredibly welcome too, as there's a lot to figure out how to do best. If you are interested in updates or want to keep in touch, I'm also on twitter <https://twitter.com/myroslavarm>, and I have a blog <https://medium.com/@myroslavarm> where I used to post about my progress in the last GSoC and about my internship at RMoD, and I will be writing there this summer, too. I'll also try to be more active in the mailing list and on discord :) Cheers, Myroslava

May 9, 2019

[Pharo 8.0] Build #263: [Fork2]2938 - Fixing FFIConstantHandleType externalType wrong in 64 bit

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

There is a new Pharo build available! The status of the build #263 was: SUCCESS. The Pull Request #3252 was integrated: "[Fork2]2938 - Fixing FFIConstantHandleType externalType wrong in 64 bit " Pull request url: https://github.com/pharo-project/pharo/pull/3252 Issue Url: https://github.com/pharo-project/pharo/issues/2938 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 9, 2019

[Pharo 8.0] Build #262: 2261-DarkTheme-depends-on-Shout

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

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

May 9, 2019

[Pharo 8.0] Build #261: 2598-isSpecial-is-not-an-explicit-name-for-a-method

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

There is a new Pharo build available! The status of the build #261 was: FAILURE. The Pull Request #3318 was integrated: "2598-isSpecial-is-not-an-explicit-name-for-a-method" Pull request url: https://github.com/pharo-project/pharo/pull/3318 Issue Url: https://github.com/pharo-project/pharo/issues/2598 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 9, 2019

[Pharo 8.0] Build #260: 3316-Slots-more-tests-improve-comments-improve-Initialized-slots

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

There is a new Pharo build available! The status of the build #260 was: SUCCESS. The Pull Request #3317 was integrated: "3316-Slots-more-tests-improve-comments-improve-Initialized-slots" Pull request url: https://github.com/pharo-project/pharo/pull/3317 Issue Url: https://github.com/pharo-project/pharo/issues/3316 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 8, 2019

Re: [Pharo-dev] Problems trying to install pharo in centos 5.11

by Christopher Fuhrman

Hello, I did the same command on WSL (Windows 10) Ubuntu 18 and diffed the two results in Notepad++. Here's what it looks like: [image: image.png] Here are the major differences I can see: - On my system there's a 'CApath: /etc/ssl/certs' (line 11) whereas on yours it's 'CApath: none' - The server's certificate 'subject: CN=files.pharo.org' (line 34) is different than yours: 'subject: /OU=Domain Control Validated/OU=PositiveSSL/CN=cluster023.hosting.ovh.net' (line 34). It't not clear to me why you're dealing with cluster023.hosting.ovh.net rather than files.pharo.org, but I'm guessing that is the crux of your problem. They have the same IP (according to my nslookup) so, it's just the hostname that's changing somehow. Hope this helps. On Tue, 7 May 2019 at 22:46, Juan <smalltalker.marcelo(a)gmail.com> wrote: > Paul ,thanks for your quicly response, > On Tue, May 7, 2019 at 5:17 PM Paul DeBruicker <pdebruic(a)gmail.com> wrote: > >> try it with a trailing slash e.g. >> >> curl https://get.pharo.org/64/ | bash >> >> > I'm tried this without succes ,y hope that extra information be useful > > curl -vv -L https://get.pharo.org/64/ | bash > * About to connect() to get.pharo.org port 443 > * Trying 164.132.235.17... connected > * Connected to get.pharo.org (164.132.235.17) port 443 > * successfully set certificate verify locations: > * CAfile: /etc/pki/tls/certs/ca-bundle.crt > CApath: none > * SSLv3, TLS handshake, Client hello (1): > SSLv3, TLS handshake, Server hello (2): > SSLv3, TLS handshake, CERT (11): > SSLv3, TLS handshake, Server key exchange (12): > SSLv3, TLS handshake, Server finished (14): > SSLv3, TLS handshake, Client key exchange (16): > SSLv3, TLS change cipher, Client hello (1): > SSLv3, TLS handshake, Finished (20): > SSLv3, TLS change cipher, Client hello (1): > SSLv3, TLS handshake, Finished (20): > SSL connection using DHE-RSA-AES128-SHA > * Server certificate: > * subject: /OU=Domain Control Validated/OU=PositiveSSL/CN= > cluster023.hosting.ovh.net > * start date: 2018-02-01 00:00:00 GMT > * expire date: 2021-01-31 23:59:59 GMT > * SSL: certificate subject name 'cluster023.hosting.ovh.net' does not > match target host name 'get.pharo.org' > * Closing connection #0 > * SSLv3, TLS alert, Client hello (1): > > curl: (51) SSL: certificate subject name 'cluster023.hosting.ovh.net' > does not match target host name 'get.pharo.org' > > > best > > Juan Marcelo Diaz Cortez. > > >> >> Juan-2 wrote >> > Hi all >> > >> > Today I was trying to install pharo, in a Centos release 5.11 (Final), >> but >> > without success. >> > the error message is >> > >> > with curl >> > >> > curl https://get.pharo.org/64 | bash >> > >> > curl: (51) SSL: certificate subject name 'cluster023.hosting.ovh.net' >> does >> > not match target host name 'get.pharo.org' >> > >> > with wget, >> > >> > wget -O- https://get.pharo.org/64 | bash >> > --2019-05-07 12:49:11 - https://get.pharo.org/64 >> > Resolving get.pharo.org ... 164.132.235.17, 2001: 41d0: 301 :: 23 >> > Connecting to get.pharo.org | 164.132.235.17 |: 443 ... connected. >> > ERROR: certificate common name `cluster023.hosting.ovh.net 'does not >> match >> > requested host name` get.pharo.org'. >> > To connect to get.pharo.org insecurely, use `--no-check-certificate '. >> > The SSL connection could not be established. >> > I wonder if this is a known error, or is it a problem with my internet >> > provider. >> > One last question, for 5.xx centos there are prerequisites for >> > installation >> > ?. >> > Any link or reference to install it? >> > >> > best regards >> > Juan M. Diaz Cortez >> >> >> >> >> >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >> >>

May 8, 2019

Re: [Pharo-dev] Problems trying to install pharo in centos 5.11

by ducasse

from my super slow connection I get ~ Â» curl https://get.pharo.org/64/ | bash % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 12695 100 12695 0 0 38713 0 --:--:-- --:--:-- --:--:-- 38704 Downloading the latest 70 Image: http://files.pharo.org/get-files/70/pharo64.zip Pharo.image Downloading the latest pharoVM: http://files.pharo.org/get-files/70/pharo64-mac-stable.zip pharo-vm/Pharo.app/Contents/MacOS/Pharo Creating starter scripts pharo and pharo-ui > On 7 May 2019, at 22:38, Juan <smalltalker.marcelo(a)gmail.com> wrote: > > Paul ,thanks for your quicly response, > On Tue, May 7, 2019 at 5:17 PM Paul DeBruicker <pdebruic(a)gmail.com <mailto:pdebruic@gmail.com>> wrote: > try it with a trailing slash e.g. > > curl https://get.pharo.org/64/ <https://get.pharo.org/64/> | bash > > > I'm tried this without succes ,y hope that extra information be useful > > curl -vv -L https://get.pharo.org/64/ <https://get.pharo.org/64/> | bash > * About to connect() to get.pharo.org <http://get.pharo.org/> port 443 > * Trying 164.132.235.17... connected > * Connected to get.pharo.org <http://get.pharo.org/> (164.132.235.17) port 443 > * successfully set certificate verify locations: > * CAfile: /etc/pki/tls/certs/ca-bundle.crt > CApath: none > * SSLv3, TLS handshake, Client hello (1): > SSLv3, TLS handshake, Server hello (2): > SSLv3, TLS handshake, CERT (11): > SSLv3, TLS handshake, Server key exchange (12): > SSLv3, TLS handshake, Server finished (14): > SSLv3, TLS handshake, Client key exchange (16): > SSLv3, TLS change cipher, Client hello (1): > SSLv3, TLS handshake, Finished (20): > SSLv3, TLS change cipher, Client hello (1): > SSLv3, TLS handshake, Finished (20): > SSL connection using DHE-RSA-AES128-SHA > * Server certificate: > * subject: /OU=Domain Control Validated/OU=PositiveSSL/CN=cluster023.hosting.ovh.net <http://cluster023.hosting.ovh.net/> > * start date: 2018-02-01 00:00:00 GMT > * expire date: 2021-01-31 23:59:59 GMT > * SSL: certificate subject name 'cluster023.hosting.ovh.net <http://cluster023.hosting.ovh.net/>' does not match target host name 'get.pharo.org <http://get.pharo.org/>' > * Closing connection #0 > * SSLv3, TLS alert, Client hello (1): > > curl: (51) SSL: certificate subject name 'cluster023.hosting.ovh.net <http://cluster023.hosting.ovh.net/>' does not match target host name 'get.pharo.org <http://get.pharo.org/>' > > > best > > Juan Marcelo Diaz Cortez. > > > > Juan-2 wrote > > Hi all > > > > Today I was trying to install pharo, in a Centos release 5.11 (Final), but > > without success. > > the error message is > > > > with curl > > > > curl https://get.pharo.org/64 <https://get.pharo.org/64> | bash > > > > curl: (51) SSL: certificate subject name 'cluster023.hosting.ovh.net <http://cluster023.hosting.ovh.net/>' does > > not match target host name 'get.pharo.org <http://get.pharo.org/>' > > > > with wget, > > > > wget -O- https://get.pharo.org/64 <https://get.pharo.org/64> | bash > > --2019-05-07 12:49:11 - https://get.pharo.org/64 <https://get.pharo.org/64> > > Resolving get.pharo.org <http://get.pharo.org/> ... 164.132.235.17, 2001: 41d0: 301 :: 23 > > Connecting to get.pharo.org <http://get.pharo.org/> | 164.132.235.17 |: 443 ... connected. > > ERROR: certificate common name `cluster023.hosting.ovh.net <http://cluster023.hosting.ovh.net/> 'does not match > > requested host name` get.pharo.org <http://get.pharo.org/>'. > > To connect to get.pharo.org <http://get.pharo.org/> insecurely, use `--no-check-certificate '. > > The SSL connection could not be established. > > I wonder if this is a known error, or is it a problem with my internet > > provider. > > One last question, for 5.xx centos there are prerequisites for > > installation > > ?. > > Any link or reference to install it? > > > > best regards > > Juan M. Diaz Cortez > > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html <http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html> >

May 8, 2019

Re: [Pharo-dev] IceCredentialsProvider sshCredentials ?

by ducasse

did you try to clone your repo by hand on your server? in my config I have also my github account/password > On 7 May 2019, at 16:33, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > I am trying to deploy on a server by building a Pharo image there. > > I want to use a readonly 'deploy user', using a specific certificate. > > I have been trying lots of things, but I cannot get where I want. > > So the user account is arbitrary, it just contains a key pair. If I add the key pair to the ssh-agent, I can clone my repository on the command line. > > Now I want to script this from Pharo. The script starts as follows: > > | remote location | > remote := IceGitRemote url: 'ssh://git@bitbucket.myhost.be:1234/tthree/t3-pharo.git'. > location := FileLocator localDirectory / 'iceberg' / remote projectName. > > IceRepositoryCreator new > remote: remote; > location: location; > createRepository. > > On my development machine (macOS), this works fine. > But this does not work on the Linux server, it says > > IceAuthenticationError: There was an authentication error while trying to execute the operation: . > This happens usually because you didn't provide a valid set of credentials. > You may fix this problem in different ways: > > 1. adding your keys to ssh-agent, executing ssh-add ~/.ssh/id_rsa in your command line. > 2. adding your keys in settings (open settings browser search for "Use custom SSH keys" and > add your public and private keys). > 3. using HTTPS instead SSH (Just use an url in the form HTTPS://etc.git) > > It does not matter if the ssh-agent has the certificate listed (ssh-add). > > Adding > > IceCredentialsProvider useCustomSsh: true. > IceCredentialsProvider sshCredentials > publicKey: '/home/t3/.ssh/id_deploy_pharo_ed25519.pub'; > privateKey: '/home/t3/.ssh/id_deploy_pharo_ed25519' > > Does not make a difference. Is this supposed to work ? > > Maybe there is some other problem ? > > Sven > >

May 8, 2019

Re: [Pharo-dev] IceCredentialsProvider sshCredentials ?

by Tim Mackinnon

Not sure if this helps - but that error is rather arbitrary. I got the same when I deleted the local iceberg directory vs my project directory in iceberg. Could this be a possibility? It doesnât react well to missing directories? Tim Sent from my iPhone > ?On 7 May 2019, at 15:33, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > I am trying to deploy on a server by building a Pharo image there. > > I want to use a readonly 'deploy user', using a specific certificate. > > I have been trying lots of things, but I cannot get where I want. > > So the user account is arbitrary, it just contains a key pair. If I add the key pair to the ssh-agent, I can clone my repository on the command line. > > Now I want to script this from Pharo. The script starts as follows: > > | remote location | > remote := IceGitRemote url: 'ssh://git@bitbucket.myhost.be:1234/tthree/t3-pharo.git'. > location := FileLocator localDirectory / 'iceberg' / remote projectName. > > IceRepositoryCreator new > remote: remote; > location: location; > createRepository. > > On my development machine (macOS), this works fine. > But this does not work on the Linux server, it says > > IceAuthenticationError: There was an authentication error while trying to execute the operation: . > This happens usually because you didn't provide a valid set of credentials. > You may fix this problem in different ways: > > 1. adding your keys to ssh-agent, executing ssh-add ~/.ssh/id_rsa in your command line. > 2. adding your keys in settings (open settings browser search for "Use custom SSH keys" and > add your public and private keys). > 3. using HTTPS instead SSH (Just use an url in the form HTTPS://etc.git) > > It does not matter if the ssh-agent has the certificate listed (ssh-add). > > Adding > > IceCredentialsProvider useCustomSsh: true. > IceCredentialsProvider sshCredentials > publicKey: '/home/t3/.ssh/id_deploy_pharo_ed25519.pub'; > privateKey: '/home/t3/.ssh/id_deploy_pharo_ed25519' > > Does not make a difference. Is this supposed to work ? > > Maybe there is some other problem ? > > Sven > >

May 7, 2019

Re: [Pharo-dev] Dependencies between git projects ?

by Paul DeBruicker

In Pharo settings you can set it to use HTTPS for all github: repos. Maybe on the first github authentication error it could ask whether they'd prefer to use anonymous HTTPS to connect to github. Sven Van Caekenberghe-2 wrote >> On 7 May 2019, at 21:32, Sean P. DeNigris < > sean@ > > wrote: >> >> Sven Van Caekenberghe-2 wrote >>> is it actually 'wrong' ? >> >> Looks okay to me. Can you say more about what you mean by âwrongâ? > > With 'wrong' I mean that if you are not a GitHub user yourself, you cannot > access a repository that way, you need to use https (IIUC). This seems to > happen automatically by Metacello though. > >> NB if your subprojects have metadata and your main project doesnât have >> to >> be compatible outside recent Pharo you can remove the code subfolder from >> those URLs and eliminate a bit of duplication > > You mean 'repository' ? I sometimes use an empty one, although it seems > 'src' is the standard now. > >> ----- >> Cheers, >> Sean >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >> -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

May 7, 2019