August 2018 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] New Iceberg Version 1.2.1

by Guillermo Polito

Hi, I'll write down some of the reasons of the project's design, like that I can afterwards copy paste it in the wiki :). First, this design did not came up from an egg. We worked on it for about two months. And it is thought to be backwards compatible and manage lots of metacello particularities. It may have things that are perfectible, sure, so let's discuss it. One of the main problems we saw in metacello, and that Iceberg inherited, was the "source subdirectory" thing. This source directory had to be specified in the CLIENT, meaning that every time we clone a repository we should know by heart the directory chose by its developer. Moreover, we lack a standard way to do it, so everybody does as he feels (root directory, src, source, repository, mc....). This has some bad consequences: - once a repository is referenced by some other project, it is more complicated to change its source directory. Imagine that tomorrow we set as standard that all git repos should have the code in src. Then voyage should change. And all its clients too. - Making a typo in the code subdirectory means sometimes super ugly errors from metacello that are difficult to debug and understand (e.g., "Cannot resolve BaselineOfMetacello WTF") Moreover, there was another problem that people started stumbling on: the fact that iceberg got confused sometimes thinking that an empty project was in filetree (to keep backwards compatibility with projects without a .properties). So we decided that for this release we wanted to revert a bit that situation. Think object: let's put the meta-data used to interpret a project's structure inside the project itself. The idea is that: - each project should contain both a .project and a .properties file. The first can contain arbitrary project meta-data (such as the source directory). The second contains the cypress properties, which are needed to correctly interpret the code inside the source directory. - a project without a .project file is an old project and cannot be interpreted, because we don't know the source directory - a project without a .properties file is an old project and is by default transformed in a project with a #filetree properties file - an old project cloned from iceberg detects the missing .project file and gives the user the opportunity to declare it (and then commit it explicitly) - an old project cloned and loaded from a Metacello expression defining a source directory will honnor the source directory defined in the Metacello expression (for backwards compatibility, and we have ~500 tests about this). # About defaults values / forcing the user to define a project First, notice that even when the repositories you load are just marked as "dirty". This is because in memory we add a project to your repository. But you're not forced to commit it. Actually, you can still load packages and baselines from that repository without committing. This is in line with Iceberg's "explicitness". We try to not do any destructive operation without asking the user first (that's why we have several preview windows for pushing, pulling, checkout, merge..., and why contrastingly with monticello we show the committed changes on the commit window...). So, instead of transparently "adding the file" we have decided to modify the project in memory and let the user the responsibility to commit that file. If there's a drawback, is that the repository is marked as dirty. Which is a bit noisy, yes, but still I think it's not so bad compared with the previous drawbacks. To solve this, we could have some default values, yes, and only mark it as dirty if the project does not follow the default value. This could work, but right now all projects use different names for their source directories. So the question is, what would be a good default? I'd like to use 'src' since this is short, well known and less alien (all these in the sense that we do not lose anything and we have a lot to gain by using it). However, not much repositories use 'src' so it will still produce a lot of "noise"... But still! Committing that file is a one-time operation. Once people fix their repositories adding the project meta-data, you will not see them dirty anymore. So we can see this as a transition noise too... Of course, new ideas are welcome. I'll let Pablo and Esteban add their points of view on this too. Guille

Aug. 7, 2018

[Pharo 7.0-dev] Build #1161: Modified the code to be similar to #select:thenDo:.

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

There is a new Pharo build available! The status of the build #1161 was: SUCCESS. The Pull Request #1651 was integrated: "Modified the code to be similar to #select:thenDo:." Pull request url: https://github.com/pharo-project/pharo/pull/1651 Issue Url: https://pharo.fogbugz.com/f/cases/22282 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Aug. 7, 2018

Re: [Pharo-dev] [Pharo 7.0-dev] Build #1160: Integrating Iceberg v1.2.1

by Esteban Lorenzano

yes. I find the message (SUCCESS or FAILURE) a bit misleading: it means some tests failed (usually the ones related to network problems). Cheers, Esteban > On 7 Aug 2018, at 12:32, Norbert Hartl <norbert(a)hartl.name> wrote: > > Is it the case that as soon as a mail like this (letâs assume it would have been a success) arrives at the mailing list there is a new pharo image on get.pharo.org <http://get.pharo.org/> that has it? > > Norbert > >> Am 07.08.2018 um 12:07 schrieb ci-pharo-ci-jenkins2(a)inria.fr <mailto:ci-pharo-ci-jenkins2@inria.fr>: >> >> There is a new Pharo build available! >> >> The status of the build #1160 was: FAILURE. >> >> The Pull Request #1672 was integrated: "Integrating Iceberg v1.2.1" >> Pull request url: https://github.com/pharo-project/pharo/pull/1672 <https://github.com/pharo-project/pharo/pull/1672> >> >> Issue Url: https://pharo.fogbugz.com/f/cases/22297 <https://pharo.fogbugz.com/f/cases/22297> >> Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2… <https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…> >

