Re: [Pharo-users] Frozen at start up

[Sean P. DeNigris]

HilaireFernandes wrote
> Any idea?

Can you try starting with `--no-default-preferences` and see if it's the
same?



-
Cheers,
Sean
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Re: [Pharo-users] GemStone/S on Docker?

[Jupiter Jones]

I’ve copied this to the GemStone list to continue the discussion.

> I wouldn't. The excellent work of Norbert was later 
> inspired/continuated/extended officially by GemStone under a much bigger 
> project called GsDevKit [1]
> 
> [1] https://github.com/GsDevKit/GsDevKit_home 
> 
+1 GsDevKit - it’s excellent for use in both development and deployment.

There’s also an ansible project [1] which may offer some guidance.

If you were planning to build containers for GemStone, there are a bunch of 
possible roles a single host might play in larger systems, but as a minimum:

1. Stone - where the repository (image) is physically managed. Typically only 
one per deployment (or more for warm failover)
2. Gem - where the VM’s run your application or services. Instances scale with 
your application.
3. Shared Page Cache - essentially shared memory access to the image that can 
be deployed in many ways to turn your applications. 

There’s a rundown on connecting distributed systems in the GS System Admin 
Guide [2]. There are likely many other roles right down to transaction logs and 
repository extents (the physical files on disc where your image is persisted), 
it just depends on how far you want to go with the flexibility of the docker 
containers.

This said, GsDevKit will setup the above three roles on a single host which 
will suit development and deployment of any small application.

Cheers,
J

[1] https://github.com/GsDevKit/GsDevKit_ansible 

[2] 
https://downloads.gemtalksystems.com/docs/GemStone64/3.4.x/GS64-SysAdminGuide-3.4/GS64-SysAdminGuide-3.4.htm?https://downloads.gemtalksystems.com/docs/GemStone64/3.4.x/GS64-SysAdminGuide-3.4/5-Distributed.htm
 

Re: [Pharo-users] Frozen at start up

[Hilaire]

Thanks I will dig on that direction.

By the way, DrGeo code at SH is obsolete. Pharo7 port is at 
http://dev.drgeo.eu, more precisely 
https://bazaar.launchpad.net/~drgeo-developers/drgeo/trunk/files/head:/src/


I should update the information page.

Thanks for the tips


Le 10/04/2018 à 21:36, teso...@gmail.com a 
écrit :

Hi Hilaire,
  I have seen the same problem when trying to reproduce the error with 
FreeTypeFonts.
I can see that the problem arise because there is a startUp of a class 
that is calling the #splash method. This method uses Delay.
As this is run during the startup of the classes, it runs with the 
higher priority. Taking precedence over the Delay scheduling process.
In Pharo 7 the startup of the session runs in higher priority so it 
cannot be interrupted.
This is done in that way to fix some problems during the 
initialization of the session (Now, I could not remember what was fixed).

I believe this actions should be executed as a deferred action.

Also I have found a problem with the requirement of the UIThemeWatery 
class, I have fixed it extending UITheme with a new subclass (same 
behavior) so the code can be loaded.


If you want I can help you to port DrGeo to Pharo7.


--
Dr. Geo
http://drgeo.eu

Re: [Pharo-users] Frozen at start up

[teso...@gmail.com]

Hi Hilaire,
  I have seen the same problem when trying to reproduce the error with
FreeTypeFonts.
I can see that the problem arise because there is a startUp of a class that
is calling the #splash method. This method uses Delay.
As this is run during the startup of the classes, it runs with the higher
priority. Taking precedence over the Delay scheduling process.
In Pharo 7 the startup of the session runs in higher priority so it cannot
be interrupted.
This is done in that way to fix some problems during the initialization of
the session (Now, I could not remember what was fixed).
I believe this actions should be executed as a deferred action.

Also I have found a problem with the requirement of the UIThemeWatery
class, I have fixed it extending UITheme with a new subclass (same
behavior) so the code can be loaded.

If you want I can help you to port DrGeo to Pharo7.

Cheers,
Pablo

On Tue, Apr 10, 2018 at 8:32 PM, Hilaire  wrote:

