Re: [Pharo-dev] Floating-point numbers with radix (non-decimal)?

[ducasse]

Hi nicolas

let us fix this :)

why 15r1.2e1 is not working?
why 15r1.2e1 is not equals to 15r1.2E1?
why would we need a new syntax?

Stef
> On 5 Sep 2019, at 00:19, Nicolas Cellier  
> wrote:
> 
> Once upon a time, only uppercase letters were accpeted as extra digits (in 
> base > 10) for both int and float
> 
> Then 15r1.2E1 was not 15r1.2e1, the later being = 15r12.E
> 
> Then it was considered better to understand hexadecimal numbers with 
> lowercase too...
> and alternate-base Float became ambiguous and were never fixed :(
> 
> This would deserve a new syntax, I don't know what makes sense, 15r1.2_e1 
> 15r1.2#e1 ...
> Changing Smalltalk syntax is among the most difficult decisions, expect 
> outcry ;)
> Maybe because it's too easy :)
> 
> 
> Le jeu. 5 sept. 2019 à 00:04, James Foster  > a écrit :
> 14r1.2e1 "16.0"
> 15r1.2e1 “1.195851851851852"
> 
> Does it make sense to have exponents for numbers that are not base 10? There 
> are tests that have large exponents for binary numbers and we are not sure 
> how to handle this in GemStone.
> 
> James
> 

Re: [Pharo-dev] [Pharo-users] [ANN] Pharo Headless - Beta (Actually what is between Alpha and Beta)

[Ben Coman]

On Mon, 12 Aug 2019 at 17:59, teso...@gmail.com  wrote:

> Hi,
>the repos is https://github.com/pharo-project/opensmalltalk-vm in
> the headless branch
>

btw, to go directly to that branch...
https://github.com/pharo-project/opensmalltalk-vm/tree/headless

