Holger
with guille, damien and two students we are looking at how to improve the
deployment of pharo and you scenario is
really interesting.
Stef
On Sat, Apr 15, 2017 at 7:59 AM, Holger Freyther wrote:
>
> > On 15. Apr 2017, at 00:23, Juraj Kubelka
> wrote:
> >
> > Hi,
>
> Hey!
>
> >> As this
2017-04-14 17:13 GMT+02:00 Hilaire :
> I tried but I can't reproduce the case with dummy code.
> I can share privately an image though.
>
> Hilaire
>
> Le 14/04/2017 à 15:24, Denis Kudriashov a écrit :
> >
> > Could you create example set of packages to reproduce problem? (to be
> > not dependant
> On 15. Apr 2017, at 00:23, Juraj Kubelka wrote:
>
> Hi,
Hey!
>> As this is a server application and I run multiple VMs with the same image
>> and there is no home directory I would prefer that no information is
>> persisted at all. Can this be done? Have there been any changes in Pharo6 in
On 14 April 2017 at 22:20, Stephane Ducasse wrote:
> This is what we always have when we release and we freeze it.
> The vm 60 will be compatible with latest pharo 60 image.
>
It is possible that I have misunderstood the whole situation and there is
no problem at all. That would be awesome. Let'
Hi,
> El 14-04-2017, a las 16:17, Holger Freyther escribió:
>
> Hi,
>
> as Pharo6 is around the corner I have moved my CI build from tracking Pharo5
> to Pharo6 but I run into a problem. Either if $HOME is not set at all or
> $HOME points to a wrong directory I run into the error below.
>
>
Not exactly sure how to do to it because I never used it.
>From what I see in SmaCCParserDebugger>>handlesContext: if you have in the
stack a context created by SmaCCParser>>parse you should have a
'SmaCCParser' button at the top right of the window. But maybe John can
provide you with more detail
This is what we always have when we release and we freeze it.
The vm 60 will be compatible with latest pharo 60 image.
On Fri, Apr 14, 2017 at 12:09 PM, Luke Gorrie wrote:
> On 14 April 2017 at 08:53, Stephane Ducasse
> wrote:
>
>> We always try to have a major release around mid/end of april
Hi,
as Pharo6 is around the corner I have moved my CI build from tracking Pharo5 to
Pharo6 but I run into a problem. Either if $HOME is not set at all or $HOME
points to a wrong directory I run into the error below.
As this is a server application and I run multiple VMs with the same image and
I tried but I can't reproduce the case with dummy code.
I can share privately an image though.
Hilaire
Le 14/04/2017 à 15:24, Denis Kudriashov a écrit :
>
> Could you create example set of packages to reproduce problem? (to be
> not dependant on your private code)
>
--
Dr. Geo
http://drgeo.eu
On Fri, Apr 14, 2017 at 5:13 PM, Igor Stasenko wrote:
>
>
> On 13 April 2017 at 22:23, Esteban Lorenzano wrote:
>
>>
>> On 13 Apr 2017, at 19:26, Asbath Sama biyalou via Pharo-users <
>> pharo-users@lists.pharo.org> wrote:
>>
>>
>> *From: *Asbath Sama biyalou
>> *Subject: **Export MongoDB to sq
Hi.
Could you create example set of packages to reproduce problem? (to be not
dependant on your private code)
2017-04-14 14:41 GMT+02:00 Hilaire :
> Tested on Pharo6, result is the same :(
> Traits logic is lost when saving the package.
>
> Squeak: 1 - Pharo6: 0
>
>
> Le 14/04/2017 à 14:33, Hila
Tested on Pharo6, result is the same :(
Traits logic is lost when saving the package.
Squeak: 1 - Pharo6: 0
Le 14/04/2017 à 14:33, Hilaire a écrit :
> So it looks like Squeak[1] is capable to produce a correct .mcz file,
> out of a package coming with Traits and class.
> By correct, read the Tr
So it looks like Squeak[1] is capable to produce a correct .mcz file,
out of a package coming with Traits and class.
By correct, read the Traits logic is not lost.
Hilaire
[1] I tested with a Squeak6 alpha waiting somewhere on my disk
--
Dr. Geo
http://drgeo.eu
Some traditional ovens cook some foods better
the answer is always
"because its a complex world and any effort to simplify it is doomed to
fail"
On Fri, Apr 14, 2017 at 12:14 PM Igor Stasenko wrote:
> On 13 April 2017 at 22:23, Esteban Lorenzano wrote:
>
>>
>> On 13 Apr 2017, at 19:26, Asbath
Part of my Discord bot as a goal was to add the ability to create database
entries so that people can quickly find documentation.
It was quite a challenge for me because I had to learn how heroku works,
PostgreSQL and all the other things but I did it!!!
In any discord channel you have now 3 comm
Ah, no my bad. Squeak was file in correctly the Trait and Class, it is
just that its browser does not let you know if a method class belong to
one of its Traits or the class itself
Le 14/04/2017 à 11:16, Hilaire a écrit :
> Give a try to filein the correct .st source file of the Traits+Classes
> p
Andrei?
Help?
On Fri, Apr 7, 2017 at 3:14 PM, Stephane Ducasse
wrote:
> Hi
>
> I found the SmaCCParserDebugger and I found the debug menu in the Smacc
> tool.
> Now I get a GT and byteCode debugger but I do not find a way to make the
> new debugger actif.
>
> Stef
>
2017-04-14 11:09 GMT+02:00 teso...@gmail.com :
> Hi, I think the problem was not clearly explained. This is the scenario
> that is problematic.
> This scenario does not happen in the new Spur implementation of
> forwarding, but I think is happening in the old one.
>
> 1. You have, let's say 3 inst
On 14 April 2017 at 08:53, Stephane Ducasse wrote:
> We always try to have a major release around mid/end of april
>
Once the dust settles, I think it would be wonderful to have this invariant:
- The latest Pharo VM source release is compatible with the latest Pharo
image.
This would make it e
2017-04-14 10:51 GMT+02:00 teso...@gmail.com :
> Hi Denis,
> in the script you are not generating instances of Class1, the problem
> is with the instances.
>
But it generates:
c1 := Class1 new.
Or what kind of generation you mean?
i don't see much difference comparing to old implementation of
#becomeForward:
the only issue is that #allInstances could report same instance twice
first, it will find an old instance (that is forwards to new one) and so,
add it to results array,
and then walking the heap further will find a new v
Give a try to filein the correct .st source file of the Traits+Classes
package. It does not get it right :(
Pharo5 get it right when loading the .st source file though.
Still investigating...
Le 14/04/2017 à 11:04, Hilaire a écrit :
> - Test on Squeak, not sure how stable it is there...
--
Dr.
On 13 April 2017 at 22:23, Esteban Lorenzano wrote:
>
> On 13 Apr 2017, at 19:26, Asbath Sama biyalou via Pharo-users <
> pharo-users@lists.pharo.org> wrote:
>
>
> *From: *Asbath Sama biyalou
> *Subject: **Export MongoDB to sql format*
> *Date: *13 April 2017 at 19:26:25 GMT+2
> *To: *Pharo user
Hi, I think the problem was not clearly explained. This is the scenario
that is problematic.
This scenario does not happen in the new Spur implementation of forwarding,
but I think is happening in the old one.
1. You have, let's say 3 instances of ClassA.
2. You add a new instance variable to Clas
On a restored Traits logic of my package, I made another attempt to
persist this time with filetree://. The net result is the same, the
Traits logic is lost in the classes using the Traits: all traits methods
are duplicated !!
To sum up, package saved with the following methods:
- *.mcz package w
On 12 April 2017 at 14:17, Guillermo Polito
wrote:
>
>
> On Wed, Apr 12, 2017 at 11:35 AM, Denis Kudriashov
> wrote:
>
>>
>> 2017-04-12 10:55 GMT+02:00 Guillermo Polito :
>>
>>> PharoClassInstaller>>migrateClasses: old to: new using:
anInstanceModification
instanceModification := anIns
Hi Denis,
in the script you are not generating instances of Class1, the problem
is with the instances.
Cheers,
Pablo
On Fri, Apr 14, 2017 at 10:04 AM, Denis Kudriashov
wrote:
>
> 2017-04-12 13:29 GMT+02:00 teso...@gmail.com :
>
>> Hi,
>> in non spur, the only improve that I think it can
On 14 April 2017 at 10:19, Stephane Ducasse wrote:
> But I do not get how doing that would handle the old instances?
> Because you want to migrate the old instances.
>
>
+1
there are no such thing as 'bad zombies', if they are there, it means you
either don't care about migrating data
or again, d
2017-04-12 13:29 GMT+02:00 teso...@gmail.com :
> Hi,
> in non spur, the only improve that I think it can be made safely is
> moving the garbage collect operation to the migration of instances side,
> only executing the garbage collect if there are instances.
>
> In spur the garbage collect it
2017-04-14 9:19 GMT+02:00 Stephane Ducasse :
> But I do not get how doing that would handle the old instances?
> Because you want to migrate the old instances.
>
But my example shows that old instances not exist after becomeFormard
operation. Or what you mean?
But I do not get how doing that would handle the old instances?
Because you want to migrate the old instances.
Stef
On Wed, Apr 12, 2017 at 1:26 PM, Denis Kudriashov
wrote:
>
> 2017-04-12 13:17 GMT+02:00 Guillermo Polito :
>
>> 1) each instance of A is becomed into its corresponding instance
31 matches
Mail list logo