Aug. 7, 2018

Re: [Pharo-dev] Minheadless trial

by Ben Coman

On 7 August 2018 at 13:22, Ben Coman <btc(a)openinworld.com> wrote: > > > Next is to try loading an Image. > + Downloaded and unzipped http://files.pharo.org/image/7 0/latest-minimal-64.zip + In Visual Studio, right-clicked CMakeLists.txt > Debug and Launch Settings > pharo.exe + Edited the presented "launch.vs.json" as follows... { "version": "0.2.1", "defaults": {}, "configurations": [ { "type": "default", "project": "CMakeLists.txt", "projectTarget": "pharo.exe (dist\\pharo.exe)", "name": "pharo.exe with image (dist\\pharo.exe)", "args": [ "C:\\#Dev\\latest-minimal-64\\Pharo7.0-metacello-64bit-65cff7b.image", "s" ] }, ] } Now running "x64-Debug" and "pharo.exe with image" I find it gets hung up in... sqAllocateMemory(usqInt minHeapSize, usqInt desiredHeapSize) in call... alloc = sqAllocateMemorySegmentOfSizeAboveAllocatedSizeInto (roundUpToPage(desiredHeapSize), address, &allocBytes); with... desiredHeapSize ==> 39583744 (~39MB) address ==> 0x00007ff7d6e00000 where inside that call... void *sqAllocateMemorySegmentOfSizeAboveAllocatedSizeInto(sqInt size, void *minAddress, sqInt *allocatedSizePointer)" has... size ==> 39583744 minAddress ==> 0x00007ff7d6e00000 address ==> 0x00000000d6e00000 bytes ==> 39583744 (~39MB) delta ==> 1048576 it gets stuck the following loop... https://github.com/bencoman/opensmalltalk-vm/blob/8231b96f9b/platforms/win3… while ((usqIntptr_t)(address + bytes) > (usqIntptr_t)address) { alloc = VirtualAlloc(address, bytes, MEM_COMMIT|MEM_RESERVE, PAGE_READWRITE); ... if (alloc >= (char *)minAddress) && (alloc <= address + delta)) return alloc; ... address += delta; } where... alloc ==> 0x00000000d6e00000 (alloc >= (char *)minAddress) ==> false. which is effectively... (does this seem normal?) ((char *)minAddress-address)/delta ==> 134,180,864 loops before exit. but... (alloc >= (char *)address) ==> true. would exit on the first pass of the loop, except... /* For some reason (large page support?) we can ask for a page-aligned * address such as 0xNNNNf000 but VirtualAlloc will answer 0xNNNN0000. * So accept allocs above minAddress rather than allocs above address */ where back one level "minAddress" is derived like this... /* choose a suitable starting point. In MinGW the malloc heap is below the * program, so take the max of a malloc and something form uninitialized * data. */ hint = malloc(1); free(hint); hint = max(hint,(char *)&fIsConsole); address = (char *)(((usqInt)hint + alignment - 1) & ~(alignment - 1)); address passed-by-value into minAddress Now I'm out of my depth trying to understand the background on that logic, but if I blindly change the loop exit condition from... (alloc >= (char *)minAddress) to... (alloc >= (char *)address) then osvm_loadImage(tempImageNameAttempt() and subsequently osvm_loadDefaultImage() succeed. So some expert attention would be good here (as time permits) In the meantime, I'll forge ahead to play with osvm_run(); cheers -ben P.S. making "#define printProbes 1" and "fIsConsole = 1;" shows... probing [00000000D6E00000,00000000D93C0000) probing [00000000D6F00000,00000000D94C0000) probing [00000000D7000000,00000000D95C0000) probing [00000000D7100000,00000000D96C0000) probing [00000000D7200000,00000000D97C0000) probing [00000000D7300000,00000000D98C0000) probing [00000000D7400000,00000000D99C0000) probing [00000000D7500000,00000000D9AC0000) probing [00000000D7600000,00000000D9BC0000)

