Re: [Pharo-dev] How to use git with gitfiletree

[Peter Uhnák]

you would need something like gittonel://, which doesn't exist

but you could still use tonel://, commit in pharo using metacello, and then
in command line using git... annoying but if you want to use tonel+git
without iceberg, then you have no other choice (unless you actually create
gittonel://)

On Thu, Mar 1, 2018 at 10:48 PM, Alexandre Bergel 
wrote:

> I will not be able to try soon. Semester is starting here, with its load
> of things…
>
> Alexandre
>
>
> > On Mar 1, 2018, at 4:36 PM, Stephane Ducasse 
> wrote:
> >
> > Alex
> >
> > Now I was thinking that it should be easy to introduce a tonel fileout
> > menu on a package. We should pay attention to extensions differently.
> > Then for loading I would just support load and no merge since the
> > merge will be done by git on the command-line.
> > If you give a try, I would like to try because right now I'm stuck
> > with my book code.
> > I do not have the time to try to hack this now. But may be saturday on
> > the highway if I do not drive.
> >
> > Stef
> >
> > On Thu, Mar 1, 2018 at 10:04 PM, Stephane Ducasse
> >  wrote:
> >> I read
> >> https://www.peteruhnak.com/blog/2016/07/25/how-to-use-
> git-and-github-with-pharo/
> >> and I have the impression that I cannot use tonel and gitfiletree.
> >>
> >> So I will wait for the next version of iceberg and focus on my
> >> vacation during that period.
> >>
> >> Stef
> >>
> >> On Thu, Mar 1, 2018 at 9:46 PM, Alexandre Bergel
> >>  wrote:
> >>> That would be fantastic to have!
> >>>
> >>> Alexandre
> >>>
>  On Mar 1, 2018, at 2:23 PM, Stephane Ducasse 
> wrote:
> 
>  Hi
> 
>  I would like to use git without iceberg.
>  It is possible to use gitfiletree with tonel?
> 
>  I want to commit in tonel format
>  from Pharo 6.1 and not using Iceberg because it does not work
>  on my code.
> 
>  I'm looking for a small tutorial.
> 
>  Stef
> 
> >>>
> >>>
> >
>
>
>

Re: [Pharo-dev] Is Smalltalk CI working with 6.1?

[Peter Uhnák]

This is because tonel is not yet supported.

I've worked on that a bit last year but I don't know why I stopped... I
think because I couldn't commit to SmalltalkCI without generating billion
metadata changes (tried different Pharo versions, iceberg, gitfiletree,
filetree), and in the end got frustrated and stopped.

If someone wants to continue, it should be pretty straight-forward
https://github.com/peteruhnak/smalltalkCI/commit/413e6a59b30e869ab49c4b50b7eb0539f1d696a0

On Thu, Mar 1, 2018 at 10:40 PM, Gabriel Cotelli 
wrote:

> Looks Ok to me.
>
> We have some baselines with 6.1 support and SmalltalkCI running against
> travis and it works.
>
> But not in tonel format, we're using the old filetree format, so maybe
> there's something to configure to enable tonel support in SmalltalkCI?
>
> Just for reference look at the baseline and SmalltalkCI code in
> https://github.com/ba-st/Buoy .
>
> On Thu, Mar 1, 2018 at 6:25 PM, Stephane Ducasse 
> wrote:
>
>> Hi
>>
>> I'm trying to make travis and smalltalkci working for the roelTyper.
>> Followed the tutorial of Peter
>> but I cannot make it work.
>>
>> https://travis-ci.org/RMODINRIA/RoelTyper
>>
>> I get this error
>>
>> ..RETRY->BaselineOfRoelTyper
>> ...RETRY->BaselineOfRoelTyper
>> ...FAILED->BaselineOfRoelTyperCould not resolve: BaselineOfRoelTyper
>> [BaselineOfRoelTyper] in
>> /home/travis/smalltalkCI-master/_builds/pharo-local/package-cache
>> filetree:///home/travis/build/RMODINRIA/RoelTyper/src
>>
>> and I have no idea how to debug it since the BaselineOfRoelTyper is in
>> the src folder
>>
>> https://github.com/RMODINRIA/RoelTyper/tree/master/src
>>
>> I do not have idea how to debug this.
>>
>> Stef
>>
>>
>

Re: [Pharo-dev] How to use git with gitfiletree

[Alexandre Bergel]

I will not be able to try soon. Semester is starting here, with its load of 
things…

Alexandre


> On Mar 1, 2018, at 4:36 PM, Stephane Ducasse  wrote:
> 
> Alex
> 
> Now I was thinking that it should be easy to introduce a tonel fileout
> menu on a package. We should pay attention to extensions differently.
> Then for loading I would just support load and no merge since the
> merge will be done by git on the command-line.
> If you give a try, I would like to try because right now I'm stuck
> with my book code.
> I do not have the time to try to hack this now. But may be saturday on
> the highway if I do not drive.
> 
> Stef
> 
> On Thu, Mar 1, 2018 at 10:04 PM, Stephane Ducasse
>  wrote:
>> I read
>> https://www.peteruhnak.com/blog/2016/07/25/how-to-use-git-and-github-with-pharo/
>> and I have the impression that I cannot use tonel and gitfiletree.
>> 
>> So I will wait for the next version of iceberg and focus on my
>> vacation during that period.
>> 
>> Stef
>> 
>> On Thu, Mar 1, 2018 at 9:46 PM, Alexandre Bergel
>>  wrote:
>>> That would be fantastic to have!
>>> 
>>> Alexandre
>>> 
 On Mar 1, 2018, at 2:23 PM, Stephane Ducasse  
 wrote:
 
 Hi
 
 I would like to use git without iceberg.
 It is possible to use gitfiletree with tonel?
 
 I want to commit in tonel format
 from Pharo 6.1 and not using Iceberg because it does not work
 on my code.
 
 I'm looking for a small tutorial.
 
 Stef
 
>>> 
>>> 
> 

Re: [Pharo-dev] Is Smalltalk CI working with 6.1?

[Gabriel Cotelli]

Looks Ok to me.

We have some baselines with 6.1 support and SmalltalkCI running against
travis and it works.

But not in tonel format, we're using the old filetree format, so maybe
there's something to configure to enable tonel support in SmalltalkCI?

Just for reference look at the baseline and SmalltalkCI code in
https://github.com/ba-st/Buoy .

On Thu, Mar 1, 2018 at 6:25 PM, Stephane Ducasse 
wrote:

> Hi
>
> I'm trying to make travis and smalltalkci working for the roelTyper.
> Followed the tutorial of Peter
> but I cannot make it work.
>
> https://travis-ci.org/RMODINRIA/RoelTyper
>
> I get this error
>
> ..RETRY->BaselineOfRoelTyper
> ...RETRY->BaselineOfRoelTyper
> ...FAILED->BaselineOfRoelTyperCould not resolve: BaselineOfRoelTyper
> [BaselineOfRoelTyper] in
> /home/travis/smalltalkCI-master/_builds/pharo-local/package-cache
> filetree:///home/travis/build/RMODINRIA/RoelTyper/src
>
> and I have no idea how to debug it since the BaselineOfRoelTyper is in
> the src folder
>
> https://github.com/RMODINRIA/RoelTyper/tree/master/src
>
> I do not have idea how to debug this.
>
> Stef
>
>

Re: [Pharo-dev] How to use git with gitfiletree

[Stephane Ducasse]

Alex

Now I was thinking that it should be easy to introduce a tonel fileout
menu on a package. We should pay attention to extensions differently.
Then for loading I would just support load and no merge since the
merge will be done by git on the command-line.
If you give a try, I would like to try because right now I'm stuck
with my book code.
I do not have the time to try to hack this now. But may be saturday on
the highway if I do not drive.

Stef

On Thu, Mar 1, 2018 at 10:04 PM, Stephane Ducasse
 wrote:
> I read
> https://www.peteruhnak.com/blog/2016/07/25/how-to-use-git-and-github-with-pharo/
> and I have the impression that I cannot use tonel and gitfiletree.
>
> So I will wait for the next version of iceberg and focus on my
> vacation during that period.
>
> Stef
>
> On Thu, Mar 1, 2018 at 9:46 PM, Alexandre Bergel
>  wrote:
>> That would be fantastic to have!
>>
>> Alexandre
>>
>>> On Mar 1, 2018, at 2:23 PM, Stephane Ducasse  
>>> wrote:
>>>
>>> Hi
>>>
>>> I would like to use git without iceberg.
>>> It is possible to use gitfiletree with tonel?
>>>
>>> I want to commit in tonel format
>>> from Pharo 6.1 and not using Iceberg because it does not work
>>> on my code.
>>>
>>> I'm looking for a small tutorial.
>>>
>>> Stef
>>>
>>
>>

[Pharo-dev] [Pharo 7.0-dev] Build #640: 21455-MessageBrowserTest-needs-to-be-moved-to-a-dedicated-test-package

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!

The status of the build #640 was: FAILURE.

The Pull Request #997 was integrated: 
"21455-MessageBrowserTest-needs-to-be-moved-to-a-dedicated-test-package"
Pull request url: https://github.com/pharo-project/pharo/pull/997

Issue Url: https://pharo.fogbugz.com/f/cases/21455
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/640/

Re: [Pharo-dev] How can I introduce a new package in Pharo 70

[Stephane Ducasse]

Thanks Cyril.

Since I break everything I touch I will not do it.
Today the PR that I did went totally fucked up and I closed it and
this one was trivial.

So I will give a try. I will wait until the next version of Iceberg
because I cannot work
anymore with the current version: sometimes it works smoothly and
perfect and sometimes
this is horrible and crashing all the time.

I do not expect that the bash scripts get in commit when I did not
touch the command line

https://github.com/pharo-project/pharo/pull/995

try {
cleanWs()
unstash "bootstrap${architecture}"
- shell "bash -c 'bootstrap/scripts/run${prefix}Tests.sh
${architecture} ${env.STAGE_NAME}'"
- junit allowEmptyResults: true, testResults: "${env.STAGE_NAME}*.xml"
+ shell "bash -c 'bootstrap/scripts/run${prefix}Tests.sh ${architecture}'"
+ junit allowEmptyResults: true, testResults: '*.xml'
success = !(currentBuild.result == 'UNSTABLE')
echo "Tests run with result ${currentBuild.result}"
} catch(e) {
@@ -40,7 +40,7 @@ def runTests(architecture, prefix=''){
}
return success || (tries == retryTimes)
}
- archiveArtifacts allowEmptyArchive: true, artifacts:
"${env.STAGE_NAME}*.xml", fingerprint: true
+ archiveArtifacts allowEmptyArchive: true, artifacts: '*.xml',
fingerprint: true
cleanWs()
}

