- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Pharo-users] New Iceberg Version 1.2.1
by Norbert Hartl Aug. 9, 2018

Aug. 9, 2018

> Am 08.08.2018 um 14:12 schrieb Herbert VojÄÃk <herby(a)mailbox.sk>: > > > > Damien Pollet wrote on 8. 8. 2018 13:53: >> First of all, quick stupid question: I'm currently loading my code with gitlocal://./src <gitlocal://./src> as the repository URL (my workflow starts in a terminal rather than in a Pharo image) >> Should I just remove the /src part, now that my repo has the project metadata? >> Also, are more features planned for the .project file? E.g. what about storing a default selection for Calypso and the Test Runner in there? >> On Wed, 8 Aug 2018 at 10:28, Norbert Hartl <norbert(a)hartl.name <mailto:norbert@hartl.name> <mailto:norbert@hartl.name <mailto:norbert@hartl.name>>> wrote: >> - I donât think there can be a âstandard wayâ of defining source >> directory. And I donât think that a tool should enforce this >> however. I keep frontend and backend code in some repositories >> together so the source is in my case in backend/source. What does it >> mean for users not using the âstandardâ name? >> Sure there can. Look at any ruby or maven project, they all have strong conventions for organizing projects and standard config files for deviating from those conventions. >> I would have preferred if Iceberg picked one convention (arbitrarily) in the absence of a .project file instead of forcing its explicit presence. IMHO the choice of default directory per se (be it ./, ./src, ./source or whatever) matters less than the fact that there is a convention in place. >> - I donât see why there needs to be a 1:1 relationship between a >> repository and working copy in pharo. It is like this at the moment >> already but the .project file manifests this. So it should not be >> supported to have more source dirs in one git repo? It might be not >> a good idea that the client has to write the source dir but it opens >> the possibility that there can be more than one. >> I see your point here, but by using separate source directories you're sort of creating a hydra projectâ¦ What I mean here is that the source directories are separate, but their histories are tangled. If you want separate source dirs it kinda means that you want separate change histories, doesn't it? What if the same class has diverging definitions in separate directories (I wonder what maven does in that caseâ¦)? > > There are monorepos. Some people / companies love them. > One of these companies we know for good. It is google. Google has one (!) repositoryf for all their software. And that is the point I want to stretch here. One repo with one project and a standard source directory is too theoretical and too narrow in thoughts. Today there is no possibility to reliably make one product out of multiple repos. Git submodule and git subtree are not even close to something reliable and usable. Descriptions like metacello are language centric. So what is the most secure way of defining a single product? It is the mono repo. That is the main reason I have my sources in backend/source because there is a javascript frontend in the same repo because I want to have one reliable source that defines my product and I can be sure that the backend and frontend are always the ones that match. I donât think it is a good idea if we once leave the island to embrace something like git just to make git islandish a little later. Just to be very clear. We are talking about two files: .project and .properties. I have nothing against .properties because we have multiple formats possible so making it explicit is a good idea. But .project makes every repo a single source repo. If we enforce .properties files why do we not scan the repo for directories containing this file? If none is found we cannot know (or we add looking at some default locations). If multiple directory are found I can add that to iceberg as a real project out of the combination for repository-source directory. This way I could have multiple projects out of one repo. And with the possibility of having multiple source directories it is obvious that the path still needs to be added to a url in metacello. Unless there is one of this directories marked to be the default which would be loaded if no directory is given. This way the default directory would be the one selected if only one is there. So you can have multiple projects in one repo and if this is only one per project the directory can be automatically resolved. Use case kept. Norbert >> On the other hand, separate source directories would be helpful to work with git-subrepo and similar toolsâ¦ >> -- >> Damien Pollet >> type less, do more [ | ] http://people.untyped.org/damien.pollet <http://people.untyped.org/damien.pollet>

3 2

New Iceberg Version 1.2.1
by tesonep＠gmail.com Aug. 9, 2018

Aug. 9, 2018

