Re: [Pharo-dev] Beacon for Pharo 7

Hi all, Just to state my position about the integration of Beacon. My main concern now is that I do not want to it become Glamour. I do not want to integrate a new tool that will be half integrated and not maintained because "the future is elsewhere". If people would like to introduce Beacon,

[Pharo-dev] [Iceberg] Call for contributions

Hi everybody, just for information, we have gathered some ideas on possible contributions for iceberg besides those in the issue tracker. We've put that in Iceberg's wiki: https://github.com/pharo-vcs/iceberg/wiki/How-to-help-us,-What-you-could-contribute The idea is that those contributions

Re: [Pharo-dev] [Pharo-users] [Ann] Some new iceberg videos

/iceberg/wiki/Branching-and-Merging On Thu, May 24, 2018 at 10:06 AM, Guillermo Polito < guillermopol...@gmail.com> wrote: > > > On Thu, May 24, 2018 at 9:51 AM, Guillermo Polito < > guillermopol...@gmail.com> wrote: > >> Hi Tim, >> >> On Wed, May 23, 201

Re: [Pharo-dev] [Pharo-users] [Ann] Some new iceberg videos

On Thu, May 24, 2018 at 9:51 AM, Guillermo Polito <guillermopol...@gmail.com > wrote: > Hi Tim, > > On Wed, May 23, 2018 at 6:32 PM, Tim Mackinnon <tim@testit.works> wrote: > >> Guille - the text reads very well, I’ll try and look at the videos later. >> &g

Re: [Pharo-dev] [Pharo-users] [Ann] Some new iceberg videos

rt options for this one? I'll check and replace the video. Thanks! > > Tim > > On 23 May 2018, at 17:09, Guillermo Polito <guillermopol...@gmail.com> > wrote: > > Hi all, > > This time (just before releasing a new version of iceberg) I wanted to > sha

[Pharo-dev] [Ann] Some new iceberg videos

Hi all, This time (just before releasing a new version of iceberg) I wanted to share some videos with you. Feedback is welcome. !! How to contribute to Iceberg https://youtu.be/yGr5HvVWM0M This video shows how to contribute to iceberg. For this, you should update your iceberg installation and

Re: [Pharo-dev] FileDoesNotExist vs FileDoesNotExistException

If I'm recalling well (which I might not :)) there is one thing (that I don't quite like) that prevents these two classes to be easily merged into one: their #defaultAction. On Mon, May 21, 2018 at 7:07 PM, Alistair Grant wrote: > On Mon, May 21, 2018 at 03:01:57PM +0200,

Re: [Pharo-dev] LibFFI/NB Cairo External Module Not Found debugging

/library/windows/desktop/ms684175%28v=vs.85%29.aspx On Sun, May 20, 2018 at 9:46 PM, Guillermo Polito <guillermopol...@gmail.com > wrote: > > > On Sat, May 19, 2018 at 1:37 PM, Peter Uhnák <i.uh...@gmail.com> wrote: > >> Hi, >> >> some Windows users are rep

Re: [Pharo-dev] LibFFI/NB Cairo External Module Not Found debugging

On Sat, May 19, 2018 at 1:37 PM, Peter Uhnák wrote: > Hi, > > some Windows users are repeatedly running into Pharo failing to load Cairo > library on Windows (see stack screenshot at the bottom). > > The problem is that I have no idea how to even start debugging this. > > Is

Re: [Pharo-dev] Pharo 7 Launch Failure - Freetype Problem?

/Pharo7.0-32bit-b901561.zip On Sun, May 20, 2018 at 7:48 PM, Guillermo Polito <guillermopol...@gmail.com > wrote: > I'd say it looks more like an FFI bug than a Freetype bug, but we should > investigate it... > > On Sat, May 19, 2018 at 3:26 PM, Sean P. DeNigris <s...@clip

Re: [Pharo-dev] Pharo 7 Launch Failure - Freetype Problem?

I'd say it looks more like an FFI bug than a Freetype bug, but we should investigate it... On Sat, May 19, 2018 at 3:26 PM, Sean P. DeNigris wrote: > Following the contribution instructions on the website [1] to review the PR > for issue 15230 [2], I downloaded the build

Re: [Pharo-dev] [Seaside-dev] Seaside loading broken in Pharo 7

On Sat, May 19, 2018 at 2:59 AM, Cyril Ferlicot D. wrote: > Le 18/05/2018 à 21:42, Sean P. DeNigris a écrit : > > Tim Mackinnon wrote > >> Hi what does it mean “Iceberg does not manage yet upgrade of the local > >> clones” > > > > This is most commonly encountered when

[Pharo-dev] [Ann] OSSubprocess 1.0.0

