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

Pharo Launcher Error

by Brad Selfridge

I'm trying to run the Pharo6.1 Launcher. I'm getting the following error when running from a command line: * "This interpreter (vers. 68021) cannot read image file (vers. 6521)."* I'm running the 64bit vm built on July 20th and I downloaded the latest launcher at: *http://files.pharo.org/platform/launcher/PharoLauncher-user-stable-2017.09.29.zip* Thanks for any help, ----- Brad Selfridge -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Oct. 2, 2017

Re: [Pharo-dev] Two GitHub organizations

by Esteban Lorenzano

> On 2 Oct 2017, at 17:33, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > > 2017-10-02 17:26 GMT+02:00 Sean P. DeNigris <sean(a)clipperadams.com <mailto:sean@clipperadams.com>>: > Peter UhnÃ¡k wrote > > http://forum.world.st/IMPORTANT-iceberg-home-changed-tp4944480p4944684.html <http://forum.world.st/IMPORTANT-iceberg-home-changed-tp4944480p4944684.html> > > I still don't understand :/ > > Me too :) > I think it was not actually discussed and explained. At least linked thread not describes it. not everything can be discussed, but it was explained (in that link, it is explained very well): - it is easier to organise related work into teams (for example: iceberg, libgit2 bindings, filetree and now tonel) than to have everything on same team. - is also a marketing stuff: more groups of pharo related stuff in github. - it is also an easy choice: if that does not works, is very easy to change and group everything (but today I still think it was a good decision) Esteban > > What benefit justifies the complexity of > multiple organizations? Isn't the concept of GH orgs inherently and > specifically to host multiple projects?! > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html <http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html> > >

Oct. 2, 2017

Re: [Pharo-dev] Esteban's ChangeLog week of 25 September 2017

by Esteban Lorenzano

