- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Ann] Iceberg 0.7.5

by Guillermo Polito

On Thu, May 3, 2018 at 5:25 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > Will it be too hard to do 6.2? I encourage the backport but it will break > stuff which is also really annoying. > @esteban? :) I'd really like to have that or a 6.1.1, a way to actually differentiate them... > > Norbert > > > Am 03.05.2018 um 17:16 schrieb Guillermo Polito <guillermopolito(a)gmail.com > >: > > Time for the weekly Iceberg update. > > Iceberg 0.7.5. will be in the next Pharo build. > Thanks to all brave users, issue reporters and contributors :). > > Key improvements: > - Several improvements in metacello integration. (see #625, #664, #688 + > more tests) > - For those using CI, we think this release will also fix > https://github.com/pharo-vcs/iceberg/issues/643 > > Infrastructure improvements: > - In 0.7.4 we introduced in the build tests againt pharo 6.1 and 64 bits > * https://travis-ci.org/pharo-vcs/iceberg/builds/372408795 > - In 0.7.5 all iceberg tests run green on Pharo 6.1 32 bits > * https://travis-ci.org/pharo-vcs/iceberg/builds/374433920 > - In the next release we plan to do a pass on 64 bits > > ** Pharo 6.1 backport ** > - We plan to backport this version to Pharo 6.1 > - Cyril has been using the development version of Iceberg on Pharo 6.1 > for a couple of weeks now. > - This plus the green CI encourages us to backport to Pharo 6.1 > > Detailed ChangesLog: > > #625 Non explicit error while loading a project > #758 [Regression] Repair action clone is not setting pharo repository > #756 Iceberg dev-0.7 is broken in Pharo6.1 (Instance of > IceTipURLLabelMorph did not understand #addEmphasis:) > #749 Adding repair actions to the code subdirectory missing problem > #655 Rename extension method buildToolbarItem of CommandActivator > #755 Extracting the URL label behavior as a component that we can reuse > #468 Commiting via Iceberg does not commit package removal > #750 Add possibility to see current commit in Repositories/Package view > #754 Showing and coping the Commit ID > #753 Create branch dialog layout is broken > #664 Package wrongly shown with "uncommited changes" status > #752 Add "invalid ssh" > #747 Cloning a Git repository should change the path with the project name. > #738 Remove "pharo" Repository with "also remove from filesystem" gives > error > #746 Make tests run on pharo 6 > #735 Issue while registering a new project on Pharo 6.1 > #733 Add license file > #740 Fogbugz panel: Improve label, focus order and layout > #549 IceRestoreRepositoryModel should have a class comment > #688 Duplicated project error when loading in a fresh image > > Enjoy, > Guille in behalf of all people that contributed :) > > > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

May 3, 2018

[Pharo 7.0-dev] Build #830: 21765-cleanup-interactiveParserFor-

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

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

May 3, 2018

Re: [Pharo-dev] [Ann] Iceberg 0.7.5

by Norbert Hartl

