Smalltalk › Pharo › Pharo Smalltalk Developers

cannot write to the changes file

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

10 messages Options

Ben Coman

cannot write to the changes file

Before creating an Issue, can someone confirm the following behaviour on Windows 10 ?

Downloaded and unzipped into the same folder...

* http://files.pharo.org/image/70/Pharo-7.0.0-alpha.build.425.sha.eb0a6fb.arch.32bit.zip

* http://files.pharo.org/vm/pharo-spur32/win/pharo-win-i386-201711262336-8879e2e.zip

The directory contains...

Pharo7.0-32bit-eb0a6fb.image

Pharo7.0-32bit-eb0a6fb.changes

Pharo.exe

Double-clicking Pharo.exe produces notification...

Information

Pharo cannot write to the changes file named

C:\Users\....\pharo\Pharo7.0-32bit-eb0a6fb.changes.

Please check that you have write permission for this file.

You won't be able to save this image correctly until you fix this.

However if I edit to AST-Tests-Core > NumberParserTest >> testFail

to add "My Comment"

then close all windows, Save&Quit the Image,

restart Pharo by double-clicking on Pharo.exe,

and open System Browser on testFail

I can see my comment.

I'm not clear on exactly how it works but I presume that restarting the

Image would require "My Comment" to be read from the changes file,

but notepad shows its not in the changes file.

So perhaps the error notification is part of a transition in-Image sources and

nothing to worry about?

cheers -ben

alistairgrant

Re: cannot write to the changes file

Hi Ben,

I've seen this (on Windows 10), 32 bit.

It wasn't happening last time I used Win10, some time in the last 4 months.

Cheers,

Alistair

(From my phone)

On 13 Jan. 2018 05:44, "Ben Coman" <[hidden email]> wrote:

Before creating an Issue, can someone confirm the following behaviour on Windows 10 ?
Downloaded and unzipped into the same folder...
* http://files.pharo.org/image/70/Pharo-7.0.0-alpha.build.425.sha.eb0a6fb.arch.32bit.zip
* http://files.pharo.org/vm/pharo-spur32/win/pharo-win-i386-201711262336-8879e2e.zip

The directory contains...
Pharo7.0-32bit-eb0a6fb.image
Pharo7.0-32bit-eb0a6fb.changes
Pharo.exe

Double-clicking Pharo.exe produces notification...
Information
Pharo cannot write to the changes file named
C:\Users\....\pharo\Pharo7.0-32bit-eb0a6fb.changes.
Please check that you have write permission for this file.
You won't be able to save this image correctly until you fix this.

However if I edit to AST-Tests-Core > NumberParserTest >> testFail
to add "My Comment"
then close all windows, Save&Quit the Image,
restart Pharo by double-clicking on Pharo.exe,
and open System Browser on testFail
I can see my comment.

I'm not clear on exactly how it works but I presume that restarting the
Image would require "My Comment" to be read from the changes file,
but notepad shows its not in the changes file.
So perhaps the error notification is part of a transition in-Image sources and
nothing to worry about?

cheers -ben

Ben Coman

Re: cannot write to the changes file

In reply to this post by Ben Coman

On 13 January 2018 at 12:43, Ben Coman <[hidden email]> wrote:

Before creating an Issue, can someone confirm the following behaviour on Windows 10 ?
Downloaded and unzipped into the same folder...
* http://files.pharo.org/image/70/Pharo-7.0.0-alpha.build.425.sha.eb0a6fb.arch.32bit.zip
* http://files.pharo.org/vm/pharo-spur32/win/pharo-win-i386-201711262336-8879e2e.zip

The directory contains...
Pharo7.0-32bit-eb0a6fb.image
Pharo7.0-32bit-eb0a6fb.changes
Pharo.exe

Double-clicking Pharo.exe produces notification...
Information
Pharo cannot write to the changes file named
C:\Users\....\pharo\Pharo7.0-32bit-eb0a6fb.changes.
Please check that you have write permission for this file.
You won't be able to save this image correctly until you fix this.

and btw, with notepad I can edit and and save the file no problem.

cheers -ben

However if I edit to AST-Tests-Core > NumberParserTest >> testFail
to add "My Comment"
then close all windows, Save&Quit the Image,
restart Pharo by double-clicking on Pharo.exe,
and open System Browser on testFail
I can see my comment.

I'm not clear on exactly how it works but I presume that restarting the
Image would require "My Comment" to be read from the changes file,
but notepad shows its not in the changes file.
So perhaps the error notification is part of a transition in-Image sources and
nothing to worry about?

cheers -ben

alistairgrant

Re: cannot write to the changes file

On 13 January 2018 at 08:35, Ben Coman <[hidden email]> wrote:

>
>
> On 13 January 2018 at 12:43, Ben Coman <[hidden email]> wrote:
>>
>> Before creating an Issue, can someone confirm the following behaviour on
>> Windows 10 ?
>> Downloaded and unzipped into the same folder...
>> *
>> http://files.pharo.org/image/70/Pharo-7.0.0-alpha.build.425.sha.eb0a6fb.arch.32bit.zip
>> *
>> http://files.pharo.org/vm/pharo-spur32/win/pharo-win-i386-201711262336-8879e2e.zip
>>
>> The directory contains...
>> Pharo7.0-32bit-eb0a6fb.image
>> Pharo7.0-32bit-eb0a6fb.changes
>> Pharo.exe
>>
>> Double-clicking Pharo.exe produces notification...
>> Information
>> Pharo cannot write to the changes file named
>> C:\Users\....\pharo\Pharo7.0-32bit-eb0a6fb.changes.
>> Please check that you have write permission for this file.
>> You won't be able to save this image correctly until you fix this.
>
>
> and btw, with notepad I can edit and and save the file no problem.
> cheers -ben