I'm really glad to see smalltalksrc on github for its accessibility.
The concern then is synchronization with the original Monticello repo.
Could a branch "headless-tracking-vmmaker" be created as a pure-mirror
updated by a daily CI job
so Github Compare View  can be used to easily see differences (
https://github.blog/2010-03-01-introducing-github-compare-view/)
This would make it easier for anyone to experiment locally merging in
vmmaker updates without needing access to the particular conversion-tool
being used.
That is, it would fan out better to potential contributors.

It might be useful to similarly have an independent
"headless-tracking-extracted".
How is the extraction currently being done?
Is it a script being run adhoc by particular people or is it run by a CI
job?
Again it would fan out better to potential contributors to not need access
to the extraction script.

cheers -ben

Re: [Pharo-dev] Floating-point numbers with radix (non-decimal)?

[Nicolas Cellier]

Once upon a time, only uppercase letters were accpeted as extra digits (in
base > 10) for both int and float

Then 15r1.2E1 was not 15r1.2e1, the later being = 15r12.E

Then it was considered better to understand hexadecimal numbers with
lowercase too...
and alternate-base Float became ambiguous and were never fixed :(

This would deserve a new syntax, I don't know what makes sense, 15r1.2_e1
15r1.2#e1 ...
Changing Smalltalk syntax is among the most difficult decisions, expect
outcry ;)
Maybe because it's too easy :)


Le jeu. 5 sept. 2019 à 00:04, James Foster  a
écrit :

> 14r1.2e1 "16.0"
> 15r1.2e1 “1.195851851851852"
>
> Does it make sense to have exponents for numbers that are not base 10?
> There are tests that have large exponents for binary numbers and we are not
> sure how to handle this in GemStone.
>
> James
>
>

[Pharo-dev] Floating-point numbers with radix (non-decimal)?

[James Foster]

14r1.2e1 "16.0"
15r1.2e1 “1.195851851851852"

Does it make sense to have exponents for numbers that are not base 10? There 
are tests that have large exponents for binary numbers and we are not sure how 
to handle this in GemStone.

James

Re: [Pharo-dev] [Pharo-users] Pharo Branding Organization on GitHub

[ducasse]

thanks for the initiative. 
I think that we have more material around, like alternate logo. 
It would be nice to collect also the svg versions?

I know that lusy did also design for mugs.


> On 4 Sep 2019, at 17:25, Torsten Bergmann  wrote:
> 
> Hi,
> 
> the Pharo community is growing and our lovely Pharo system is an innovation 
> driver with cool tools and projects 
> but it is also used in real projects in research and business setups.
> 
> There are still many entries left on all our TODO lists - not only in shaping 
> the next stable Pharo release(s) 
> but also in bringing more attention to people about what Pharo is all about.
> 
> A few of us already follow a well know marketing phrase: “Do good and talk 
> about it!” as some report about Pharo news
> in BLOGS, on TWITTER or by writing articles on MEDIUM.com or even books. I 
> also like that we have a growing number
> of YOUTUBE videos about Pharo. We also have a regular Newsletter - even a 
> Facebook page, ...
> 
> This gives visibility to Pharo activities and is already a good step in doing 
> some advertising.
> 
> An additional important lesson in successful marketing is that one has to 
> give a homogenous "Brand Identity" to a project or product
> to be easily recognizable and rememberable over time. We already have the 
> nice lighthouse and use it all over - but often it 
> is hard to find the logo or other marketing material in correct size or 
> correct graphics format. We should improve on that side
> too.
> 
> As we work mostly with git I therefore now have setup a new organization 
> "pharo-brand":
> 
>   https://github.com/pharo-brand
> 
> that should give easy access and group existing branding material in one 
> place.
> 
> The site now already includes the following three projects:
> 
>   1. pharo-brand-material
> 
>  This should be the place for "logo" and "logo-flat". In the 
> subdirectories you will find the logo in three different
>  variations:
> 
> - logo composed of text + icon + beacon
> - logo composed of icon + beacon
> - logo beacon only
> 
>   including subdirectories for "vector" (like SVG, PDF) and "screen" 
> formats (like PNG, BMP, ...)
> 
>   2. pharo-github-images
> 
>  These are the Icons i created for the various github organizations like
> 
> - https://github.com/pharo-project
> - https://github.com/pharo-nosql
> - https://github.com/pharo-rdbms
> - https://github.com/pharo-contributions
> - https://github.com/pharo-brand
> 
>  and a template for additional ones 
> 
>   3. pharo-jingle
> 
> A jingle is a short song or tune used in advertising. Jingles are a form 
> of sound and or video branding - when you see it often
> as an intro or outro you will more easily remember the brand name (Pharo 
> in this case).
> 
> This repository includes a "Pharo jingle" that can be used as a start or 
> end section within own custom videos about Pharo and 
> related projects.
> 
> The short video jingle was created using a free video software called 
> OpenShot using a sound jingle from freesound.org
> 
> - Pharo_HDV720_24p_1280x720.mp4
> - Pharo_HDV1080_25p_1920x1080.mp4
> - Pharo_HDV1440_25p_1440x1080.mp4
> 
> Note that the jingle is currently a proposal - if you have better ones we 
> can discuss it within the community on the mailinglist.
> 
> 
> I hope the repos will improve a little bit the situation in finding and 
> organizing the brand material.
> Feel free to comment and give feedback or even add marketing material 
> (templates, icons or other) yourself to the repos.
> 
> Thanks
> T.
> 

Re: [Pharo-dev] humanReadablePrintString

[Hilaire]

https://github.com/pharo-project/pharo/issues/4497

Le 04/09/2019 à 15:57, Sven Van Caekenberghe a écrit :
> Yes, probably.

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

[Pharo-dev] [Pharo 8.0] Build #698: Improving performance of athens

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!
  
The status of the build #698 was: SUCCESS.

The Pull Request #4464 was integrated: "Improving performance of athens"
Pull request url: https://github.com/pharo-project/pharo/pull/4464

Issue Url: https://github.com/pharo-project/pharo/issues/improving
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/Pharo8.0/698/

Re: [Pharo-dev] Pharo Branding Organization on GitHub

[Julien]

Nice initiative Torsten!

Cheers,

Julien

---
Julien Delplanque
Doctorant à l’Université de Lille
http://juliendelplanque.be/phd.html
Equipe Rmod, Inria
Bâtiment B 40, Avenue Halley 59650 Villeneuve d'Ascq
Numéro de téléphone: +333 59 35 86 40

> Le 4 sept. 2019 à 17:25, Torsten Bergmann  a écrit :
> 
> Hi,
> 
> the Pharo community is growing and our lovely Pharo system is an innovation 
> driver with cool tools and projects 
> but it is also used in real projects in research and business setups.
> 
> There are still many entries left on all our TODO lists - not only in shaping 
> the next stable Pharo release(s) 
> but also in bringing more attention to people about what Pharo is all about.
> 
> A few of us already follow a well know marketing phrase: “Do good and talk 
> about it!” as some report about Pharo news
> in BLOGS, on TWITTER or by writing articles on MEDIUM.com or even books. I 
> also like that we have a growing number
> of YOUTUBE videos about Pharo. We also have a regular Newsletter - even a 
> Facebook page, ...
> 
> This gives visibility to Pharo activities and is already a good step in doing 
> some advertising.
> 
> An additional important lesson in successful marketing is that one has to 
> give a homogenous "Brand Identity" to a project or product
> to be easily recognizable and rememberable over time. We already have the 
> nice lighthouse and use it all over - but often it 
> is hard to find the logo or other marketing material in correct size or 
> correct graphics format. We should improve on that side
> too.
> 
> As we work mostly with git I therefore now have setup a new organization 
> "pharo-brand":
> 
>   https://github.com/pharo-brand
> 
> that should give easy access and group existing branding material in one 
> place.
> 
> The site now already includes the following three projects:
> 
>   1. pharo-brand-material
> 
>  This should be the place for "logo" and "logo-flat". In the 
> subdirectories you will find the logo in three different
>  variations:
> 
> - logo composed of text + icon + beacon
> - logo composed of icon + beacon
> - logo beacon only
> 
>   including subdirectories for "vector" (like SVG, PDF) and "screen" 
> formats (like PNG, BMP, ...)
> 
>   2. pharo-github-images
> 
>  These are the Icons i created for the various github organizations like
> 
> - https://github.com/pharo-project
> - https://github.com/pharo-nosql
> - https://github.com/pharo-rdbms
> - https://github.com/pharo-contributions
> - https://github.com/pharo-brand
> 
>  and a template for additional ones 
> 
>   3. pharo-jingle
> 
> A jingle is a short song or tune used in advertising. Jingles are a form 
> of sound and or video branding - when you see it often
> as an intro or outro you will more easily remember the brand name (Pharo 
> in this case).
> 
> This repository includes a "Pharo jingle" that can be used as a start or 
> end section within own custom videos about Pharo and 
> related projects.
> 
> The short video jingle was created using a free video software called 
> OpenShot using a sound jingle from freesound.org
> 
> - Pharo_HDV720_24p_1280x720.mp4
> - Pharo_HDV1080_25p_1920x1080.mp4
> - Pharo_HDV1440_25p_1440x1080.mp4
> 
> Note that the jingle is currently a proposal - if you have better ones we 
> can discuss it within the community on the mailinglist.
> 
> 
> I hope the repos will improve a little bit the situation in finding and 
> organizing the brand material.
> Feel free to comment and give feedback or even add marketing material 
> (templates, icons or other) yourself to the repos.
> 
> Thanks
> T.
> 

[Pharo-dev] [Pharo 8.0] Build #697: UFFI-introduce-FFIBit-type

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!
  
The status of the build #697 was: FAILURE.

The Pull Request #4471 was integrated: "UFFI-introduce-FFIBit-type"
Pull request url: https://github.com/pharo-project/pharo/pull/4471

Issue Url: https://github.com/pharo-project/pharo/issues/UFFI
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/Pharo8.0/697/

Re: [Pharo-dev] Launcher: Missing version file for older Pharo

[ducasse]

Yes


> On 4 Sep 2019, at 19:10, Sean P. DeNigris  wrote:
> 
> ducasse wrote
>> Can you open a bug entry
> 
> Sure. For Launcher?
> 
> 
> 
> -
> Cheers,
> Sean
> --
> Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html
> 

Re: [Pharo-dev] Fund rising for the new Spec20 book.

[ducasse]

Hi sean

Thanks and sorry for the burden. I got some japanese supporters.
So it should work internationally. 
Could you tell me your bank and I can ask the platform?

> On 4 Sep 2019, at 19:04, Sean P. DeNigris  wrote:
> 
> The site said that my bank refused the transaction. I tried on two cards.
> Does it work internationally? Is there another way to send the money?
> 
> 
> 
> -
> Cheers,
> Sean
> --
> Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html
> 

Re: [Pharo-dev] Launcher: Missing version file for older Pharo

[Sean P. DeNigris]

ducasse wrote
> Can you open a bug entry

Sure. For Launcher?



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

Re: [Pharo-dev] Fund rising for the new Spec20 book.

[Sean P. DeNigris]

The site said that my bank refused the transaction. I tried on two cards.
Does it work internationally? Is there another way to send the money?



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

Re: [Pharo-dev] Launcher: Missing version file for older Pharo

[ducasse]

yes now we should add in the todo and check 
Can you open a bug entry


> On 4 Sep 2019, at 17:10, Sean P. DeNigris  wrote:
> 
> Would it be possible to add a pharo.version file to the zip for older (<5.0)
> Pharos? 
> 
> Right now, Launcher can't determine the version and the file has to be
> created manually. Since those versions aren't getting updated, I would
> assume it's a one-time task. I didn't file a Launcher issue because I guess
> it's an issue with the file server, not with Launcher per se.
> 
> 
> 
> -
> Cheers,
> Sean
> --
> Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html
> 

Re: [Pharo-dev] Epicea Feedback

[Sean P. DeNigris]

Done:
https://github.com/pharo-project/pharo/issues/4496
https://github.com/pharo-project/pharo/issues/4495



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

[Pharo-dev] Pharo Branding Organization on GitHub

[Torsten Bergmann]

Hi,

the Pharo community is growing and our lovely Pharo system is an innovation 
driver with cool tools and projects 
but it is also used in real projects in research and business setups.

There are still many entries left on all our TODO lists - not only in shaping 
the next stable Pharo release(s) 
but also in bringing more attention to people about what Pharo is all about.

A few of us already follow a well know marketing phrase: “Do good and talk 
about it!” as some report about Pharo news
in BLOGS, on TWITTER or by writing articles on MEDIUM.com or even books. I also 
like that we have a growing number
of YOUTUBE videos about Pharo. We also have a regular Newsletter - even a 
Facebook page, ...

This gives visibility to Pharo activities and is already a good step in doing 
some advertising.

An additional important lesson in successful marketing is that one has to give 
a homogenous "Brand Identity" to a project or product
to be easily recognizable and rememberable over time. We already have the nice 
lighthouse and use it all over - but often it 
is hard to find the logo or other marketing material in correct size or correct 
graphics format. We should improve on that side
too.

As we work mostly with git I therefore now have setup a new organization 
"pharo-brand":

   https://github.com/pharo-brand

that should give easy access and group existing branding material in one place.

The site now already includes the following three projects:

   1. pharo-brand-material
  
  This should be the place for "logo" and "logo-flat". In the 
subdirectories you will find the logo in three different
  variations:

 - logo composed of text + icon + beacon
 - logo composed of icon + beacon
 - logo beacon only
  
   including subdirectories for "vector" (like SVG, PDF) and "screen" 
formats (like PNG, BMP, ...)

   2. pharo-github-images

  These are the Icons i created for the various github organizations like

 - https://github.com/pharo-project
 - https://github.com/pharo-nosql
 - https://github.com/pharo-rdbms
 - https://github.com/pharo-contributions
 - https://github.com/pharo-brand

  and a template for additional ones 

   3. pharo-jingle

 A jingle is a short song or tune used in advertising. Jingles are a form 
of sound and or video branding - when you see it often
 as an intro or outro you will more easily remember the brand name (Pharo 
in this case).

 This repository includes a "Pharo jingle" that can be used as a start or 
end section within own custom videos about Pharo and 
 related projects.

 The short video jingle was created using a free video software called 
OpenShot using a sound jingle from freesound.org

 - Pharo_HDV720_24p_1280x720.mp4
 - Pharo_HDV1080_25p_1920x1080.mp4
 - Pharo_HDV1440_25p_1440x1080.mp4

 Note that the jingle is currently a proposal - if you have better ones we 
can discuss it within the community on the mailinglist.


I hope the repos will improve a little bit the situation in finding and 
organizing the brand material.
Feel free to comment and give feedback or even add marketing material 
(templates, icons or other) yourself to the repos.

Thanks
T.

[Pharo-dev] Launcher: Missing version file for older Pharo

[Sean P. DeNigris]

Would it be possible to add a pharo.version file to the zip for older (<5.0)
Pharos? 

Right now, Launcher can't determine the version and the file has to be
created manually. Since those versions aren't getting updated, I would
assume it's a one-time task. I didn't file a Launcher issue because I guess
it's an issue with the file server, not with Launcher per se.



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

[Pharo-dev] [Pharo 8.0] Build #696: fix/blockprinting

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!
  
The status of the build #696 was: FAILURE.

The Pull Request #4493 was integrated: "fix/blockprinting"
Pull request url: https://github.com/pharo-project/pharo/pull/4493

Issue Url: https://github.com/pharo-project/pharo/issues/fix/blockprinting
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/Pharo8.0/696/

Re: [Pharo-dev] humanReadablePrintString

[Sven Van Caekenberghe]

Yes, probably.

> On 4 Sep 2019, at 15:32, Hilaire  wrote:
> 
> Hi,
> 
> This code leads to an error:
> 
> "On place 10'000 € à un taux de 4 % par année.
> Au bout de combien d'années aura-t-on 20'000 € ?"
> | annee |
> annee := [ :capital |
> ((capital / 1) log / (1 + 0.04) log) years
> humanReadablePrintString  ].
> annee value: 2 .
> 
> #printWithCommasOn: is understood only by integer.
> 
> In my opinion printHumanReadableOn: should be edited as:
> 
> ../..
> 
> (wholeNanoseconds 'nanosecond')) do: [ :each |
> count := (self perform: each first) truncated.
> count > 0 
> 
> ../..
> 
> Opinion?
> 
> Hilaire
> 
> 
> -- 
> Dr. Geo
> http://drgeo.eu
> 
> 
> 

[Pharo-dev] humanReadablePrintString

[Hilaire]

Hi,

This code leads to an error:

"On place 10'000 € à un taux de 4 % par année.
Au bout de combien d'années aura-t-on 20'000 € ?"
| annee |
annee := [ :capital |
    ((capital / 1) log / (1 + 0.04) log) years
humanReadablePrintString  ].
annee value: 2 .

#printWithCommasOn: is understood only by integer.

In my opinion printHumanReadableOn: should be edited as:

../..

        (wholeNanoseconds 'nanosecond')) do: [ :each |
        count := (self perform: each first) truncated.
        count > 0 

../..

Opinion?

Hilaire


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

[Pharo-dev] [Pharo 8.0] Build #695: FAILURE

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!
  
The status of the build #695 was: FAILURE.

Could not extract further issue information from commit message: Create 
weekly-digest.yml

another try...
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/Pharo8.0/695/

Re: [Pharo-dev] possible Windows Update "1903" Iceberg problem

[Tudor Girba]

Super cool!! Thanks!

We will happily test.

Cheers,
Doru



> On Sep 4, 2019, at 10:04 AM, Guillermo Polito  
> wrote:
> 
> Hi all,
> 
> Sorry for not communicating better :).
> We know this is an important issue and we did move it to top priority even 
> prior to this email ;).
> Doru, to answer you, what people can do for the moment is to test what we are 
> going to propose in a couple of hours in your windows machines.
> With Pablo we have tested in several Windows 10 machines pre- and post- 
> update 1903. Still we would like people testing on their setups and other 
> windows versions
> 
> We have been working the last couple of days debugging openssh and libgit, 
> and building a version with a more up-to-date version of openssh.
> We will come back later this morning / early afternoon with 
> - a new vm setup using up to date versions of openssh
> - a description of workarounds for those tied to old versions of the VM
> So people can test.
> 
> Cheers,
> Guille and Pablo
> 
>> El 4 sept 2019, a las 8:38, ducasse  escribió:
>> 
>> I saw everybody super busy and I imagine that they will reply soon. 
>> I’m travelling to give Pharo lectures. 
>> 
>>> On 3 Sep 2019, at 19:23, Tudor Girba  wrote:
>>> 
>>> Hi,
>>> 
>>> Is there a way to speed the work on this one?
>>> 
>>> At this moment, people cannot load any code in Pharo on Windows 10.
>>> 
>>> Cheers,
>>> Doru
>>> 
>>> --
>>> www.feenk.com
>>> "Every thing has its own flow."
>>> 
 On 28 Aug 2019, at 16:20, ducasse  wrote:
 
 tx doru
 
 Stef
 