Will it be too hard to do 6.2? I encourage the backport but it will break stuff which is also really annoying. Norbert > Am 03.05.2018 um 17:16 schrieb Guillermo Polito <guillermopolito(a)gmail.com>: > > Time for the weekly Iceberg update. > > Iceberg 0.7.5. will be in the next Pharo build. > Thanks to all brave users, issue reporters and contributors :). > > Key improvements: > - Several improvements in metacello integration. (see #625, #664, #688 + more tests) > - For those using CI, we think this release will also fix https://github.com/pharo-vcs/iceberg/issues/643 <https://github.com/pharo-vcs/iceberg/issues/643> > > Infrastructure improvements: > - In 0.7.4 we introduced in the build tests againt pharo 6.1 and 64 bits > * https://travis-ci.org/pharo-vcs/iceberg/builds/372408795 <https://travis-ci.org/pharo-vcs/iceberg/builds/372408795> > - In 0.7.5 all iceberg tests run green on Pharo 6.1 32 bits > * https://travis-ci.org/pharo-vcs/iceberg/builds/374433920 <https://travis-ci.org/pharo-vcs/iceberg/builds/374433920> > - In the next release we plan to do a pass on 64 bits > > ** Pharo 6.1 backport ** > - We plan to backport this version to Pharo 6.1 > - Cyril has been using the development version of Iceberg on Pharo 6.1 for a couple of weeks now. > - This plus the green CI encourages us to backport to Pharo 6.1 > > Detailed ChangesLog: > > #625 Non explicit error while loading a project > #758 [Regression] Repair action clone is not setting pharo repository > #756 Iceberg dev-0.7 is broken in Pharo6.1 (Instance of IceTipURLLabelMorph did not understand #addEmphasis:) > #749 Adding repair actions to the code subdirectory missing problem > #655 Rename extension method buildToolbarItem of CommandActivator > #755 Extracting the URL label behavior as a component that we can reuse > #468 Commiting via Iceberg does not commit package removal > #750 Add possibility to see current commit in Repositories/Package view > #754 Showing and coping the Commit ID > #753 Create branch dialog layout is broken > #664 Package wrongly shown with "uncommited changes" status > #752 Add "invalid ssh" > #747 Cloning a Git repository should change the path with the project name. > #738 Remove "pharo" Repository with "also remove from filesystem" gives error > #746 Make tests run on pharo 6 > #735 Issue while registering a new project on Pharo 6.1 > #733 Add license file > #740 Fogbugz panel: Improve label, focus order and layout > #549 IceRestoreRepositoryModel should have a class comment > #688 Duplicated project error when loading in a fresh image > > Enjoy, > Guille in behalf of all people that contributed :)

May 3, 2018

Re: [Pharo-dev] Failing tests

by Guillermo Polito

Exactly that :) https://pharo.fogbugz.com/f/cases/21822/Fix-Zn-Tests-due-to-encrypted-googl… https://github.com/pharo-project/pharo/pull/1290 On Thu, May 3, 2018 at 5:18 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > > On 3 May 2018, at 17:12, Guillermo Polito <guillermopolito(a)gmail.com> > wrote: > > > > Hi all, > > > > There are a couple of Zn tests that are failing not even in the CI but > locally in my machine. > > This happens because the tests are trying to do a request to > > > > encrypted.google.com > > > > and expecting a 200, but they are instead receiving: > > > > 301 Moved Permanently text/html > > > > From the response, I guess we should do the request to > > > > https://www.google.com/search?q=Smalltalk > > > > instead. > > > > This solves the failures on my side. Sven, is that Ok if we push those > patches to the tests to Pharo? > > Right, these would be the changed versions then: > > testPlain > | query stream request response | > self isNativeSSLPluginPresent ifFalse: [ ^ self ]. > query := 'Smalltalk'. > stream := ZdcSecureSocketStream openConnectionToHostNamed: ' > www.google.com' port: 443. > [ > request := String streamContents: [ :out | > out << 'GET /search?q=' << query << ' HTTP/1.1' << > String crlf. > out << 'Host: www.google.com' << String crlf. > out << 'Connection: close' << String crlf. > out << String crlf ]. > stream connect. > stream nextPutAll: request asByteArray. > stream flush. > response := stream upToEnd asString. > ] ensure: [ stream close ]. > self assert: (response includesSubstring: '200 OK'). > self assert: (response includesSubstring: 'Google'). > self assert: (response includesSubstring: 'Smalltalk'). > > testRequestResponse > | query stream request response | > self ensureSocketStreamFactory. > self isNativeSSLPluginPresent ifFalse: [ ^ self ]. > query := 'Smalltalk'. > stream := ZdcSecureSocketStream openConnectionToHostNamed: ' > www.google.com' port: 443. > [ > request := ZnRequest get: 'https://www.google.com/ > search?q=', query. > stream connect. > request writeOn: stream. > stream flush. > response := ZnResponse readFrom: stream. > ] ensure: [ stream close ]. > self assert: response isSuccess. > self assert: (response contents includesSubstring: 'Google'). > self assert: (response contents includesSubstring: 'Smalltalk'). > > I will apply them upstream as well. > > > -- > > > > Guille Polito > > Research Engineer > > > > Centre de Recherche en Informatique, Signal et Automatique de Lille > > CRIStAL - UMR 9189 > > French National Center for Scientific Research - http://www.cnrs.fr > > > > Web: http://guillep.github.io > > Phone: +33 06 52 70 66 13 > > > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

May 3, 2018

Re: [Pharo-dev] Failing tests

by Sven Van Caekenberghe

