- Pharo-users - lists.pharo.org

Re: [Pharo-users] Pharo based system monitoring (Nagios like)?

by Alistair Grant

Hi Norbet, On Sat, Jul 22, 2017 at 10:52:16PM +0200, Norbert Hartl wrote: > Hi, > > I just made it nagios compatible. I developed it because I'm using munin [1]. > You can look at this [2] blog post how to do it. If you have questions just > ask. > > Norbert > > [1] http://munin-monitoring.org/ > [2] http://norbert.hartl.name/blog/2015/05/16/ > system-monitoring-for-pharo-images/ Thanks very much for your reply. What I was hoping to find was something that acted as the server, not just an agent. But I'll still have a look at this as it will be useful to help monitor pharo processes. Thanks again, Alistair > Am 22.07.2017 um 19:41 schrieb Alistair Grant <akgrant0710(a)gmail.com>: > > > Hi Everyone, > > Does anyone know of a system monitoring library written in Pharo (or at > least smalltalk)? > > I'm looking for something that provides functionality similar to nagios > and will allow me to monitor the basics, e.g. free disk space, cpu > usage, process presence, etc. > > I found Norbert Hartl's Monitoring library, but that looks like it acts > as an agent for nagios or similar. > > Thanks, > Alistair >

July 24, 2017

Re: [Pharo-users] [ANN] Pharo 6.1 (summer) released!

by Herby VojÄÃk

Esteban Lorenzano wrote: > Hi, > > We are releasing Pharo 6.1. > Usually, between each major version we just apply bugfixes changing the > build number and not announcing new versions but this time is different > since the fixes applied required a new VM. > The principal reason for the new version is to update Iceberg support, > bringing it to macOS 64bits version. > > So, now Pharo 6.1 comes with Iceberg 0.5.5, which includes: > > - running on macOS 64bits > - adds cherry pick > - adds major improvements on performance for big repositories > - adds pull request review plugin > - repositories browser: group branches by remote > - adds bitbucket and gitlab to recognised providers on metacello integration > - uses libgit v0.25.1 as backend > - several bugfixes Nice, thanks. Alas, the issue I mentioned in Iceberg + github is still present (though the compile: workaround still works). > Other important change: > > - linux vm by default is now vm threaded heartbeat. > > We still miss 64bits Windows (sorry for that), but we are getting there. > I hope to have it running right after ESUG. > > To download 6.1 version, you can go to http://pharo.org/download page, > or with zeroconf: > > wget -O- get.pharo.org <http://get.pharo.org> | bash > > Enjoy! > Esteban Herby

July 24, 2017

Re: [Pharo-users] [ANN] Pharo 6.1 (summer) released!

by Norbert Hartl

Thank you! That is so cool. Norbert > Am 24.07.2017 um 13:56 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > > Hi, > > We are releasing Pharo 6.1. > Usually, between each major version we just apply bugfixes changing the build number and not announcing new versions but this time is different since the fixes applied required a new VM. > The principal reason for the new version is to update Iceberg support, bringing it to macOS 64bits version. > > So, now Pharo 6.1 comes with Iceberg 0.5.5, which includes: > > - running on macOS 64bits > - adds cherry pick > - adds major improvements on performance for big repositories > - adds pull request review plugin > - repositories browser: group branches by remote > - adds bitbucket and gitlab to recognised providers on metacello integration > - uses libgit v0.25.1 as backend > - several bugfixes > > Other important change: > > - linux vm by default is now vm threaded heartbeat. > > We still miss 64bits Windows (sorry for that), but we are getting there. I hope to have it running right after ESUG. > > To download 6.1 version, you can go to http://pharo.org/download <http://pharo.org/download> page, or with zeroconf: > > wget -O- get.pharo.org <http://get.pharo.org/> | bash > > Enjoy! > Esteban

July 24, 2017

Re: [Pharo-users] [Pharo-dev] [ANN] Pharo 6.1 (summer) released!

by Sven Van Caekenberghe

Thank you, sounds like a really cool move. > On 24 Jul 2017, at 13:56, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Hi, > > We are releasing Pharo 6.1. > Usually, between each major version we just apply bugfixes changing the build number and not announcing new versions but this time is different since the fixes applied required a new VM. > The principal reason for the new version is to update Iceberg support, bringing it to macOS 64bits version. > > So, now Pharo 6.1 comes with Iceberg 0.5.5, which includes: > > - running on macOS 64bits > - adds cherry pick > - adds major improvements on performance for big repositories > - adds pull request review plugin > - repositories browser: group branches by remote > - adds bitbucket and gitlab to recognised providers on metacello integration > - uses libgit v0.25.1 as backend > - several bugfixes > > Other important change: > > - linux vm by default is now vm threaded heartbeat. > > We still miss 64bits Windows (sorry for that), but we are getting there. I hope to have it running right after ESUG. > > To download 6.1 version, you can go to http://pharo.org/download page, or with zeroconf: > > wget -O- get.pharo.org | bash > > Enjoy! > Esteban