> On 28 Aug 2019, at 16:01, Tudor Girba  wrote:
> 
> Hi
> 
> I opened an issue: https://github.com/pharo-project/pharo/issues/4437
> 
> I believe this should be treated as critical given that we cannot load 
> code in Pharo 7 (or 8) which makes it almost useless for users.
> 
> Cheers,
> Doru
> 
> 
>> On Aug 27, 2019, at 10:54 AM, Tudor Girba  wrote:
>> 
>> Hi,
>> 
>> We just encountered this on two different machines. We got this after 
>> the update to Windows 1903. For us it’s a critical issue at this point. 
>> What can we do to help with this?
>> 
>> Cheers,
>> Doru
>> 
>> 
>> 
>>> On Aug 17, 2019, at 12:50 PM, Ben Coman  wrote:
>>> 
>>> hi Stef,  
>>> I feel you missed my point. Probably I wasn't clear this has already 
>>> been tested with latest Pharo 8 launched by PharoLauncher.  
>>> The problem occurs with Pharo 7.0.3(64 bit) and with 
>>> Pharo8.0-SNAPSHOT-build.635(64 bit) 
>>> after Microsoft Windows Update 1903...
>>> https://www.computerworld.com/article/3409621/microsoft-starts-windows-10s-1803-to-1903-forced-upgrade.html
>>>   
>>> 
>>> If indeed 1903 is the cause, with this update now being *forced* down 
>>> on people, this will potentially soon impact more and more Windows 
>>> users.
>>> But my guess that 1903 is the culprit needs to be confirmed.  
>>> So I am requesting someone with access to multiple Windows machines 
>>> directly compare a 1903 machine with a pre-1903 machine. 
>>> 
>>> cheers -ben
>>> 
>>> On Sat, 17 Aug 2019 at 12:58, ducasse  wrote:
>>> Hi ben 
>>> 
>>> in the pharo launcher if you click on P8.0 (development version) you 
>>> get access to all the builds. 
>>> 
>>> Stef
>>> 
 On 16 Aug 2019, at 16:02, Ben Coman  wrote:
 
 IThis morning the May 2019 Windows Update "1903" forced itself onto my 
 computer and now 64-bits Pharo seems to have a problem with 
 git_remote_fetch() FFI callout.  I no longer have a non-1903 machine 
 to directly compare behaviour before "1903".  Can someone familiar 
 with this area with both "pre-1903" and "1903" machines triage whether 
 "1903" is indeed the cause?
 
 A few other recent reports are noted here...
 https://github.com/pharo-project/pharo/issues/3418  
 
 cheers -ben