Hi all, News from the OSSubprocess side. For those who do not know it, OSSubprocess is the library to call external processes from Pharo. These are the main points of this release. - 64bits support - Issues Working on both Pharo 6 and 7 - Issue #34: Adding tests to validate that the return code

Re: [Pharo-dev] File/Stream changes: one Integer decoder/encoder to rule them all

On Fri, Apr 20, 2018 at 5:24 PM, Sven Van Caekenberghe wrote: > Hi, > > After the File and Stream changes in Pharo 7, a binary read, resp. write > stream from/to a file is actually a ZnBuffered(Read|Write)Stream on a > BinaryFileStream. You access these using

Re: [Pharo-dev] Problems with the removal of Nautilus

iewedDiffFor:of: #repairIcon >> #color #annotateRubricText: #notifyBanInitiatedFor:of: >> #notifyCritique:AutoFixedFor:)" >> >> I will check them and make the issue entries. >> >> -- Pavel >> >> 2018-05-04 13:08 GMT+02:00 Pavel Krivanek <pavel.k

Re: [Pharo-dev] File, FileHandle and FileReference

Even before the refactoring, FileHandle was just using opening a file using a MultiByteFileStream. Probably FileHandle was originally thought as a clean replacement/façade of the old streams? I don't know. On Thu, May 10, 2018 at 10:16 PM, Alistair Grant wrote: > In a

Re: [Pharo-dev] Fix Base64 madness for good

YESS! On Thu, May 10, 2018 at 10:33 PM, Norbert Hartl wrote: > > > > Am 10.05.2018 um 21:42 schrieb Sven Van Caekenberghe : > > > > Hi, > > > > I propose the following: > > > > https://pharo.manuscript.com/f/cases/21870/Fix-Base64-madness-for-good > >

Re: [Pharo-dev] Aboud CI test retries

On Fri, May 4, 2018 at 10:20 AM, Ben Coman <b...@openinworld.com> wrote: > > > On 3 May 2018 at 23:35, Guillermo Polito <guillermopol...@gmail.com> > wrote: > >> Hi all, >> >> Initially the pharo build had tests that were failing randomly. >> To

Re: [Pharo-dev] Problems with the removal of Nautilus

Can someone check this https://github.com/pharo-project/pharo/pull/1293 ? On Fri, May 4, 2018 at 10:19 AM, Guillermo Polito <guillermopol...@gmail.com > wrote: > Hi, > > I've just tried to create a new package in Calypso and I got bitten by > this: > > https://pharo.f

[Pharo-dev] Problems with the removal of Nautilus

Hi, I've just tried to create a new package in Calypso and I got bitten by this: https://pharo.fogbugz.com/f/cases/21804/Creating-a-Package-from-Calypso-produces-DNU Creating a new package was an extension of Nautilus, and was never introduced in RPackage. How should we procceed? How can we

Re: [Pharo-dev] Do we kill the catalog?

Just for the record https://pharo.fogbugz.com/f/cases/21825/Improve-Catalog-loading https://github.com/pharo-project/pharo/pull/1292 Feel free to review or to propose other PRs, Guille

[Pharo-dev] Aboud CI test retries

Hi all, Initially the pharo build had tests that were failing randomly. To cope with that, we introduced a retry of the tests. Nowadays, this situation is actually very rare. Tests that fail, fail always, and randomly failing tests are not seen so often... This means however, that in the case

Re: [Pharo-dev] [Ann] Iceberg 0.7.5

ferentiate them... > > Norbert > > > Am 03.05.2018 um 17:16 schrieb Guillermo Polito <guillermopol...@gmail.com > >: > > Time for the weekly Iceberg update. > > Iceberg 0.7.5. will be in the next Pharo build. > Thanks to all brave users, issue reporters and contributo

Re: [Pharo-dev] Failing tests

Exactly that :) https://pharo.fogbugz.com/f/cases/21822/Fix-Zn-Tests-due-to-encrypted-google-com-moving https://github.com/pharo-project/pharo/pull/1290 On Thu, May 3, 2018 at 5:18 PM, Sven Van Caekenberghe <s...@stfx.eu> wrote: > > > > On 3 May 2018, at 17:12, Guillermo Po

[Pharo-dev] [Ann] Iceberg 0.7.5