> Hi,
> I have this strange situation with a DrGeo built against P7, where DrGeo
> starts, but then get frozen with this message.
> Strangely the start seems not to have completed as the UI messages are not
> localized in French.
>
> What is strange, on my PC where I built the app, this problem does not
> occur.
>
> Any idea?
>
> Thanks
>
> Hilaire
>
>
> --
> Dr. Geo
> http://drgeo.eu
>



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

[Pharo-users] Frozen at start up

[Hilaire]

Hi,
I have this strange situation with a DrGeo built against P7, where DrGeo 
starts, but then get frozen with this message.
Strangely the start seems not to have completed as the UI messages are 
not localized in French.


What is strange, on my PC where I built the app, this problem does not 
occur.


Any idea?

Thanks

Hilaire


--
Dr. Geo
http://drgeo.eu

Re: [Pharo-users] FreeFontProvider unload [was] Re: Black screen on Mac OSX

[Hilaire]

Hi Pablo,

DrGeo is shipped with two fonts, depending on the system locale at DrGeo 
start up, one or another one is used. So the cache need to be reset at. 
May be there is better to handle that, it worked pretty well until now.


Hilaire


Le 10/04/2018 à 10:53, teso...@gmail.com a 
écrit :

Hi Hilaire,
  thanks for spliting the subject, I have missed the discussion in the 
other thread.


The #unload message should be used to clean up the system in case the 
class is unload from the system.
That's why the logic has been move to the #resetCurrent method that is 
called during the shutdown of the image.


However, the question is not if the method should be included in a 
compatibility package or if the users should send #resetCurrent.
The problem is why it is needed to clean up the font cache, it should 
not be needed. The only scenario I think is if you want to replace a 
font (in the Pharo world a Face, because there is a font per each 
combination of face and point size) named exactly the same with 
another one. I think this is no normal behavior.


I will try to see why this is needed when loading DrGeo in Pharo7 and 
fix the FT implementation not to need it.

Maybe it is hiding a bigger issue.



--
Dr. Geo
http://drgeo.eu

Re: [Pharo-users] Iceberg: whom to email directly?

[Herbert Vojčík]

Ben Coman wrote:



On 10 April 2018 at 23:46, Herbert Vojčík > wrote:

I have a strict "no github account" policy.

Whom/where should I post to report issues?

Thanks, Herby


https://pharo.fogbugz.com


Ironically, I ask because of 
https://pharo.fogbugz.com/f/cases/21684/Integrate-Iceberg-0-7#BugEvent.200101, 
but, thanks. Maybe the issue in question is actually reposted / tracked.



cheers -ben

Re: [Pharo-users] Iceberg: whom to email directly?

[Ben Coman]

On 10 April 2018 at 23:46, Herbert Vojčík  wrote:

> I have a strict "no github account" policy.
>
> Whom/where should I post to report issues?
>
> Thanks, Herby
>
>
https://pharo.fogbugz.com

cheers -ben

[Pharo-users] Iceberg: whom to email directly?

[Herbert Vojčík]

I have a strict "no github account" policy.

Whom/where should I post to report issues?

Thanks, Herby

Re: [Pharo-users] [Pharo-dev] [TechTalk] April 12: GIT with Iceberg

[Esteban Lorenzano]

more like to present the new UI (it received a complete revamp, so we need to 
inform about it ;) )

cheers!
Esteban

> On 10 Apr 2018, at 16:34, Marcus Denker  wrote:
> 
> Hi,
> 
> There next TechTalk will be April 12: GIT with Iceberg
> 
>   https://association.pharo.org/event-2797068
> 
> 
> A regular chat about Pharo. Happens on Discord.
> 
> The Tech talks are open to both members and non-members! 
> 
> Topic:  GIT with Iceberg. Demo of improved UI
> 
> We will send an information to all subscribers some hours before the talk 
> starts.
> 
> 
> 

[Pharo-users] [TechTalk] April 12: GIT with Iceberg

[Marcus Denker]

Hi,

There next TechTalk will be April 12: GIT with Iceberg

https://association.pharo.org/event-2797068


A regular chat about Pharo. Happens on Discord.

The Tech talks are open to both members and non-members! 

Topic:  GIT with Iceberg. Demo of improved UI

We will send an information to all subscribers some hours before the talk 
starts.

Re: [Pharo-users] GemStone/S on Docker?