> On 3 May 2018, at 17:12, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > Hi all, > > There are a couple of Zn tests that are failing not even in the CI but locally in my machine. > This happens because the tests are trying to do a request to > > encrypted.google.com > > and expecting a 200, but they are instead receiving: > > 301 Moved Permanently text/html > > From the response, I guess we should do the request to > > https://www.google.com/search?q=Smalltalk > > instead. > > This solves the failures on my side. Sven, is that Ok if we push those patches to the tests to Pharo? Right, these would be the changed versions then: testPlain | query stream request response | self isNativeSSLPluginPresent ifFalse: [ ^ self ]. query := 'Smalltalk'. stream := ZdcSecureSocketStream openConnectionToHostNamed: 'www.google.com' port: 443. [ request := String streamContents: [ :out | out << 'GET /search?q=' << query << ' HTTP/1.1' << String crlf. out << 'Host: www.google.com' << String crlf. out << 'Connection: close' << String crlf. out << String crlf ]. stream connect. stream nextPutAll: request asByteArray. stream flush. response := stream upToEnd asString. ] ensure: [ stream close ]. self assert: (response includesSubstring: '200 OK'). self assert: (response includesSubstring: 'Google'). self assert: (response includesSubstring: 'Smalltalk'). testRequestResponse | query stream request response | self ensureSocketStreamFactory. self isNativeSSLPluginPresent ifFalse: [ ^ self ]. query := 'Smalltalk'. stream := ZdcSecureSocketStream openConnectionToHostNamed: 'www.google.com' port: 443. [ request := ZnRequest get: 'https://www.google.com/search?q=', query. stream connect. request writeOn: stream. stream flush. response := ZnResponse readFrom: stream. ] ensure: [ stream close ]. self assert: response isSuccess. self assert: (response contents includesSubstring: 'Google'). self assert: (response contents includesSubstring: 'Smalltalk'). I will apply them upstream as well. > -- > > Guille Polito > Research Engineer > > Centre de Recherche en Informatique, Signal et Automatique de Lille > CRIStAL - UMR 9189 > French National Center for Scientific Research - http://www.cnrs.fr > > Web: http://guillep.github.io > Phone: +33 06 52 70 66 13

May 3, 2018

[Ann] Iceberg 0.7.5

by Guillermo Polito