So there is something fundamentally broken with the merge.

Stef

On Thu, Mar 1, 2018 at 4:38 PM, Cyril Ferlicot  wrote:
> On Thu, Mar 1, 2018 at 4:28 PM, Stephane Ducasse
>  wrote:
>> Hi
>>
>> I would like to gather all refactoring-based deprecated methods and I
>> need to introduce a package in Pharo 70.
>> How do I do that?
>>
> Hi,
> You need to:
> - Add the package to the related baseline (Else it will not be loaded
> during the bootstrap)
> - In Iceberg add the package to the project. In the package tab, use
> "Add package"
> - Synchronize full repository to commit
>
>> Stef
>>
>
>
>
> --
> Cyril Ferlicot
> https://ferlicot.fr
>

[Pharo-dev] Is Smalltalk CI working with 6.1?

[Stephane Ducasse]

Hi

I'm trying to make travis and smalltalkci working for the roelTyper.
Followed the tutorial of Peter
but I cannot make it work.

https://travis-ci.org/RMODINRIA/RoelTyper

I get this error

..RETRY->BaselineOfRoelTyper
...RETRY->BaselineOfRoelTyper
...FAILED->BaselineOfRoelTyperCould not resolve: BaselineOfRoelTyper
[BaselineOfRoelTyper] in
/home/travis/smalltalkCI-master/_builds/pharo-local/package-cache
filetree:///home/travis/build/RMODINRIA/RoelTyper/src

