Re: [Pharo-users] [ANN] Smalltalk's Successor

2020-08-10 Thread Stéphane Ducasse
Richard if you would like to have a real impact why don’t you help for real to copy edit and improve documentation. This is not your articles that will attract people, a strong documentation smoothing the learning curve will. This is super easy you can edit text right in your web browser. I d

Re: [Pharo-users] [ANN] Smalltalk's Successor

2020-08-10 Thread horrido
It's true, Smalltalk faces the same dilemma as Linux and Lisp. As a /family/ of languages, portability is a genuine issue. There's no getting around this dichotomy. You can have either a flexibility of choice or the tyranny of one standard, but not both. The decision is a fact of life that we fac

Re: [Pharo-users] [ANN] Smalltalk's Successor

2020-08-10 Thread Richard O'Keefe
Here is a challenge: What is "Smalltalk"? VAST, VW, and Pharo are quite different environments. To the extent that they share a common syntax (which they don't, quite), fine, but porting nontrivial code between them is NOT easy. They certainly have very little in common as GUI kits. All praise a

Re: [Pharo-users] CannotWriteData errors in P3 and Seaside

2020-08-10 Thread Esteban Maringolo
Looking at the Postgres side of the log I find that the connection was reset from the other side (it is Pharo). The reason for that is yet unknown to me. Since I don't do anything (that I'm aware of). golfware_database.1.9sl4bt9j6cv5@gw| 2020-08-10 20:02:35.939 UTC [132] LOG: could not recei

Re: [Pharo-users] CannotWriteData errors in P3 and Seaside

2020-08-10 Thread Esteban Maringolo
My Seaside session isn't closing the connection, only when unregistered, but this seems to be something else I don't know. I saw there is logging, and I need to set it up in general (including Fuel serialized stacks). Looking in the web apparently there is the need for a keepalive that is not in p

Re: [Pharo-users] CannotWriteData errors in P3 and Seaside

2020-08-10 Thread Esteban Maringolo
To add to this hard to reproduce issue, it only happens in production (where if not?) when running within a Docker Swarm where PostgreSQL is inside the Swarm, so there might be something there fiddling with the network, or I don't know really :-/ Regards. Esteban A. Maringolo On Mon, Aug 10, 202

Re: [Pharo-users] CannotWriteData errors in P3 and Seaside

2020-08-10 Thread Sven Van Caekenberghe
Hi Esteban, I have a web app with P3 under Seaside in production and it works fine. But that is without Glorp, nor any connection pooling. You say the connection seems closed, maybe the closing got triggered by your app somehow ? How do you clean up expired sessions ? How do you handle logouts

[Pharo-users] CannotWriteData errors in P3 and Seaside

2020-08-10 Thread Esteban Maringolo
Hi all, Sven ;-) I'm having erratic P3 errors in a recent application I wrote using Pharo, Seaside and Glorp with P3 as driver. Each Seaside session has a GlorpSession, which in turn has a P3Connection in its accessor. I don't know why, but sometimes the P3Connection socket is closed, and then wh

Re: [Pharo-users] Extract-method refactoring erratic behavior in Pharo 8

2020-08-10 Thread Stéphane Ducasse
Thanks. This is a useful information. We found a bug in calypso, apparently the editor is sometimes working on the edited text and sometimes on the previous version (via the object). Philippe did you open the issue we talked about? Tx > On 8 Aug 2020, at 01:36, Esteban Maringolo wrote: > > H

[Pharo-users] [ANN] Smalltalk's Successor

2020-08-10 Thread Richard Kenneth Eng
https://smalltalk.tech.blog/2020/08/10/smalltalks-successor/ A bold claim. It'll be interesting to see if anybody challenges me on this.