Aug. 7, 2018

Re: [Pharo-dev] Minheadless trial

by Tim Mackinnon

Guys - do keep pushing on this - I think its quite important in this world of serverlessâ¦ it shows we are very relevant. +10 > On 7 Aug 2018, at 13:36, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Iâm slowly working on that VM because we want it to be the default for Pharo 8. > In our vision, it should be a responsibility of the image to start or not a graphical UI, so we are preparing (we have been preparing to it for years, actually) to achieve this behaviour. > To make this work, we need all platforms covered (and another huge quantity of changes here and there). > Anyway, I didnât merge because I wanted to have win64 covered, not just what we have now, and since no-one was using that VM I didnât feel pression to do it :) > > Cheers, > Esteban > > >> On 7 Aug 2018, at 08:50, Norbert Hartl <norbert(a)hartl.name <mailto:norbert@hartl.name>> wrote: >> >> What keeps you from doing a pull request to opensmalltalk-vm ? >> >> Am 07.08.2018 um 07:47 schrieb Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>>: >> >>> Hi Ben, >>> >>> Sorry for coming here so late, I didnât see this thread before. >>> I already have a working minheadless branch that was adapted to Eliotâs process. >>> It was working for Pharo in Linux and Mac (Windows was ongoing but not finished, thatâs why is not pushed). >>> >>> You can find this branch here: >>> >>> https://github.com/estebanlm/opensmalltalk-vm/tree/add-minheadless-vm <https://github.com/estebanlm/opensmalltalk-vm/tree/add-minheadless-vm> >>> >>> Interesting part is that I didnât tackled any of the issues you are working on, so the work is easily mergeable :) >>> >>> Cheers, >>> Esteban >>> >>> Ps: with some changes in image, Iâm using exclusively this VM since a couple of months and it works fine. >>> >>> >>>> On 7 Aug 2018, at 07:22, Ben Coman <btc(a)openinworld.com <mailto:btc@openinworld.com>> wrote: >>>> >>>> On 7 August 2018 at 05:12, Eliot Miranda <eliot.miranda(a)gmail.com <mailto:eliot.miranda@gmail.com>> wrote: >>>> >>>> Hi Ben, >>>> Feel free to make this edit and commit >>>> >>>> I'm pushing changes here... >>>> https://github.com/bencoman/opensmalltalk-vm/tree/MinimalisticHeadless-x64-… <https://github.com/bencoman/opensmalltalk-vm/tree/MinimalisticHeadless-x64-…> >>>> >>>> and the diff can be tracked here... >>>> https://github.com/bencoman/opensmalltalk-vm/compare/MinimalisticHeadless..… <https://github.com/bencoman/opensmalltalk-vm/compare/MinimalisticHeadless..…> >>>> >>>> >>>> ------------------------ >>>> On 6 August 2018 at 13:22, Ben Coman <btc(a)openinworld.com <mailto:btc@openinworld.com>> wrote: >>>> On 6 August 2018 at 11:50, Ben Coman <btc(a)openinworld.com <mailto:btc@openinworld.com>> wrote: >>>> >>>> https://github.com/ronsaldo/opensmalltalk-vm/blob/be7b1c03/platforms/minhea… <https://github.com/ronsaldo/opensmalltalk-vm/blob/be7b1c03/platforms/minhea…> >>>> typedef HRESULT WINAPI (*SetProcessDpiAwarenessFunctionPointer) (int awareness); >>>> C2059 sqPlatformSpecific-Win32.c:80 syntax error: '(' >>>> E0651 a calling convention may not be followed by a nested declarator. >>>> >>>> The following change reduces build errors to 1... >>>> typedef HRESULT (*SetProcessDpiAwarenessFunctionPointer) (int awareness); >>>> >>>> but I'm not sure of the implications. >>>> >>>> I found the correct solution to this... >>>> "The trick is placing the [call declaration] inside the parentheses" >>>> https://stackoverflow.com/questions/4830355/function-pointer-and-calling-co… <https://stackoverflow.com/questions/4830355/function-pointer-and-calling-co…> >>>> >>>> i.e. the following compiles cleanly >>>> typedef HRESULT (WINAPI *SetProcessDpiAwarenessFunctionPointer) (int awareness); >>>> >>>> >>>> ----------------------------- >>>> Now running the VM (without parameters) I get... >>>> Debug Assertion Failed! >>>> Program: ...\x64-Debug\dist\pharo.exe >>>> File: minkernel\crts\ucrt\src\appcrt\tran\amd64\ieee.c >>>> Line: 106 >>>> Expression: (mask&~(_MCW_DN | _MCW_EM | _MCW_RC))==0 >>>> >>>> at the call to _controlfp(FPU_DEFAULT, _MCW_EM | _MCW_RC | _MCW_PC | _MCW_IC); >>>> https://github.com/ronsaldo/opensmalltalk-vm/blob/be7b1c03/platforms/minhea… <https://github.com/ronsaldo/opensmalltalk-vm/blob/be7b1c03/platforms/minhea…> >>>> >>>> >>>> According to https://msdn.microsoft.com/en-us/library/e9b52ceh.aspx <https://msdn.microsoft.com/en-us/library/e9b52ceh.aspx> >>>> x64 does not support _MCW_PC or _MCW_IC >>>> but I'm clueless about the implications of these FPU flags. >>>> Could our math guys please advise? >>>> >>>> Eliminating those two flags allows a VM run successfully without loading an Image. >>>> i.e. it successfully passes... >>>> osvm_initialize(); >>>> osvm_parseCommandLineArguments(argc, argv); >>>> osvm_initializeVM(); >>>> >>>> Next is to try loading an Image. >>>> >>>> cheers -ben >>> >