>>> 
>> 
>> --
>> feenk.com
>> 
>> "Not knowing how to do something is not an argument for how it cannot be 
>> done."
>> 
> 
> --
> feenk.com
> 
> “Live like you mean it."
> 
> 
 
 
 
>>> 
>> 
>> 
>> 
> 
> 

--
feenk.com

"Innovation comes in the least expected form. 
That is, if it is expected, it already happened."

Re: [Pharo-dev] possible Windows Update "1903" Iceberg problem

[Guillermo Polito]

Hi all,

Sorry for not communicating better :).
We know this is an important issue and we did move it to top priority even 
prior to this email ;).
Doru, to answer you, what people can do for the moment is to test what we are 
going to propose in a couple of hours in your windows machines.
With Pablo we have tested in several Windows 10 machines pre- and post- update 
1903. Still we would like people testing on their setups and other windows 
versions

We have been working the last couple of days debugging openssh and libgit, and 
building a version with a more up-to-date version of openssh.
We will come back later this morning / early afternoon with 
 - a new vm setup using up to date versions of openssh
 - a description of workarounds for those tied to old versions of the VM
So people can test.

Cheers,
Guille and Pablo

> El 4 sept 2019, a las 8:38, ducasse  escribió:
> 
> I saw everybody super busy and I imagine that they will reply soon. 
> I’m travelling to give Pharo lectures. 
> 
>> On 3 Sep 2019, at 19:23, Tudor Girba  wrote:
>> 
>> Hi,
>> 
>> Is there a way to speed the work on this one?
>> 
>> At this moment, people cannot load any code in Pharo on Windows 10.
>> 
>> Cheers,
>> Doru
>> 
>> --
>> www.feenk.com
>> "Every thing has its own flow."
>> 
>>> On 28 Aug 2019, at 16:20, ducasse  wrote:
>>> 
>>> tx doru
>>> 
>>> Stef
>>> 
 On 28 Aug 2019, at 16:01, Tudor Girba  wrote:
 
 Hi
 
 I opened an issue: https://github.com/pharo-project/pharo/issues/4437
 
 I believe this should be treated as critical given that we cannot load 
 code in Pharo 7 (or 8) which makes it almost useless for users.
 
 Cheers,
 Doru
 
 