Time for the weekly Iceberg update. Iceberg 0.7.5. will be in the next Pharo build. Thanks to all brave users, issue reporters and contributors :). Key improvements: - Several improvements in metacello integration. (see #625, #664, #688 + more tests) - For those using CI, we think this release

[Pharo-dev] Failing tests

Hi all, There are a couple of Zn tests that are failing not even in the CI but locally in my machine. This happens because the tests are trying to do a request to encrypted.google.com and expecting a 200, but they are instead receiving: 301 Moved Permanently text/html >From the response, I

Re: [Pharo-dev] Pharo Bootstrap familiarity

Hi Ben, as Nicolas said, yes, MOP is for Meta Object Protocol (really nice book btw https://www.amazon.com/Art-Metaobject-Protocol-Gregor-Kiczales/dp/0262610744 ). Ben, the process is not carved in stone and we are fully aware that it can be enhanced :). Any enhancement, even the littlest one,

Re: [Pharo-dev] [ANN] ba-st Web Stack family gets a new member: Willow-Mixpanel and new releases

Thanks! On Tue, May 1, 2018 at 3:28 PM, Gabriel Cotelli wrote: > Hi, > > We're happy to announce a new member in the Web Stack family hosted at > https://github.com/ba-st/ : Willow-Mixpanel > . > > This is also a multi-release

Re: [Pharo-dev] self-backporting from P7 to P6.1

On Mon, Apr 30, 2018 at 12:19 PM, Peter Uhnák wrote: > > The idea is that people should do the opposite: code for Pharo7, while >> being in Pharo 6. >> > > Exactly. Several times I was put off contributing to P7, because I needed > a solution now, and not in year when P7 comes

Re: [Pharo-dev] self-backporting from P7 to P6.1

Esteban did some work on making a forward compatibility package for spec. github://pharo-contributions/Spec70Compatibility:v1.0.0/src The idea is that people should do the opposite: code for Pharo7, while being in Pharo 6. But that covers only Spec. We have to think if there is some automatic

[Pharo-dev] [Ann] Iceberg 0.7.4

Hi all, Time for the weekly Iceberg update. The next pharo build will include Iceberg 0.7.4, with many improvements done during this last week. Documentation wise, all documentation/workflow valid for 0.7.3 is still valid for 0.7.4. Thanks to all brave users, issue reporters and contributors :).

Re: [Pharo-dev] Is Beacon still planned to be added to P7?

On Mon, Apr 23, 2018 at 1:13 PM, Tudor Girba wrote: > I hope so. Beacon is ready to be integrated, but I do not know if there is > enough bandwidth right now due to the Iceberg work. > Well, if people issue a pull request I'll gladly review it. Guille > > Doru > > > On

Re: [Pharo-dev] Do we kill the catalog?

Hi all, I think that we are all aligned. Stef may be "too strong" in his way of talking, but he raised an issue: we should probably do an iteration on the catalog. And I think we all agree on that? So, what would be a list of tasks for it? (I copy past what Stef put before) - Use Metacello API.

Re: [Pharo-dev] Do we kill the catalog?

Hi all, IMHO, the problem is not metacello or gofer but the fact that the catalog uses the old Metacello API: i.e., Gofer new repository: 'zzz'; configurationOf: 'XXX'; load. (ConfigurationOfXXX project version: #YYY) load instead of the *new* Metacello API Metacello new repository:

Re: [Pharo-dev] Environment variables encoding ?

Hi, I think this problem is not environment variable exclusive. It also affects file paths and others. So far Pharo does not detect the locale to perform the encoding and it should be nice to do it. On Tue, Apr 17, 2018 at 10:56 AM, Henrik Sperre Johansen < henrik.s.johan...@veloxit.no> wrote:

Re: [Pharo-dev] DelayScheduler cleanup & Bootstrap

On Sun, Apr 15, 2018 at 3:19 PM, Ben Coman wrote: > I am doing a pass to cleanup the DelayScheduler hierarchy. > I'll be refactoring of the hierarchy to aid code understanding > and eliminate redundant instance variables from the original code. > The target structure is

Re: [Pharo-dev] Iceberg2.0 crash test passed :)

Is that Pharo 7? On Fri, Apr 13, 2018 at 9:43 PM, Serge Stinckwich < serge.stinckw...@gmail.com> wrote: > Yes I was able to commit also. > Very slick interface :-) > > > But now, every time I want to commit, my image crash and I have: > > Assertion failed: (git_atomic_get(__n_inits) > 0),

Re: [Pharo-dev] Iceberg2.0 crash test passed :)

I want your bug reports! Le ven. 13 avr. 2018 à 21:09, Stephane Ducasse a écrit : > I could commit my first commit with iceberg 2.0 > Well done > > It feels nicer :). > > Stef > > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et

Re: [Pharo-dev] [Pharo-users] [TechTalk] April 12: GIT with Iceberg