July 24, 2017

Re: [Pharo-users] [Pharo-dev] [ANN] Pharo 6.1 (summer) released!

by Tudor Girba

Great job! Doru > On Jul 24, 2017, at 1:56 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Hi, > > We are releasing Pharo 6.1. > Usually, between each major version we just apply bugfixes changing the build number and not announcing new versions but this time is different since the fixes applied required a new VM. > The principal reason for the new version is to update Iceberg support, bringing it to macOS 64bits version. > > So, now Pharo 6.1 comes with Iceberg 0.5.5, which includes: > > - running on macOS 64bits > - adds cherry pick > - adds major improvements on performance for big repositories > - adds pull request review plugin > - repositories browser: group branches by remote > - adds bitbucket and gitlab to recognised providers on metacello integration > - uses libgit v0.25.1 as backend > - several bugfixes > > Other important change: > > - linux vm by default is now vm threaded heartbeat. > > We still miss 64bits Windows (sorry for that), but we are getting there. I hope to have it running right after ESUG. > > To download 6.1 version, you can go to http://pharo.org/download page, or with zeroconf: > > wget -O- get.pharo.org | bash > > Enjoy! > Esteban -- www.tudorgirba.com www.feenk.com "To lead is not to demand things, it is to make them happen."

July 24, 2017

[ANN] Pharo 6.1 (summer) released!

by Esteban Lorenzano

Hi, We are releasing Pharo 6.1. Usually, between each major version we just apply bugfixes changing the build number and not announcing new versions but this time is different since the fixes applied required a new VM. The principal reason for the new version is to update Iceberg support, bringing it to macOS 64bits version. So, now Pharo 6.1 comes with Iceberg 0.5.5, which includes: - running on macOS 64bits - adds cherry pick - adds major improvements on performance for big repositories - adds pull request review plugin - repositories browser: group branches by remote - adds bitbucket and gitlab to recognised providers on metacello integration - uses libgit v0.25.1 as backend - several bugfixes Other important change: - linux vm by default is now vm threaded heartbeat. We still miss 64bits Windows (sorry for that), but we are getting there. I hope to have it running right after ESUG. To download 6.1 version, you can go to http://pharo.org/download <http://pharo.org/download> page, or with zeroconf: wget -O- get.pharo.org | bash Enjoy! Esteban

July 24, 2017

Re: [Pharo-users] Question

by phil＠highoctane.be

LargeInteger is not what you should use. Try this: v:= SmallInteger minVal - 1 In 64-bit, one gets:"-1152921504606846977" and there you have a LargeNegativeInteger that prints properly. v := SmallInteger maxval + 1 "1152921504606846976" same but positive. You have Integers that are Numbers and why bother with the large or small thing? It works. If things are getting slow, well, profile and optimize. Phil On Mon, Jul 24, 2017 at 10:54 AM, Koos Brandt <brandt.koos(a)gmail.com> wrote: > Hi > > I am still learning but something weird happened. > > In a new Workspace > > Do-it myVar := LargeInteger new > Print-it myVar <error in printString: try 'Inspect it' to debug> > > When I inspect it I get > SubclassResponsibility: LargeInteger had the subclass responsibility to > implement #printOn:base: > > When I browse LargeInteger, then at Integer level I get a message ânewâ as > follows: > > *new* > > * self == Integer ifTrue: [* > * ^ self error: 'Integer is an abstract class. Make a concrete > subclass.'].* > * ^ super new* > > I looked for new higher up in the hierarchy(super), but could not see it. > Maybe I am a bit dumb still with looking up. > > I tried on SmallInteger a new, but got back > Error: SmallIntegers can only be created by performing arithmetic. > > I then checked and noticed that SmallInteger actually have new and > basicNew implemented (override) > > So the error I got on smallinteger was from the override > LargeInteger has no override, but has a âsilent" error > > This seems a bit weird to me > > Just so you know I also tried > Do-it myVar := LargeInteger new: 10000 > Print-it myVar class. -> LargeInteger > Dot-it myVar := myVar + 1 > > The last statement hangs the image! (Tried 3 times) > > Comment: > 1. I am surprised that Do-it did not give me an error on the new: (there > is a message is the hierarchy of new:neg and maybe the neg is optional?) > 2. The new: seemed to have created 10000 LargeIntegers > 3. I tried the new: also with just 5, and same result, image hang. (I > thought 10,000 was maybe a very large loop for the + 1..) > > Did I damage something in the image maybe? I started this one just > yesterday to look at MOOC week1. > > I do not need LargeIntegers for now but â¦ > > > This is Pharo 6.0 64 Bit on Mac OSX Sierra 10.12.5 (iMac 27, 2.9GHz Intel > Core i5, 16GB RAM) > > Regards > > Koos Brandt > 0824542028 > > > >