> On Aug 27, 2019, at 10:54 AM, Tudor Girba  wrote:
> 
> Hi,
> 
> We just encountered this on two different machines. We got this after the 
> update to Windows 1903. For us it’s a critical issue at this point. What 
> can we do to help with this?
> 
> Cheers,
> Doru
> 
> 
> 
>> On Aug 17, 2019, at 12:50 PM, Ben Coman  wrote:
>> 
>> hi Stef,  
>> I feel you missed my point. Probably I wasn't clear this has already 
>> been tested with latest Pharo 8 launched by PharoLauncher.  
>> The problem occurs with Pharo 7.0.3(64 bit) and with 
>> Pharo8.0-SNAPSHOT-build.635(64 bit) 
>> after Microsoft Windows Update 1903...
>> https://www.computerworld.com/article/3409621/microsoft-starts-windows-10s-1803-to-1903-forced-upgrade.html
>>   
>> 
>> If indeed 1903 is the cause, with this update now being *forced* down on 
>> people, this will potentially soon impact more and more Windows users.
>> But my guess that 1903 is the culprit needs to be confirmed.  
>> So I am requesting someone with access to multiple Windows machines 
>> directly compare a 1903 machine with a pre-1903 machine. 
>> 
>> cheers -ben
>> 
>> On Sat, 17 Aug 2019 at 12:58, ducasse  wrote:
>> Hi ben 
>> 
>> in the pharo launcher if you click on P8.0 (development version) you get 
>> access to all the builds. 
>> 
>> Stef
>> 
>>> On 16 Aug 2019, at 16:02, Ben Coman  wrote:
>>> 
>>> IThis morning the May 2019 Windows Update "1903" forced itself onto my 
>>> computer and now 64-bits Pharo seems to have a problem with 
>>> git_remote_fetch() FFI callout.  I no longer have a non-1903 machine to 
>>> directly compare behaviour before "1903".  Can someone familiar with 
>>> this area with both "pre-1903" and "1903" machines triage whether 
>>> "1903" is indeed the cause?
>>> 
>>> A few other recent reports are noted here...
>>> https://github.com/pharo-project/pharo/issues/3418  
>>> 
>>> cheers -ben
>> 
> 
> --
> feenk.com
> 
> "Not knowing how to do something is not an argument for how it cannot be 
> done."
> 
 
 --
 feenk.com
 
 “Live like you mean it."
 
 