[Mariano Martinez Peck]

On Tue, Apr 10, 2018 at 9:32 AM, sergio ruiz  wrote:

>
> What do you mean by „something that doesn’t require refactoring“ ?
>
>
> I used mongo voyager for a few projects.. i ended up having to refactor
> here and there to get it to work (to connect my data mongodb).. I’d like to
> try an object database.
>
>
> I think to put GemStone/S on docker should be easy package wise. Years ago
> when I used GemStone I created these scripts
>
> https://github.com/noha/stone-creator
>
>
>
> great! i’ll take a look at this.
>
>
I wouldn't. The excellent work of Norbert was later
inspired/continuated/extended officially by GemStone under a much bigger
project called GsDevKit [1]

[1] https://github.com/GsDevKit/GsDevKit_home

Cheers,



> Thanks!
>
>
> 
> peace,
> sergio
> photographer, journalist, visionary
>
> Public Key: http://bit.ly/29z9fG0
> #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV
> http://www.codeandmusic.com
> http://www.twitter.com/sergio_101
> http://www.facebook.com/sergio101
>



-- 
Mariano
http://marianopeck.wordpress.com

Re: [Pharo-users] GemStone/S on Docker?

[Esteban Lorenzano]

> On 10 Apr 2018, at 14:32, sergio ruiz  wrote:
> 
>> 
>> What do you mean by „something that doesn’t require refactoring“ ?
>> 
> 
> I used mongo voyager for a few projects.. i ended up having to refactor here 
> and there to get it to work (to connect my data mongodb).. I’d like to try an 
> object database.

I could use an example of those refactors. 
the objective of Voyage is to not need that :)

cheers,
Esteban

> 
> 
>> I think to put GemStone/S on docker should be easy package wise. Years ago 
>> when I used GemStone I created these scripts
>> 
>> https://github.com/noha/stone-creator 
>> 
>> 
> 
> great! i’ll take a look at this.
> 
> Thanks!
> 
> 
> 
> peace,
> sergio
> photographer, journalist, visionary
> 
> Public Key: http://bit.ly/29z9fG0 
> #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV
> http://www.codeandmusic.com 
> http://www.twitter.com/sergio_101 
> http://www.facebook.com/sergio101 

Re: [Pharo-users] GemStone/S on Docker?

[sergio ruiz]

What do you mean by „something that doesn’t require refactoring“ ?


I used mongo voyager for a few projects.. i ended up having to refactor here 
and there to get it to work (to connect my data mongodb).. I’d like to try an 
object database.


I think to put GemStone/S on docker should be easy package wise. Years ago when 
I used GemStone I created these scripts

https://github.com/noha/stone-creator



great! i’ll take a look at this.

Thanks!



peace,
sergio
photographer, journalist, visionary

Public Key: http://bit.ly/29z9fG0
#BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV
http://www.codeandmusic.com
http://www.twitter.com/sergio_101
http://www.facebook.com/sergio101

signature.asc
Description: Message signed with OpenPGP using AMPGpg

Re: [Pharo-users] FreeFontProvider unload [was] Re: Black screen on Mac OSX

[teso...@gmail.com]

Hi Hilaire,
  thanks for spliting the subject, I have missed the discussion in the
other thread.

The #unload message should be used to clean up the system in case the class
is unload from the system.
That's why the logic has been move to the #resetCurrent method that is
called during the shutdown of the image.

However, the question is not if the method should be included in a
compatibility package or if the users should send #resetCurrent.
The problem is why it is needed to clean up the font cache, it should not
be needed. The only scenario I think is if you want to replace a font (in
the Pharo world a Face, because there is a font per each combination of
face and point size) named exactly the same with another one. I think this
is no normal behavior.

I will try to see why this is needed when loading DrGeo in Pharo7 and fix
the FT implementation not to need it.
Maybe it is hiding a bigger issue.

Cheers,
Pablo

On Mon, Apr 9, 2018 at 9:52 PM, Hilaire  wrote:

> I tracked the problem, it is related to change in the FreeTypeFontProvider
> behavior.
>
> In P3, #unload message cleared the cache. In P7, #unload just does
> nothing. Seems to be replaced by #resetCurrent
>
> Hilaire
>
>
> Le 07/04/2018 à 17:43, Stephane Ducasse a écrit :
>
>> Hi Hilaire
>>
>> The app goes to the dock but nothing happens. What is strange is that
>> it is assigned to none display.
>> I tried to open the drgeo.image with my working Pharo6.1VM and it did not
>> work.
>> I tried to open the drgeo.image with my working Pharo70VM and it did not
>> work.
>> => did not open.
>>
>> I could open one of my Phaor 70 images with the VM you ship.
>>
>> I have no log files or others. So I do not know what to do.
>>
>
> --
> Dr. Geo
> http://drgeo.eu
>
>
>
>


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

Re: [Pharo-users] GemStone/S on Docker?

[Norbert Hartl]

> Am 10.04.2018 um 05:03 schrieb sergio ruiz :
> 
> Has anyone set up GemStone/S on Docker?
> 
> I have another project that I need persistence on. In the past, I have use 
> voyager, but I’d really like to use something that doesn’t require 
> refactoring. I was looking at Magma, but it looks like that is Squeak only.
> 
> 
What do you mean by „something that doesn’t require refactoring“ ?

I think to put GemStone/S on docker should be easy package wise. Years ago when 
I used GemStone I created these scripts

https://github.com/noha/stone-creator 

in order to create a simple directory containing a stone. This directory would 
be suitable to be copied into a docker image. The extent and log dirs can then 
be mapped from the outside. But I’m not sure it will work out at the end. 
Docker is for isolating processes from the underlying OS. But GemStone 
limitations of the community edition use e.g. CPU pinning to make sure you only 
use two cores. I don’t know if those things can conflict with the way docker 
works. But if you are successful let me know :)

Norbert
> 
> peace,
> sergio
> photographer, journalist, visionary
> 
> Public Key: http://bit.ly/29z9fG0 
> #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV
> http://www.codeandmusic.com 
> http://www.twitter.com/sergio_101 
> http://www.facebook.com/sergio101 

Re: [Pharo-users] "News" section of the website down

[Esteban Lorenzano]

tx, is fixed now but I needed to clean a bit to make it happen :( 

> On 10 Apr 2018, at 08:19, Stephane Ducasse  wrote:
> 
> Tx mathieu.
> We will fix it.
> 
> 
> On Mon, Apr 9, 2018 at 10:28 PM, Mathieu Dubois via Pharo-users
>  wrote:
>> 
>> 
>> -- Forwarded message --
>> From: Mathieu Dubois 
>> To: pharo-users@lists.pharo.org
>> Cc:
>> Bcc:
>> Date: Mon, 9 Apr 2018 22:28:31 +0200
>> Subject: Re: "News" section of the website down
>> Just wanted to report that the "news" section still doesn't work (same error 
>> than before).
>> 
>> Le 27/03/2018 à 19:56, Mathieu Dubois a écrit :
>>> 
>>> Hello,
>>> 
>>> I don't know how to report that but for several weeks (maybe months), I 
>>> can't reach the "News" section of the website (I have tried from several 
>>> locations with different ISP). I usually get a timeout error (error 524 
>>> from Cloudflare) that comes from pharo.org.
>>> 
>>> Mathieu
>>> 
>> 
>> 
>> 
> 

Re: [Pharo-users] "News" section of the website down

[Stephane Ducasse]

Tx mathieu.
We will fix it.


On Mon, Apr 9, 2018 at 10:28 PM, Mathieu Dubois via Pharo-users
 wrote:
>
>
> -- Forwarded message --
> From: Mathieu Dubois 
> To: pharo-users@lists.pharo.org
> Cc:
> Bcc:
> Date: Mon, 9 Apr 2018 22:28:31 +0200
> Subject: Re: "News" section of the website down
> Just wanted to report that the "news" section still doesn't work (same error 
> than before).
>
> Le 27/03/2018 à 19:56, Mathieu Dubois a écrit :
>>
>> Hello,
>>
>> I don't know how to report that but for several weeks (maybe months), I 
>> can't reach the "News" section of the website (I have tried from several 
>> locations with different ISP). I usually get a timeout error (error 524 from 
>> Cloudflare) that comes from pharo.org.
>>
>> Mathieu
>>
>
>
>