and I have no idea how to debug it since the BaselineOfRoelTyper is in
the src folder

https://github.com/RMODINRIA/RoelTyper/tree/master/src

I do not have idea how to debug this.

Stef

Re: [Pharo-dev] How to use git with gitfiletree

[Stephane Ducasse]

I read
https://www.peteruhnak.com/blog/2016/07/25/how-to-use-git-and-github-with-pharo/
and I have the impression that I cannot use tonel and gitfiletree.

So I will wait for the next version of iceberg and focus on my
vacation during that period.

Stef

On Thu, Mar 1, 2018 at 9:46 PM, Alexandre Bergel
 wrote:
> That would be fantastic to have!
>
> Alexandre
>
>> On Mar 1, 2018, at 2:23 PM, Stephane Ducasse  wrote:
>>
>> Hi
>>
>> I would like to use git without iceberg.
>> It is possible to use gitfiletree with tonel?
>>
>> I want to commit in tonel format
>> from Pharo 6.1 and not using Iceberg because it does not work
>> on my code.
>>
>> I'm looking for a small tutorial.
>>
>> Stef
>>
>
>

[Pharo-dev] [Pharo 7.0-dev] Build #639: 21458-remove-Package-MessageBrowserRefactoringAddition

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!

The status of the build #639 was: SUCCESS.

The Pull Request #994 was integrated: 
"21458-remove-Package-MessageBrowserRefactoringAddition"
Pull request url: https://github.com/pharo-project/pharo/pull/994

Issue Url: https://pharo.fogbugz.com/f/cases/21458
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/639/

Re: [Pharo-dev] [Pharo-users] [ANN] ba-st Web Stack new versions available

[Alexandre Bergel]

Impressive work!!

Alexandre

> On Feb 19, 2018, at 3:08 PM, Gabriel Cotelli  wrote:
> 
> Hi,
> 
> We're happy to announce a new version of the Web Stack hosted at 
> https://github.com/ba-st/. This is a multi-release announcement of the 
> following related project versions:
>   • Willow v6.0.0. Changes since latest announcement:
>   • Added interaction on document load
>   • Improved temporarily disabling command
>   • Added identification support to unordered lists
>   • Improved new location opening commands
>   • Improved interaction fuctions to always include the event as 
> a parameter
>   • Improved asynchronic links to auto-configure a script doing 
> preventDefault
>   • Refactored the link support
>   • Willow-Bootstrap v6.0.0 
>   • Updated Willow base support to v6.0.0 
>   • Improved Split Button support to allow triggering actions on 
> the main button only
>   • Willow-JQueryUI v5.0.0
>   • Updated Willow base support to v6.0.0 
>   • Willow-SpinKit v3.0.0
>   • Updated Willow base support to v6.0.0 
>   • Willow-Playground v2.0.0 
>   • Updated dependencies to the latest versions
>   • RenoirSt v4.0.0
>   • Removed Pharo 4 support
>   • Updated dependencies
> SemanticUI integration is still a work in progress. There's a new Materialize 
> CSS integration being worked on by Francisco Ortiz.
> 
> Find a more detailed changelog and migration instructions on the release 
> pages of each repository.
> 
> Anyone interested in joining our ba-st projects is welcomed, and you can also 
> start following our new tech blog @ mercap for Smalltalk and Pharo related 
> posts and experience reports.
> 
> Regards,
> Gabriel Cotelli, Maxi Tabacman and all the contributors.

Re: [Pharo-dev] How to use git with gitfiletree

[Alexandre Bergel]

That would be fantastic to have!

Alexandre

> On Mar 1, 2018, at 2:23 PM, Stephane Ducasse  wrote:
> 
> Hi
> 
> I would like to use git without iceberg.
> It is possible to use gitfiletree with tonel?
> 
> I want to commit in tonel format
> from Pharo 6.1 and not using Iceberg because it does not work
> on my code.
> 
> I'm looking for a small tutorial.
> 
> Stef
> 

[Pharo-dev] [Pharo 7.0-dev] Build #638: Added Contribute.md

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!

The status of the build #638 was: SUCCESS.

The Pull Request #991 was integrated: "Added Contribute.md"
Pull request url: https://github.com/pharo-project/pharo/pull/991

Issue Url: https://pharo.fogbugz.com/f/cases/patch
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/638/

[Pharo-dev] How to use git with gitfiletree

[Stephane Ducasse]

Hi

I would like to use git without iceberg.
It is possible to use gitfiletree with tonel?

I want to commit in tonel format
from Pharo 6.1 and not using Iceberg because it does not work
on my code.

I'm looking for a small tutorial.

Stef