New Iceberg Version 1.2.1 [ https://github.com/pharo-vcs/iceberg/releases/tag/v1.2.0 + https://github.com/pharo-vcs/iceberg/releases/tag/v1.2.1] Thanks to all brave users, issue reporters, and contributors :). This version includes the implementation of projects. Projects are a way of defining basic metadata of the repository. Now, this metadata just includes the source directory. This means that people do not need anymore to provide ALL THE TIME the source directory. Instead, every repository includes a project file that provides it. Iceberg will guide people to create the given file. This file is managed by Iceberg and people should not touch it from the outside or accept the consequences :). This version is integrated in the latest Pharo 7 images. #New Features - #866 Introduce first version of Projects #Infrastructure - #870 Improving tests of Metacello Integration - #903 Split basic tests from metacello tests in CI - #914 Sync Wiki with documentation directory automatically - #934 Manually check metacello integration dialogs - #935 Try to refrite the metacello integration tests. - #940 Installation in new Pharo should also bootstrap pharo repository #Enhancements - #675 The History of a Method in Calypso should show a progress bar. - #788 Show progress during network operations (fetch,push, ...) Libgit. - #875 Tonel plugin does not delete .filetree Migration - #897 Update to OSSubprocess 1.0.1 - #911 Repair Checkout branch should appear in "no project found" - #933 Fix Edit repository dialog - #939 IceInteractiveErrorVisitor duplicates IceTipInteractiveErrorVisitor - #944 Extract pharo repository bootstrap code into iceberg #Bug Fixes - #828 Convert sources to tonel raises an Exception - #839 Infinite loop in IceGitLocalRepositoryType if the path is wrong - #849 VM crash while saving credentials Credential Manager - #851 .properties file is not create if project is imported and not cloned. - #869 Error msg after an http timeout is unreadable - #873 Error with credential provider Credential Manager - #874 The integration with Metacello does not work when there is a src directory, but not project file. - #880 Putting "." in project src field gives dnu - #884 Edit Project Dialog tries to select 'src' folder as default, but does not handle if it does not exists - #886 Edit Project Dialog does not allow to select the root of the repository as source directory - #888 Could not locate repository does not have subdirectory anymore. - #889 Loading an unborn project through metacello does not work - #894 GitHubAPI fails when the API responds with a 204 No Content - #901 I get a DNU projectName.... - #902 Edit project metadata does not detect default format - #918 Cloning pharo from a sync'ed repository does not correctly show dirty packages - #928 Pull request cancel - #930 Changed ivar/slot name in stateful trait not recognized as a change - #931 DNU when trying to unload an Iceberg pkg where underlying Pharo pkg has been removed - #932 Pharo repository forgets packages - #938 Do not catch assertion failures - #941 Iceberg pre-installed repository has wrong repair action - #946 Fixing Metacello Integration Tests - #948 Cloning from github creates an invalid remote - #950 Iceberg v1.2.0 breaks projects Metacello Integration bug - #951 New project window should be coherent on the vocabulary UI enhancement - #953 Make remote request anonymous enhancement - #952 Cannot Clone Pharo Repository Pharo plugin bug - #955 Repair actions for repositories with fetch required are wrong UI bug -- Pablo Tesone. tesonep(a)gmail.com

4 7

[Pharo 7.0-dev] Build #1166: 22306-RubSurfaceSelectionShape-ivar-tag-unused
by ci-pharo-ci-jenkins2＠inria.fr Aug. 9, 2018

Aug. 9, 2018

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

1 0

[Pharo 7.0-dev] Build #1165: 22302-isDefinition-on-RBVariableNode-should-check-sequence-defines
by ci-pharo-ci-jenkins2＠inria.fr Aug. 9, 2018

Aug. 9, 2018

There is a new Pharo build available! The status of the build #1165 was: FAILURE. The Pull Request #1676 was integrated: "22302-isDefinition-on-RBVariableNode-should-check-sequence-defines" Pull request url: https://github.com/pharo-project/pharo/pull/1676 Issue Url: https://pharo.fogbugz.com/f/cases/22302 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

CI Down
by Guillermo Polito Aug. 8, 2018

Aug. 8, 2018

Hi all, Since yesterday evening, CI is down because of Inria network problems at the level of Paris. Inria tells us that they do not have yet an estimation of how much time it will take to fix it. Until then, there will be no CI testing PRs nor new builds. Previous Pharo builds are still available in http://files.pharo.org/, which is hosted in OVH. I'll keep you updated, Guille

4 6

[Pharo 7.0-dev] Build #1164: 21955-remove-methods-from-TClass-and-friends
by ci-pharo-ci-jenkins2＠inria.fr Aug. 8, 2018

Aug. 8, 2018

There is a new Pharo build available! The status of the build #1164 was: FAILURE. The Pull Request #1657 was integrated: "21955-remove-methods-from-TClass-and-friends" Pull request url: https://github.com/pharo-project/pharo/pull/1657 Issue Url: https://pharo.fogbugz.com/f/cases/21955 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1163: 22268-MCFileTreeFileSystemUtils-classwriteSteamForindo-should-delete-the-file-if-it-exists
by ci-pharo-ci-jenkins2＠inria.fr Aug. 8, 2018

Aug. 8, 2018

There is a new Pharo build available! The status of the build #1163 was: SUCCESS. The Pull Request #1639 was integrated: "22268-MCFileTreeFileSystemUtils-classwriteSteamForindo-should-delete-the-file-if-it-exists" Pull request url: https://github.com/pharo-project/pharo/pull/1639 Issue Url: https://pharo.fogbugz.com/f/cases/22268 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1162: 22245-Package-ReleaseTests-should-be-Release-Tests
by ci-pharo-ci-jenkins2＠inria.fr Aug. 8, 2018

Aug. 8, 2018

There is a new Pharo build available! The status of the build #1162 was: SUCCESS. The Pull Request #1674 was integrated: "22245-Package-ReleaseTests-should-be-Release-Tests" Pull request url: https://github.com/pharo-project/pharo/pull/1674 Issue Url: https://pharo.fogbugz.com/f/cases/22245 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

About the infinite debugger
by Guillermo Polito Aug. 8, 2018

Aug. 8, 2018

Hi all, during today's sprint we have been working with lots of people on the infinite debugger problem (https://pharo.fogbugz.com/f/cases/22085/) We have checked the emails sent in the latest month. Then, together with Quentin, Pablo, Pavel, Yoan we have been discussing and testing hypothesis all day. We have been also comparing the debuggers code between pharo 3/4 (where the bug was is present) and pharo 7, but this was not necessarily straight forward as the code is not the same and there is no easy diff... AAAAND, we have found that the problem may come from a wrong pragma marker. Just removing that pragma gives us back the same behaviour as in Pharo 3/4. :D https://github.com/pharo-project/pharo/pull/1621 I know that the exception handling/debugging has been modified several times in the latest years (some refactorings, hiding contexts...), we unfortunately don't have tests for it, so I'd like some more pair of eyes on it. Ben, Martin could you take a look? Thanks all for the fish, Guille

14 27

Iceberg: Cannot Clone Pharo Repository
by Eric Gade Aug. 7, 2018

Aug. 7, 2018

I am having (new) issues cloning my forked pharo repository in a fresh P7 image for development. Git objects are pulled from the repository successfully, but during the checkout phase the error posted below occurs (I can also provide a fuel dump by request). Here is my current system: OSX 10.13.1 (High Sierra) Pharo 7.0 Build information: Pharo-7.0+alpha.build.1159.sha.65cff7b3c78af7ecf3728abdd2f44bf0cbc8a548 (32 Bit) My fork: https://github.com/darth-cheney/pharo Error Stack: ``` IceUnknownCommit(Object)>>doesNotUnderstand: #adopt IcePharoPlugin>>repositoryWillBeCreated: [ :each | each repositoryWillBeCreated: aRepository ] in IcePluginManager>>repositoryWillBeCreated: in Block: [ :each | each repositoryWillBeCreated: aRepositor...etc... Array(SequenceableCollection)>>do: IcePluginManager>>repositoryWillBeCreated: IceRepositoryCreator>>cloneRepository [ self validate. self isCloning ifTrue: [ self cloneRepository ] ifFalse: [ self addLocalRepository ] ] in IceRepositoryCreator>>createRepository in Block: [ self validate.... BlockClosure>>on:do: IceRepositoryCreator>>createRepository [ ^ IceRepositoryCreator new repository: repository; remote: (IceGitRemote url: self remoteUrl); location: self projectLocation location; createRepository ] in IceTipGitHubRepositoryPanel(IceTipGitRepositoryPanel)>>newRepository in Block: [ ^ IceRepositoryCreator new... [ :bar | bar label: aString. aBlock value ] in MorphicUIManager(UIManager)>>informUser:during: in Block: [ :bar | ... [ :bar | aBlock value: bar ] in MorphicUIManager>>informUserDuring: in Block: [ :bar | aBlock value: bar ] BlockClosure>>cull: [ ^ block cull: self ] in [ self prepareForRunning. CurrentJob value: self during: [ ^ block cull: self ] ] in Job>>run in Block: [ ^ block cull: self ] [ activeProcess psValueAt: index put: anObject. aBlock value ] in CurrentJob(DynamicVariable)>>value:during: in Block: [ activeProcess psValueAt: index put: anObject.... BlockClosure>>ensure: CurrentJob(DynamicVariable)>>value:during: CurrentJob class(DynamicVariable class)>>value:during: [ self prepareForRunning. CurrentJob value: self during: [ ^ block cull: self ] ] in Job>>run in Block: [ self prepareForRunning.... BlockClosure>>ensure: Job>>run MorphicUIManager(UIManager)>>displayProgress:from:to:during: MorphicUIManager>>informUserDuring: MorphicUIManager(UIManager)>>informUser:during: IceTipGitHubRepositoryPanel(IceTipGitRepositoryPanel)>>newRepository IceTipGitHubRepositoryPanel>>newRepository IceTipRegisterRepositoryDialog>>doAccept [ self doAccept. true ] in IceTipRegisterRepositoryDialog(IceTipOptionDialog)>>accept in Block: [ self doAccept.... BlockClosure>>on:do: IceTipRegisterRepositoryDialog(IceTipOptionDialog)>>accept ``` -- Eric

2 3