Pharo-dev
By thread
pharo-dev@lists.pharo.org
By month
Messages by month
- ----- 2026 -----
- July
- June
- May
- April
- March
- February
- January
- ----- 2025 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2024 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2023 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2022 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2021 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2020 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2019 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2018 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2017 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2016 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2015 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2014 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2013 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2012 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2011 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2010 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2009 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2008 -----
- December
- November
- October
- September
- August
- July
- June
- May
November 2015
- 972 messages
Re: [Pharo-dev] Basic versioning of GitHub repositories from within Pharo
by Dimitris Chloupis
hmm i put my user name and password I press enter and gives me a MNU:
receiver of "asZnUrl" is nil
On Mon, Nov 23, 2015 at 6:54 PM Dimitris Chloupis <kilon.alios(a)gmail.com>
wrote:
> Actually its not a bummer at all, Github has an amazing set of features,
> 99% why people use git, including me, is because of Github. Taking also
> into account that no other alternative of Github is as remotely as popular
> and the biggest competitor , gitorious , just died.
>
> Having Github API suppoer inside Pharo is as important if not more
> important than having git support. You can even commit files with the
> Github API, so its far from just a browser, issue and wiki tracker. I will
> definetly take a look at your code and I would like to thank you as a huge
> fan of Github, very much.
>
> On Mon, Nov 23, 2015 at 6:51 PM Skip Lentz <skip.lentz(a)inria.fr> wrote:
>
>>
>> > On Nov 23, 2015, at 5:45 PM, Max Leske <maxleske(a)gmail.com> wrote:
>> >
>> > Sweet! Youâre not using the LibGit bindings for this, are you?
>>
>> No, Iâm not. But it would be interesting to try something similar to this
>> with the LibGit bindings :). I might take a stab at this..
>> Right now itâs tied to the GitHub API which is kind of a bummer, but for
>> prototype purposes itâs alright in my opinion.
>>
>
Nov. 23, 2015
Re: [Pharo-dev] Basic versioning of GitHub repositories from within Pharo
by Skip Lentz
> On Nov 23, 2015, at 5:54 PM, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote:
>
> Actually its not a bummer at all, Github has an amazing set of features, 99% why people use git, including me, is because of Github. Taking also into account that no other alternative of Github is as remotely as popular and the biggest competitor , gitorious , just died.
>
> Having Github API suppoer inside Pharo is as important if not more important than having git support. You can even commit files with the Github API, so its far from just a browser, issue and wiki tracker. I will definetly take a look at your code and I would like to thank you as a huge fan of Github, very much.
Thank you, I knew someone would like it. If you want to take a stab at creating a commit, you should look at the CommitBuilder class and its class comment. You can pass it a directory reference as an argument and it will commit all the files once you send #push to it. (This also works with an in-memory directory using the MemoryStore for the FileSystem, which I think is an interesting use-case).
I will expand it with some more documentation within the coming week. As for the API, there are still some TODOs :).
Nov. 23, 2015
Re: [Pharo-dev] Basic versioning of GitHub repositories from within Pharo
by Dimitris Chloupis
Actually its not a bummer at all, Github has an amazing set of features,
99% why people use git, including me, is because of Github. Taking also
into account that no other alternative of Github is as remotely as popular
and the biggest competitor , gitorious , just died.
Having Github API suppoer inside Pharo is as important if not more
important than having git support. You can even commit files with the
Github API, so its far from just a browser, issue and wiki tracker. I will
definetly take a look at your code and I would like to thank you as a huge
fan of Github, very much.
On Mon, Nov 23, 2015 at 6:51 PM Skip Lentz <skip.lentz(a)inria.fr> wrote:
>
> > On Nov 23, 2015, at 5:45 PM, Max Leske <maxleske(a)gmail.com> wrote:
> >
> > Sweet! Youâre not using the LibGit bindings for this, are you?
>
> No, Iâm not. But it would be interesting to try something similar to this
> with the LibGit bindings :). I might take a stab at this..
> Right now itâs tied to the GitHub API which is kind of a bummer, but for
> prototype purposes itâs alright in my opinion.
>
Nov. 23, 2015
Re: [Pharo-dev] Basic versioning of GitHub repositories from within Pharo
by Skip Lentz
> On Nov 23, 2015, at 5:45 PM, Max Leske <maxleske(a)gmail.com> wrote:
>
> Sweet! Youâre not using the LibGit bindings for this, are you?
No, Iâm not. But it would be interesting to try something similar to this with the LibGit bindings :). I might take a stab at this..
Right now itâs tied to the GitHub API which is kind of a bummer, but for prototype purposes itâs alright in my opinion.
Nov. 23, 2015
Re: [Pharo-dev] Basic versioning of GitHub repositories from within Pharo
by Max Leske
Sweet! Youâre not using the LibGit bindings for this, are you?
Cheers,
Max
> On 23 Nov 2015, at 16:25, Skip Lentz <skip.lentz(a)inria.fr> wrote:
>
> Hi everyone,
>
> As part of my internship I am creating bindings to the GitHub API in Pharo.
> As a prototype and demo, I have created a small tool last week to do some basic versioning, namely checking out a version, committing a version and showing a log of commits along with a branch tree.
>
> Hereâs a screenshot: http://i.imgur.com/iMfWOvp.png <http://i.imgur.com/iMfWOvp.png>
>
> The repository of the bindings and the tool is here: http://smalltalkhub.com/#!/~Balletie/GitHub <http://smalltalkhub.com/#!/~Balletie/GitHub>
> To load the tool into your image, execute:
>
> (ConfigurationOfGitHub project version: #development) load: #tool
>
> Keep in mind that this is tied to GitHub, since internally it uses the API. A nice side effect of this is that everything can be done in-memory. That is, thereâs no local copy on the filesystem. One does not even need git installed.
>
> That being said, feel free to take off with my prototype and make it work with e.g. the LibGit bindings in Pharo.
>
> Known bug:
> - When selecting a different repository from the dropdown while a version is also selected in the log, one gets a DNU. To work around this for the time being, just deselect the version before you switch repositories.
>
> Let me know what you think and feel free to ask some questions.
>
> Skip
Nov. 23, 2015
Re: [Pharo-dev] vm crash in SmalltalkImage>garbageCollect
by Max Leske
Reprocucible as per your steps:
Segmentation fault Mon Nov 23 17:42:47 2015
https://github.com/pharo-project/pharo-vm.git Commit: 28d077d8df494ce050ca42c97c892471e8b8740c Date: 2015-10-16 12:02:43 +0200 By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #15016
C stack backtrace:
0 Pharo 0x0004cacf reportStackState + 159
Smalltalk stack dump:
0xbffbe11c M SmalltalkImage>garbageCollect 0x1fd49e30: a(n) SmalltalkImage
0xbffbe140 I GTExampleOrganizer>reset 0x216acc5c: a(n) GTExampleOrganizer
0x216ad57c is not a context
Most recent primitives
@
@
@
@
@
perform:with:
fractionPart
truncated
@
basicNew
@
@
@
@
@
@
@
@
@
@
@
@
perform:with:
fractionPart
truncated
perform:with:
fractionPart
truncated
@
basicNew
@
@
@
@
@
@
@
@
@
basicNew
basicNew
basicNew
@
@
@
@
@
shallowCopy
new
new:
new:
basicNew
basicNew
new:
basicNew
new:
replaceFrom:to:with:startingAt:
new:
basicNew
new:
replaceFrom:to:with:startingAt:
new:
basicNew
@
new:
at:put:
at:put:
perform:with:
perform:with:
perform:
@
@
basicNew
@
@
@
@
@
@
basicNew
@
new:
at:put:
at:put:
perform:with:
perform:with:
perform:
@
@
basicNew
@
@
@
@
@
@
new
@
@
@
@
@
basicNew
@
@
new:
at:put:
@
@
basicNew
@
@
@
@
new:
at:put:
at:put:
at:put:
at:put:
new:
@
at:put:
@
at:put:
@
at:put:
@
at:put:
@
@
@
@
@
@
basicNew
@
@
basicNew
@
@
basicNew
@
@
@
@
@
shallowCopy
shallowCopy
@
@
new:
at:put:
at:put:
at:put:
at:put:
new:
@
at:put:
@
at:put:
@
at:put:
@
at:put:
@
@
@
@
@
@
basicNew
@
@
basicNew
@
@
basicNew
@
@
@
@
@
basicNew
@
@
@
@
basicNew
@
@
basicNew
@
@
basicNew
@
@
@
@
@
basicNew
@
@
@
@
basicNew
@
@
perform:
basicNew
new:
basicNew
new:
basicNew
new:
shallowCopy
shallowCopy
primUTCMicrosecondsClock
//
basicNew
basicNew
new:
at:put:
at:put:
at:put:
at:put:
value
valueNoContextSwitch
basicNew
new:
basicNew
new:
new:
basicNew
new:
replaceFrom:to:with:startingAt:
primitiveGarbageCollect
**IncrementalGC**
**FullGC**
garbageCollectMost
**IncrementalGC**
basicNew
new:
someInstance
basicNew
new:
someInstance
basicNew
new:
someInstance
new:
basicNew
new:
replaceFrom:to:with:startingAt:
primitiveGarbageCollect
**IncrementalGC**
**FullGC**
(Segmentation fault)
./pharo: line 11: 16509 Abort trap: 6 "$DIR"/"pharo-vm/Pharo.app/Contents/MacOS/Pharo" --headless "$@â
> On 23 Nov 2015, at 17:30, Andrei Chis <chisvasileandrei(a)gmail.com> wrote:
>
> The image is small 25.4 MB.
>
> First I'd like to know if this can be reproduced by others.
>
> On Mon, Nov 23, 2015 at 5:09 PM, Mariano Martinez Peck <marianopeck(a)gmail.com <mailto:marianopeck@gmail.com>> wrote:
> What is the size of the .image when you are about to run GC?
>
> On Mon, Nov 23, 2015 at 12:59 PM, Andrei Chis <chisvasileandrei(a)gmail.com <mailto:chisvasileandrei@gmail.com>> wrote:
> Hi,
>
> With both the latest and stable vm I have an use case in which the vm crashed in SmalltalkImage>>garbageCollect.
>
> To set up an image that exhibits the failure , execute this with the latest pharo version:
>
> /pharo Pharo.image eval --save "{ { 'ConfigurationOfRubric'. 'Pharo'. 'Rubric' }. { 'ConfigurationOfGlamourCore'. 'Moose'. 'Glamour' }. { 'ConfigurationOfGTInspectorCore'. 'Moose'. 'GToolkit' }. { 'ConfigurationOfGTPlaygroundCore'. 'Moose'. 'GToolkit' }. { 'ConfigurationOfGTEventRecorder'. 'Moose'. 'GToolkit' }. { 'ConfigurationOfGTSpotter'. 'Moose'. 'GToolkit' }. } do: [ :spec | Gofer new smalltalkhubUser: spec second project: spec third; package: spec first; load ]."
>
> ./pharo Pharo.image config http://www.smalltalkhub.com/mc/Pharo/Pharo50Inbox/main <http://www.smalltalkhub.com/mc/Pharo/Pharo50Inbox/main> ConfigurationOfGToolkitCore --install=3.2
>
> Then attempting to run the following code triggers the failure:
>
> ./pharo Pharo.image eval --save "TestRunner open model packageSearchUpdate: 'gt-tests-inspector'; classSearchUpdate: 'GTInspectorExamplesTest'; runAll"
>
> Based on the trace below the failure happens when the test GTInspectorExamplesTest calls 'Smalltalk>>garbageCollect' in the setUp method.
>
> That call can be removed, however, in other runs the failure happens in other methods calling Smalltalk>>garbageCollect.
>
> Is it possible that this is a bug with the image (some broken object) or is it a vm bug?
>
> Cheers,
>
> Andrei
>
>
>
>
>
> andrei$ ./pharo Pharo.image eval --save "{ { 'ConfigurationOfRubric'. 'Pharo'. 'Rubric' }. { 'ConfigurationOfGlamourCore'. 'Moose'. 'Glamour' }. { 'ConfigurationOfGTInspectorCore'. 'Moose'. 'GToolkit' }. { 'ConfigurationOfGTPlaygroundCore'. 'Moose'. 'GToolkit' }. { 'ConfigurationOfGTEventRecorder'. 'Moose'. 'GToolkit' }. { 'ConfigurationOfGTSpotter'. 'Moose'. 'GToolkit' }. } do: [ :spec | Gofer new smalltalkhubUser: spec second project: spec third; package: spec first; load ]."
>
> andrei$ ./pharo Pharo.image config http://www.smalltalkhub.com/mc/Pharo/Pharo50Inbox/main <http://www.smalltalkhub.com/mc/Pharo/Pharo50Inbox/main> ConfigurationOfGToolkitCore --install=3.2
>
> andrei$ ./pharo Pharo.image eval --save "TestRunner open model packageSearchUpdate: 'gt-tests-inspector'; classSearchUpdate: 'GTInspectorExamplesTest'; runAll"
>
>
>
> Segmentation fault Mon Nov 23 16:48:36 2015
>
>
>
>
>
> https://github.com/pharo-project/pharo-vm.git <https://github.com/pharo-project/pharo-vm.git> Commit: 28d077d8df494ce050ca42c97c892471e8b8740c Date: 2015-10-16 12:02:43 +0200 By: Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> Jenkins build #15016
>
>
>
> C stack backtrace:
>
> 0 Pharo 0x0004cacf reportStackState + 159
>
>
>
>
>
> Smalltalk stack dump:
>
> 0xbffbf1a0 M SmalltalkImage>garbageCollect 0x1fd49e30: a(n) SmalltalkImage
>
> 0xbffbf1c0 I GTInspectorExamplesTest>setUp 0x2126bc80: a(n) GTInspectorExamplesTest
>
> 0x2126cb90 is not a context
>
>
>
> Most recent primitives
>
> @
>
> basicNew
>
> @
>
> @
>
> @
>
> @
>
> @
>
> @
>
> @
>
> @
>
> @
>
> basicNew
>
> basicNew
>
> basicNew
>
> @
>
> @
>
> @
>
> @
>
> shallowCopy
>
> new
>
> new:
>
> new:
>
> basicNew
>
> basicNew
>
> new:
>
> basicNew
>
> new:
>
> replaceFrom:to:with:startingAt:
>
> new:
>
> basicNew
>
> new:
>
> replaceFrom:to:with:startingAt:
>
> new:
>
> basicNew
>
> @
>
> new:
>
> at:put:
>
> at:put:
>
> perform:with:
>
> perform:with:
>
> perform:
>
> @
>
> @
>
> basicNew
>
> @
>
> @
>
> @
>
> @
>
> @
>
> @
>
> basicNew
>
> @
>
> new:
>
> at:put:
>
> at:put:
>
> perform:with:
>
> perform:with:
>
> perform:
>
> @
>
> @
>
> basicNew
>
> @
>
> @
>
> @
>
> @
>
> @
>
> @
>
> new
>
> @
>
> @
>
> @
>
> @
>
> @
>
> basicNew
>
> @
>
> @
>
> new:
>
> at:put:
>
> @
>
> @
>
> basicNew
>
> @
>
> @
>
> @
>
> @
>
> new:
>
> at:put:
>
> at:put:
>
> at:put:
>
> at:put:
>
> new:
>
> @
>
> at:put:
>
> @
>
> at:put:
>
> @
>
> at:put:
>
> @
>
> at:put:
>
> @
>
> @
>
> @
>
> @
>
> @
>
> @
>
> basicNew
>
> @
>
> @
>
> basicNew
>
> @
>
> @
>
> basicNew
>
> @
>
> @
>
> @
>
> @
>
> @
>
> shallowCopy
>
> shallowCopy
>
> @
>
> @
>
> new:
>
> at:put:
>
> at:put:
>
> at:put:
>
> at:put:
>
> new:
>
> @
>
> at:put:
>
> @
>
> at:put:
>
> @
>
> at:put:
>
> @
>
> at:put:
>
> @
>
> @
>
> @
>
> @
>
> @
>
> @
>
> basicNew
>
> @
>
> @
>
> basicNew
>
> @
>
> @
>
> basicNew
>
> @
>
> @
>
> @
>
> @
>
> @
>
> basicNew
>
> @
>
> @
>
> @
>
> @
>
> basicNew
>
> @
>
> @
>
> basicNew
>
> @
>
> @
>
> basicNew
>
> @
>
> @
>
> @
>
> @
>
> @
>
> basicNew
>
> @
>
> @
>
> @
>
> @
>
> basicNew
>
> @
>
> @
>
> perform:
>
> basicNew
>
> new:
>
> basicNew
>
> new:
>
> basicNew
>
> new:
>
> shallowCopy
>
> shallowCopy
>
> primUTCMicrosecondsClock
>
> //
>
> basicNew
>
> basicNew
>
> new:
>
> at:put:
>
> at:put:
>
> at:put:
>
> at:put:
>
> value
>
> valueNoContextSwitch
>
> basicNew
>
> new:
>
> basicNew
>
> new:
>
> new:
>
> basicNew
>
> new:
>
> replaceFrom:to:with:startingAt:
>
> primitiveGarbageCollect
>
> **IncrementalGC**
>
> **FullGC**
>
> garbageCollectMost
>
> **IncrementalGC**
>
> basicNew
>
> new:
>
> someInstance
>
> basicNew
>
> new:
>
> someInstance
>
> basicNew
>
> new:
>
> someInstance
>
> new:
>
> basicNew
>
> new:
>
> replaceFrom:to:with:startingAt:
>
> primitiveGarbageCollect
>
> **IncrementalGC**
>
> **FullGC**
>
> garbageCollectMost
>
> **IncrementalGC**
>
> wait
>
> shallowCopy
>
> shallowCopy
>
> signal
>
> wait
>
> shallowCopy
>
> shallowCopy
>
> at:put:
>
> at:put:
>
> at:put:
>
> at:put:
>
> at:put:
>
> at:put:
>
> signal
>
> wait
>
> shallowCopy
>
> shallowCopy
>
> at:put:
>
> at:put:
>
> signal
>
> new:
>
> basicNew
>
> new:
>
> replaceFrom:to:with:startingAt:
>
> primitiveGarbageCollect
>
> **IncrementalGC**
>
> **FullGC**
>
>
>
> (Segmentation fault)
>
> ./pharo: line 11: 5224 Abort trap: 6 "$DIR"/"pharo-vm/Pharo.app/Contents/MacOS/Pharo" --headless "$@"
>
>
>
>
> --
> Mariano
> http://marianopeck.wordpress.com <http://marianopeck.wordpress.com/>
>
Nov. 23, 2015
Re: [Pharo-dev] vm crash in SmalltalkImage>garbageCollect
by Andrei Chis
The image is small 25.4 MB.
First I'd like to know if this can be reproduced by others.
On Mon, Nov 23, 2015 at 5:09 PM, Mariano Martinez Peck <
marianopeck(a)gmail.com> wrote:
> What is the size of the .image when you are about to run GC?
>
> On Mon, Nov 23, 2015 at 12:59 PM, Andrei Chis <chisvasileandrei(a)gmail.com>
> wrote:
>
>> Hi,
>>
>> With both the latest and stable vm I have an use case in which the vm
>> crashed in SmalltalkImage>>garbageCollect.
>>
>> To set up an image that exhibits the failure , execute this with the
>> latest pharo version:
>>
>> /pharo Pharo.image eval --save "{ { 'ConfigurationOfRubric'. 'Pharo'.
>> 'Rubric' }. { 'ConfigurationOfGlamourCore'. 'Moose'. 'Glamour' }. {
>> 'ConfigurationOfGTInspectorCore'. 'Moose'. 'GToolkit' }. {
>> 'ConfigurationOfGTPlaygroundCore'. 'Moose'. 'GToolkit' }. {
>> 'ConfigurationOfGTEventRecorder'. 'Moose'. 'GToolkit' }. {
>> 'ConfigurationOfGTSpotter'. 'Moose'. 'GToolkit' }. } do: [ :spec | Gofer
>> new smalltalkhubUser: spec second project: spec third; package: spec first;
>> load ]."
>>
>> ./pharo Pharo.image config
>> http://www.smalltalkhub.com/mc/Pharo/Pharo50Inbox/main
>> ConfigurationOfGToolkitCore --install=3.2
>>
>> Then attempting to run the following code triggers the failure:
>>
>> ./pharo Pharo.image eval --save "TestRunner open model
>> packageSearchUpdate: 'gt-tests-inspector'; classSearchUpdate:
>> 'GTInspectorExamplesTest'; runAll"
>>
>> Based on the trace below the failure happens when the
>> test GTInspectorExamplesTest calls 'Smalltalk>>garbageCollect' in the setUp
>> method.
>>
>> That call can be removed, however, in other runs the failure happens in
>> other methods calling Smalltalk>>garbageCollect.
>>
>> Is it possible that this is a bug with the image (some broken object) or
>> is it a vm bug?
>>
>> Cheers,
>>
>> Andrei
>>
>>
>>
>> andrei$ ./pharo Pharo.image eval --save "{ { 'ConfigurationOfRubric'.
>> 'Pharo'. 'Rubric' }. { 'ConfigurationOfGlamourCore'. 'Moose'. 'Glamour' }.
>> { 'ConfigurationOfGTInspectorCore'. 'Moose'. 'GToolkit' }. {
>> 'ConfigurationOfGTPlaygroundCore'. 'Moose'. 'GToolkit' }. {
>> 'ConfigurationOfGTEventRecorder'. 'Moose'. 'GToolkit' }. {
>> 'ConfigurationOfGTSpotter'. 'Moose'. 'GToolkit' }. } do: [ :spec | Gofer
>> new smalltalkhubUser: spec second project: spec third; package: spec first;
>> load ]."
>>
>> andrei$ ./pharo Pharo.image config
>> http://www.smalltalkhub.com/mc/Pharo/Pharo50Inbox/main
>> ConfigurationOfGToolkitCore --install=3.2
>>
>> andrei$ ./pharo Pharo.image eval --save "TestRunner open model
>> packageSearchUpdate: 'gt-tests-inspector'; classSearchUpdate:
>> 'GTInspectorExamplesTest'; runAll"
>>
>>
>> Segmentation fault Mon Nov 23 16:48:36 2015
>>
>>
>>
>> https://github.com/pharo-project/pharo-vm.git Commit:
>> 28d077d8df494ce050ca42c97c892471e8b8740c Date: 2015-10-16 12:02:43 +0200
>> By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #15016
>>
>>
>> C stack backtrace:
>>
>> 0 Pharo 0x0004cacf reportStackState + 159
>>
>>
>>
>> Smalltalk stack dump:
>>
>> 0xbffbf1a0 M SmalltalkImage>garbageCollect 0x1fd49e30: a(n) SmalltalkImage
>>
>> 0xbffbf1c0 I GTInspectorExamplesTest>setUp 0x2126bc80: a(n)
>> GTInspectorExamplesTest
>>
>> 0x2126cb90 is not a context
>>
>>
>> Most recent primitives
>>
>> @
>>
>> basicNew
>>
>> @
>>
>> @
>>
>> @
>>
>> @
>>
>> @
>>
>> @
>>
>> @
>>
>> @
>>
>> @
>>
>> basicNew
>>
>> basicNew
>>
>> basicNew
>>
>> @
>>
>> @
>>
>> @
>>
>> @
>>
>> shallowCopy
>>
>> new
>>
>> new:
>>
>> new:
>>
>> basicNew
>>
>> basicNew
>>
>> new:
>>
>> basicNew
>>
>> new:
>>
>> replaceFrom:to:with:startingAt:
>>
>> new:
>>
>> basicNew
>>
>> new:
>>
>> replaceFrom:to:with:startingAt:
>>
>> new:
>>
>> basicNew
>>
>> @
>>
>> new:
>>
>> at:put:
>>
>> at:put:
>>
>> perform:with:
>>
>> perform:with:
>>
>> perform:
>>
>> @
>>
>> @
>>
>> basicNew
>>
>> @
>>
>> @
>>
>> @
>>
>> @
>>
>> @
>>
>> @
>>
>> basicNew
>>
>> @
>>
>> new:
>>
>> at:put:
>>
>> at:put:
>>
>> perform:with:
>>
>> perform:with:
>>
>> perform:
>>
>> @
>>
>> @
>>
>> basicNew
>>
>> @
>>
>> @
>>
>> @
>>
>> @
>>
>> @
>>
>> @
>>
>> new
>>
>> @
>>
>> @
>>
>> @
>>
>> @
>>
>> @
>>
>> basicNew
>>
>> @
>>
>> @
>>
>> new:
>>
>> at:put:
>>
>> @
>>
>> @
>>
>> basicNew
>>
>> @
>>
>> @
>>
>> @
>>
>> @
>>
>> new:
>>
>> at:put:
>>
>> at:put:
>>
>> at:put:
>>
>> at:put:
>>
>> new:
>>
>> @
>>
>> at:put:
>>
>> @
>>
>> at:put:
>>
>> @
>>
>> at:put:
>>
>> @
>>
>> at:put:
>>
>> @
>>
>> @
>>
>> @
>>
>> @
>>
>> @
>>
>> @
>>
>> basicNew
>>
>> @
>>
>> @
>>
>> basicNew
>>
>> @
>>
>> @
>>
>> basicNew
>>
>> @
>>
>> @
>>
>> @
>>
>> @
>>
>> @
>>
>> shallowCopy
>>
>> shallowCopy
>>
>> @
>>
>> @
>>
>> new:
>>
>> at:put:
>>
>> at:put:
>>
>> at:put:
>>
>> at:put:
>>
>> new:
>>
>> @
>>
>> at:put:
>>
>> @
>>
>> at:put:
>>
>> @
>>
>> at:put:
>>
>> @
>>
>> at:put:
>>
>> @
>>
>> @
>>
>> @
>>
>> @
>>
>> @
>>
>> @
>>
>> basicNew
>>
>> @
>>
>> @
>>
>> basicNew
>>
>> @
>>
>> @
>>
>> basicNew
>>
>> @
>>
>> @
>>
>> @
>>
>> @
>>
>> @
>>
>> basicNew
>>
>> @
>>
>> @
>>
>> @
>>
>> @
>>
>> basicNew
>>
>> @
>>
>> @
>>
>> basicNew
>>
>> @
>>
>> @
>>
>> basicNew
>>
>> @
>>
>> @
>>
>> @
>>
>> @
>>
>> @
>>
>> basicNew
>>
>> @
>>
>> @
>>
>> @
>>
>> @
>>
>> basicNew
>>
>> @
>>
>> @
>>
>> perform:
>>
>> basicNew
>>
>> new:
>>
>> basicNew
>>
>> new:
>>
>> basicNew
>>
>> new:
>>
>> shallowCopy
>>
>> shallowCopy
>>
>> primUTCMicrosecondsClock
>>
>> //
>>
>> basicNew
>>
>> basicNew
>>
>> new:
>>
>> at:put:
>>
>> at:put:
>>
>> at:put:
>>
>> at:put:
>>
>> value
>>
>> valueNoContextSwitch
>>
>> basicNew
>>
>> new:
>>
>> basicNew
>>
>> new:
>>
>> new:
>>
>> basicNew
>>
>> new:
>>
>> replaceFrom:to:with:startingAt:
>>
>> primitiveGarbageCollect
>>
>> **IncrementalGC**
>>
>> **FullGC**
>>
>> garbageCollectMost
>>
>> **IncrementalGC**
>>
>> basicNew
>>
>> new:
>>
>> someInstance
>>
>> basicNew
>>
>> new:
>>
>> someInstance
>>
>> basicNew
>>
>> new:
>>
>> someInstance
>>
>> new:
>>
>> basicNew
>>
>> new:
>>
>> replaceFrom:to:with:startingAt:
>>
>> primitiveGarbageCollect
>>
>> **IncrementalGC**
>>
>> **FullGC**
>>
>> garbageCollectMost
>>
>> **IncrementalGC**
>>
>> wait
>>
>> shallowCopy
>>
>> shallowCopy
>>
>> signal
>>
>> wait
>>
>> shallowCopy
>>
>> shallowCopy
>>
>> at:put:
>>
>> at:put:
>>
>> at:put:
>>
>> at:put:
>>
>> at:put:
>>
>> at:put:
>>
>> signal
>>
>> wait
>>
>> shallowCopy
>>
>> shallowCopy
>>
>> at:put:
>>
>> at:put:
>>
>> signal
>>
>> new:
>>
>> basicNew
>>
>> new:
>>
>> replaceFrom:to:with:startingAt:
>>
>> primitiveGarbageCollect
>>
>> **IncrementalGC**
>>
>> **FullGC**
>>
>>
>> (Segmentation fault)
>>
>> ./pharo: line 11: 5224 Abort trap: 6
>> "$DIR"/"pharo-vm/Pharo.app/Contents/MacOS/Pharo" --headless "$@"
>>
>
>
>
> --
> Mariano
> http://marianopeck.wordpress.com
>
Nov. 23, 2015
Re: [Pharo-dev] vm crash in SmalltalkImage>garbageCollect
by Max Leske
This sounds suspiciously like the same thing we had with Fuel 2 or 3 years back. Search for "Frequent SegFaults in PharoVM with Pharo 3.0â. The problem there was with Opal though and the #timesRepeat: message IIRC.
Max
> On 23 Nov 2015, at 16:59, Andrei Chis <chisvasileandrei(a)gmail.com> wrote:
>
> Hi,
>
> With both the latest and stable vm I have an use case in which the vm crashed in SmalltalkImage>>garbageCollect.
>
> To set up an image that exhibits the failure , execute this with the latest pharo version:
>
> /pharo Pharo.image eval --save "{ { 'ConfigurationOfRubric'. 'Pharo'. 'Rubric' }. { 'ConfigurationOfGlamourCore'. 'Moose'. 'Glamour' }. { 'ConfigurationOfGTInspectorCore'. 'Moose'. 'GToolkit' }. { 'ConfigurationOfGTPlaygroundCore'. 'Moose'. 'GToolkit' }. { 'ConfigurationOfGTEventRecorder'. 'Moose'. 'GToolkit' }. { 'ConfigurationOfGTSpotter'. 'Moose'. 'GToolkit' }. } do: [ :spec | Gofer new smalltalkhubUser: spec second project: spec third; package: spec first; load ]."
>
> ./pharo Pharo.image config http://www.smalltalkhub.com/mc/Pharo/Pharo50Inbox/main <http://www.smalltalkhub.com/mc/Pharo/Pharo50Inbox/main> ConfigurationOfGToolkitCore --install=3.2
>
> Then attempting to run the following code triggers the failure:
>
> ./pharo Pharo.image eval --save "TestRunner open model packageSearchUpdate: 'gt-tests-inspector'; classSearchUpdate: 'GTInspectorExamplesTest'; runAll"
>
> Based on the trace below the failure happens when the test GTInspectorExamplesTest calls 'Smalltalk>>garbageCollect' in the setUp method.
>
> That call can be removed, however, in other runs the failure happens in other methods calling Smalltalk>>garbageCollect.
>
> Is it possible that this is a bug with the image (some broken object) or is it a vm bug?
>
> Cheers,
>
> Andrei
>
>
>
>
>
> andrei$ ./pharo Pharo.image eval --save "{ { 'ConfigurationOfRubric'. 'Pharo'. 'Rubric' }. { 'ConfigurationOfGlamourCore'. 'Moose'. 'Glamour' }. { 'ConfigurationOfGTInspectorCore'. 'Moose'. 'GToolkit' }. { 'ConfigurationOfGTPlaygroundCore'. 'Moose'. 'GToolkit' }. { 'ConfigurationOfGTEventRecorder'. 'Moose'. 'GToolkit' }. { 'ConfigurationOfGTSpotter'. 'Moose'. 'GToolkit' }. } do: [ :spec | Gofer new smalltalkhubUser: spec second project: spec third; package: spec first; load ]."
>
> andrei$ ./pharo Pharo.image config http://www.smalltalkhub.com/mc/Pharo/Pharo50Inbox/main <http://www.smalltalkhub.com/mc/Pharo/Pharo50Inbox/main> ConfigurationOfGToolkitCore --install=3.2
>
> andrei$ ./pharo Pharo.image eval --save "TestRunner open model packageSearchUpdate: 'gt-tests-inspector'; classSearchUpdate: 'GTInspectorExamplesTest'; runAll"
>
>
>
> Segmentation fault Mon Nov 23 16:48:36 2015
>
>
>
>
>
> https://github.com/pharo-project/pharo-vm.git <https://github.com/pharo-project/pharo-vm.git> Commit: 28d077d8df494ce050ca42c97c892471e8b8740c Date: 2015-10-16 12:02:43 +0200 By: Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> Jenkins build #15016
>
>
>
> C stack backtrace:
>
> 0 Pharo 0x0004cacf reportStackState + 159
>
>
>
>
>
> Smalltalk stack dump:
>
> 0xbffbf1a0 M SmalltalkImage>garbageCollect 0x1fd49e30: a(n) SmalltalkImage
>
> 0xbffbf1c0 I GTInspectorExamplesTest>setUp 0x2126bc80: a(n) GTInspectorExamplesTest
>
> 0x2126cb90 is not a context
>
>
>
> Most recent primitives
>
> @
>
> basicNew
>
> @
>
> @
>
> @
>
> @
>
> @
>
> @
>
> @
>
> @
>
> @
>
> basicNew
>
> basicNew
>
> basicNew
>
> @
>
> @
>
> @
>
> @
>
> shallowCopy
>
> new
>
> new:
>
> new:
>
> basicNew
>
> basicNew
>
> new:
>
> basicNew
>
> new:
>
> replaceFrom:to:with:startingAt:
>
> new:
>
> basicNew
>
> new:
>
> replaceFrom:to:with:startingAt:
>
> new:
>
> basicNew
>
> @
>
> new:
>
> at:put:
>
> at:put:
>
> perform:with:
>
> perform:with:
>
> perform:
>
> @
>
> @
>
> basicNew
>
> @
>
> @
>
> @
>
> @
>
> @
>
> @
>
> basicNew
>
> @
>
> new:
>
> at:put:
>
> at:put:
>
> perform:with:
>
> perform:with:
>
> perform:
>
> @
>
> @
>
> basicNew
>
> @
>
> @
>
> @
>
> @
>
> @
>
> @
>
> new
>
> @
>
> @
>
> @
>
> @
>
> @
>
> basicNew
>
> @
>
> @
>
> new:
>
> at:put:
>
> @
>
> @
>
> basicNew
>
> @
>
> @
>
> @
>
> @
>
> new:
>
> at:put:
>
> at:put:
>
> at:put:
>
> at:put:
>
> new:
>
> @
>
> at:put:
>
> @
>
> at:put:
>
> @
>
> at:put:
>
> @
>
> at:put:
>
> @
>
> @
>
> @
>
> @
>
> @
>
> @
>
> basicNew
>
> @
>
> @
>
> basicNew
>
> @
>
> @
>
> basicNew
>
> @
>
> @
>
> @
>
> @
>
> @
>
> shallowCopy
>
> shallowCopy
>
> @
>
> @
>
> new:
>
> at:put:
>
> at:put:
>
> at:put:
>
> at:put:
>
> new:
>
> @
>
> at:put:
>
> @
>
> at:put:
>
> @
>
> at:put:
>
> @
>
> at:put:
>
> @
>
> @
>
> @
>
> @
>
> @
>
> @
>
> basicNew
>
> @
>
> @
>
> basicNew
>
> @
>
> @
>
> basicNew
>
> @
>
> @
>
> @
>
> @
>
> @
>
> basicNew
>
> @
>
> @
>
> @
>
> @
>
> basicNew
>
> @
>
> @
>
> basicNew
>
> @
>
> @
>
> basicNew
>
> @
>
> @
>
> @
>
> @
>
> @
>
> basicNew
>
> @
>
> @
>
> @
>
> @
>
> basicNew
>
> @
>
> @
>
> perform:
>
> basicNew
>
> new:
>
> basicNew
>
> new:
>
> basicNew
>
> new:
>
> shallowCopy
>
> shallowCopy
>
> primUTCMicrosecondsClock
>
> //
>
> basicNew
>
> basicNew
>
> new:
>
> at:put:
>
> at:put:
>
> at:put:
>
> at:put:
>
> value
>
> valueNoContextSwitch
>
> basicNew
>
> new:
>
> basicNew
>
> new:
>
> new:
>
> basicNew
>
> new:
>
> replaceFrom:to:with:startingAt:
>
> primitiveGarbageCollect
>
> **IncrementalGC**
>
> **FullGC**
>
> garbageCollectMost
>
> **IncrementalGC**
>
> basicNew
>
> new:
>
> someInstance
>
> basicNew
>
> new:
>
> someInstance
>
> basicNew
>
> new:
>
> someInstance
>
> new:
>
> basicNew
>
> new:
>
> replaceFrom:to:with:startingAt:
>
> primitiveGarbageCollect
>
> **IncrementalGC**
>
> **FullGC**
>
> garbageCollectMost
>
> **IncrementalGC**
>
> wait
>
> shallowCopy
>
> shallowCopy
>
> signal
>
> wait
>
> shallowCopy
>
> shallowCopy
>
> at:put:
>
> at:put:
>
> at:put:
>
> at:put:
>
> at:put:
>
> at:put:
>
> signal
>
> wait
>
> shallowCopy
>
> shallowCopy
>
> at:put:
>
> at:put:
>
> signal
>
> new:
>
> basicNew
>
> new:
>
> replaceFrom:to:with:startingAt:
>
> primitiveGarbageCollect
>
> **IncrementalGC**
>
> **FullGC**
>
>
>
> (Segmentation fault)
>
> ./pharo: line 11: 5224 Abort trap: 6 "$DIR"/"pharo-vm/Pharo.app/Contents/MacOS/Pharo" --headless "$@"
>
Nov. 23, 2015
Re: [Pharo-dev] vm crash in SmalltalkImage>garbageCollect
by Mariano Martinez Peck
What is the size of the .image when you are about to run GC?
On Mon, Nov 23, 2015 at 12:59 PM, Andrei Chis <chisvasileandrei(a)gmail.com>
wrote:
> Hi,
>
> With both the latest and stable vm I have an use case in which the vm
> crashed in SmalltalkImage>>garbageCollect.
>
> To set up an image that exhibits the failure , execute this with the
> latest pharo version:
>
> /pharo Pharo.image eval --save "{ { 'ConfigurationOfRubric'. 'Pharo'.
> 'Rubric' }. { 'ConfigurationOfGlamourCore'. 'Moose'. 'Glamour' }. {
> 'ConfigurationOfGTInspectorCore'. 'Moose'. 'GToolkit' }. {
> 'ConfigurationOfGTPlaygroundCore'. 'Moose'. 'GToolkit' }. {
> 'ConfigurationOfGTEventRecorder'. 'Moose'. 'GToolkit' }. {
> 'ConfigurationOfGTSpotter'. 'Moose'. 'GToolkit' }. } do: [ :spec | Gofer
> new smalltalkhubUser: spec second project: spec third; package: spec first;
> load ]."
>
> ./pharo Pharo.image config
> http://www.smalltalkhub.com/mc/Pharo/Pharo50Inbox/main
> ConfigurationOfGToolkitCore --install=3.2
>
> Then attempting to run the following code triggers the failure:
>
> ./pharo Pharo.image eval --save "TestRunner open model
> packageSearchUpdate: 'gt-tests-inspector'; classSearchUpdate:
> 'GTInspectorExamplesTest'; runAll"
>
> Based on the trace below the failure happens when the
> test GTInspectorExamplesTest calls 'Smalltalk>>garbageCollect' in the setUp
> method.
>
> That call can be removed, however, in other runs the failure happens in
> other methods calling Smalltalk>>garbageCollect.
>
> Is it possible that this is a bug with the image (some broken object) or
> is it a vm bug?
>
> Cheers,
>
> Andrei
>
>
>
> andrei$ ./pharo Pharo.image eval --save "{ { 'ConfigurationOfRubric'.
> 'Pharo'. 'Rubric' }. { 'ConfigurationOfGlamourCore'. 'Moose'. 'Glamour' }.
> { 'ConfigurationOfGTInspectorCore'. 'Moose'. 'GToolkit' }. {
> 'ConfigurationOfGTPlaygroundCore'. 'Moose'. 'GToolkit' }. {
> 'ConfigurationOfGTEventRecorder'. 'Moose'. 'GToolkit' }. {
> 'ConfigurationOfGTSpotter'. 'Moose'. 'GToolkit' }. } do: [ :spec | Gofer
> new smalltalkhubUser: spec second project: spec third; package: spec first;
> load ]."
>
> andrei$ ./pharo Pharo.image config
> http://www.smalltalkhub.com/mc/Pharo/Pharo50Inbox/main
> ConfigurationOfGToolkitCore --install=3.2
>
> andrei$ ./pharo Pharo.image eval --save "TestRunner open model
> packageSearchUpdate: 'gt-tests-inspector'; classSearchUpdate:
> 'GTInspectorExamplesTest'; runAll"
>
>
> Segmentation fault Mon Nov 23 16:48:36 2015
>
>
>
> https://github.com/pharo-project/pharo-vm.git Commit:
> 28d077d8df494ce050ca42c97c892471e8b8740c Date: 2015-10-16 12:02:43 +0200
> By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #15016
>
>
> C stack backtrace:
>
> 0 Pharo 0x0004cacf reportStackState + 159
>
>
>
> Smalltalk stack dump:
>
> 0xbffbf1a0 M SmalltalkImage>garbageCollect 0x1fd49e30: a(n) SmalltalkImage
>
> 0xbffbf1c0 I GTInspectorExamplesTest>setUp 0x2126bc80: a(n)
> GTInspectorExamplesTest
>
> 0x2126cb90 is not a context
>
>
> Most recent primitives
>
> @
>
> basicNew
>
> @
>
> @
>
> @
>
> @
>
> @
>
> @
>
> @
>
> @
>
> @
>
> basicNew
>
> basicNew
>
> basicNew
>
> @
>
> @
>
> @
>
> @
>
> shallowCopy
>
> new
>
> new:
>
> new:
>
> basicNew
>
> basicNew
>
> new:
>
> basicNew
>
> new:
>
> replaceFrom:to:with:startingAt:
>
> new:
>
> basicNew
>
> new:
>
> replaceFrom:to:with:startingAt:
>
> new:
>
> basicNew
>
> @
>
> new:
>
> at:put:
>
> at:put:
>
> perform:with:
>
> perform:with:
>
> perform:
>
> @
>
> @
>
> basicNew
>
> @
>
> @
>
> @
>
> @
>
> @
>
> @
>
> basicNew
>
> @
>
> new:
>
> at:put:
>
> at:put:
>
> perform:with:
>
> perform:with:
>
> perform:
>
> @
>
> @
>
> basicNew
>
> @
>
> @
>
> @
>
> @
>
> @
>
> @
>
> new
>
> @
>
> @
>
> @
>
> @
>
> @
>
> basicNew
>
> @
>
> @
>
> new:
>
> at:put:
>
> @
>
> @
>
> basicNew
>
> @
>
> @
>
> @
>
> @
>
> new:
>
> at:put:
>
> at:put:
>
> at:put:
>
> at:put:
>
> new:
>
> @
>
> at:put:
>
> @
>
> at:put:
>
> @
>
> at:put:
>
> @
>
> at:put:
>
> @
>
> @
>
> @
>
> @
>
> @
>
> @
>
> basicNew
>
> @
>
> @
>
> basicNew
>
> @
>
> @
>
> basicNew
>
> @
>
> @
>
> @
>
> @
>
> @
>
> shallowCopy
>
> shallowCopy
>
> @
>
> @
>
> new:
>
> at:put:
>
> at:put:
>
> at:put:
>
> at:put:
>
> new:
>
> @
>
> at:put:
>
> @
>
> at:put:
>
> @
>
> at:put:
>
> @
>
> at:put:
>
> @
>
> @
>
> @
>
> @
>
> @
>
> @
>
> basicNew
>
> @
>
> @
>
> basicNew
>
> @
>
> @
>
> basicNew
>
> @
>
> @
>
> @
>
> @
>
> @
>
> basicNew
>
> @
>
> @
>
> @
>
> @
>
> basicNew
>
> @
>
> @
>
> basicNew
>
> @
>
> @
>
> basicNew
>
> @
>
> @
>
> @
>
> @
>
> @
>
> basicNew
>
> @
>
> @
>
> @
>
> @
>
> basicNew
>
> @
>
> @
>
> perform:
>
> basicNew
>
> new:
>
> basicNew
>
> new:
>
> basicNew
>
> new:
>
> shallowCopy
>
> shallowCopy
>
> primUTCMicrosecondsClock
>
> //
>
> basicNew
>
> basicNew
>
> new:
>
> at:put:
>
> at:put:
>
> at:put:
>
> at:put:
>
> value
>
> valueNoContextSwitch
>
> basicNew
>
> new:
>
> basicNew
>
> new:
>
> new:
>
> basicNew
>
> new:
>
> replaceFrom:to:with:startingAt:
>
> primitiveGarbageCollect
>
> **IncrementalGC**
>
> **FullGC**
>
> garbageCollectMost
>
> **IncrementalGC**
>
> basicNew
>
> new:
>
> someInstance
>
> basicNew
>
> new:
>
> someInstance
>
> basicNew
>
> new:
>
> someInstance
>
> new:
>
> basicNew
>
> new:
>
> replaceFrom:to:with:startingAt:
>
> primitiveGarbageCollect
>
> **IncrementalGC**
>
> **FullGC**
>
> garbageCollectMost
>
> **IncrementalGC**
>
> wait
>
> shallowCopy
>
> shallowCopy
>
> signal
>
> wait
>
> shallowCopy
>
> shallowCopy
>
> at:put:
>
> at:put:
>
> at:put:
>
> at:put:
>
> at:put:
>
> at:put:
>
> signal
>
> wait
>
> shallowCopy
>
> shallowCopy
>
> at:put:
>
> at:put:
>
> signal
>
> new:
>
> basicNew
>
> new:
>
> replaceFrom:to:with:startingAt:
>
> primitiveGarbageCollect
>
> **IncrementalGC**
>
> **FullGC**
>
>
> (Segmentation fault)
>
> ./pharo: line 11: 5224 Abort trap: 6
> "$DIR"/"pharo-vm/Pharo.app/Contents/MacOS/Pharo" --headless "$@"
>
--
Mariano
http://marianopeck.wordpress.com
Nov. 23, 2015
Re: [Pharo-dev] Does Pharo stores original author of methods?
by Nicolas Cellier
It's not Monticello per se. It's the backend (the server) which is too
naive.
The .mcz must be considered as a unit of exchange between the server (the
repository) and the client (the working copy). And please note that in
Monticello, it's not the only way to exchange data, it can also be a .mcd
(a diff).
Nothing forces the server to store the .mcz as is. That's just a naive
implementation. Chris Muller demonstrated how to use a database (magma) as
backend...
2015-11-23 12:12 GMT+01:00 Marcus Denker <marcus.denker(a)inria.fr>:
>
> > On 22 Nov 2015, at 20:12, EuanM <euanmee(a)gmail.com> wrote:
> >
> > Is there any reason against amending Monticello to store and save all
> > author's names?
>
> It does. *If* you have all the versions⦠but doing anything with âall the
> versionsâ
> is so slow (you need to download them, unpack themâ¦) that we do not even
> have
> a tool to show the history of a method.
> (getting the oldest should be simpler, if you have complete history+this
> .mcz is
> there).
>
> Monticello is meant to be a system to save the complete history of a
> project
> (if you keep all the MCZ available), but the idea to save every tiny
> revision as
> a complete snapshot, zip compresses, makes it near impossible to do
> anything
> with the history in practice.
>
> With today disks, a practical SCM would allow anyone to have the *complete*
> history on the local disk. Monticello does now allow that in any practical
> way.
>
> >
> > Presumably, we'd also want a tool that could extract amnders' names
> > all the way back to the first commit of a package?
> >
> > How many on-line Monticello repositories are in common use?
> >
> > (I know of SqueakSource.com, Smalltalkhub.com and SqueakSource3)
> >
> > Are there active administrators for each of those repositories that
> > would allow us to update the repositories to use the updated
> > Monticello?
> >
> > On 22 November 2015 at 15:42, Marcus Denker <marcus.denker(a)inria.fr>
> wrote:
> >>
> >> On 20 Nov 2015, at 14:35, Denis Kudriashov <dionisiydk(a)gmail.com>
> wrote:
> >>
> >>
> >> 2015-11-20 14:21 GMT+01:00 Marcus Denker <marcus.denker(a)inria.fr>:
> >>>
> >>> epicea data is not stored forever. It is seasion based and the shipped
> >>> image is
> >>> clean.
> >>
> >>
> >> But current source of this info is changes file (maybe sources). And I
> >> remember you planned to store current sources in image. And such
> information
> >> can be there too.
> >> Maybe I miss something?
> >>
> >>
> >> The original author is not really that much of information. And storing
> it
> >> for every method in the image would take space.
> >>
> >> As I said: the whole idea of using a source revision control system is
> that
> >> you have the *complete* history available, but
> >> not wasting RAM.
> >>
> >> Marcus
> >
>
>
>
Nov. 23, 2015