Re: [Pharo-users] pharo bash script with startup

2018-06-27 Thread Tim Mackinnon
I’ve not noticed that problem on ubuntu or AWS lambda so there must be something different going on. Sent from my iPhone > On 27 Jun 2018, at 07:30, Otto Behrens wrote: > > Hi, > > I just installed pharo 6.1 using the .zip file > (http://files.pharo.org/platform/Pharo6.1-64-linux.zip) and ba

Re: [Pharo-users] pharo bash script with startup

2018-06-27 Thread Julián Maestri
Try with ./pharo or try with an absolute image path. On Wed, Jun 27, 2018, 04:03 Tim Mackinnon wrote: > I’ve not noticed that problem on ubuntu or AWS lambda so there must be > something different going on. > > Sent from my iPhone > > On 27 Jun 2018, at 07:30, Otto Behrens wrote: > > Hi, > > I

Re: [Pharo-users] Microservices using Pharo

2018-06-27 Thread Norbert Hartl
Joachim, > Am 27.06.2018 um 07:42 schrieb jtuc...@objektfabrik.de: > > Norbert, > > Am 26.06.18 um 21:41 schrieb Norbert Hartl: >> >> >> Am 26.06.2018 um 20:44 schrieb Andrei Stebakov > >: >> >>> What would be an example for load balancer for Pharo images? Can we r

Re: [Pharo-users] pharo bash script with startup

2018-06-27 Thread Otto Behrens
I am running with an absolute image path. The issue is definitely exec "$image" in the script. If I remove the "", i.e. exec $image, then it works. /opt/pharo/pharo6.1-64/bin/lib/pharo/5.0-201708271955/pharo "my.image startup.st" gives me the same problem On Wed, Jun 27, 2018 at 9:28 AM, Julián

Re: [Pharo-users] pharo bash script with startup

2018-06-27 Thread Guillermo Polito
That's strange, is this a new problem or you always had it? I've just tested it, pharo 61 64 bits. $ wget -O - https://get.pharo.org/64/61+vm | bash [SNIP] $ ./pharo Pharo.image eval 1+1 2 Maybe the so called starter scripts (pharo, pharo-ui) are not the same using zeroconf and by downloading a

Re: [Pharo-users] pharo bash script with startup

2018-06-27 Thread Norbert Hartl
> Am 27.06.2018 um 09:38 schrieb Otto Behrens : > > I am running with an absolute image path. > > The issue is definitely exec "$image" in the script. If I remove the "", i.e. > exec $image, then it works. > > /opt/pharo/pharo6.1-64/bin/lib/pharo/5.0-201708271955/pharo "my.image > startup.

Re: [Pharo-users] pharo bash script with startup

2018-06-27 Thread Otto Behrens
I extracted the file that I downloaded again and checked. The file ( http://files.pharo.org/platform/Pharo6.1-64-linux.zip) seems to have an old VM zipped: /opt/pharo/pharo6.1-64/bin/lib/pharo/5.0-201708271955 What I get with wget -O - https://get.pharo.org/64/61+vm | bash is: pharo-vm/lib/pha

Re: [Pharo-users] Microservices using Pharo

2018-06-27 Thread jtuc...@objektfabrik.de
Norbert, thanks for your insighgts, explanations and thoughts. It is good to read and learn from people who are a step or two ahead... Am 27.06.18 um 09:31 schrieb Norbert Hartl: Joachim, Am 27.06.2018 um 07:42 schrieb jtuc...@objektfabrik.de : Norbert, A

Re: [Pharo-users] pharo bash script with startup

2018-06-27 Thread Otto Behrens
Thanks, but it does not. I give a full path for both the image and the startup files. It must have something to do with the stuff packaged in the zip file. On Wed, Jun 27, 2018 at 9:59 AM, Norbert Hartl wrote: > > > Am 27.06.2018 um 09:38 schrieb Otto Behrens : > > I am running with an absolut

Re: [Pharo-users] Microservices using Pharo

2018-06-27 Thread Andrei Stebakov
Thank you guys for your insiteful answers. I wish we could have some kind of article summarizing those approaches so that next devs wouldn't have to reinvent the wheel but start with some tried approach and maybe improve it. As I only scratched the surface learning Pharo, I may have some naive ques

Re: [Pharo-users] pharo bash script with startup

2018-06-27 Thread K K Subbu
On Wednesday 27 June 2018 01:08 PM, Otto Behrens wrote: I am running with an absolute image path. The issue is definitely exec "$image" in the script. If I remove the "", i.e. exec $image, then it works. The double quotes are required here to skip splitting arguments with embedded spaces into

Re: [Pharo-users] Microservices using Pharo

2018-06-27 Thread Norbert Hartl
> Am 27.06.2018 um 10:09 schrieb "jtuc...@objektfabrik.de" > : > > Norbert, > > > thanks for your insighgts, explanations and thoughts. It is good to read and > learn from people who are a step or two ahead... > >> Am 27.06.18 um 09:31 schrieb Norbert Hartl: >> Joachim, >> >>> Am 27.06.201

Re: [Pharo-users] Microservices using Pharo

2018-06-27 Thread Norbert Hartl
> Am 27.06.2018 um 15:08 schrieb Andrei Stebakov : > > Thank you guys for your insiteful answers. I wish we could have some kind of > article summarizing those approaches so that next devs wouldn't have to > reinvent the wheel but start with some tried approach and maybe improve it. > As I onl

Re: [Pharo-users] [Pharo-dev] [Ann] OSSubprocess v1.0.1

2018-06-27 Thread Mariano Martinez Peck
Excellent catch! Thanks Guille and the rest of the crew! On Tue, Jun 26, 2018 at 11:25 AM Guillermo Polito wrote: > Hi all, > > There is a new version of OSSubprocess available. This is a Bugfix > release. This release fixes a problem with waitpid that happened > regularly and randomly in OSSubp

Re: [Pharo-users] pharo bash script with startup

2018-06-27 Thread K K Subbu
On Wednesday 27 June 2018 06:39 PM, K K Subbu wrote: The double quotes are required here to skip splitting arguments with embedded spaces into different words. I suspect the error is earlier in the image=$@ assignment. This requires double quotes. Double quotes are also required while callin

Re: [Pharo-users] Yet another Pharo in docker

2018-06-27 Thread Herbert Vojčík
Updated with 60541 release of 6.1. Herby Vojčík wrote on 18. 10. 2017 22:17: Herby Vojčík wrote: https://hub.docker.com/r/herbysk/pharo/ Thanks to gotchas@dockerhub whose scripts I adapted.

Re: [Pharo-users] pharo bash script with startup

2018-06-27 Thread Hernán Morales Durand
2018-06-27 10:50 GMT-03:00 K K Subbu : > On Wednesday 27 June 2018 06:39 PM, K K Subbu wrote: >> >> >> The double quotes are required here to skip splitting arguments with >> embedded spaces into different words. >> >> I suspect the error is earlier in the image=$@ assignment. This requires >> doub

Re: [Pharo-users] pharo bash script with startup

2018-06-27 Thread Tim Mackinnon
When we get confirmation of success - we need to make sure this gets applied to both zeroconf and official downloads. Anything we can do to simplify and make it robust is gratefully appreciated as there is nothing worse than falling at the lunch hurdle. It’s cool to see so many clever minds on

Re: [Pharo-users] Iceberg - finding deleted classes, reverting versions?

2018-06-27 Thread Tim Mackinnon
Hey thanks Ben - this still doesn’t work for me… good idea to try on the Pharo repo itself. I have a fork of it, which I catch up periodically - so I tried a similar suggestion to you - went into my directory (underneath the src folder) and typed: log --diff-filter=D --summary --graph --pretty

Re: [Pharo-users] Iceberg - finding deleted classes, reverting versions?

2018-06-27 Thread Tim Mackinnon
And just to add to this - I just did a git clone (git clone g...@github.com :pharo-project/pharo.git) in a fresh directory and can see that same deleted file - and when I try to do a checkout, it gives the path spec error. This is very weird - is it some osx thing? I wi

Re: [Pharo-users] Iceberg - finding deleted classes, reverting versions?

2018-06-27 Thread Tim Mackinnon
For the record - I get the same error using those steps on Ubuntu as well. So I must be doing something wrong? (Note in my message when I pasted the command used - I neglected the git in front of: log --diff-filter=D --summary —pretty="format:%cd | %h | %H | %cn%n-> %s%n”) Tim > On 28 Jun 2

Re: [Pharo-users] pharo bash script with startup

2018-06-27 Thread Otto Behrens
Thanks for the effort guys. I tried to download the image, sources and vm separately (basically extracted what https://get.pharo.org/64/61+vm does), but ran into fresh trouble. Firstly, is "wget -O - https://get.pharo.org/64/61+vm | bash" not risky in terms of security? It should be quite possibl