Aug. 7, 2018

Re: [Pharo-dev] Minheadless trial

by Esteban Lorenzano

Iâm slowly working on that VM because we want it to be the default for Pharo 8. In our vision, it should be a responsibility of the image to start or not a graphical UI, so we are preparing (we have been preparing to it for years, actually) to achieve this behaviour. To make this work, we need all platforms covered (and another huge quantity of changes here and there). Anyway, I didnât merge because I wanted to have win64 covered, not just what we have now, and since no-one was using that VM I didnât feel pression to do it :) Cheers, Esteban > On 7 Aug 2018, at 08:50, Norbert Hartl <norbert(a)hartl.name> wrote: > > What keeps you from doing a pull request to opensmalltalk-vm ? > > Am 07.08.2018 um 07:47 schrieb Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>>: > >> Hi Ben, >> >> Sorry for coming here so late, I didnât see this thread before. >> I already have a working minheadless branch that was adapted to Eliotâs process. >> It was working for Pharo in Linux and Mac (Windows was ongoing but not finished, thatâs why is not pushed). >> >> You can find this branch here: >> >> https://github.com/estebanlm/opensmalltalk-vm/tree/add-minheadless-vm <https://github.com/estebanlm/opensmalltalk-vm/tree/add-minheadless-vm> >> >> Interesting part is that I didnât tackled any of the issues you are working on, so the work is easily mergeable :) >> >> Cheers, >> Esteban >> >> Ps: with some changes in image, Iâm using exclusively this VM since a couple of months and it works fine. >> >> >>> On 7 Aug 2018, at 07:22, Ben Coman <btc(a)openinworld.com <mailto:btc@openinworld.com>> wrote: >>> >>> On 7 August 2018 at 05:12, Eliot Miranda <eliot.miranda(a)gmail.com <mailto:eliot.miranda@gmail.com>> wrote: >>> >>> Hi Ben, >>> Feel free to make this edit and commit >>> >>> I'm pushing changes here... >>> https://github.com/bencoman/opensmalltalk-vm/tree/MinimalisticHeadless-x64-… <https://github.com/bencoman/opensmalltalk-vm/tree/MinimalisticHeadless-x64-…> >>> >>> and the diff can be tracked here... >>> https://github.com/bencoman/opensmalltalk-vm/compare/MinimalisticHeadless..… <https://github.com/bencoman/opensmalltalk-vm/compare/MinimalisticHeadless..…> >>> >>> >>> ------------------------ >>> On 6 August 2018 at 13:22, Ben Coman <btc(a)openinworld.com <mailto:btc@openinworld.com>> wrote: >>> On 6 August 2018 at 11:50, Ben Coman <btc(a)openinworld.com <mailto:btc@openinworld.com>> wrote: >>> >>> https://github.com/ronsaldo/opensmalltalk-vm/blob/be7b1c03/platforms/minhea… <https://github.com/ronsaldo/opensmalltalk-vm/blob/be7b1c03/platforms/minhea…> >>> typedef HRESULT WINAPI (*SetProcessDpiAwarenessFunctionPointer) (int awareness); >>> C2059 sqPlatformSpecific-Win32.c:80 syntax error: '(' >>> E0651 a calling convention may not be followed by a nested declarator. >>> >>> The following change reduces build errors to 1... >>> typedef HRESULT (*SetProcessDpiAwarenessFunctionPointer) (int awareness); >>> >>> but I'm not sure of the implications. >>> >>> I found the correct solution to this... >>> "The trick is placing the [call declaration] inside the parentheses" >>> https://stackoverflow.com/questions/4830355/function-pointer-and-calling-co… <https://stackoverflow.com/questions/4830355/function-pointer-and-calling-co…> >>> >>> i.e. the following compiles cleanly >>> typedef HRESULT (WINAPI *SetProcessDpiAwarenessFunctionPointer) (int awareness); >>> >>> >>> ----------------------------- >>> Now running the VM (without parameters) I get... >>> Debug Assertion Failed! >>> Program: ...\x64-Debug\dist\pharo.exe >>> File: minkernel\crts\ucrt\src\appcrt\tran\amd64\ieee.c >>> Line: 106 >>> Expression: (mask&~(_MCW_DN | _MCW_EM | _MCW_RC))==0 >>> >>> at the call to _controlfp(FPU_DEFAULT, _MCW_EM | _MCW_RC | _MCW_PC | _MCW_IC); >>> https://github.com/ronsaldo/opensmalltalk-vm/blob/be7b1c03/platforms/minhea… <https://github.com/ronsaldo/opensmalltalk-vm/blob/be7b1c03/platforms/minhea…> >>> >>> >>> According to https://msdn.microsoft.com/en-us/library/e9b52ceh.aspx <https://msdn.microsoft.com/en-us/library/e9b52ceh.aspx> >>> x64 does not support _MCW_PC or _MCW_IC >>> but I'm clueless about the implications of these FPU flags. >>> Could our math guys please advise? >>> >>> Eliminating those two flags allows a VM run successfully without loading an Image. >>> i.e. it successfully passes... >>> osvm_initialize(); >>> osvm_parseCommandLineArguments(argc, argv); >>> osvm_initializeVM(); >>> >>> Next is to try loading an Image. >>> >>> cheers -ben >>

