Current 3.0 download is broken

> Hi all,
>
> I wanted to toy around with 3.0 for a moment today, so I downloaded the last image from http://files.pharo.org/image/30/Pharo-Image-3.0-latest.zip It is unresponsive with 100% CPU usage. I thought it was a VM issue of mine, so I downloaded the installer , and this has the same issue. I
>
> This is MacOS, I'm still on 10.8.5, I attach PharoDebug.log below for your perusal
>
> Greetings,
>
> <PharoDebug.log>
>
> ---> Save our in-boxes! http://emailcharter.org <---
>
> Johan Fabry   -   http://pleiad.cl/~jfabry
> PLEIAD lab  -  Computer Science Department (DCC)  -  University of Chile
>

>
> On 08 Nov 2013, at 20:54, Johan Fabry <[hidden email]> wrote:
>
>> Hi all,
>>
>> I wanted to toy around with 3.0 for a moment today, so I downloaded the last image from http://files.pharo.org/image/30/Pharo-Image-3.0-latest.zip It is unresponsive with 100% CPU usage. I thought it was a VM issue of mine, so I downloaded the installer , and this has the same issue. I
>>
>> This is MacOS, I'm still on 10.8.5, I attach PharoDebug.log below for your perusal
>>
>
> Do you use a startup script? It might be incompatible and trigger a strange bug…
>
> Marcus
>
>
>

>
> Nope, I just unzip the new image and double click it. (+ I never defined any startup script anywhere)
>
> On Nov 9, 2013, at 9:52 AM, Marcus Denker <[hidden email]> wrote:
>
>>
>> On 08 Nov 2013, at 20:54, Johan Fabry <[hidden email]> wrote:
>>
>>> Hi all,
>>>
>>> I wanted to toy around with 3.0 for a moment today, so I downloaded the last image from http://files.pharo.org/image/30/Pharo-Image-3.0-latest.zip It is unresponsive with 100% CPU usage. I thought it was a VM issue of mine, so I downloaded the installer , and this has the same issue. I
>>>
>>> This is MacOS, I'm still on 10.8.5, I attach PharoDebug.log below for your perusal
>>>
>>
>> Do you use a startup script? It might be incompatible and trigger a strange bug…
>>
>> Marcus
>>
>>
>>
>
>
>
> ---> Save our in-boxes! http://emailcharter.org <---
>
> Johan Fabry   -   http://pleiad.cl/~jfabry
> PLEIAD lab  -  Computer Science Department (DCC)  -  University of Chile
>
>

> On 2013-11-09, at 14:17, Camillo Bruni <[hidden email]> wrote:
>> On 2013-11-09, at 14:00, Marcus Denker <[hidden email]> wrote:
>>> On 09 Nov 2013, at 13:55, Johan Fabry <[hidden email]> wrote:
>>>> Nope, I just unzip the new image and double click it. (+ I never defined any startup script anywhere)
>>>>
>>> do you have a .sources file?
>>
>> probably that, since the lookup logic changed the other day. I will try without the .sources
>
> Confirmed, if I open the image without sources it hangs (strangely enough not even with stderr output)
> Saving the image with sources and then opening it again without sources works, producing a proper warning

>
> On 2013-11-09, at 14:29, Camillo Bruni <[hidden email]> wrote:
>
>> On 2013-11-09, at 14:17, Camillo Bruni <[hidden email]> wrote:
>>> On 2013-11-09, at 14:00, Marcus Denker <[hidden email]> wrote:
>>>> On 09 Nov 2013, at 13:55, Johan Fabry <[hidden email]> wrote:
>>>>> Nope, I just unzip the new image and double click it. (+ I never defined any startup script anywhere)
>>>>>
>>>> do you have a .sources file?
>>>
>>> probably that, since the lookup logic changed the other day. I will try without the .sources
>>
>> Confirmed, if I open the image without sources it hangs (strangely enough not even with stderr output)
>> Saving the image with sources and then opening it again without sources works, producing a proper warning
>
> https://pharo.fogbugz.com/f/cases/12129/FileLocator-is-not-initialized-at-the-right-point-during-startup

>
> On Nov 9, 2013, at 10:52 AM, Camillo Bruni <[hidden email]> wrote:
>
>>
>> On 2013-11-09, at 14:29, Camillo Bruni <[hidden email]> wrote:
>>
>>> On 2013-11-09, at 14:17, Camillo Bruni <[hidden email]> wrote:
>>>> On 2013-11-09, at 14:00, Marcus Denker <[hidden email]> wrote:
>>>>> On 09 Nov 2013, at 13:55, Johan Fabry <[hidden email]> wrote:
>>>>>> Nope, I just unzip the new image and double click it. (+ I never defined any startup script anywhere)
>>>>>>
>>>>> do you have a .sources file?
>>>>
>>>> probably that, since the lookup logic changed the other day. I will try without the .sources
>>>
>>> Confirmed, if I open the image without sources it hangs (strangely enough not even with stderr output)
>>> Saving the image with sources and then opening it again without sources works, producing a proper warning
>>
>> https://pharo.fogbugz.com/f/cases/12129/FileLocator-is-not-initialized-at-the-right-point-during-startup
>
> Confirmed from my end: putting a PharoV20.sources in the same directory as the VM (Pharo.app) solved the problem. Note that putting it in the same directory as the image does NOT solve the problem. I don't know what the expected behavior is anymore, so I am just reporting both behaviors here.
>
> Thanks for looking into this!
>
> ---> Save our in-boxes! http://emailcharter.org <---
>
> Johan Fabry   -   http://pleiad.cl/~jfabry
> PLEIAD lab  -  Computer Science Department (DCC)  -  University of Chile
>
>
>