On Fri, Apr 13, 2018 at 7:34 PM, Ben Coman <b...@openinworld.com> wrote: > > > On 14 April 2018 at 01:10, Guillermo Polito <guillermopol...@gmail.com> > wrote: > >> >> >> On Fri, Apr 13, 2018 at 5:57 PM, Ben Coman <b...@openinworld.com> wrote:

Re: [Pharo-dev] [Pharo-users] [TechTalk] April 12: GIT with Iceberg

On Fri, Apr 13, 2018 at 5:57 PM, Ben Coman <b...@openinworld.com> wrote: > > > On 13 April 2018 at 23:15, Alistair Grant <akgrant0...@gmail.com> wrote: > >> On 13 April 2018 at 17:07, Cyril Ferlicot <cyril.ferli...@gmail.com> >> wrote: >> >

Re: [Pharo-dev] [Pharo-users] [TechTalk] April 12: GIT with Iceberg

On Fri, Apr 13, 2018 at 5:38 PM, Alistair Grant <akgrant0...@gmail.com> wrote: > Hi Guille, > > On 13 April 2018 at 17:29, Guillermo Polito <guillermopol...@gmail.com> > wrote: > > > > > > On Fri, Apr 13, 2018 at 5:15 PM, Alistair Grant <akgrant0..

Re: [Pharo-dev] [Pharo-users] [TechTalk] April 12: GIT with Iceberg

On Fri, Apr 13, 2018 at 5:15 PM, Alistair Grant <akgrant0...@gmail.com> wrote: > On 13 April 2018 at 17:07, Cyril Ferlicot <cyril.ferli...@gmail.com> > wrote: > > > > > > On ven. 13 avr. 2018 at 17:03, Guillermo Polito < > guillermopol...@

Re: [Pharo-dev] [Pharo-users] [TechTalk] April 12: GIT with Iceberg

On Fri, Apr 13, 2018 at 4:26 PM, Ben Coman wrote: > > > On 13 April 2018 at 21:14, Marcus Denker wrote: > >> >> >> On 13 Apr 2018, at 15:04, Andrei Stebakov wrote: >> >> Can you make the video available online? >> >> >>

Re: [Pharo-dev] Images, VMs and 32 vs 64bit

VMs share most of the code. At least the basic interpreter, primitives and garbage collector. But there are some platform specificities such as how some plugins are managed. Also there are different JIT backends, one per platform. I don't know if a VM comes shipped with all of them or just the one

Re: [Pharo-dev] help wanted: normalising LF on tonel for Pharo project

Both, the checkbox will be used to set the property in disk at some point :). On Tue, Apr 10, 2018 at 11:55 PM, Esteban Lorenzano <esteba...@gmail.com> wrote: > or a .iceberg file? > > Esteban > > ps: yep, we need it… we will have it, why not start now? > > On 10 Ap

Re: [Pharo-dev] help wanted: normalising LF on tonel for Pharo project

It could be a checkbox in the "create repository dialog". "Use lf as default line ending" (and set it to true by default (?)) On Tue, Apr 10, 2018 at 11:50 PM, Peter Uhnák wrote: > An argument can be made that Pharo would _always_ produce LF. > I don't think I've ever

Re: [Pharo-dev] help wanted: normalising LF on tonel for Pharo project

I'd say yes? https://github.com/libgit2/libgit2/commit/b83fd07880307106deb0ac7cb0d415d85c27f465 ? On Tue, Apr 10, 2018 at 11:42 PM, Guillermo Polito < guillermopol...@gmail.com> wrote: > Yes, that is the thing. Is libgit reading that properties file or not? > I'll do some digging.

Re: [Pharo-dev] help wanted: normalising LF on tonel for Pharo project

Yes, that is the thing. Is libgit reading that properties file or not? I'll do some digging.. On Tue, Apr 10, 2018 at 11:31 PM, Peter Uhnák wrote: > > Git for Windows even asks you if you want to automatically convert CRLF > > to LF during checkin and back to CRLF on

Re: [Pharo-dev] Loading code with iceberg

Hi Javier, you should register your repository, otherwise it will be just garbage collected: [[[ myRepository register. ]]] On Sun, Apr 1, 2018 at 4:57 PM, Javier Pimás wrote: > We are loading some code using Iceberg API in pharo6.1. That works fine, > the problem

Re: [Pharo-dev] Build 739 breaks project load initialization order?

PR: https://github.com/pharo-project/pharo/pull/1161 I added a test to avoid this problem in the future. Guille On Thu, Mar 29, 2018 at 9:36 AM, Guillermo Polito <guillermopol...@gmail.com > wrote: > Issue: https://pharo.manuscript.com/f/cases/21658/ > Monticello-initializers-are

Re: [Pharo-dev] Build 739 breaks project load initialization order?