Time for the weekly Iceberg update. Iceberg 0.7.5. will be in the next Pharo build. Thanks to all brave users, issue reporters and contributors :). Key improvements: - Several improvements in metacello integration. (see #625, #664, #688 + more tests) - For those using CI, we think this release will also fix https://github.com/pharo-vcs/iceberg/issues/643 Infrastructure improvements: - In 0.7.4 we introduced in the build tests againt pharo 6.1 and 64 bits * https://travis-ci.org/pharo-vcs/iceberg/builds/372408795 - In 0.7.5 all iceberg tests run green on Pharo 6.1 32 bits * https://travis-ci.org/pharo-vcs/iceberg/builds/374433920 - In the next release we plan to do a pass on 64 bits ** Pharo 6.1 backport ** - We plan to backport this version to Pharo 6.1 - Cyril has been using the development version of Iceberg on Pharo 6.1 for a couple of weeks now. - This plus the green CI encourages us to backport to Pharo 6.1 Detailed ChangesLog: #625 Non explicit error while loading a project #758 [Regression] Repair action clone is not setting pharo repository #756 Iceberg dev-0.7 is broken in Pharo6.1 (Instance of IceTipURLLabelMorph did not understand #addEmphasis:) #749 Adding repair actions to the code subdirectory missing problem #655 Rename extension method buildToolbarItem of CommandActivator #755 Extracting the URL label behavior as a component that we can reuse #468 Commiting via Iceberg does not commit package removal #750 Add possibility to see current commit in Repositories/Package view #754 Showing and coping the Commit ID #753 Create branch dialog layout is broken #664 Package wrongly shown with "uncommited changes" status #752 Add "invalid ssh" #747 Cloning a Git repository should change the path with the project name. #738 Remove "pharo" Repository with "also remove from filesystem" gives error #746 Make tests run on pharo 6 #735 Issue while registering a new project on Pharo 6.1 #733 Add license file #740 Fogbugz panel: Improve label, focus order and layout #549 IceRestoreRepositoryModel should have a class comment #688 Duplicated project error when loading in a fresh image Enjoy, Guille in behalf of all people that contributed :)

May 3, 2018

Failing tests

by Guillermo Polito

Hi all, There are a couple of Zn tests that are failing not even in the CI but locally in my machine. This happens because the tests are trying to do a request to encrypted.google.com and expecting a 200, but they are instead receiving: 301 Moved Permanently text/html >From the response, I guess we should do the request to https://www.google.com/search?q=Smalltalk instead. This solves the failures on my side. Sven, is that Ok if we push those patches to the tests to Pharo? -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

May 3, 2018

Re: [Pharo-dev] [Pharo-users] [Ann] Iceberg 0.7.3

by Sven Van Caekenberghe

Hi Guillermo (et al), I finally found the time to test this new setup and I found it much easier and quite straightforward to make a PR. The new approach, with the simpler UI and lots more dialogs/explanations (and the glossary) is really well done. It felt much better, much higher quality. I am sure we are on the right track now. Thanks for all the hard work. Sven > On 25 Apr 2018, at 10:27, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > Hi all, > > We just introduced Iceberg 0.7.3 into Pharo. This new version solves several issues people had when contributing to Pharo in general and others. I've made a screencast on how to contribute to Pharo, and added some tutorial and glossary in Iceberg's wiki. > > Below the links and the changes log. > > Thanks for making your issue reports ^^. We will schedule a backporting to Pharo6.1 in a couple of weeks, once we have another iteration. > > Cheers, > Guille > > # Contribute to Pharo with Iceberg 0.7.3 > > - wiki page: https://github.com/pharo-vcs/iceberg/wiki/Contribute-to-Pharo-with-Iceberg-… > > - Screencast: https://www.youtube.com/watch?v=PK2yCu2rWCc&feature=youtu.because > > This screencast shows how to use Iceberg 0.7.3 to contribute to latest Pharo 7, by cloning from scratch your own (potentially outdated) clone. > > This video will guide you through: > - solve the "Missing local repository" by cloning > - solve the "Fetch required" that appears because the fork is out of date > - solve the "Detached working copy" by creating a new branch > - use the pharo plugin to create an issue branch > - make some changes, commit them and push them to your fork > - make a pull request > > If you already have a clone, you can just import an existing repository from your disk. The rest of the instructions should be the same. > > If you don't have a fork, create one before doing anything else. > > New videos to come with more explanations. > > # Iceberg Glossary > > https://github.com/pharo-vcs/iceberg/wiki/Iceberg-glossary > > # 0.7.3 ChangesLog > > â¢ #693: fixing problem when the announcement of changes in a package is nil. (bug, important) > â¢ #682: update update script (Pharo6-backport) > â¢ #681: Author name is not correctly decoded (UI, enhancement) > â¢ #680: Repair actions dialog should explain the situation (UI, enhancement, important) > â¢ #679: Create branch repair action should show create branch from issue if available (Pharo plugin, UI) > â¢ #678: Iceberg does not correctly recognize packages (bug, important) > â¢ #677: Unknown commit can only be solved with repair action (Model, bug, important) > â¢ #676: Unknown commit state is not properly shown (UI, bug, important) > â¢ #667: Merging branches with file deletion doesn't seem possible (bug, important, merge) > â¢ #666: Iceberg sometimes add a $ to commit message (Model, bug) > â¢ #662: The Pharo plugin has to do the fetch only if required. (Pharo plugin, enhancement) > â¢ #660: Add a star badge in the push button in case of a new branch () > â¢ #658: Progress Bar during checkout of Repository. (UI, enhancement) > â¢ #657: Confusing UI: Ghost Test maybe should be default? (UI, enhancement) > â¢ #656: Typo in Progress Bar (UI, bug) > â¢ #651: When pushing a new branch the list of commit is empty (UI, bug) > â¢ #650: "Create new branch from issue" is leaving image in detached working copy state () > â¢ #649: The VM is crashing when trying to use Iceberg from a saved image (bug) > â¢ #645: IceLibgitRepository should use "utilities" protocol instead of "utils" (clean up) > â¢ #644: Unnecessary temp in IceTipGitHubRepositoryPanel>>#getGitHubRepository" (clean up) > â¢ #643: LGit_GIT_ERROR: error authenticating: no auth sock variable loading a Tonel based baseline dependency in smalltalkCI (bug, important) > â¢ #639: Create pull request fails if branch has not been pushed (Github plugin, bug) > â¢ #636: The pull button should have a star badge when it has no upstream (UI, enhancement, important) > â¢ #634: Travis is not building Pull Requests (CI, bug, important) > â¢ #624: add "add remote" to remote picking on pull/push browsers (enhancement) > â¢ #610: Fix for issue #608 and #607. (clean up) > â¢ #609: New branch repair action does not refresh dirty packages (UI, bug) > â¢ #583: Creating a tonel project does not commit the properties file (Model, bug) > â¢ #542: Bug during commit of a new package (Model, bug) > > > -- > > Guille Polito > Research Engineer > > Centre de Recherche en Informatique, Signal et Automatique de Lille > CRIStAL - UMR 9189 > French National Center for Scientific Research - http://www.cnrs.fr > > Web: http://guillep.github.io > Phone: +33 06 52 70 66 13

May 3, 2018

[Pharo 7.0-dev] Build #829: 21818-RBPatternBlockNode-fix-problems-introduced-by-ast-Eval-use

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

There is a new Pharo build available! The status of the build #829 was: SUCCESS. The Pull Request #1285 was integrated: "21818-RBPatternBlockNode-fix-problems-introduced-by-ast-Eval-use" Pull request url: https://github.com/pharo-project/pharo/pull/1285 Issue Url: https://pharo.fogbugz.com/f/cases/21818 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 3, 2018

[Pharo 7.0-dev] Build #828: 21764-Optimize-RBSmallLinkContextselfMessages-and-friends

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

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

May 3, 2018