- Pharo-users - lists.pharo.org

Re: [Pharo-users] I probably messed up with .changes...

by Thierry Goubier

2015-07-06 14:39 GMT+02:00 Matthieu Lacaton <matthieu.lacaton(a)gmail.com>: > What image version did you use? > > > I used number 50074 > > > Maybe you can iterator over all methods decompile, and save as new code? >> Maybe you can open the image without the changes file and try to create a >> package or file out the package? >> > > I manually looked inside many of my .changes with Notepad++ and I couldn't > find any of the related methods. > If I open the image without the changes file I can't export anything. > > By the way, when I try the "Recover lost changes" from inside the image I > cannot go back very far. I have a big .changes with about 200 snapshots but > I can only go back to the last ~~ 20s or so. Is it normal ? It's the first > time I use the .changes file so I don't really know how it works. > There is a hard-coded limit in the recover last changes. Last time I had to help someone do a difficult recovery, I had to change that limit in a method somewhere... don't remember which one. Don't trust the changes anyway. It's bound to be replaced. The strategy I suggest is: - Use Monticello and makes frequent saves of your packages - Practice rebuilding your image: write a script or a makefile which loads everything and set your settings. -> Better still: include both your build script and your packages inside the same repository so that they can be versionned together. Git works very well this way, and you can use filetree or GitFileTree for that. > > No, not your fault, this should not happen. The changes file is for >> "recover if you messed up the image". If the changes file gets corrupted, >> then this is a serious bug. >> > > Well I really don't know :s The only thing I can tell is that I have an > image with some totally broken "written" methods but their execution works > just fine. The "normal" source code of these methods apparently is nowhere > to be found. However, inside the .changes some more recent methods are > correctly registered so the problem probably happened only once with a > bunch of methods I wrote at a given time (actually broken methods are not > methods I wrote entirely but methods I changed). > Looks like a set of shifted source pointers. If you dare, what you could do is regenerate the source for all those methods by decompilation and recompiling them. You would get all thoses t2, t3 etc... but you would be then able to redocument them at your rythm (and get Nautilus working again). > > I did some testings and I found a way to reproduce what I experienced : > If you manually rename an image without renaming the .changes you cannot > browse the code inside Nautilus without getting errors. However, you can > use the finder just fine to find any method. These methods are decompiled > methods (with variable names in t1 t2 etc.) but you can modify them without > getting errors. Then you can save your image and it works fine. > Now if you rename the image to the name it had in the first place you can > use it properly but the method you modified in between will be broken at > some point. > > But to be honest, even if it kinds of reproduce my problem I am not sure > this is what i did. Maybe I manually renamed the image, that's definitely > possible, but i don't remember re-renaming it to its prior name. Moreover, > when doing so you end up with a new .changes file which is very small and > has the source code of the methods you modified and I don't have any small > .changes file. > > I am still quite unsure at this point. > If you find any way to confirm what you did, please share. Maybe there is a bug somewhere and, given the consequences, we need to correct it. Thierry

July 6, 2015

Re: [Pharo-users] I probably messed up with .changes...

by Matthieu Lacaton

