June 2017 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Windows 10 crash - LoadLibrary(SurfacePlugin.dll) (998: Invalid access to memory location.

by Eliot Miranda

Hi Andrei, On Tue, Jun 27, 2017 at 7:43 AM, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > Hi, > > On Windows 10 with the Pharo 6 release and the latest vm [1] I get the > following crash when attempting to save the image after doing some more > intensive computations: > > ------------------------------------------------------------ > ------------------------------ > # Debug console > # To close: F2 -> 'debug options' -> 'show output console' > # To disable: F2 -> 'debug options' -> 'show console on errors' > LoadLibrary(SurfacePlugin) (998: Invalid access to memory location. > > ) > LoadLibrary(SurfacePlugin.dll) (998: Invalid access to memory location. > > ) > LoadLibrary(c:\pharo6\SurfacePlugin) (998: Invalid access to memory > location. > > ) > LoadLibrary(c:\pharo6\SurfacePlugin.dll) (998: Invalid access to memory > location. > > ) > LoadLibrary(SurfacePlugin) (998: Invalid access to memory location. > > ) > LoadLibrary(SurfacePlugin.dll) (998: Invalid access to memory location. > > ) > LoadLibrary(c:\pharo6\SurfacePlugin) (998: Invalid access to memory > location. > > ) > LoadLibrary(c:\pharo6\SurfacePlugin.dll) (998: Invalid access to memory > location. > > ) > LoadLibrary(SurfacePlugin) (998: Invalid access to memory location. > > ) > LoadLibrary(SurfacePlugin.dll) (998: Invalid access to memory location. > > ) > LoadLibrary(c:\pharo6\SurfacePlugin) (998: Invalid access to memory > location. > > ) > LoadLibrary(c:\pharo6\SurfacePlugin.dll) (998: Invalid access to memory > location. > > ) > ------------------------------------------------------------ > ------------------------------ > > The image take around 600MB before the crash but that is expected. > I've seen that this error was appearing before in the past. > Any suggestions of how to debug it? > Build a console VM (you should see PharoConsoleUnstripped.exe in build/vm, buildast/vm & builddbg/vm) and run under gdb from a console window. Make sure the Pharo window doesn't obscure the console window so you can notice when a crash happens. You'll then be able to get a backtrace, see where the illegal access is, what the system is trying to do, etc. If you're lost in gdb, when you get the crash Skype me and we can try and look at it together. Cheers, > Andrei > > [1] http://files.pharo.org/vm/pharo-spur32/win/pharo-win- > i386-201706211817-f54456f.zip > _,,,^..^,,,_ best, Eliot

June 27, 2017

Re: [Pharo-dev] FileReference>>/ and path canonicalisation

by K K Subbu

On Monday 26 June 2017 01:42 PM, Alistair Grant wrote: > 1. Path's are canonicalised during initial creation, but are not when > extending the path, i.e. sending #/ > > E.g. > > '/dev/shm/d1/d2/../t1.txt' asFileReference " File @ /dev/shm/d1/t1.txt" > > '/dev/shm/d1/' asFileReference / 'd2/../t1.txt' " File @ /dev/shm/d1/d2/../t1.txt" > > Automatic canonicalisation is problematic as the code doesn't handle > symbolic links in the path name: > > ('/dev/shm/d1/' asFileReference / 's3/../t2.txt') exists " true (correct answer)" > > '/dev/shm/d1/s3/../t2.txt' asFileReference exists " false (wrong answer)" The meaning of 's3/..' is ambiguous when s3 is a symlink. Should 's3' be resolved or not before #parent op is applied? Disambiguation depends on context, so early canonicalization is a bug. My own preference is to not to canonicalize at all and 's3/..' should be left as {s3, ..}. See http://man7.org/linux/man-pages/man7/path_resolution.7.html > 2. In an attempt to be completely general, the argument to #/ is assumed > to be a single directory / file. This is incorrect as the path > delimiter is not allowed to be part of the file name. The result is > that path comparisons and operations such as #parent give unexpected > results. Path class>>from:delimiter has a bug. It attempts to canonicalize elements parsed from the String regardless of the context. If the code is changed to: pathClass withAll: (aDelimiterCharacter split: aString) your test will pass. I wonder why Path was subclassed from Object and not from SequenceableCollection? > My PR modified FileSystem so that: > > 1. Canonicalisation is separated out as an operation that has to be > manually requested: > > '/dev/shm/d1/d2/../t1.txt' asFileReference " File @ /dev/shm/d1/d2/../t1.txt" > > '/dev/shm/d1/d2/../t1.txt' asFileReference canonicalize " File @ /dev/shm/d1/t1.txt" I am ok with this. > 2. The argument to #/ can be either a single file / directory name or a > path. > > ('/dev/shm/d1/' asFileReference / 'd2/d3/t3.txt') parent " File @ /dev/shm/d1/d2/d3" ok with this too. > 3. Adds unit tests to cover the changed behaviour. >... > Before I submit the patch, does anyone have any strong objections to the > changes as described above? None from my side. Regards .. Subbu

June 27, 2017

Re: [Pharo-dev] [ANN] P3, a modern, lean and mean PostgreSQL client for Pharo

by Michael Forster

On Tue, Jun 27, 2017 at 7:56 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > P3 is a modern, lean and mean PostgreSQL client for Pharo. > > P3Client uses frontend/backend protocol 3.0 (PostgreSQL version 7.4 [2003] and later), implementing the simple query cycle. It supports plaintext and md5 password authentication as well as SSL connections. When SQL queries return row data, incoming data is efficiently converted to objects. P3Client supports most common PostgreSQL types. > > With P3DatabaseDriver, an interface between Glorp, an advanced object-relational mapper, and P3Client, most Glorp unit tests pass (the same number as the older, proven PostgresV2 driver, that is using the legacy 2.0 protocol). This was the initial design goal. > > More info, usage examples and code at https://github.com/svenvc/P3 > > P3 is written in pure Pharo, using a TCP network connection to PostgreSQL. > > This is an alpha release for the brave of heart that needs more real world testing before it is ready for general release. > > Sven > > PS: I wrote this using 64-bit Pharo 6 on macOS using the Calypso browser and it was a beautiful & satisfying experience. Thank you Denis, well done ! I also used Iceberg a second time and it starts to feel natural to me. Thank you Nico and Esteban ! > > Very nice, Sven. Common Lisp's loss was Pharo's gain ;-) Mike

June 27, 2017

Windows 10 crash - LoadLibrary(SurfacePlugin.dll) (998: Invalid access to memory location.

by Andrei Chis

Hi, On Windows 10 with the Pharo 6 release and the latest vm [1] I get the following crash when attempting to save the image after doing some more intensive computations: ------------------------------------------------------------------------------------------ # Debug console # To close: F2 -> 'debug options' -> 'show output console' # To disable: F2 -> 'debug options' -> 'show console on errors' LoadLibrary(SurfacePlugin) (998: Invalid access to memory location. ) LoadLibrary(SurfacePlugin.dll) (998: Invalid access to memory location. ) LoadLibrary(c:\pharo6\SurfacePlugin) (998: Invalid access to memory location. ) LoadLibrary(c:\pharo6\SurfacePlugin.dll) (998: Invalid access to memory location. ) LoadLibrary(SurfacePlugin) (998: Invalid access to memory location. ) LoadLibrary(SurfacePlugin.dll) (998: Invalid access to memory location. ) LoadLibrary(c:\pharo6\SurfacePlugin) (998: Invalid access to memory location. ) LoadLibrary(c:\pharo6\SurfacePlugin.dll) (998: Invalid access to memory location. ) LoadLibrary(SurfacePlugin) (998: Invalid access to memory location. ) LoadLibrary(SurfacePlugin.dll) (998: Invalid access to memory location. ) LoadLibrary(c:\pharo6\SurfacePlugin) (998: Invalid access to memory location. ) LoadLibrary(c:\pharo6\SurfacePlugin.dll) (998: Invalid access to memory location. ) ------------------------------------------------------------------------------------------ The image take around 600MB before the crash but that is expected. I've seen that this error was appearing before in the past. Any suggestions of how to debug it? Cheers, Andrei [1] http://files.pharo.org/vm/pharo-spur32/win/pharo-win-i386-201706211817-f544…

June 27, 2017

Re: [Pharo-dev] Pharo 7 provisional HOWTO

by Pavel Krivanek

2017-06-27 16:17 GMT+02:00 Serge Stinckwich <serge.stinckwich(a)gmail.com>: > On Tue, Jun 27, 2017 at 3:10 PM, Pavel Krivanek > <pavel.krivanek(a)gmail.com> wrote: > > > > > > 2017-06-27 15:57 GMT+02:00 Serge Stinckwich <serge.stinckwich(a)gmail.com > >: > >> > >> On Mon, Jun 26, 2017 at 12:14 PM, Pavel Krivanek > >> <pavel.krivanek(a)gmail.com> wrote: > >> > Hi, > >> > > >> > this mail describes how to start to send pull requests to Pharo 7 > Github > >> > repository from Pharo 7. > >> > >> Thank you for the great explanation Pavel. > >> > >> > Preparations > >> > ===================== > >> > > >> > - you need to have a Github account and set SSH keys. See > >> > https://help.github.com/articles/connecting-to-github-with-ssh/ > >> > - create own pharo-project/pharo repository fork. Go to > >> > https://github.com/pharo-project/pharo, click on "Fork" button and > >> > follow > >> > the instructions > >> > >> [ ... ] > >> > >> > Issue processing > >> > ===================== > >> > > >> > - create new case on FogBugz to get the issue number > >> > - open Iceberg and from the context menu on the 'pharo' repository do: > >> > Pharo > >> > - Create new branch from FogBugz issue, enter the issue ID and it will > >> > fill > >> > the full branch name for you > >> > - create your changes (you can do it before the creation of the branch > >> > too) > >> > - commit and push your changes in Iceberg, this way you will commit > your > >> > branch to your fork repository. Remember that the Iceberg commit > window > >> > has > >> > two buttons, one for local commit, the second for commit with > immediate > >> > push. They can be very long because they contain the full branch > (issue) > >> > name > >> > - in Iceberg in the 'pharo' repository context menu do: Pharo - Create > >> > pull > >> > request, fill your > >> > - fill your Github credentials > >> > - leave the PR title, comment is not required, check the pull request > >> > head > >> > and base. The base MUST be pharo-project/pharo development. Create the > >> > pull > >> > requests > >> > - go to https://github.com/pharo-project/pharo/pulls, check your pull > >> > requests and put URL of it into the issue record on FogBugz (as a > >> > comment). > >> > Resolve the issue as Fix review needed > >> > >> It means, there is no PR without a corresponding FogBugz issue ? > > > > > > Yes, at least for code changes we would like to keep this relation. If > it is > > a really trivial change in readme or something like that, we can accept > no > > related issue record. > > Please prefer to comment the issues instead of PRs directly to have all > > information at one place. > > Thank you Pavel for the explanation. > > Maybe in the future, it will make sense to put everything in the PR > and use github issues. > You will use CI travis builds for all PR ? > For now we will use FogBugz because it has a lot of nice features and good API. Maybe we will switch it in future but now we should not change too many things at once :-) For several reasons we now prefer to use own infrastructure for checking of PRs (mainly because of MacOS issues on Travis). But again, it can be changed in future. Cheers, -- Pavel Regards, > -- > Serge Stinckwich > UCN & UMI UMMISCO 209 (IRD/UPMC) > Every DSL ends up being Smalltalk > http://www.doesnotunderstand.org/ > >

June 27, 2017

Re: [Pharo-dev] Epicea feedback

by Martin Dias

Hello Jan, thanks for your feedback. I will have a look asap. Feel free to report it in fogbugz. MartÃn On Tue, Jun 27, 2017 at 8:26 AM, Jan BlizniÄenko <bliznjan(a)fit.cvut.cz> wrote: > Hello > > I'd like to thank you for creating the Epicea. It is way more user-friendly > and dependable than previous change-handling tool. Browsing, applying and > reverting changes is way easier. > > Just one note: > It is not exactly clear from first look how to properly reapply changes > after an image has been closed without saving. If I select all changes I > want to apply without using any filter, those changes are reapplied in > wrong > order (if I changed a method two times, first the new version is applied > and > then the old one). As far as I understood, I have to use filter to show > only > latest changes, but I think it could be clearer in the UI that I need to do > so (or something completely different?) for applying changes. > > Thank you > Jan > > > > -- > View this message in context: http://forum.world.st/Epicea- > feedback-tp4952661.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

June 27, 2017

Re: [Pharo-dev] Pharo 7 provisional HOWTO

by Serge Stinckwich

On Tue, Jun 27, 2017 at 3:10 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > > 2017-06-27 15:57 GMT+02:00 Serge Stinckwich <serge.stinckwich(a)gmail.com>: >> >> On Mon, Jun 26, 2017 at 12:14 PM, Pavel Krivanek >> <pavel.krivanek(a)gmail.com> wrote: >> > Hi, >> > >> > this mail describes how to start to send pull requests to Pharo 7 Github >> > repository from Pharo 7. >> >> Thank you for the great explanation Pavel. >> >> > Preparations >> > ===================== >> > >> > - you need to have a Github account and set SSH keys. See >> > https://help.github.com/articles/connecting-to-github-with-ssh/ >> > - create own pharo-project/pharo repository fork. Go to >> > https://github.com/pharo-project/pharo, click on "Fork" button and >> > follow >> > the instructions >> >> [ ... ] >> >> > Issue processing >> > ===================== >> > >> > - create new case on FogBugz to get the issue number >> > - open Iceberg and from the context menu on the 'pharo' repository do: >> > Pharo >> > - Create new branch from FogBugz issue, enter the issue ID and it will >> > fill >> > the full branch name for you >> > - create your changes (you can do it before the creation of the branch >> > too) >> > - commit and push your changes in Iceberg, this way you will commit your >> > branch to your fork repository. Remember that the Iceberg commit window >> > has >> > two buttons, one for local commit, the second for commit with immediate >> > push. They can be very long because they contain the full branch (issue) >> > name >> > - in Iceberg in the 'pharo' repository context menu do: Pharo - Create >> > pull >> > request, fill your >> > - fill your Github credentials >> > - leave the PR title, comment is not required, check the pull request >> > head >> > and base. The base MUST be pharo-project/pharo development. Create the >> > pull >> > requests >> > - go to https://github.com/pharo-project/pharo/pulls, check your pull >> > requests and put URL of it into the issue record on FogBugz (as a >> > comment). >> > Resolve the issue as Fix review needed >> >> It means, there is no PR without a corresponding FogBugz issue ? > > > Yes, at least for code changes we would like to keep this relation. If it is > a really trivial change in readme or something like that, we can accept no > related issue record. > Please prefer to comment the issues instead of PRs directly to have all > information at one place. Thank you Pavel for the explanation. Maybe in the future, it will make sense to put everything in the PR and use github issues. You will use CI travis builds for all PR ? Regards, -- Serge Stinckwich UCN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

June 27, 2017

Re: [Pharo-dev] Pharo 7 provisional HOWTO

by Pavel Krivanek

2017-06-27 15:57 GMT+02:00 Serge Stinckwich <serge.stinckwich(a)gmail.com>: > On Mon, Jun 26, 2017 at 12:14 PM, Pavel Krivanek > <pavel.krivanek(a)gmail.com> wrote: > > Hi, > > > > this mail describes how to start to send pull requests to Pharo 7 Github > > repository from Pharo 7. > > Thank you for the great explanation Pavel. > > > Preparations > > ===================== > > > > - you need to have a Github account and set SSH keys. See > > https://help.github.com/articles/connecting-to-github-with-ssh/ > > - create own pharo-project/pharo repository fork. Go to > > https://github.com/pharo-project/pharo, click on "Fork" button and > follow > > the instructions > > [ ... ] > > > Issue processing > > ===================== > > > > - create new case on FogBugz to get the issue number > > - open Iceberg and from the context menu on the 'pharo' repository do: > Pharo > > - Create new branch from FogBugz issue, enter the issue ID and it will > fill > > the full branch name for you > > - create your changes (you can do it before the creation of the branch > too) > > - commit and push your changes in Iceberg, this way you will commit your > > branch to your fork repository. Remember that the Iceberg commit window > has > > two buttons, one for local commit, the second for commit with immediate > > push. They can be very long because they contain the full branch (issue) > > name > > - in Iceberg in the 'pharo' repository context menu do: Pharo - Create > pull > > request, fill your > > - fill your Github credentials > > - leave the PR title, comment is not required, check the pull request > head > > and base. The base MUST be pharo-project/pharo development. Create the > pull > > requests > > - go to https://github.com/pharo-project/pharo/pulls, check your pull > > requests and put URL of it into the issue record on FogBugz (as a > comment). > > Resolve the issue as Fix review needed > > It means, there is no PR without a corresponding FogBugz issue ? > Yes, at least for code changes we would like to keep this relation. If it is a really trivial change in readme or something like that, we can accept no related issue record. Please prefer to comment the issues instead of PRs directly to have all information at one place. Cheers, -- Pavel > Regards, > -- > Serge Stinckwich > UCN & UMI UMMISCO 209 (IRD/UPMC) > Every DSL ends up being Smalltalk > http://www.doesnotunderstand.org/ > >

June 27, 2017

Re: [Pharo-dev] Pharo 7 provisional HOWTO

by Esteban Lorenzano

> On 27 Jun 2017, at 15:57, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: > > On Mon, Jun 26, 2017 at 12:14 PM, Pavel Krivanek > <pavel.krivanek(a)gmail.com> wrote: >> Hi, >> >> this mail describes how to start to send pull requests to Pharo 7 Github >> repository from Pharo 7. > > Thank you for the great explanation Pavel. > >> Preparations >> ===================== >> >> - you need to have a Github account and set SSH keys. See >> https://help.github.com/articles/connecting-to-github-with-ssh/ >> - create own pharo-project/pharo repository fork. Go to >> https://github.com/pharo-project/pharo, click on "Fork" button and follow >> the instructions > > [ ... ] > >> Issue processing >> ===================== >> >> - create new case on FogBugz to get the issue number >> - open Iceberg and from the context menu on the 'pharo' repository do: Pharo >> - Create new branch from FogBugz issue, enter the issue ID and it will fill >> the full branch name for you >> - create your changes (you can do it before the creation of the branch too) >> - commit and push your changes in Iceberg, this way you will commit your >> branch to your fork repository. Remember that the Iceberg commit window has >> two buttons, one for local commit, the second for commit with immediate >> push. They can be very long because they contain the full branch (issue) >> name >> - in Iceberg in the 'pharo' repository context menu do: Pharo - Create pull >> request, fill your >> - fill your Github credentials >> - leave the PR title, comment is not required, check the pull request head >> and base. The base MUST be pharo-project/pharo development. Create the pull >> requests >> - go to https://github.com/pharo-project/pharo/pulls, check your pull >> requests and put URL of it into the issue record on FogBugz (as a comment). >> Resolve the issue as Fix review needed > > It means, there is no PR without a corresponding FogBugz issue ? it should not. same as before with SLICEs, there was no slice without issue :) Esteban > > Regards, > -- > Serge Stinckwich > UCN & UMI UMMISCO 209 (IRD/UPMC) > Every DSL ends up being Smalltalk > http://www.doesnotunderstand.org/ >

June 27, 2017

Re: [Pharo-dev] Pharo 7 provisional HOWTO

by Serge Stinckwich

On Mon, Jun 26, 2017 at 12:14 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > Hi, > > this mail describes how to start to send pull requests to Pharo 7 Github > repository from Pharo 7. Thank you for the great explanation Pavel. > Preparations > ===================== > > - you need to have a Github account and set SSH keys. See > https://help.github.com/articles/connecting-to-github-with-ssh/ > - create own pharo-project/pharo repository fork. Go to > https://github.com/pharo-project/pharo, click on "Fork" button and follow > the instructions [ ... ] > Issue processing > ===================== > > - create new case on FogBugz to get the issue number > - open Iceberg and from the context menu on the 'pharo' repository do: Pharo > - Create new branch from FogBugz issue, enter the issue ID and it will fill > the full branch name for you > - create your changes (you can do it before the creation of the branch too) > - commit and push your changes in Iceberg, this way you will commit your > branch to your fork repository. Remember that the Iceberg commit window has > two buttons, one for local commit, the second for commit with immediate > push. They can be very long because they contain the full branch (issue) > name > - in Iceberg in the 'pharo' repository context menu do: Pharo - Create pull > request, fill your > - fill your Github credentials > - leave the PR title, comment is not required, check the pull request head > and base. The base MUST be pharo-project/pharo development. Create the pull > requests > - go to https://github.com/pharo-project/pharo/pulls, check your pull > requests and put URL of it into the issue record on FogBugz (as a comment). > Resolve the issue as Fix review needed It means, there is no PR without a corresponding FogBugz issue ? Regards, -- Serge Stinckwich UCN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

June 27, 2017