> On 2 Oct 2017, at 17:23, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > EstebanLM wrote >> This is my weekly ChangeLog > > Go, Esteban!! > > One tiny nickpick: I feel like this log would be more intuitive in ascending > chronological order (i.e. #reversed). yeah, it might be :) I will add a TODOâ¦ but it will not arrive next week ;) Esteban > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >

Oct. 2, 2017

Re: [Pharo-dev] Two GitHub organizations

by Denis Kudriashov

2017-10-02 17:26 GMT+02:00 Sean P. DeNigris <sean(a)clipperadams.com>: > Peter UhnÃ¡k wrote > > http://forum.world.st/IMPORTANT-iceberg-home- > changed-tp4944480p4944684.html > > I still don't understand :/ Me too :) I think it was not actually discussed and explained. At least linked thread not describes it. > What benefit justifies the complexity of > multiple organizations? Isn't the concept of GH orgs inherently and > specifically to host multiple projects?! > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html > >

Oct. 2, 2017

Re: [Pharo-dev] Two GitHub organizations

by Sean P. DeNigris

Peter UhnÃ¡k wrote > http://forum.world.st/IMPORTANT-iceberg-home-changed-tp4944480p4944684.html I still don't understand :/ What benefit justifies the complexity of multiple organizations? Isn't the concept of GH orgs inherently and specifically to host multiple projects?! ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Oct. 2, 2017

Re: [Pharo-dev] Esteban's ChangeLog week of 25 September 2017

by Sean P. DeNigris

EstebanLM wrote > This is my weekly ChangeLog Go, Esteban!! One tiny nickpick: I feel like this log would be more intuitive in ascending chronological order (i.e. #reversed). ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Oct. 2, 2017

Re: [Pharo-dev] Iceberg Contribution Barrier

by Sean P. DeNigris

EstebanLM wrote > You want to contribute to iceberg? Yes, I followed Guille's instructions, substituting the Iceberg GH repo for Pharo's, but I don't think I updated Iceberg. Iceberg showed only my changes, but maybe I got lucky that I was working on a part that hadn't changed in the mean time? Anyway, I was able to commit to my Iceberg fork and then via the GH web UI submit a PR to the canonically Iceberg repo. ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Oct. 2, 2017

Re: [Pharo-dev] pharo --help returning non-zero exit status

by Stephane Ducasse

Esteban, Eliot, Clement was is the process to get this fix in the VM? On Sun, Oct 1, 2017 at 9:05 AM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > Ah, perfect. Thanks! > > peter > > On Sun, Oct 1, 2017 at 8:41 AM, K K Subbu <kksubbu.ml(a)gmail.com> wrote: >> >> On Sunday 01 October 2017 11:27 AM, Peter UhnÃ¡k wrote: >>> >>> Hi, >>> >>> why does executing `pharo --help` return exit status 1? The operation >>> succeeded, so I don't see a reason for a failure return state. >> >> >> This is a bug. See the thread at >> >> >> >> http://forum.world.st/Re-Pharo-dev-pharo-help-returns-exit-code-1-on-ubuntu… >> >> The proposed fix is pending review at: >> >> https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/136 >> >> Regards .. Subbu >> >> >

Oct. 2, 2017

Re: [Pharo-dev] Non-deterministic ombu errors

by Stephane Ducasse

Martin if you publish a fix for 6.1 we will port it back because this is important. Stef On Fri, Sep 29, 2017 at 3:55 PM, Martin Dias <tinchodias(a)gmail.com> wrote: > Now I do not know the best way for you to get the new fixed version. It's > too late to include it in P6.1, I guess, so... either add epicea into > metacello configuration or wait until P7. > > > > On Fri, Sep 29, 2017 at 5:34 AM, Jan BlizniÄenko <bliznjan(a)fit.cvut.cz> > wrote: >> >> I'm glad it has known reason then, thank you for looking into it, all I >> was >> able to find out was that it relates to non-ascii characters and that >> build >> on our production server fails because of that :) >> >> Jan >> >> >> tinchodias wrote >> > On Sun, Sep 24, 2017 at 5:49 AM, Sven Van Caekenberghe < >> >> > sven@ >> >> > > wrote: >> > >> >> >> >> > On 23 Sep 2017, at 22:42, Jan BlizniÄenko < >> >> > bliznjan@.cvut >> >> > > wrote: >> >> > >> >> > Hello >> >> > >> >> > I am having very similar errors from time to time when manually >> >> > loading >> >> code >> >> > into Pharo from filetree (gitfiletree), but only in one of my >> >> > projects >> >> which >> >> > contains non-ASCII characters like ÄÅ¡ÄÅÅ¾Ã½Ã¡ÃÃ©Å¯ÃºÅ¥Ä. For the very same >> >> reason >> >> > (not able to find why sometimes the error is there and sometimes is >> >> not), I >> >> > did not report it yet, but it is quite annoying. Retrying loading the >> >> > package helps every time. >> >> >> >> I think was reported before. I believe Ombu somewhere takes an >> >> arbitrary >> >> chunk of bytes out of an UTF-8 encoded file (like the last 100 of >> >> something >> >> like that) and then starts reading that. With UTF-8, a variable length >> >> encoding, that can be dangerous because you could end up in the middle >> >> of >> >> a >> >> character, not between encoded character boundaries. This would also >> >> explain the randomness, as it is highly dependent on the contents. >> >> >> >> ZnUTF8Encoder>>#backOnStream: can be used to make sure you are really >> >> at >> >> the start of an encoded character. >> >> >> > >> > >> > Hello >> > >> > This issue was reported as: >> > >> > >> > https://pharo.fogbugz.com/f/cases/20112/Epicea-can-fail-while-reading-non-a… >> > >> > My apologies for the bug... I introduced that code as an i/o >> > optimization >> > but wasn't properly tested. >> > >> > Thnks Sven, but I finally used stream's #basicNext (as Henrik suggested >> > in >> > fogbugz) which skips forward. >> > >> > >> > Martin >> >> >> >> >> >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >> >

Oct. 2, 2017

Esteban's ChangeLog week of 25 September 2017

by estebanlm＠gmail.com

Hello! This is my weekly ChangeLog, from 25 September 2017 to 1 October 2017. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=25/9/2017&to=1/10/2017 ChangeLog ========= 28 September 2017: ------------------ * I spent my day preparing [iceberg 0.6](https://github.com/pharo-vcs/iceberg/commits/dev-0.6) to be released and I think I didn't do a bad you. * I integrate two PR to dev-0.5 and then merge it to dev-0.6 * I closed issues [#470](https://github.com/pharo-vcs/iceberg/issues/470) and [#239](https://github.com/pharo-vcs/iceberg/issues/239) * I fixed a problem on cherry-pick and renamed/removed classes (not reported as issue, but there) * I added a "full sync" option meant to verify the full repository differences (this is useful in certain cases) ... and I'm still trying to get a loadable version of latest metacello (which will come with tonel integration) 27 September 2017: ------------------ * I'm still making latest [metacello](http://github.com/metacello/metacello) version to work properly on Pharo, so we can integrate it into Pharo 7.0 (and we can also update Iceberg). Right now, I have what I think is a "working version", but I'm still figuring out how to include it into Pharo (other than regular merge in image, export... which I think will be our approach until we have subtrees) 24 September 2017: ------------------ * I forget to say that friday with Ronie we made win32 headless version work :) Now, it just remains win64 version... and of course, we will need to start test intensively so we can have good support for the moment of release. cheers! Esteban

Oct. 2, 2017