>>> 
>>> 
>>> 
>> 
> 
> 
> 

[Pharo-dev] [Pharo 8.0] Build #694: writeScanOn-is-dead-code

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!
  
The status of the build #694 was: FAILURE.

The Pull Request #4484 was integrated: "writeScanOn-is-dead-code"
Pull request url: https://github.com/pharo-project/pharo/pull/4484

Issue Url: https://github.com/pharo-project/pharo/issues/writeScanOn
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/Pharo8.0/694/

Re: [Pharo-dev] possible Windows Update "1903" Iceberg problem

[ducasse]

I saw everybody super busy and I imagine that they will reply soon. 
I’m travelling to give Pharo lectures. 

> On 3 Sep 2019, at 19:23, Tudor Girba  wrote:
> 
> Hi,
> 
> Is there a way to speed the work on this one?
> 
> At this moment, people cannot load any code in Pharo on Windows 10.
> 
> Cheers,
> Doru
> 
> --
> www.feenk.com
> "Every thing has its own flow."
> 
>> On 28 Aug 2019, at 16:20, ducasse  wrote:
>> 
>> tx doru
>> 
>> Stef
>> 
>>> On 28 Aug 2019, at 16:01, Tudor Girba  wrote:
>>> 
>>> Hi
>>> 
>>> I opened an issue: https://github.com/pharo-project/pharo/issues/4437
>>> 
>>> I believe this should be treated as critical given that we cannot load code 
>>> in Pharo 7 (or 8) which makes it almost useless for users.
>>> 
>>> Cheers,
>>> Doru
>>> 
>>> 
 On Aug 27, 2019, at 10:54 AM, Tudor Girba  wrote:
 
 Hi,
 
 We just encountered this on two different machines. We got this after the 
 update to Windows 1903. For us it’s a critical issue at this point. What 
 can we do to help with this?
 
 Cheers,
 Doru
 
 
 