> > What image version did you use? I used number 50074 Maybe you can iterator over all methods decompile, and save as new code? > Maybe you can open the image without the changes file and try to create a > package or file out the package? > I manually looked inside many of my .changes with Notepad++ and I couldn't find any of the related methods. If I open the image without the changes file I can't export anything. By the way, when I try the "Recover lost changes" from inside the image I cannot go back very far. I have a big .changes with about 200 snapshots but I can only go back to the last ~~ 20s or so. Is it normal ? It's the first time I use the .changes file so I don't really know how it works. No, not your fault, this should not happen. The changes file is for > "recover if you messed up the image". If the changes file gets corrupted, > then this is a serious bug. > Well I really don't know :s The only thing I can tell is that I have an image with some totally broken "written" methods but their execution works just fine. The "normal" source code of these methods apparently is nowhere to be found. However, inside the .changes some more recent methods are correctly registered so the problem probably happened only once with a bunch of methods I wrote at a given time (actually broken methods are not methods I wrote entirely but methods I changed). I did some testings and I found a way to reproduce what I experienced : If you manually rename an image without renaming the .changes you cannot browse the code inside Nautilus without getting errors. However, you can use the finder just fine to find any method. These methods are decompiled methods (with variable names in t1 t2 etc.) but you can modify them without getting errors. Then you can save your image and it works fine. Now if you rename the image to the name it had in the first place you can use it properly but the method you modified in between will be broken at some point. But to be honest, even if it kinds of reproduce my problem I am not sure this is what i did. Maybe I manually renamed the image, that's definitely possible, but i don't remember re-renaming it to its prior name. Moreover, when doing so you end up with a new .changes file which is very small and has the source code of the methods you modified and I don't have any small .changes file. I am still quite unsure at this point. 2015-07-06 10:36 GMT+02:00 Nicolai Hess <nicolaihess(a)web.de>: > > > 2015-07-06 9:55 GMT+02:00 Matthieu Lacaton <matthieu.lacaton(a)gmail.com>: > >> Hello, >> >> I would just like to report something that happened to me today. >> >> As I was working on a project, I tried inserting an instance variable to >> one of my classes. >> Starting from this moment something became very weird. First, some >> subclasses were not listed as subclasses anymore, then I realised during >> the execution that allocating my new instance variable was actually >> modifying another instance variable. >> >> I tried digging up a bit and I found out that many of my methods were a >> complete mess. >> When browsing with Nautilus the title of the method was for example: >> "addProperty:key:". However the corpse of the method was totally random >> with something like that for example: >> "ient; >> width: 1. >> graphic strokeStyle: _strokeStyle" >> >> So, reportedly, the name of the method was "ient;" ... >> >> Basically I had many methods where the source code was just random chunks >> of other methods. >> >> The funnier thing is that everything worked perfectly fine during >> execution. >> >> I tried to look at different backup images I had to see when everything >> began to go wrong and I realised I had been working with broken source code >> for about a week. >> > > What image version did you use? > > > >> >> So if I understand correctly, I probably messed up with the .changes file >> (I don't remembr how but maybe I copied the .image without the .changes or >> renamed the .image or i don't know). >> And now the compiled code is okay but the source code is lost so >> everything is working fine until the system tries to recompile everything ? >> >> Now my question is : is there a way to fix the issue ? I tried exporting >> the package to a .mcz but I had bugs everywhere. I imported the old working >> package to an .mcz and tried browsing the differences with the broken one >> just to manually get back eveything I changed during this week. But I >> couldn't cause there were bugs everytime I tried to browse the changes. >> Basically, are all my changes definitely lost or is there a way to get it >> back somehow (at least the raw source code) ? >> > > Maybe you can iterator over all methods decompile, and save as new code? > Maybe you can open the image without the changes file and try to create a > package or file out the package? > > >> >> I know that I fucked up and this is my fault but it would have been nice >> if something (anything) told me earlier that I did something wrong. I've >> been adding / modifying lots of methods and even executing the program for >> a week now and absolutely nothing told me that something was wrong until I >> tried adding an instance variable. >> > > No, not your fault, this should not happen. The changes file is for > "recover if you messed up the image". If the changes file gets corrupted, > then this is a serious bug. > > >> >> I am in a situation where I actually wrote and "saved" code and now it >> seems lost... that's frustrating :( >> >> Thanks, >> >> Matthieu >> > >

July 6, 2015

Re: [Pharo-users] Clearing objects from .changes

by Peter UhnÃ¡k