Issue: https://pharo.manuscript.com/f/cases/21658/Monticello-initializers-are-not-enabled-by-default On Thu, Mar 29, 2018 at 9:33 AM, Guillermo Polito <guillermopol...@gmail.com > wrote: > I'm checking it. > > It may be a side effect of: https://github.com/pharo- > proje

Re: [Pharo-dev] Build 739 breaks project load initialization order?

I'm checking it. It may be a side effect of: https://github.com/pharo-project/pharo/pull/1130 Short story long: - building Pharo we need to ensure that class initializations are executed in a particular order, so some metacello configurations are disabling monticello initializers during

Re: [Pharo-dev] Experiment: New Download page based on Pharo Launcher

On Fri, Mar 23, 2018 at 7:53 PM, Ben Coman wrote: > > > On 23 March 2018 at 11:31, Ben Coman wrote: > >> >> >> On 23 March 2018 at 05:14, Cédrick Béler wrote: >> >>> Hi, >>> >>> I just saw students and they still have some problem

Re: [Pharo-dev] Pavel's ChangeLog week of 2018-03-19

Can't we make Extensions first class objects in ring? On Mon, Mar 26, 2018 at 11:02 AM, Pavel Krivanek wrote: > 2018-03-26 10:52 GMT+02:00 Stephane Ducasse : > > Pavel > > > > Why we do not know if this is a class or trait? > > Imagine that you

Re: [Pharo-dev] [pharo-project/pharo] 21646 AbstractFileReference should use "utilities" protocol name (#1149)

Hi Torsten, I like all this cleanups and recategorizations. But I have two requests, tell me what you think: - first and more important. I'd like that we define a convention document in a wiki page or pillar document for protocols. What are the correct protocols to use and why? This is

Re: [Pharo-dev] Experiment: New Download page based on Pharo Launcher

If the launcher had a command line interface, I'd use it all the time :) On Tue, Mar 20, 2018 at 10:15 AM, Marcus Denker wrote: > Hi, > > > I'm really glad PharoLauncher has been promoted to the download page, > but it seems some people want to push PharoLauncher to *be*

Re: [Pharo-dev] New Files in Pharo - Migration Guide, How To's and examples

Yes, it would be good to have those kind of methods. But there are some other constraints to have into account :) - introducing these without introducing duplications is right now complicated because streams do not share a hierarchy - having a common hierarchy is maybe complicated: ZnStreams

[Pharo-dev] New Files in Pharo - Migration Guide, How To's and examples

Hi all, I've put some minutes summarizing the new APIs provided by the combination of the new File implementation and the Zn encoders. They all basically follow the decorator pattern to stack different responsibilities such as buffering, encoding, line ending convertions. Please, do not hesitate

Re: [Pharo-dev] pharo bootstrap is in inconsistent state

On Mon, Mar 19, 2018 at 2:13 PM, Alistair Grant <akgrant0...@gmail.com> wrote: > Hi Guille, > > On 19 March 2018 at 13:59, Guillermo Polito <guillermopol...@gmail.com> > wrote: > > Hi! > > > > On Mon, Mar 19, 2018 at 9:17 AM, Alistair Grant <ak

Re: [Pharo-dev] pharo bootstrap is in inconsistent state

Hi! On Mon, Mar 19, 2018 at 9:17 AM, Alistair Grant wrote: [SNIP] > > https://pharo.fogbugz.com/f/cases/21615/Separate-bootstrap-process-in-to- > distinct-stages > > https://github.com/pharo-project/pharo/pull/1127 > > This does the first step of breaking the bootstrap

Re: [Pharo-dev] Performances of source code search on latest Pharo

Yes, looking at the stack in the profiler, there is a buffered stream missing in there. The thing is that source/changes file reading/writing required special attention in the migration (or the image became unusable :)). I'll fix it tomorrow first thing in the morning, if you can wait a couple of

Re: [Pharo-dev] Pharo 7 new file stream encoders

That should be fixed now. I proposed also the rename. I can revert it if needed. On Fri, Mar 16, 2018 at 1:04 PM, Sven Van Caekenberghe <s...@stfx.eu> wrote: > > > > On 16 Mar 2018, at 11:29, Guillermo Polito <guillermopol...@gmail.com> > wrote: > > >

Re: [Pharo-dev] FileHandle creates a buffered stream on a buffered stream

Nice catch. The write stream is well defined in comparison. https://pharo.fogbugz.com/f/cases/21604/FileHandle-creates-a-buffered-stream-on-a-buffered-stream https://github.com/pharo-project/pharo/pull/1118 Can somebody review please? Tx, Guille On Thu, Mar 15, 2018 at 4:00 PM, Sven Van