Aug. 7, 2018

Re: [Pharo-dev] New Iceberg Version 1.2.1

by Norbert Hartl

Forgot one thing. I find the new project feature quite intrusive. It will add those file to all repos unasked. So I have a lot of dirty projects I have no write access to. How is this supposed to work. Isnât it better to assume defaults and add an option to add project files? Norbert > Am 07.08.2018 um 12:05 schrieb tesonep(a)gmail.com: > > 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.0> + https://github.com/pharo-vcs/iceberg/releases/tag/v1.2.1 <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 <mailto:tesonep@gmail.com>

Aug. 7, 2018

Re: [Pharo-dev] New Iceberg Version 1.2.1

by Norbert Hartl

Great, thanks! I used 1.2.0 a few days ago and I had some problems: - some repos like voyage had a .properties file in the repo with content â{}â. This made the repo unusable. The only thing noticed is that in the repo view in iceberg the packages were named Voyage-Core.package instead of Voyage-Core - I had a problem that I cherry picked changes in my project and commited but then all other changes were gone, too. I need to revert and then reapply the changes with epicea in order to have it in iceberg. It can be it was influenced by the above problem but I need to check again which I will. Norbert > Am 07.08.2018 um 12:05 schrieb tesonep(a)gmail.com: > > 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.0> + https://github.com/pharo-vcs/iceberg/releases/tag/v1.2.1 <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 <mailto:tesonep@gmail.com>

Aug. 7, 2018

Re: [Pharo-dev] [Pharo 7.0-dev] Build #1160: Integrating Iceberg v1.2.1

by Norbert Hartl

Is it the case that as soon as a mail like this (letâs assume it would have been a success) arrives at the mailing list there is a new pharo image on get.pharo.org <http://get.pharo.org/> that has it? Norbert > Am 07.08.2018 um 12:07 schrieb ci-pharo-ci-jenkins2(a)inria.fr: > > There is a new Pharo build available! > > The status of the build #1160 was: FAILURE. > > The Pull Request #1672 was integrated: "Integrating Iceberg v1.2.1" > Pull request url: https://github.com/pharo-project/pharo/pull/1672 > > Issue Url: https://pharo.fogbugz.com/f/cases/22297 > Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Aug. 7, 2018

[Pharo 7.0-dev] Build #1160: Integrating Iceberg v1.2.1

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

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

Aug. 7, 2018