Excellent! Now I have successfully lowered the build size from 38MB to just 13MB. :) Thanks, Peter On Mon, Jul 6, 2015 at 11:10 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > What you (probably) want is called 'condensing the changes'. > Have a look at the class PharoChangesCondenser. > > << I create a new more compact changes files with a single version of each > method in the image. >> > > > On 06 Jul 2015, at 11:08, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > > > Is it possible to remove all references to a class after it has been > removed everywhere? > > > > For example I can delete all classes of package > 'Roassal2-Builder-Grapher' > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > pkg := RPackageOrganizer default packageNamed: 'Roassal2'. > > grapherTag := pkg classTags detect: [ :each | each name = > #'Builder-Grapher' ]. > > grapherTag classes do: [ :each | removeClass value: each ]. > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > > However this leaves the .changes file intact, even after I do "Smalltalk > cleanUp: true". > > > > The reason why I am doing this is to lower the size of .changes/.images > files which are massive just after loading my project... so it takes a lot > of space for testing... > > > > Thanks, > > Peter > > >

July 6, 2015

Re: [Pharo-users] Clearing objects from .changes

by Sven Van Caekenberghe

What you (probably) want is called 'condensing the changes'. Have a look at the class PharoChangesCondenser. << I create a new more compact changes files with a single version of each method in the image. >> > On 06 Jul 2015, at 11:08, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > Is it possible to remove all references to a class after it has been removed everywhere? > > For example I can delete all classes of package 'Roassal2-Builder-Grapher' > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > pkg := RPackageOrganizer default packageNamed: 'Roassal2'. > grapherTag := pkg classTags detect: [ :each | each name = #'Builder-Grapher' ]. > grapherTag classes do: [ :each | removeClass value: each ]. > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > However this leaves the .changes file intact, even after I do "Smalltalk cleanUp: true". > > The reason why I am doing this is to lower the size of .changes/.images files which are massive just after loading my project... so it takes a lot of space for testing... > > Thanks, > Peter

July 6, 2015

Clearing objects from .changes

by Peter UhnÃ¡k

Is it possible to remove all references to a class after it has been removed everywhere? For example I can delete all classes of package 'Roassal2-Builder-Grapher' ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ pkg := RPackageOrganizer default packageNamed: 'Roassal2'. grapherTag := pkg classTags detect: [ :each | each name = #'Builder-Grapher' ]. grapherTag classes do: [ :each | removeClass value: each ]. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ However this leaves the .changes file intact, even after I do "Smalltalk cleanUp: true". The reason why I am doing this is to lower the size of .changes/.images files which are massive just after loading my project... so it takes a lot of space for testing... Thanks, Peter

July 6, 2015

Re: [Pharo-users] I probably messed up with .changes...

by Nicolai Hess

2015-07-06 9:55 GMT+02:00 Matthieu Lacaton <matthieu.lacaton(a)gmail.com>: > Hello, > > I would just like to report something that happened to me today. > > As I was working on a project, I tried inserting an instance variable to > one of my classes. > Starting from this moment something became very weird. First, some > subclasses were not listed as subclasses anymore, then I realised during > the execution that allocating my new instance variable was actually > modifying another instance variable. > > I tried digging up a bit and I found out that many of my methods were a > complete mess. > When browsing with Nautilus the title of the method was for example: > "addProperty:key:". However the corpse of the method was totally random > with something like that for example: > "ient; > width: 1. > graphic strokeStyle: _strokeStyle" > > So, reportedly, the name of the method was "ient;" ... > > Basically I had many methods where the source code was just random chunks > of other methods. > > The funnier thing is that everything worked perfectly fine during > execution. > > I tried to look at different backup images I had to see when everything > began to go wrong and I realised I had been working with broken source code > for about a week. > What image version did you use? > > So if I understand correctly, I probably messed up with the .changes file > (I don't remembr how but maybe I copied the .image without the .changes or > renamed the .image or i don't know). > And now the compiled code is okay but the source code is lost so > everything is working fine until the system tries to recompile everything ? > > Now my question is : is there a way to fix the issue ? I tried exporting > the package to a .mcz but I had bugs everywhere. I imported the old working > package to an .mcz and tried browsing the differences with the broken one > just to manually get back eveything I changed during this week. But I > couldn't cause there were bugs everytime I tried to browse the changes. > Basically, are all my changes definitely lost or is there a way to get it > back somehow (at least the raw source code) ? > Maybe you can iterator over all methods decompile, and save as new code? Maybe you can open the image without the changes file and try to create a package or file out the package? > > I know that I fucked up and this is my fault but it would have been nice > if something (anything) told me earlier that I did something wrong. I've > been adding / modifying lots of methods and even executing the program for > a week now and absolutely nothing told me that something was wrong until I > tried adding an instance variable. > No, not your fault, this should not happen. The changes file is for "recover if you messed up the image". If the changes file gets corrupted, then this is a serious bug. > > I am in a situation where I actually wrote and "saved" code and now it > seems lost... that's frustrating :( > > Thanks, > > Matthieu >

July 6, 2015

I probably messed up with .changes...

by Matthieu Lacaton

Hello, I would just like to report something that happened to me today. As I was working on a project, I tried inserting an instance variable to one of my classes. Starting from this moment something became very weird. First, some subclasses were not listed as subclasses anymore, then I realised during the execution that allocating my new instance variable was actually modifying another instance variable. I tried digging up a bit and I found out that many of my methods were a complete mess. When browsing with Nautilus the title of the method was for example: "addProperty:key:". However the corpse of the method was totally random with something like that for example: "ient; width: 1. graphic strokeStyle: _strokeStyle" So, reportedly, the name of the method was "ient;" ... Basically I had many methods where the source code was just random chunks of other methods. The funnier thing is that everything worked perfectly fine during execution. I tried to look at different backup images I had to see when everything began to go wrong and I realised I had been working with broken source code for about a week. So if I understand correctly, I probably messed up with the .changes file (I don't remembr how but maybe I copied the .image without the .changes or renamed the .image or i don't know). And now the compiled code is okay but the source code is lost so everything is working fine until the system tries to recompile everything ? Now my question is : is there a way to fix the issue ? I tried exporting the package to a .mcz but I had bugs everywhere. I imported the old working package to an .mcz and tried browsing the differences with the broken one just to manually get back eveything I changed during this week. But I couldn't cause there were bugs everytime I tried to browse the changes. Basically, are all my changes definitely lost or is there a way to get it back somehow (at least the raw source code) ? I know that I fucked up and this is my fault but it would have been nice if something (anything) told me earlier that I did something wrong. I've been adding / modifying lots of methods and even executing the program for a week now and absolutely nothing told me that something was wrong until I tried adding an instance variable. I am in a situation where I actually wrote and "saved" code and now it seems lost... that's frustrating :( Thanks, Matthieu

July 6, 2015

Re: [Pharo-users] Athens and radial gradient

by Nicolai Hess

2015-06-18 14:49 GMT+02:00 Matthieu Lacaton <matthieu.lacaton(a)gmail.com>: > Hello, > > I wanted to use Athens API to define a radial gradient and I saw that the > class RadialGradientPaint only had one radius as instance variable and it > seemed to me it was passed as the end radius while the start radius was set > to 0. > Does it mean that if I want to define a start radius different from 0 I > need to call the backend directly ? > Well, that is the Athens API, it may happen of course, that a one backend (for example - AthensCairo) could supports more arguments. Maybe the API was choosen that way, because this is the API that can be implemented by Balloon and Cairo. (of course, this isn't really important because all users of this library explicit work with the AthensCairoSurface the backend, and to me, it looks no one cares). > > Thanks, > > Matthieu >

July 5, 2015

Re: [Pharo-users] Kivy

by Alain Plantec

> I'm not sure that we need a DSL. Iâm not sure that we donât need a DSL :) Spec is a kind of dsl and the idea is cool. >> This is a point that particularly interests me, especially regarding >> declarative syntax. >> Yes, but unfortunately not in 3 month (for my part)... > > Not for Brick too :) give one full year to Aliaksel together with Glenn :) > >> >> Regards, >> Glenn. >> >> >> >> >> ----- >> Glenn CavarlÃ© >> -- >> View this message in context: http://forum.world.st/Kivy-tp4835739p4835775.html >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >> >> > >

July 5, 2015

Re: [Pharo-users] Situation - Raspberry PI and Pharo + Squeak

by Attila Magyar

Hi Marten, Currently I'm using this this vm from here http://www.mirandabanda.org/files/Cog/VM/VM.r3395/cogspurlinuxhtARM-15.26.3… with the latest Pharo 5 spur image from here http://files.pharo.org/image/50/latest-spur32.zip As far as I know, spur is a new memory manager but I'm not familiar with the details. There is also a stack vm that works with ordinary images, but it lacks JIT compilation therefore a lot slower than cog. Attila -- View this message in context: http://forum.world.st/Situation-Raspberry-PI-and-Pharo-Squeak-tp4835873p483… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

July 5, 2015