>> On 09 Nov 2013, at 15:37, Johan Fabry <[hidden email]> wrote:
>>> For double completeness ;-) The one-click download Pharo3.0-mac.zip has the same problem. The included source file is in the wrong directory. It should be moved out of Contents/Resources and moved into Contents/MacOS. Then the one-click also runs.
>>
>> That seems to be a regression from how it once was, so it should be fixed ASAP.
>
> It was fixed and actually extended to take more source locations into account.
> But somehow FileLocator is not properly initialized and thus the additional locations
> are not properly resolved.
>
>

> Camillo
>
> I read the bug entry and your explanation.
> Now could not we find a solution that is not based on postscript?
> Why? because I'm thinking that soon (or later) we will bootstrap from sources and I would love to have
> as much as behavior inside the initialize so that we do not forget a little message and get the system shaky.
>
> Stef
>
>>> On 09 Nov 2013, at 15:37, Johan Fabry <[hidden email]> wrote:
>>>> For double completeness ;-) The one-click download Pharo3.0-mac.zip has the same problem. The included source file is in the wrong directory. It should be moved out of Contents/Resources and moved into Contents/MacOS. Then the one-click also runs.
>>>
>>> That seems to be a regression from how it once was, so it should be fixed ASAP.
>>
>> It was fixed and actually extended to take more source locations into account.
>> But somehow FileLocator is not properly initialized and thus the additional locations
>> are not properly resolved.

>
> I should reopen the issue since the problem persists.
>
> On 2013-11-10, at 12:37, Stéphane Ducasse <[hidden email]> wrote:
>> Camillo
>>
>> I read the bug entry and your explanation.
>> Now could not we find a solution that is not based on postscript?
>> Why? because I'm thinking that soon (or later) we will bootstrap from sources and I would love to have
>> as much as behavior inside the initialize so that we do not forget a little message and get the system shaky.
>>
>> Stef
>>
>>>> On 09 Nov 2013, at 15:37, Johan Fabry <[hidden email]> wrote:
>>>>> For double completeness ;-) The one-click download Pharo3.0-mac.zip has the same problem. The included source file is in the wrong directory. It should be moved out of Contents/Resources and moved into Contents/MacOS. Then the one-click also runs.
>>>>
>>>> That seems to be a regression from how it once was, so it should be fixed ASAP.
>>>
>>> It was fixed and actually extended to take more source locations into account.
>>> But somehow FileLocator is not properly initialized and thus the additional locations
>>> are not properly resolved.
>
>

>
> On Nov 10, 2013, at 2:05 PM, Camillo Bruni <[hidden email]> wrote:
>
>> It did not solve the issue yet :/, I will have to look into it next week.
>
> Don't ;)
> You should not touch Pharo related things and start use pomodoroes to blast your phd
>
> Stef
>> In any case, I think it would be unrelated to a bootstrap since FileLocator
>> is already lazily initialized. There is just the typical problem on how and
>> when to update a singleton…
> Ok so this is good then.
>
>>
>> I should reopen the issue since the problem persists.

>
> On principle, a big +1 on going forward on the PhD! :-)
>
> But, the one-click download Pharo3.0-mac.zip being broken is an important issue that should be addressed fairly quickly in my opinion. As I said, the sources file should be moved out of Contents/Resources and moved into Contents/MacOS. Then the one-click also runs.
>
> On Nov 10, 2013, at 10:29 AM, Stéphane Ducasse <[hidden email]> wrote:
>
>>
>> On Nov 10, 2013, at 2:05 PM, Camillo Bruni <[hidden email]> wrote:
>>
>>> It did not solve the issue yet :/, I will have to look into it next week.
>>
>> Don't ;)
>> You should not touch Pharo related things and start use pomodoroes to blast your phd
>>
>> Stef
>>> In any case, I think it would be unrelated to a bootstrap since FileLocator
>>> is already lazily initialized. There is just the typical problem on how and
>>> when to update a singleton…
>> Ok so this is good then.
>>
>>>
>>> I should reopen the issue since the problem persists.
>
>
>
> ---> Save our in-boxes! http://emailcharter.org <---
>
> Johan Fabry   -   http://pleiad.cl/~jfabry
> PLEIAD lab  -  Computer Science Department (DCC)  -  University of Chile
>