Re: [Pharo-dev] Pharo 7 new file stream encoders

Thierry, Sven, Can you review https://github.com/pharo-project/pharo/pull/1116 ? Tx, Guille On Fri, Mar 16, 2018 at 11:29 AM, Guillermo Polito < guillermopol...@gmail.com> wrote: > Hi, > > Yes, I'll provide a PR with that functionality soon. Probably in that case > *ZnCrP

Re: [Pharo-dev] Pharo 7 new file stream encoders

Hi, Yes, I'll provide a PR with that functionality soon. Probably in that case *ZnCrPortableWriteStream* is not the right name for that class. Sven, do you think renaming it now (before it has lots of users) would be acceptable towards backwards compatibility? Otherwise I would name it

Re: [Pharo-dev] Epicea changes broken in latest 7

I cannot reproduce it from here... does your file have non-ascii characters? On Wed, Mar 14, 2018 at 10:55 AM, Sven Van Caekenberghe wrote: > World Menu > Tools > Code Changes > > click on any change, boom. > > [ :error | > (OmFileStoreReadingError > readingError: error >

Re: [Pharo-dev] cannot write to the changes file

Yes, the changes files were being opened twice, and the second time it failed :). On Tue, Mar 13, 2018 at 11:11 PM, Cyril Ferlicot D. < cyril.ferli...@gmail.com> wrote: > Le 13/01/2018 à 18:03, Ben Coman a écrit : > > > > Great! That was quick work (thanks Pavel.) > > Do you have an issue for me

Re: [Pharo-dev] MCMczWriter>>#flush breaks

On Tue, Mar 13, 2018 at 8:08 PM, Sven Van Caekenberghe wrote: > Hi, > > I was trying to merge in Zinc changes from the latest Pharo 7 back to the > MC Zinc repos. It seems like MCMczWriter>>#flush breaks [1]. I can save to > the package cache but not to an Http repo, nor copy to

Re: [Pharo-dev] Error opening Zinc MC repository in latest Pharo 7

that, is to create a pharo repository. That should "bind" the proxy version infos... On Tue, Mar 13, 2018 at 3:40 PM, Sven Van Caekenberghe <s...@stfx.eu> wrote: > Well it is so magic that I do not understand what is happening ... > > > On 13 Mar 2018, at 15:32, Gu

Re: [Pharo-dev] Error opening Zinc MC repository in latest Pharo 7

Ah, that's Iceberg's magic proxies I think :/ On Tue, Mar 13, 2018 at 3:05 PM, Sven Van Caekenberghe wrote: > For some reason I can no longer open Zinc's old school MC repository in > Pharo-7.0+alpha.build.690.sha.ffd58dcc88a0698be21b52b565a86316799cb25d > (32 Bit) > >

Re: [Pharo-dev] Loading configuration of spur

ncoder class>>#isExtension: which seems to have been removed from > the image. It is a bit different to typical doesNotUnderstand errors > because it opens an emergency evaluator and leaves the image unusable. > > On Mon, Mar 12, 2018 at 6:10 AM, Guillermo Polito < > guillermopol...@g

Re: [Pharo-dev] Loading configuration of spur

Hi, I'll Esteban answer better but I don't know if that VMMaker mirror is up to date. Taking a look at the images/newImage.sh script, it is using Pharo5.0. But I see no reason for it not working on latest versions. Probably some patches are required... What is your error? On Sun, Mar 11, 2018

[Pharo-dev] generated webdoc?

Hi all, I know that we had before the generated webdoc from pharo releases in the file server (files.pharo.org). But I cannot see it anymore. Do we still have it hosted somewhere? We were planning to use it as online material for a course. I know that it is mostly not needed, but newby students

Re: [Pharo-dev] Released versions in Pharo Bootstrap

Hi Dale! On Mon, Mar 5, 2018 at 8:07 PM, Dale Henrichs < dale.henri...@gemtalksystems.com> wrote: > > > On 03/05/2018 09:07 AM, Guillermo Polito wrote: > >> On the other side, there is the fact that Metacello baselines are so far >> nice to describ

Re: [Pharo-dev] Released versions in Pharo Bootstrap

t; 2018-03-05 17:17 GMT+01:00 Denis Kudriashov <dionisi...@gmail.com>: > >> 2018-03-05 17:02 GMT+01:00 Cyril Ferlicot <cyril.ferli...@gmail.com>: >> >>> >>> On Mon, Mar 5, 2018 at 4:51 PM, Guillermo Polito < >>> guillermopol...@gmail.com&

Re: [Pharo-dev] Released versions in Pharo Bootstrap

> Commander. And ClassAnnotation will be in Kernel. > So we will need to load them in another time than Calypso. > > Now we can just put them directly into #loadCalypso method. (there are > three dependencies) > It will fix my problem and make Pharo build reproducible. > >

Re: [Pharo-dev] Released versions in Pharo Bootstrap

On Mon, Mar 5, 2018 at 4:45 PM, Cyril Ferlicot <cyril.ferli...@gmail.com> wrote: > > On Mon, Mar 5, 2018 at 4:38 PM, Guillermo Polito < > guillermopol...@gmail.com> wrote: > >> But, "one single class" does not mean anything. Because it depends from &

Re: [Pharo-dev] Released versions in Pharo Bootstrap

But, "one single class" does not mean anything. Because it depends from which branch/commitish you are loading it from... Can you explain better what is the problem because I am not getting it... In any case, independently of where is the burden, I want to veto any new integration that may make

Re: [Pharo-dev] [Vm-dev] OSSubprocess 0.2.5 fails in Pharo 6.1 64 bits (macOS)

Hmm, wait, I think these are two different issues :) I managed to successfully use OSSubprocess in 64bits with some tweaks. The problem is that OSSubprocess does some manual type coertions like assumming 32 bits: collectArgumentPointersInto: aPointer [...] aPointer nbUInt32AtOffset:

Re: [Pharo-dev] [Vm-dev] OSSubprocess 0.2.5 fails in Pharo 6.1 64 bits (macOS)

I'll try making a PR now to fix that. On Mon, Feb 26, 2018 at 10:19 AM, Guillermo Polito < guillermopol...@gmail.com> wrote: > Hmm, wait, I think these are two different issues :) > > I managed to successfully use OSSubprocess in 64bits with some tweaks. The > problem is that

Re: [Pharo-dev] "curl https://get.pharo.org/64 | bash" does not work (on Mac)

These pages are wrong (at least): http://pharo.org/download https://pharo.org/gnu-linux-installation-64 https://pharo.org/gnu-linux-installation On Sun, Feb 25, 2018 at 9:36 PM, Stephane Ducasse wrote: > which page? > >

Re: [Pharo-dev] Pull Request 20898-MultiByteFileStream-upToAll-does-not-work-correctly-with-UTF-8

Well, It looks like when you read tonel files with your changes there are some "invisible" characters left over in the stream. I think that first you should be able to reproduce the issue locally without bootstrapping by trying to import a tonel file in an image with your changes. Just take any

Re: [Pharo-dev] Monticello file out bug during bootstrap

Hi Alistair, Can you provide some more context on what are you trying to do and how? Generally you should not change anything in the bootstrap, just modify the classes you want to modify and commit them into the repository. The bootstrap will take care of it. The only cases when you need to

Re: [Pharo-dev] #valueWithPossibleArgs:, #valueWithEnoughArguments:, and #cull:

++999^1000 :) On Fri, Feb 23, 2018 at 7:32 AM, Stephane Ducasse wrote: > Thanks Sven > I thought that suddenly I was an idiot. > > > On Thu, Feb 22, 2018 at 11:47 AM, Sven Van Caekenberghe > wrote: > > > > > >> On 22 Feb 2018, at 10:41, Clément Bera

Re: [Pharo-dev] VirtualMachine vs. Platform and Bootstrap

On Fri, Feb 16, 2018 at 10:18 AM, Torsten Bergmann wrote: > Hi, > > 1. We can query for the VIRTUAL MACHINE and ask if it is 32 or 64 bit > (internally depending on wordSize): > > Smalltalk vm is32Bit > >Anything OK on that side. > > 2. We can also query for the

Re: [Pharo-dev] Iceberg experience report - synchronising README change made on github

On Thu, Feb 8, 2018 at 6:28 AM, Ben Coman wrote: > Could the Iceberg gurus try and comment on the following workflow. > > Please familiarise with the first four commits here... > https://github.com/Traadh/cloudflareun/network > > from these actions... > > "first commit" --

Re: [Pharo-dev] Cleaning up... baseClass, instanceSide, theNonMetaclass

In my code I use to use instanceSide and classSide. don't know why. Maybe they are clearer to me? On Sun, Feb 11, 2018 at 8:59 PM, Denis Kudriashov wrote: > 2018-02-11 18:14 GMT+01:00 Stephane Ducasse : > >> Hi >> >> We already got this discussion

Re: [Pharo-dev] git workflow (iceberg) and monticello packages

On Sun, Feb 4, 2018 at 11:07 PM, Nicolai Hess wrote: > Hi , > > I am still not sure I understand the git based development workflow. > > I set up my image and repository as described by the guide. > > now, if new commits are in the pharo-project, iceberg shows the list of