Re: [Pharo-dev] Help not losing my changes :(

[Stephane Ducasse]

Thanks. In fact all the commit was fucked up so I will refork and reclone. :(


On Thu, Mar 1, 2018 at 6:03 PM, Alistair Grant  wrote:
> If this is the same as a known problem, just close the error and try
> to commit again.
>
> Cheers,
> Alistair
>
> On 1 March 2018 at 16:58, Stephane Ducasse  wrote:
>> I took the latest version of Pharo 70 and I coded some cleanings
>> and when I change the remote to pull from Pharo I got a lot of fetch
>> and load happening
>> But I do not know if I should merge incoming.
>> probably.
>>
>> And then I got an error IceVersionDoesNotExist: there is no versoin
>> for package: SunitUI-Testing in commit 00db9
>>
>>
>> Now when I commit my work I get KeyNotFound: key 'Metacello-Cypress'
>> not found in Dictionary
>> I often get this KeyNotFound error.
>>
>> What can I do to avoid losing my work.
>>
>> Stef
>>
>

[Pharo-dev] [Pharo 7.0-dev] Build #637: 21456-Small-clean-EyeInspector-remove-Test-move-resize-on-ImageMorph-to-ImageMorph

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!

The status of the build #637 was: SUCCESS.

The Pull Request #992 was integrated: 
"21456-Small-clean-EyeInspector-remove-Test-move-resize-on-ImageMorph-to-ImageMorph"
Pull request url: https://github.com/pharo-project/pharo/pull/992

Issue Url: https://pharo.fogbugz.com/f/cases/21456
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/637/

Re: [Pharo-dev] [Vm-dev] FFI Struct Argument Pass By Value Fails on Mac 64 bit

[Todd Blanchard]

I got pulled off to do some $ work and haven't got back to this but I would 
like to get back to it.

Has there been any progress on this in the publicly available 64bit VM?

I see there is a completely separate FFI plugin for 32 vs 64 and worry 64 is 
still not quite ready for real work.

> On Dec 3, 2017, at 7:18 AM, Ben Coman  wrote:
> 
> 
> 
> On 27 November 2017 at 00:24, Todd Blanchard  > wrote:
>  
> i'm getting the idea that we should probably write a test suite/library for 
> FFI
> 
> I noticed these...
> * 
> https://github.com/OpenSmalltalk/opensmalltalk-vm/blob/Cog/platforms/unix/plugins/SqueakFFIPrims/ffi-test-main.c
>  
> 
> * 
> https://github.com/OpenSmalltalk/opensmalltalk-vm/blob/Cog/platforms/Cross/plugins/SqueakFFIPrims/sqFFITestFuncs.c
>  
> 
> * 
> https://github.com/OpenSmalltalk/opensmalltalk-vm/blob/Cog/platforms/Cross/plugins/IA32ABI/AlienSUnitTestProcedures.c
>  
> 
> 
> These look like c-code test frames for FFI.  Could these be built by the 
> OpenSmalltalk CI to be normally shipped with the VM so that Image-side CI can 
> test against them?
> 
> And also some general info...
> * 
> https://github.com/OpenSmalltalk/opensmalltalk-vm/blob/Cog/platforms/unix/plugins/SqueakFFIPrims/00README
>  
> 
> 
>  
> 
>> On Nov 24, 2017, at 12:54 AM, Ben Coman > > wrote:
>> 
>> 
>> On 24 November 2017 at 13:16, Ben Coman > > wrote:
>> 
>> 
>> On 22 November 2017 at 21:59, Ben Coman > > wrote:
>> 
>> 
>> On 22 November 2017 at 13:38, Todd Blanchard > > wrote:
>>  
>> I've been trying to track this down for a couple weeks now.
> 
>> 
>> I have concluded that structs passed by value to functions on the 64 bit VM 
>> are not properly populated.  The struct's memory is all zero'd.
>> 
>> I found this while trying to work with LibClang and found that functions 
>> that fetched code locations from code ranges always returned invalid zero'd 
>> locations.  After spending some time with lldb I have traced the problem 
>> into the native code and found that the argument is not correct.
>> 
>> I've carved out the wee bit of clang to reproduce this in a tiny library.
>> 
>> The gist of it is below and the entire file is included.  Basically the 
>> struct passed to the function clang_getRangeStart is zero'd memory 
>> regardless of the data I send from the image side.
> 
> 
> My last analysis discovered something interesting about strings defined 
> inside shared libraries being handled differently, but only later realised I 
> had chased the wrong rabbit down the hole.  
>  
> I've now investigated the premise you actually poses, and I agree, that 
> structs being zero is some cases.  
> The attached zipfile containing  libstruct.c  a few comparison cases - three 
> "good" layouts that work fine and one "bad" that mostly gets zeros but 
> sometimes other weird numbers.  There is a Makefile with three main targets:
> 1. make layout - statically compiles  libstruct.c  and runs produced  a.out  
> to display structure layouts 
> 
> 2. make run - downloads Pharo, starts it loading  LibStruct.st 
>   , then you manually run 
> LibStruct>>>LibStructTest>>#testStructs and observe structure values on 
> console
> 
> 3. make debug - starts LLDB to run Pharo with breakpoints pre-configured for 
> when you run #testStructs.  
>Note Pharo will freeze and you need to move to LLDB.  Try these 
> commands... 
>   frame variable
>   call print_struct(_fmt, )
>   continue
> 
> That works on Ubuntu 16.04 64 bit. 
> You will need to tune it for OSX.
> clang and lldb are required.
> 
> 
> The offsets configured in the class variables of all ExternalStructs 
> correctly matches that reported by the C code test frame results here...
> 
> $ make layout
> clang -g libstruct.c
> ./a.out
> 
> GoodStruct1:
>   uint32_t:int1:  01 4 
>   uint32_t:int2:  05 4 
> GoodStruct2:
>   uint32_t:int1:  01 4 
>   uint32_t:int2:  05 4 
>   void*:ptr_data: 09 8 
> GoodStruct3:
>   void*:ptr_data: 01 8 
>   uint32_t:int1:  09 4 
>   uint32_t:int2:  13 4 
> BadStruct:
>   void*:ptr_data1:01 8 
>   void*:ptr_data2:09 8 
>   

Re: [Pharo-dev] Help not losing my changes :(

[Alistair Grant]

If this is the same as a known problem, just close the error and try
to commit again.

Cheers,
Alistair

On 1 March 2018 at 16:58, Stephane Ducasse  wrote:
> I took the latest version of Pharo 70 and I coded some cleanings
> and when I change the remote to pull from Pharo I got a lot of fetch
> and load happening
> But I do not know if I should merge incoming.
> probably.
>
> And then I got an error IceVersionDoesNotExist: there is no versoin
> for package: SunitUI-Testing in commit 00db9
>
>
> Now when I commit my work I get KeyNotFound: key 'Metacello-Cypress'
> not found in Dictionary
> I often get this KeyNotFound error.
>
> What can I do to avoid losing my work.
>
> Stef
>

[Pharo-dev] [Pharo 7.0-dev] Build #636: 21454-remove-newAutoAcceptTextEntryForgetTextsetTextgetEnabledhelpentryCompletion

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!

The status of the build #636 was: SUCCESS.

The Pull Request #993 was integrated: 
"21454-remove-newAutoAcceptTextEntryForgetTextsetTextgetEnabledhelpentryCompletion"
Pull request url: https://github.com/pharo-project/pharo/pull/993

Issue Url: https://pharo.fogbugz.com/f/cases/21454
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/636/

[Pharo-dev] Help not losing my changes :(

[Stephane Ducasse]

I took the latest version of Pharo 70 and I coded some cleanings
and when I change the remote to pull from Pharo I got a lot of fetch
and load happening
But I do not know if I should merge incoming.
probably.

And then I got an error IceVersionDoesNotExist: there is no versoin
for package: SunitUI-Testing in commit 00db9


Now when I commit my work I get KeyNotFound: key 'Metacello-Cypress'
not found in Dictionary
I often get this KeyNotFound error.

What can I do to avoid losing my work.

Stef

Re: [Pharo-dev] [Request for comment] Hermes package

[teso...@gmail.com]

Nice Idea, I have added comments to the packages, classes and methods. This
will be in the new version that will be integrated with the new Traits
implementation.
I am still cleaning some comments that Denis and Pavel have done and we can
integrate it.

Then we change the name, I liked BootstrapCodeLoader, I think I can find a
non conflicting prefix.

Cheers.

On Thu, Mar 1, 2018 at 4:29 PM, Stephane Ducasse 
wrote:

> +1
>
> On Thu, Mar 1, 2018 at 2:42 PM, Denis Kudriashov 
> wrote:
> > While it is very bootstrap oriented library it would be better to rename
> it
> > to BootstapCodeLoader.
> > Or PharoBootstrap-CodeLoader because we already use this prefix
> >
> > 2018-03-01 13:20 GMT+01:00 Stephane Ducasse :
> >>
> >> Hermes is a private binary format that is used to load compiled code
> >> when there is no compiler during the bootstrap.
> >> So basically hermes is loading the compiler to be able to compile
> >> other packages.
> >>
> >> Stef
> >>
> >> On Wed, Feb 28, 2018 at 4:55 PM, Alexandre Bergel
> >>  wrote:
> >> > Side question: What is Hermes?
> >> >
> >> > Alexandre
> >> >
> >> >> On Feb 28, 2018, at 1:42 AM, Torsten Bergmann 
> wrote:
> >> >>
> >> >> ... to all participating authors of the Hermes package:
> >> >>
> >> >> PLEASE COMMENT YOUR CLASSES SO WE CAN CLEAN UP AND PREPARE A
> >> >> POLISHED PHARO 7 RELEASE
> >> >>
> >> >> So many uncommented classes in there today...
> >> >>
> >> >> We can do better and we should. I dont ask for detailed documentation
> >> >> but a single comment why the class is there or what it should care
> >> >> about is often already enough.
> >> >>
> >> >> If you have time to write code then you also have the time to write
> >> >> a simple class comment!
> >> >>
> >> >> So please do you homework (which is a general request to authors
> >> >> of other packages as well)
> >> >>
> >> >> Bye
> >> >> T.
> >> >>
> >> >
> >> >
> >>
> >
>
>


-- 
Pablo Tesone.
teso...@gmail.com

[Pharo-dev] Integration deadlock?

[Stephane Ducasse]

I have a change that crosscuts calypso and iceberg.
I will produce a PR and each project should check because else I will get stuck
waiting in an integration deadlock.

https://pharo.fogbugz.com/f/cases/21459/Fixing-last-users-of-theNonMetaclass

Re: [Pharo-dev] How can I introduce a new package in Pharo 70

[Cyril Ferlicot]

On Thu, Mar 1, 2018 at 4:28 PM, Stephane Ducasse
 wrote:
> Hi
>
> I would like to gather all refactoring-based deprecated methods and I
> need to introduce a package in Pharo 70.
> How do I do that?
>
Hi,
You need to:
- Add the package to the related baseline (Else it will not be loaded
during the bootstrap)
- In Iceberg add the package to the project. In the package tab, use
"Add package"
- Synchronize full repository to commit

> Stef
>



-- 
Cyril Ferlicot
https://ferlicot.fr

Re: [Pharo-dev] [Request for comment] Hermes package

[Stephane Ducasse]

+1

On Thu, Mar 1, 2018 at 2:42 PM, Denis Kudriashov  wrote:
> While it is very bootstrap oriented library it would be better to rename it
> to BootstapCodeLoader.
> Or PharoBootstrap-CodeLoader because we already use this prefix
>
> 2018-03-01 13:20 GMT+01:00 Stephane Ducasse :
>>
>> Hermes is a private binary format that is used to load compiled code
>> when there is no compiler during the bootstrap.
>> So basically hermes is loading the compiler to be able to compile
>> other packages.
>>
>> Stef
>>
>> On Wed, Feb 28, 2018 at 4:55 PM, Alexandre Bergel
>>  wrote:
>> > Side question: What is Hermes?
>> >
>> > Alexandre
>> >
>> >> On Feb 28, 2018, at 1:42 AM, Torsten Bergmann  wrote:
>> >>
>> >> ... to all participating authors of the Hermes package:
>> >>
>> >> PLEASE COMMENT YOUR CLASSES SO WE CAN CLEAN UP AND PREPARE A
>> >> POLISHED PHARO 7 RELEASE
>> >>
>> >> So many uncommented classes in there today...
>> >>
>> >> We can do better and we should. I dont ask for detailed documentation
>> >> but a single comment why the class is there or what it should care
>> >> about is often already enough.
>> >>
>> >> If you have time to write code then you also have the time to write
>> >> a simple class comment!
>> >>
>> >> So please do you homework (which is a general request to authors
>> >> of other packages as well)
>> >>
>> >> Bye
>> >> T.
>> >>
>> >
>> >
>>
>

[Pharo-dev] How can I introduce a new package in Pharo 70

[Stephane Ducasse]

Hi

I would like to gather all refactoring-based deprecated methods and I
need to introduce a package in Pharo 70.
How do I do that?

Stef

Re: [Pharo-dev] "External module not found" while loading metacello project

[Cyrille Delaunay]

Yeah this was imprecise

Here is our build process:
To get a mac pharo vm, we use this url:

https://files.pharo.org/get-files/61/pharo-mac-stable.zip

To get a pharo image, we use the one retrieved with:

wget --quiet -O - get.pharo.org/61+vm | bash


I juste made a test with fresh image and vm retrieved using the above links.
But I was not able to reproduce !

So I guess there might be something wrong during our build process (in
between getting image + vm AND getting our source code loaded)
Or maybe we are not really getting these images and vms.

I will investigate more and come back if I have more elements




2018-03-01 11:05 GMT+01:00 Esteban Lorenzano :

> whet is this “latest vm” ? how do you get it?
> which 6 image are you getting?
>
> Esteban
>
>
> On 1 Mar 2018, at 10:39, Cyrille Delaunay  wrote:
>
> Hello,
>
> I am getting the error "External module not found" while trying to load a
> metacello project.
> I am running the latest 32 bits pharo 6 image and vm available with
> zeroconf script.
> The concerned external module seems to be "libgit" (self ffiCall: #(int
> git_libgit2_init()))
> But the plugin seems to be available within the vm folder:
>
> 
>
> The issue can be reproduced with any metacello project.
> For example, from the catalog, you can load the configuration of
> VoyageMongo.
> Then inspect:
>
> Metacello new
> configuration: 'VoyageMongo';
> version: #development;
> repository: 'http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo60';
> load.
>
> I am able to collect to following information using the System reporter:
>
> Image
> -
> /Users/cdelaunay/Work/synectique-images/demo/synintegration/61/Java-OnWeb-
> Demo/Java-OnWeb.image
> Pharo6.0
> Latest update: #60535
> Unnamed
>
> Virtual Machine
> ---
> /Users/cdelaunay/Work/synectique-images/demo/synintegration/61/Java-OnWeb-
> Demo/pharo-mac-vm/Pharo.app/Contents/MacOS/Pharo
> CoInterpreter VMMaker.oscog-eem.2254 uuid: 
> 4f2c2cce-f4a2-469a-93f1-97ed941df0ad
> Jul 20 2017
> StackToRegisterMappingCogit VMMaker.oscog-eem.2252 uuid:
> 2f3e9b0e-ecd3-4adf-b092-cce2e2587a5c Jul 20 2017
> VM: 201707201942 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $
> Date: Thu Jul 20 12:42:21 2017 -0700 $ Plugins: 201707201942
> https://github.com/OpenSmalltalk/opensmalltalk-vm.git $
>
> Mac OS X built on Jul 20 2017 21:45:23 UTC Compiler: 4.2.1 Compatible
> Apple LLVM 6.1.0 (clang-602.0.53)
> VMMaker versionString VM: 201707201942 https://github.com/
> OpenSmalltalk/opensmalltalk-vm.git $ Date: Thu Jul 20 12:42:21 2017 -0700
> $ Plugins: 201707201942 https://github.com/OpenSmalltalk/opensmalltalk-
> vm.git $
> CoInterpreter VMMaker.oscog-eem.2254 uuid: 
> 4f2c2cce-f4a2-469a-93f1-97ed941df0ad
> Jul 20 2017
> StackToRegisterMappingCogit VMMaker.oscog-eem.2252 uuid:
> 2f3e9b0e-ecd3-4adf-b092-cce2e2587a5c Jul 20 2017
>
> Virtual Machine Commandline Options
> ---
> none
>
> Loaded VM Modules
> -
> AioPlugin VMConstruction-Plugins-AioPlugin-eem.18 (i)
> B2DPlugin VMMaker.oscog-eem.2252 (i)
> BitBltPlugin VMMaker.oscog-eem.2243 (i)
> FT2Plugin Freetype-Plugin-EstebanLorenzano.70 (e)
> FilePlugin VMMaker.oscog-nice.2233 (i)
> FloatArrayPlugin VMMaker.oscog-eem.2254 (i)
> JPEGReadWriter2Plugin VMMaker.oscog-eem.2243 (e)
> LargeIntegers v2.0 VMMaker.oscog-eem.2079 (i)
> LocalePlugin VMMaker.oscog-eem.2064 (e)
> Matrix2x3Plugin VMMaker.oscog-eem.1975 (i)
> MiscPrimitivePlugin VMMaker.oscog-eem.2254 (i)
> SecurityPlugin VMMaker.oscog-eem.2166 (i)
> SocketPlugin VMMaker.oscog-eem.2064 (i)
> SqueakFFIPrims
> SurfacePlugin Jul 20 2017 (e)
> UnixOSProcessPlugin VMConstruction-Plugins-OSProcessPlugin.oscog-dtl.56
> (i)
> ZipPlugin VMMaker.oscog-eem.2243 (i)
>
> VM Built-in Modules
> ---
> ADPCMCodecPlugin VMMaker.oscog-eem.2079 (i)
> AioPlugin VMConstruction-Plugins-AioPlugin-eem.18 (i)
> AsynchFilePlugin VMMaker.oscog-eem.2030 (i)
> B2DPlugin VMMaker.oscog-eem.2252 (i)
> BMPReadWriterPlugin VMMaker.oscog-eem.1975 (i)
> BitBltPlugin VMMaker.oscog-eem.2243 (i)
> DSAPrims CryptographyPlugins-eem.12 (i)
> DropPlugin VMMaker.oscog-eem.1975 (i)
> FFTPlugin VMMaker.oscog-eem.2243 (i)
> FilePlugin VMMaker.oscog-nice.2233 (i)
> FloatArrayPlugin VMMaker.oscog-eem.2254 (i)
> GeniePlugin v2.0 15 June 2017 VMMaker.oscog-eem.2243 (i)
> HostWindowPlugin VMMaker.oscog-eem.2064 (i)
> IA32ABI VMMaker.oscog-eem.2156 (i)
> LargeIntegers v2.0 VMMaker.oscog-eem.2079 (i)
> Matrix2x3Plugin VMMaker.oscog-eem.1975 (i)
> MiscPrimitivePlugin VMMaker.oscog-eem.2254 (i)
> SecurityPlugin VMMaker.oscog-eem.2166 (i)
> SocketPlugin VMMaker.oscog-eem.2064 (i)
> SoundCodecPrims VMMaker.oscog-eem.1975 (i)
> SoundGenerationPlugin VMMaker.oscog-eem.2079 (i)
> SoundPlugin VMMaker.oscog-eem.2218 (i)
> SqueakFFIPrims
> StarSqueakPlugin VMMaker.oscog-eem.2079 (i)
> UnixOSProcessPlugin VMConstruction-Plugins-OSProcessPlugin.oscog-dtl.56
> (i)
> VMProfileMacSupportPlugin 

[Pharo-dev] [Pharo 7.0-dev] Build #635: 21453-small-cleanup-in-Rubric

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!

The status of the build #635 was: SUCCESS.

The Pull Request #990 was integrated: "21453-small-cleanup-in-Rubric"
Pull request url: https://github.com/pharo-project/pharo/pull/990

Issue Url: https://pharo.fogbugz.com/f/cases/21453
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/635/

Re: [Pharo-dev] [Request for comment] Hermes package

[Denis Kudriashov]

While it is very bootstrap oriented library it would be better to rename it
to BootstapCodeLoader.
Or PharoBootstrap-CodeLoader because we already use this prefix

2018-03-01 13:20 GMT+01:00 Stephane Ducasse :

> Hermes is a private binary format that is used to load compiled code
> when there is no compiler during the bootstrap.
> So basically hermes is loading the compiler to be able to compile
> other packages.
>
> Stef
>
> On Wed, Feb 28, 2018 at 4:55 PM, Alexandre Bergel
>  wrote:
> > Side question: What is Hermes?
> >
> > Alexandre
> >
> >> On Feb 28, 2018, at 1:42 AM, Torsten Bergmann  wrote:
> >>
> >> ... to all participating authors of the Hermes package:
> >>
> >> PLEASE COMMENT YOUR CLASSES SO WE CAN CLEAN UP AND PREPARE A
> >> POLISHED PHARO 7 RELEASE
> >>
> >> So many uncommented classes in there today...
> >>
> >> We can do better and we should. I dont ask for detailed documentation
> >> but a single comment why the class is there or what it should care
> >> about is often already enough.
> >>
> >> If you have time to write code then you also have the time to write
> >> a simple class comment!
> >>
> >> So please do you homework (which is a general request to authors
> >> of other packages as well)
> >>
> >> Bye
> >> T.
> >>
> >
> >
>
>

[Pharo-dev] [Pharo 7.0-dev] Build #634: 21451-GT-extensions-for-FileLocator

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!

The status of the build #634 was: SUCCESS.

The Pull Request #989 was integrated: "21451-GT-extensions-for-FileLocator"
Pull request url: https://github.com/pharo-project/pharo/pull/989

Issue Url: https://pharo.fogbugz.com/f/cases/21451
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/634/

[Pharo-dev] [Pharo 7.0-dev] Build #633: 17947-TextMorph-uses-the-wrong-menu

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!

The status of the build #633 was: SUCCESS.

The Pull Request #987 was integrated: "17947-TextMorph-uses-the-wrong-menu"
Pull request url: https://github.com/pharo-project/pharo/pull/987

Issue Url: https://pharo.fogbugz.com/f/cases/17947
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/633/

Re: [Pharo-dev] [Request for comment] Hermes package

[Stephane Ducasse]

Hermes is a private binary format that is used to load compiled code
when there is no compiler during the bootstrap.
So basically hermes is loading the compiler to be able to compile
other packages.

Stef

On Wed, Feb 28, 2018 at 4:55 PM, Alexandre Bergel
 wrote:
> Side question: What is Hermes?
>
> Alexandre
>
>> On Feb 28, 2018, at 1:42 AM, Torsten Bergmann  wrote:
>>
>> ... to all participating authors of the Hermes package:
>>
>> PLEASE COMMENT YOUR CLASSES SO WE CAN CLEAN UP AND PREPARE A
>> POLISHED PHARO 7 RELEASE
>>
>> So many uncommented classes in there today...
>>
>> We can do better and we should. I dont ask for detailed documentation
>> but a single comment why the class is there or what it should care
>> about is often already enough.
>>
>> If you have time to write code then you also have the time to write
>> a simple class comment!
>>
>> So please do you homework (which is a general request to authors
>> of other packages as well)
>>
>> Bye
>> T.
>>
>
>

[Pharo-dev] [ANN] New 6.1 backport: 21344 Add Fuel 2.2.0 to pharo 6.1

[Esteban Lorenzano]

https://pharo.fogbugz.com/f/cases/21344/Add-Fuel-2-2-0-to-pharo-6-1

Esteban

ps: (I do not remember the format of this mails ;) )

Re: [Pharo-dev] "External module not found" while loading metacello project

[Esteban Lorenzano]

whet is this “latest vm” ? how do you get it?
which 6 image are you getting?

Esteban


> On 1 Mar 2018, at 10:39, Cyrille Delaunay  wrote:
> 
> Hello,
> 
> I am getting the error "External module not found" while trying to load a 
> metacello project.
> I am running the latest 32 bits pharo 6 image and vm available with zeroconf 
> script.
> The concerned external module seems to be "libgit" (self ffiCall: #(int 
> git_libgit2_init()))
> But the plugin seems to be available within the vm folder:
> 
> 
> 
> The issue can be reproduced with any metacello project.
> For example, from the catalog, you can load the configuration of VoyageMongo.
> Then inspect:
> 
> Metacello new
> configuration: 'VoyageMongo';
> version: #development;
> repository: 'http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo60 
> ';
> load.
> 
> I am able to collect to following information using the System reporter:
> 
> Image
> -
> /Users/cdelaunay/Work/synectique-images/demo/synintegration/61/Java-OnWeb-Demo/Java-OnWeb.image
> Pharo6.0
> Latest update: #60535
> Unnamed
> 
> Virtual Machine
> ---
> /Users/cdelaunay/Work/synectique-images/demo/synintegration/61/Java-OnWeb-Demo/pharo-mac-vm/Pharo.app/Contents/MacOS/Pharo
> CoInterpreter VMMaker.oscog-eem.2254 uuid: 
> 4f2c2cce-f4a2-469a-93f1-97ed941df0ad Jul 20 2017
> StackToRegisterMappingCogit VMMaker.oscog-eem.2252 uuid: 
> 2f3e9b0e-ecd3-4adf-b092-cce2e2587a5c Jul 20 2017
> VM: 201707201942 https://github.com/OpenSmalltalk/opensmalltalk-vm.git 
>  $ Date: Thu Jul 20 
> 12:42:21 2017 -0700 $ Plugins: 201707201942 
> https://github.com/OpenSmalltalk/opensmalltalk-vm.git 
>  $
> 
> Mac OS X built on Jul 20 2017 21:45:23 UTC Compiler: 4.2.1 Compatible Apple 
> LLVM 6.1.0 (clang-602.0.53)
> VMMaker versionString VM: 201707201942 
> https://github.com/OpenSmalltalk/opensmalltalk-vm.git 
>  $ Date: Thu Jul 20 
> 12:42:21 2017 -0700 $ Plugins: 201707201942 
> https://github.com/OpenSmalltalk/opensmalltalk-vm.git 
>  $
> CoInterpreter VMMaker.oscog-eem.2254 uuid: 
> 4f2c2cce-f4a2-469a-93f1-97ed941df0ad Jul 20 2017
> StackToRegisterMappingCogit VMMaker.oscog-eem.2252 uuid: 
> 2f3e9b0e-ecd3-4adf-b092-cce2e2587a5c Jul 20 2017
> 
> Virtual Machine Commandline Options
> ---
> none
> 
> Loaded VM Modules
> -
> AioPlugin VMConstruction-Plugins-AioPlugin-eem.18 (i)
> B2DPlugin VMMaker.oscog-eem.2252 (i)
> BitBltPlugin VMMaker.oscog-eem.2243 (i)
> FT2Plugin Freetype-Plugin-EstebanLorenzano.70 (e)
> FilePlugin VMMaker.oscog-nice.2233 (i)
> FloatArrayPlugin VMMaker.oscog-eem.2254 (i)
> JPEGReadWriter2Plugin VMMaker.oscog-eem.2243 (e)
> LargeIntegers v2.0 VMMaker.oscog-eem.2079 (i)
> LocalePlugin VMMaker.oscog-eem.2064 (e)
> Matrix2x3Plugin VMMaker.oscog-eem.1975 (i)
> MiscPrimitivePlugin VMMaker.oscog-eem.2254 (i)
> SecurityPlugin VMMaker.oscog-eem.2166 (i)
> SocketPlugin VMMaker.oscog-eem.2064 (i)
> SqueakFFIPrims
> SurfacePlugin Jul 20 2017 (e)
> UnixOSProcessPlugin VMConstruction-Plugins-OSProcessPlugin.oscog-dtl.56 (i)
> ZipPlugin VMMaker.oscog-eem.2243 (i)
> 
> VM Built-in Modules
> ---
> ADPCMCodecPlugin VMMaker.oscog-eem.2079 (i)
> AioPlugin VMConstruction-Plugins-AioPlugin-eem.18 (i)
> AsynchFilePlugin VMMaker.oscog-eem.2030 (i)
> B2DPlugin VMMaker.oscog-eem.2252 (i)
> BMPReadWriterPlugin VMMaker.oscog-eem.1975 (i)
> BitBltPlugin VMMaker.oscog-eem.2243 (i)
> DSAPrims CryptographyPlugins-eem.12 (i)
> DropPlugin VMMaker.oscog-eem.1975 (i)
> FFTPlugin VMMaker.oscog-eem.2243 (i)
> FilePlugin VMMaker.oscog-nice.2233 (i)
> FloatArrayPlugin VMMaker.oscog-eem.2254 (i)
> GeniePlugin v2.0 15 June 2017 VMMaker.oscog-eem.2243 (i)
> HostWindowPlugin VMMaker.oscog-eem.2064 (i)
> IA32ABI VMMaker.oscog-eem.2156 (i)
> LargeIntegers v2.0 VMMaker.oscog-eem.2079 (i)
> Matrix2x3Plugin VMMaker.oscog-eem.1975 (i)
> MiscPrimitivePlugin VMMaker.oscog-eem.2254 (i)
> SecurityPlugin VMMaker.oscog-eem.2166 (i)
> SocketPlugin VMMaker.oscog-eem.2064 (i)
> SoundCodecPrims VMMaker.oscog-eem.1975 (i)
> SoundGenerationPlugin VMMaker.oscog-eem.2079 (i)
> SoundPlugin VMMaker.oscog-eem.2218 (i)
> SqueakFFIPrims
> StarSqueakPlugin VMMaker.oscog-eem.2079 (i)
> UnixOSProcessPlugin VMConstruction-Plugins-OSProcessPlugin.oscog-dtl.56 (i)
> VMProfileMacSupportPlugin VMMaker.oscog-eem.2079 (i)
> ZipPlugin VMMaker.oscog-eem.2243 (i)
> 
> Virtual Machine Parameters
> --
> #1417575824   end (v3)/size(Spur) of old-space (0-based, read-only)
> #22457904 end (v3)/size(Spur) of young/new-space (read-only)
> #3422576128   end (v3)/size(Spur) of heap (read-only)
> #4nil nil (was allocationCount (read-only))
> #5nil nil