> On Aug 17, 2019, at 12:50 PM, Ben Coman  wrote:
> 
> hi Stef,  
> I feel you missed my point. Probably I wasn't clear this has already been 
> tested with latest Pharo 8 launched by PharoLauncher.  
> The problem occurs with Pharo 7.0.3(64 bit) and with 
> Pharo8.0-SNAPSHOT-build.635(64 bit) 
> after Microsoft Windows Update 1903...
> https://www.computerworld.com/article/3409621/microsoft-starts-windows-10s-1803-to-1903-forced-upgrade.html
>   
> 
> If indeed 1903 is the cause, with this update now being *forced* down on 
> people, this will potentially soon impact more and more Windows users.
> But my guess that 1903 is the culprit needs to be confirmed.  
> So I am requesting someone with access to multiple Windows machines 
> directly compare a 1903 machine with a pre-1903 machine. 
> 
> cheers -ben
> 
> On Sat, 17 Aug 2019 at 12:58, ducasse  wrote:
> Hi ben 
> 
> in the pharo launcher if you click on P8.0 (development version) you get 
> access to all the builds. 
> 
> Stef
> 
>> On 16 Aug 2019, at 16:02, Ben Coman  wrote:
>> 
>> IThis morning the May 2019 Windows Update "1903" forced itself onto my 
>> computer and now 64-bits Pharo seems to have a problem with 
>> git_remote_fetch() FFI callout.  I no longer have a non-1903 machine to 
>> directly compare behaviour before "1903".  Can someone familiar with 
>> this area with both "pre-1903" and "1903" machines triage whether "1903" 
>> is indeed the cause?
>> 
>> A few other recent reports are noted here...
>> https://github.com/pharo-project/pharo/issues/3418  
>> 
>> cheers -ben
> 
 
 --
 feenk.com
 
 "Not knowing how to do something is not an argument for how it cannot be 
 done."
 
>>> 
>>> --
>>> feenk.com
>>> 
>>> “Live like you mean it."
>>> 
>>> 
>> 
>> 
>> 
>