If I open a playground (after getting the "cannot write" error above)
and execute:

SourceFiles close; ensureOpen

The changes file is successfully opened and written to.

Cheers,
Alistair

CyrilFerlicot

Re: cannot write to the changes file

In reply to this post by Ben Coman

Le 13/01/2018 à 05:43, Ben Coman a écrit :

> Before creating an Issue, can someone confirm the following behaviour on
> Windows 10 ?
> Downloaded and unzipped into the same folder...
> * http://files.pharo.org/image/70/Pharo-7.0.0-alpha.build.425.sha.eb0a6fb.arch.32bit.zip
> * http://files.pharo.org/vm/pharo-spur32/win/pharo-win-i386-201711262336-8879e2e.zip
>
> The directory contains...
> Pharo7.0-32bit-eb0a6fb.image
> Pharo7.0-32bit-eb0a6fb.changes
> Pharo.exe
>
> Double-clicking Pharo.exe produces notification...
> Information
> Pharo cannot write to the changes file named
> C:\Users\....\pharo\Pharo7.0-32bit-eb0a6fb.changes.
> Please check that you have write permission for this file.
> You won't be able to save this image correctly until you fix this.
>
> However if I edit to AST-Tests-Core > NumberParserTest >> testFail
> to add "My Comment"
> then close all windows, Save&Quit the Image,
> restart Pharo by double-clicking on Pharo.exe,
> and open System Browser on testFail
> I can see my comment.
>
> I'm not clear on exactly how it works but I presume that restarting the
> Image would require "My Comment" to be read from the changes file,
> but notepad shows its not in the changes file.
> So perhaps the error notification is part of a transition in-Image
> sources and
> nothing to worry about?
>
> cheers -ben

Hi,

For my part it inform that the source file cannot be written at launch
but in the end it is written.

This problem comes from a refactoring in the location system I think.

--
Cyril Ferlicot
https://ferlicot.fr

http://www.synectique.eu
2 rue Jacques Prévert 01,
59650 Villeneuve d'ascq France

signature.asc (836 bytes) Download Attachment

CyrilFerlicot

Re: cannot write to the changes file

Le 13/01/2018 à 12:36, Cyril Ferlicot D. a écrit :
>
> Hi,
>
> For my part it inform that the source file cannot be written at launch
> but in the end it is written.
>
> This problem comes from a refactoring in the location system I think.
>

Pavel located the problem with the merge of this PR: :
https://github.com/pharo-project/pharo/pull/553

--
Cyril Ferlicot
https://ferlicot.fr

http://www.synectique.eu
2 rue Jacques Prévert 01,
59650 Villeneuve d'ascq France

signature.asc (836 bytes) Download Attachment

Stephane Ducasse-3

Re: cannot write to the changes file

Excellent!
Tx pavel.

On Sat, Jan 13, 2018 at 12:37 PM, Cyril Ferlicot D.
<[hidden email]> wrote:

> Le 13/01/2018 à 12:36, Cyril Ferlicot D. a écrit :
>>
>> Hi,
>>
>> For my part it inform that the source file cannot be written at launch
>> but in the end it is written.
>>
>> This problem comes from a refactoring in the location system I think.
>>
>
> Pavel located the problem with the merge of this PR: :
> https://github.com/pharo-project/pharo/pull/553
>
> --
> Cyril Ferlicot
> https://ferlicot.fr
>
> http://www.synectique.eu
> 2 rue Jacques Prévert 01,
> 59650 Villeneuve d'ascq France
>

Ben Coman

Re: cannot write to the changes file

In reply to this post by CyrilFerlicot

On 13 January 2018 at 19:37, Cyril Ferlicot D. <[hidden email]> wrote:

Great! That was quick work (thanks Pavel.)
Do you have an issue for me to follow, or should I create it?

cheers -ben

CyrilFerlicot

Re: cannot write to the changes file

Le 13/01/2018 à 18:03, Ben Coman a écrit :
>
> Great! That was quick work (thanks Pavel.)
> Do you have an issue for me to follow, or should I create it?
>
> cheers -ben
>

It seems that the problem was corrected today (probably the change in
File usage).

Can someone else confirm?

--
Cyril Ferlicot
https://ferlicot.fr

signature.asc (836 bytes) Download Attachment

Guillermo Polito

Re: cannot write to the changes file

Yes, the changes files were being opened twice, and the second time it failed :).

On Tue, Mar 13, 2018 at 11:11 PM, Cyril Ferlicot D. <[hidden email]> wrote:

Le 13/01/2018 à 18:03, Ben Coman a écrit :
>
> Great! That was quick work (thanks Pavel.)
> Do you have an issue for me to follow, or should I create it?
>
> cheers -ben
>

It seems that the problem was corrected today (probably the change in
File usage).

Can someone else confirm?

--
Cyril Ferlicot
https://ferlicot.fr

Guille Polito

Research Engineer

Centre de Recherche en Informatique, Signal et Automatique de Lille

CRIStAL - UMR 9189

French National Center for Scientific Research - http://www.cnrs.fr

Web: http://guillep.github.io

Phone: +33 06 52 70 66 13