- Pharo-dev - lists.pharo.org

Unable to repair repository
by Alistair Grant Nov. 6, 2018

Nov. 6, 2018

Hi Everyone, In the latest Pharo (88c6b8d), attempting to repair the pharo repository, i.e. clone it, first a warning is raised: "There is no associated repository configured." and then a DNU: #pathString was sent to nil. The DNU is because IceTipCopyCommitishCommand>>canBeExecutedInContext: now sends #commitId instead of #shortCommitId. IceTipRepositoryModel>>shortCommitId has an exception handler, while #commitId doesn't. Can someone explain why the warning was added? It is a bit annoying to have to click through dialogs telling me that the repository I'm trying to create needs to be created. Using the generic Error exception handler has the risk of hiding other problems. Wouldn't it be better to create a IceRepositoryMissing error, or similar? Thanks, Alistair

2 2

[ANN] Iceberg v1.3.1
by Cyril Ferlicot Nov. 6, 2018

Nov. 6, 2018

Hello! This week we are releasing the version v1.3 of Iceberg. (https://github.com/pharo-vcs/iceberg/releases/tag/v1.3.0 +https://github.com/pharo-vcs/iceberg/releases/tag/v1.3.1) This version will be available after we merge this PR: https://github.com/pharo-project/pharo/pull/1951 This release contains some new features such as the support of self hosted gitlab, integration with github, etc. It also contains multiple bug fixes, cleanups and enhancements. On the CI part, Guille made the Appveyor build green! This will increase the stability of the windows support. Thanks to all contributors. Enjoy! Full changelog: Features #1021 Self hosted gitlab support #1027 Improved new tag dialog to generate semantic versionning tags #1044 Show a button "View on Github" when creating a PR #1008 Add "create branch from GitHub issue" option #1048 Add commands to open remotes on Github #1010 Add menu entry in extras to force calculate diff Bug corrections #975 Metacello asks too many times what to install when there are conflicting versions #980 Iceberg should Identify better the packages and the normal files #982 The Edit Project should have a Warning if it will affect the packages #986 Iceberg does not realize changes in extended classes #999 Pulling and pushing to a gitolite server asks password #984 Conversion to Tonel generates corrupted .properties #1041 Filter in repository view don't work with capital letters #1019 Metacello Integration leaves Monticello leftover repositories #859 Creating a branch and pushing does not sets the upstream #1043 Packages starting with lowercase not recognized #991 Error on right click in the project editon wizard #775 Reviewing a PR is broken #1036 Debugger if we try to merge without selecting a branch #1064 Fix failing tests regarding clean code in Pharo Enhancements #988 Iceberg should load the packages in a single MCLoader (This will make the loads of packages atomic) #1001 Use "instance creation" instead of "instance-creation" for method protocol name #1004 Use displayScaleFactor in UI #977 Add ToolTip help to the Commands #1030 Better support for binary files #1034 SSH passphrase is now hidden Cleanups #1018 Iceberg UI relies on deprecated classes from Spec and Commander #1051 Clean useless huge hierarchy in Github plugin UI Infrastructure Enhancements #1023 Fix CI for windows -- Cyril Ferlicot https://ferlicot.fr

2 2

Now this is fun ...
by Sven Van Caekenberghe Nov. 5, 2018

Nov. 5, 2018

https://github.com/pharo ;-)

6 6

[Pharo 7.0-dev] Build #1363: 22627-Integrate-Iceberg-131
by ci-pharo-ci-jenkins2＠inria.fr Nov. 5, 2018

Nov. 5, 2018

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

1 0

[ANN] 22477 DelayScheduler cleanup and refactoring [was: Where do we go now ?]
by Ben Coman Nov. 5, 2018

Nov. 5, 2018

On Fri, 13 Apr 2018 at 13:56, Benoit St-Jean via Pharo-users < pharo-users(a)lists.pharo.org> wrote: > Do we really need 8 delay schedulers (DelayMicrosecondScheduler, > DelayMillisecondScheduler, DelayNullScheduler, > DelayExperimentalSpinScheduler, DelaySpinScheduler, DelayTicklessScheduler, > DelayExperimentalCourageousScheduler, DelayExperimentalSemaphoreScheduler) > ? > I've cleaned the delay scheduling subsystem [1] to condense these alternatives and separate orthogonal functionality. After a couple of reviews this was integrated and made active in last week's Build 1273. Could anyone with test scenarios from previous issues with delays have a bash at stressing the latest build. The old(existing) DelaySpinScheduler remains in the system so it can be activated as a point of comparison (System > Settings > System > Delay Scheduler). Pending any adverse reports the final step will be to remove the old hierarchy next week. There remain separate mutex and semaphore based schedulers since: * they differ by only a couple of overridden methods * their slightly different implementations help highlight the core algorithm * they provide a simple in-Image example of different synchronisation mechanisms. * in isolating edge cases its useful to be able to compare results between implementations I've retained both microsecond and millisecond operation, but extracted into "ticker" classes orthogonal to the "scheduling" classes since: * it makes the core scheduling algorithm independent of time base * millisecond (or other custom) timebase might(?) be more efficient on smaller 32-bit embedded systems * tests can now simulate ticker time to avoid tests interfering with system's-active-scheduler VM interaction (which may be the source of some random CI failures) * delay scheduler tests are now independent of real-time (which may be the source of some random CI failures where delays are affected by varying CI server loads) * when multi-threaded FFI callbacks become available, may facilitate experimenting with: * wake-up from native timers * wake-up of embedded Pharo from the encompassing system Other refactors: * during system snapshot, save/restore of resumption times was happening at user priority which risks a race condition reported at [2]. *All* modification of resumption times now occurs at timing/highest priority. [1] https://pharo.manuscript.com/f/cases/22477/DelayScheduler-cleanup-and-refac… [2] https://pharo.manuscript.com/f/cases/18359/

5 6

[Pharo 7.0-dev] Build #1362: 22627-Integrate-Iceberg-131
by ci-pharo-ci-jenkins2＠inria.fr Nov. 5, 2018

Nov. 5, 2018

There is a new Pharo build available! The status of the build #1362 was: FAILURE. The Pull Request #1951 was integrated: "22627-Integrate-Iceberg-131" Pull request url: https://github.com/pharo-project/pharo/pull/1951 Issue Url: https://pharo.fogbugz.com/f/cases/22627 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1361: 22620-Move-zippedunzipped-from-String-to-ByteArray
by ci-pharo-ci-jenkins2＠inria.fr Nov. 5, 2018

Nov. 5, 2018

There is a new Pharo build available! The status of the build #1361 was: FAILURE. The Pull Request #1947 was integrated: "22620-Move-zippedunzipped-from-String-to-ByteArray" Pull request url: https://github.com/pharo-project/pharo/pull/1947 Issue Url: https://pharo.fogbugz.com/f/cases/22620 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1360: 22625-FileReferencenextVersion-gets-stuck-at-11
by ci-pharo-ci-jenkins2＠inria.fr Nov. 5, 2018

Nov. 5, 2018

There is a new Pharo build available! The status of the build #1360 was: SUCCESS. The Pull Request #1950 was integrated: "22625-FileReferencenextVersion-gets-stuck-at-11" Pull request url: https://github.com/pharo-project/pharo/pull/1950 Issue Url: https://pharo.fogbugz.com/f/cases/22625 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1359: 22614-Integrate-Calypso-v0120
by ci-pharo-ci-jenkins2＠inria.fr Nov. 5, 2018

Nov. 5, 2018

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

1 0

Esteban's ChangeLog week of 29 October 2018
by estebanlm＠gmail.com Nov. 5, 2018

Nov. 5, 2018

Hello! This is my weekly ChangeLog, from 29 October 2018 to 4 November 2018. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=29/10/2018&to=4/11/2018 ChangeLog ========= 29 October 2018: ---------------- * I made a PR to update [Calypso in Pharo 7 to version 0.12.0](https://github.com/pharo-project/pharo/pull/1943). While this should be very easy, in case of Calypso it is a but harder because of its dependency graph, that looks a bit like this : Calypso ClassAnnotation Commander ClassAnnotation SystemCommands Commander ClassAnnotationAnyway, in the medium term, I want to create a tool to do "chained-releases", which is not so easy because we need to modify baselines and do commits, pushs and tags. But it will be possible to do :) cheers! Esteban

1 0