July 24, 2017

Question

by Koos Brandt

Hi I am still learning but something weird happened. In a new Workspace Do-it myVar := LargeInteger new Print-it myVar <error in printString: try 'Inspect it' to debug> When I inspect it I get SubclassResponsibility: LargeInteger had the subclass responsibility to implement #printOn:base: When I browse LargeInteger, then at Integer level I get a message ânewâ as follows: new self == Integer ifTrue: [ ^ self error: 'Integer is an abstract class. Make a concrete subclass.']. ^ super new I looked for new higher up in the hierarchy(super), but could not see it. Maybe I am a bit dumb still with looking up. I tried on SmallInteger a new, but got back Error: SmallIntegers can only be created by performing arithmetic. I then checked and noticed that SmallInteger actually have new and basicNew implemented (override) So the error I got on smallinteger was from the override LargeInteger has no override, but has a âsilent" error This seems a bit weird to me Just so you know I also tried Do-it myVar := LargeInteger new: 10000 Print-it myVar class. -> LargeInteger Dot-it myVar := myVar + 1 The last statement hangs the image! (Tried 3 times) Comment: 1. I am surprised that Do-it did not give me an error on the new: (there is a message is the hierarchy of new:neg and maybe the neg is optional?) 2. The new: seemed to have created 10000 LargeIntegers 3. I tried the new: also with just 5, and same result, image hang. (I thought 10,000 was maybe a very large loop for the + 1..) Did I damage something in the image maybe? I started this one just yesterday to look at MOOC week1. I do not need LargeIntegers for now but â¦ This is Pharo 6.0 64 Bit on Mac OSX Sierra 10.12.5 (iMac 27, 2.9GHz Intel Core i5, 16GB RAM) Regards Koos Brandt 0824542028

July 24, 2017

Re: [Pharo-users] Cloning code from GitHub using Iceberg

by HernÃ¡n Morales Durand

Hi 2017-07-24 4:10 GMT-03:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > Hi, > > in fact, I think you made quite the contrary: you declared a code subdirectory that does not exits. > what you need to do is to press âEditâ¦â button and clean anything that appears in âcode subdirectoryâ field. > Thanks, that fixed it. > also, I have no idea why you have two entries for same project :) > Because I clicked "Clone repository" again, and tried to fill the "Code subdirectory" with another value to see what happens :) Cheers, HernÃ¡n > Esteban > > >> On 23 Jul 2017, at 23:22, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: >> >> Hi guys, >> >> I am trying to import code - in Pharo 6 - from a GitHub repository: >> https://github.com/jigyasa-grover/CORMAS-Pharo. The repository doesn't >> include a Baseline, and so it is not loadable using a Metacello >> expression right? >> >> I've tried to clone it with Iceberg with Remote URL: >> https://github.com/jigyasa-grover/CORMAS-Pharo.git >> >> I ended with a "Repository CORMAS-Pharo is invalid" so I wonder what's >> exactly is invalid? I can browse the history but I don't know if any >> code from that repository was already loaded in my image. >> >> The URL should be specified as the ghost text suggest? Currently the >> ghost text is: git@github.com:user/project.git >> >> Should I fill the "Code subdirectory" field? >> >> Cheers, >> >> HernÃ¡n >> <Iceberg repositories.jpeg> > >

July 24, 2017

Re: [Pharo-users] Cloning code from GitHub using Iceberg

by Alistair Grant

Hi Hernan, On Sun, Jul 23, 2017 at 06:22:52PM -0300, Hern??n Morales Durand wrote: > Hi guys, > > I am trying to import code - in Pharo 6 - from a GitHub repository: > https://github.com/jigyasa-grover/CORMAS-Pharo. The repository doesn't > include a Baseline, and so it is not loadable using a Metacello > expression right? > > I've tried to clone it with Iceberg with Remote URL: > https://github.com/jigyasa-grover/CORMAS-Pharo.git > > I ended with a "Repository CORMAS-Pharo is invalid" so I wonder what's > exactly is invalid? I can browse the history but I don't know if any > code from that repository was already loaded in my image. > > The URL should be specified as the ghost text suggest? Currently the > ghost text is: git@github.com:user/project.git > > Should I fill the "Code subdirectory" field? I just: 1. opened Icerberg 2. pressed "Clone repository" 3. Entered https://github.com/jigyasa-grover/CORMAS-Pharo.git as the URL 4. Left the subdirectory blank (opening the repository in a browser you can see that the packages are in the top level directory) 5. Clicked Create repository 6. Selected the repository, the packages tab and loaded the ConfigurationOfComas without any problem. Pharo 6.0 Latest update: #60501 Is there an easy way to tell which version of Iceberg I have loaded? I'm sure it is 0.5.x, but not what the x is. Cheers, Alistair

July 24, 2017