Re: [Pharo-dev] git and author/timestamps, 10000's of files, etc.

On Sun, Jan 14, 2018 at 7:11 PM, Dale Henrichs < dale.henri...@gemtalksystems.com> wrote: > I've been skimming the ironically named "blame" thread and just want to > clear up some apparent misconceptions. > > git/github is not the reason that the author/timestamps information was > "lost" ...

Re: [Pharo-dev] How to restore image upgrade? was New Year Wishlist (2018) ?

On Tue, Dec 26, 2017 at 11:36 PM, Nicolas Cellier < nicolas.cellier.aka.n...@gmail.com> wrote: > > > 2017-12-25 23:54 GMT+01:00 Ben Coman : > >> As a half-way house, consider that "upgrade" scripts could be a good >> mechanism >> post-Release when changes should be

Re: [Pharo-dev] Replacement for deprected MultiByteFileStream?

On Tue, Jan 2, 2018 at 1:13 PM, Henrik Sperre Johansen < henrik.s.johan...@veloxit.no> wrote: > Stephane Ducasse-3 wrote > > Hi Bernhard > > > > Have a look at how guille started to implement File package. > > (Guille is actively converting all the image users of the old > > hierarchy but last

Re: [Pharo-dev] Updating CI plugins

Jenkins and slaves are up un running. Let's cross fingers hoping everything is ok :) Keep you updated On Fri, Dec 22, 2017 at 10:14 AM, Guillermo Polito < guillermopol...@gmail.com> wrote: > Christophe is also taking benefit of this to update jenkins from 2.32.3 > LTS to 2.89.2 LT

Re: [Pharo-dev] Updating CI plugins

Christophe is also taking benefit of this to update jenkins from 2.32.3 LTS to 2.89.2 LTS On Fri, Dec 22, 2017 at 10:06 AM, Guillermo Polito < guillermopol...@gmail.com> wrote: > Hi all, > > I'm updating CI plugins. *This will require a CI restart. *The > corresponding issue

[Pharo-dev] Updating CI plugins

Hi all, I'm updating CI plugins. *This will require a CI restart. *The corresponding issue is here: https://pharo.fogbugz.com/f/cases/20884/Update-CI-Plugins The installed versions are the following: Workspace Cleanup Plugin 0.34 0.33 SCM API Plugin 2.2.6 2.2.1 Pipeline Utility Steps 1.5.1

Re: [Pharo-dev] Does pharo build not retry anymore?

12 20:13 GMT+01:00 Pavel Krivanek <pavel.kriva...@gmail.com>: >>>>>> >>>>>>> Yes, with Marcus we decreased the retryTimes variable two weeks ago >>>>>>> to 1 because in that time the validations were in really bad shape and >>>>

Re: [Pharo-dev] Dictionary newFromKeys: andValues:

Yes I think this is good. On Fri, Dec 15, 2017 at 8:32 PM, Stephane Ducasse wrote: > Hi > > I was looking at the Dictionary instance creation API and I would like to > add > newFromKeys:andValues: > Because I do not see why I have to create associations when I have >

Re: [Pharo-dev] [Pharo 7.0-dev] Build #381: 20796-String-should-understand-readStreamDowriteStreamDo-to-be-polymorph-with-FileReference

On Sun, Dec 17, 2017 at 7:00 PM, Stephane Ducasse wrote: > Yes I check the code and since a collection already has readStream and > writeStream. > This is ok. I did not like the idea that we introduced this change just for the > sake of having strings polymorphic to

Re: [Pharo-dev] [Ann] New Calypso version 0.8

On Mon, Dec 18, 2017 at 9:56 AM, Denis Kudriashov wrote: > And I made new release v0.8.4 which solves performance problem. > I found very nice solution to ensures single Calypso UI update after > multiple changes from single UI command. > For example implementors window

[Pharo-dev] Does pharo build not retry anymore?

I see that we are retrying tests only once, which is causing most (if not all) pull requests to fail sporadically... Maybe it got lost because of a mistake? Also, I'd like that changes in the build process are discussed in the mailing list from time to time... I've put a lot of effort into

Re: [Pharo-dev] Release: Conveniently browse, deactivate and reactivate halts and breakpoints with the HaltManager

Ah this is cool I'm downloading it :) On Wed, Dec 6, 2017 at 11:03 AM, Thomas Dupriez < thomas.dupr...@ens-paris-saclay.fr> wrote: > Hello, > > I have developed a package to assist developers managing their halts and > breakpoints: HaltManager. > > HaltManager provides a window showing all the

<    1   2   3   4   5   6   7   8   >