[Pharo-dev] Re: Platform Packages vs. Git Branches

you've got a solution for > triggering multi-branch runs ... workflow per branch/platform ... so I will > HAVE TO CONSIDER the branch per platform approach again :) Yeah, not perfect, but it works (reusability isn't a focus of GitHub workflows...). > > Dale > > On Mon, Aug 29, 20

[Pharo-dev] Re: Platform Packages vs. Git Branches

Hi Sean, At some point you will probably come to the same point that Seaside and Fuel have reached in the past: build your own abstraction layer (Grease in Seaside, Fuel-Platform in Fuel). There are valid arguments against this approach but, personally, I didn't have another choice for Fuel.

[Pharo-dev] Re: [ANN] Fuel 5.0.0

On 28 Feb 2022, at 20:55, Marcus Denker wrote: >>> >>> Fuel for now just ignores the whole “First class Variable” concept and >>> serialises the “raw” view of indexed instance >>> variables… (which is the right thing to do now), but that would not work >>> here anymore. >> >> Good to know. I'll

[Pharo-dev] Re: [ANN] Fuel 5.0.0

On 28 Feb 2022, at 9:27, Marcus Denker wrote: >> On 27 Feb 2022, at 19:34, Max Leske wrote: >> >> Hi everyone, >> >> I'm happy to announce Fuel version 5.0.0 today. >> >> The changes to 4.0.0 aren't huge but I've had to adjust the format once

[Pharo-dev] Re: Talents - VM Crash on P9 after Fuel Materialization

Hi Sean, I would assume that it's a Fuel issue. I've opened an issue on GitHub: https://github.com/theseion/Fuel/issues/262 Cheers, Max On 24 Feb 2022, at 17:32, s...@clipperadams.com wrote: > After serializing and then materializing an object with a talent, the trait's > instVar seems to

[Pharo-dev] Re: PTerm - Can't Find FFI Library on M1 Mac on P9

Hey Sean, I can get a terminal to open (with a bit of manual intervention) and I can type some characters. So FFI calls appear to work but the application is pretty broken on P9. This is on a x86 MacBook Pro. Simply added the repo in Iceberg and loaded the baseline. Cheers, Max On 24 Feb

[Pharo-dev] Re: Fuel projects, anyone?

iel > > On Thu, May 27, 2021 at 5:09 PM Max Leske wrote: > >> Hi everyone, >> >> I was made aware that there actually *are* people who use Fuel :) I >> rarely get feedback, apart from the spare bug report, so I was thrilled to >> hear about people who u

[Pharo-dev] Fuel for Pharo 9 on the way

Hi Just wanted to give you a heads up that I'm working on a new release of Fuel for Pharo 9. Should be done soon. Is there still time to get it integrated or are we in hard freeze already (the currently loaded version has several test failures)? Cheers, Max signature.asc Description:

Re: [Pharo-dev] Pharogenesis?

Hi Michael, That's my project :) This is the link to the repository: https://github.com/theseion/pharogenesis. I should have all the sources etc. if you need anything else. Cheers, Max On 14 May 2020, at 3:59, Michael Rueger wrote: > Hi all, > > after digging out some old pet project about

Re: [Pharo-dev] FullBlockClosure - How to create one...

Oh, interesting! I did not know that, thanks Eliot. On 1 May 2020, at 18:49, Eliot Miranda wrote: > Hi Max, > > On Thu, Apr 30, 2020 at 11:51 PM Max Leske wrote: > >> Hi Sean, >> >> You *need* an outer context. See Context>>cleanCopy, which Fuel uses to

Re: [Pharo-dev] FullBlockClosure - How to create one...

Hi Sean, You *need* an outer context. See Context>>cleanCopy, which Fuel uses to serialize blocks. Cheers, Max On 1 May 2020, at 3:23, Sean P. DeNigris wrote: > What am I not understanding about FullBlockClosure? > > I have a clean block that I'd like to turn into a FullBlockClosure so that

Re: [Pharo-dev] Programmatically change display size in Pharo 8 / 9

NC for a full interactive IDE on a server. > > But maybe you have other reasons to go in that direction. > > Sven Thanks for you thoughts. Cheers, Max > >> On 24 Apr 2020, at 10:51, Max Leske wrote: >> >> Hi all, >> >> I'm trying to change the

[Pharo-dev] Programmatically change display size in Pharo 8 / 9

Hi all, I'm trying to change the size of the display programmatically but am having some trouble. It used to be possible to do `Display setExtent: 50@50 depth: 16` and that would take care of everything. I can still do that but 1. the renderer reverts the changes immediately and 2. if I

Re: [Pharo-dev] Updated Fuel version for Pharo 8

) :) >> >> Esteban >> >> >>> On 8 Mar 2020, at 16:35, Max Leske wrote: >>> >>> Hi folks, >>> >>> I just released Fuel 3.0.2 and I'd like to update the current version in >>> Pharo 8 to the new one. I know I'm past the Pha

[Pharo-dev] Updated Fuel version for Pharo 8

Hi folks, I just released Fuel 3.0.2 and I'd like to update the current version in Pharo 8 to the new one. I know I'm past the Pharo 8 release date, so I guess it won't happen but I thought I'd ask anyway. There are no functional changes in 3.0.2 but I've updated the platform (it's currently

Re: [Pharo-dev] Doing the equivalent of "fast forward" with Iceberg

Hi Eliot, First, save your image ;) Then you should be able to fetch the changes from remote, if you haven't done so yet, and then *merge*. That should apply the changes without distroying your existing changes. You'll also get a chance to review and select the changes that will be applied

Re: [Pharo-dev] Fuel Not Serializing Stateful Traits

Hi, As I wrote to Sean on Discord, Marcus fixed that bug during ESUG. I realize now, however, that it is only fixed in Pharo 8. I would need to write a patch for Fuel to make it work in Pharo 7. Alternatively, you could include the patch in your code, then Fuel should work. Cheers, Max

Re: [Pharo-dev] Changes proposal on Pre debugger

On 10 Jul 2019, at 20:21, Cyril Ferlicot D. wrote: Hi, After talking with Steven (in copy) we agreed on possible improvements around the pre debugger. I would like to share our vision and check if the community agrees. The community agrees! ;) Context: The pre debugger is the window

Re: [Pharo-dev] Read-only image mode

Awesome! Thanks! On 9 Jul 2019, at 14:28, Pavel Krivanek wrote: > Hi, > > the current Pharo cannot deal very well in situations when you want to run > multiple instances from one image file, especially on Windows, which > complicates the setup of parallel applications. It is not able to work >

Re: [Pharo-dev] how implement isAbstract?

On 30 Mar 2019, at 21:05, Denis Kudriashov wrote: We can also look into it from the other side. All these methods are definitely a kind of code duplication. I think what we need here is an explicit property for classes. It could be even part of class definition. I'm not sure whether that's

Re: [Pharo-dev] how implement isAbstract?

On 30 Mar 2019, at 20:56, Denis Kudriashov wrote: > Hi Max. > > сб, 30 мар. 2019 г. в 19:08, Max Leske : > >> Hi Denis, >> >> I'm not too happy with any of those. For my own applications I use the >> following: >> >> isAbstract >> ^ self su

Re: [Pharo-dev] how implement isAbstract?

Hi Denis, I'm not too happy with any of those. For my own applications I use the following: isAbstract ^ self subclasses notEmpty and: [ (self class localSelectors includes: #isReallyAbstract) not or: [ self isReallyAbstract ] ]

Re: [Pharo-dev] Questions about DebugSession>>isContextPostMortem:

On 21 Mar 2019, at 11:06, Thomas Dupriez wrote: Hi Thomas, Hello, While looking at the DebugSession>>isContextPostMortem: method (code below), I got three questions: 1) There is a check for whether the suspendedContext (top context) of the process is nil. Does it even make sense for a

Re: [Pharo-dev] Weird SUnit/TestRunner behavior

) and the image keeps growing like crazy. I can tell you for my experience that in our case it gets easily to GB-sized images, and the GC is not very happy with this. Indeed. On Tue, Mar 19, 2019 at 12:04 PM Attila Magyar wrote: Max Leske wrote To answer your question: yes that has been

Re: [Pharo-dev] Weird SUnit/TestRunner behavior

To answer your question: yes that has been the case for a long time. The same is true for #runCase BTW. Only #setUp is sent after #tearDown (see #prepareToRunAgain). Max On 18 Mar 2019, at 14:05, Attila Magyar wrote: Thanks, I added the ticket. -- Sent from:

Re: [Pharo-dev] OSProcess for Pharo 7

executable output to run a generation command) On 14 Mar 2019, at 16:38, ducasse wrote: On 14 Mar 2019, at 17:33, Max Leske wrote: On 13 Mar 2019, at 11:55, ducasse wrote: Ok now one of these days we will have to have all the important libraries hosted in the same place. It is not sure

Re: [Pharo-dev] OSProcess for Pharo 7

Mar 2019, at 08:00, Max Leske wrote: Hi all, Pharo 7 no longer includes #ifNotNilDo:, meaning that OSProcess loading fails. I volunteer to update OSProcess for Pharo 7 but I need someone to tell me what the expected workflow is. AFAICT, we've simply copied the current ConfigurationOf

Re: [Pharo-dev] OSProcess for Pharo 7

. I assume that there will be some objections to that (e.g. because of loading in Squeak?) and we (I at least) don't want to maintain a fork / mirror on Github. Pulling from SqueakSource works fine for now. Max Let me know if it helps. Stef On 11 Mar 2019, at 08:00, Max Leske wrote: Hi

Re: [Pharo-dev] OSProcess for Pharo 7

) don't want to maintain a fork / mirror on Github. Pulling from SqueakSource works fine for now. Max Let me know if it helps. Stef On 11 Mar 2019, at 08:00, Max Leske wrote: Hi all, Pharo 7 no longer includes #ifNotNilDo:, meaning that OSProcess loading fails. I volunteer to update

Re: [Pharo-dev] #currentWorkingDirectoryPath is not correct on macOS when using drag and drop to open

On 8 Mar 2019, at 8:33, Alistair Grant wrote: Hi Max, On Fri, 8 Mar 2019 at 08:21, Max Leske wrote: Hi, OSPlatform>>currentWorkingDirectoryPath (used by Path>>workingDirectory, used by Metacello to resolve local paths) always answers '/' for me when I drag the image onto th

[Pharo-dev] #currentWorkingDirectoryPath is not correct on macOS when using drag and drop to open

Hi, OSPlatform>>currentWorkingDirectoryPath (used by Path>>workingDirectory, used by Metacello to resolve local paths) always answers '/' for me when I drag the image onto the VM to open. I'm sure that's a "feature" of macOS but it's very annoying. In addition, FileLocator imageDirectory

Re: [Pharo-dev] Apparently Zodiac plugin can crash VM on Linux

to fix this would be to make ZnClient work with openssl 1.1 Max On 16 Jan 2019, at 16:37, Sven Van Caekenberghe wrote: On 16 Jan 2019, at 16:28, Max Leske wrote: On 15 Jan 2019, at 22:59, Sven Van Caekenberghe wrote: Doing HTTPS client calls is part of the standard test suite, so

Re: [Pharo-dev] [Glass] Bug in Regex?

me know. Great. I'll take a look when I get a chance. > > [1] https://github.com/pharo-project/pharo/issues/2679 > > Cheers, > > > On Thu, Feb 21, 2019 at 10:44 AM Max Leske wrote: > >> On 21 Feb 2019, at 13:40, Mariano Martinez Peck wrote: >> >>&

Re: [Pharo-dev] [Glass] Bug in Regex?

one knows a bit more the history here? Thanks On Thu, Feb 21, 2019 at 5:18 AM Max Leske wrote: Hi Mariano, Yes, there is indeed such a bug (if it hasn't been fixed in an update to VBRegex that is). The bug is simple to work around though, as all you have to do is sort your branch (|) ter

Re: [Pharo-dev] [Glass] Bug in Regex?

Hi Mariano, Yes, there is indeed such a bug (if it hasn't been fixed in an update to VBRegex that is). The bug is simple to work around though, as all you have to do is sort your branch (|) terms by length. Here's the comment I've written for a regex generating method is use: " The sorting

Re: [Pharo-dev] Can't Install Launcher on Mac Mojave

Yeah. I hadn't realized that you were launching Iceberg *within* launcher. I launched an image first and then opened Iceberg in there. Max On 14 Feb 2019, at 23:26, Christophe Demarey wrote: Le 14 févr. 2019 à 22:34, Sean P. DeNigris a écrit : demarey wrote Probably because the email

Re: [Pharo-dev] Can't Install Launcher on Mac Mojave

I downloaded it again, extracted it to /Applications, ran Pharo7-64bit and opened Iceberg without issues. Launcher created the working directory at ~/Documents/Pharo, which should be fine w.r.t. permissions. I'm out of ideas... On 13 Feb 2019, at 19:23, Sean P. DeNigris wrote: Max Leske

Re: [Pharo-dev] Can't Install Launcher on Mac Mojave

Nope. I downloaded launcher just 20 minutes ago on Mojave and am using it without problems. Where did you extract it to? Did you extract it as a different user? Did you try to run it from within the .dmg directly? Max On 13 Feb 2019, at 3:42, Sean P. DeNigris wrote: Just dl-ed launcher

Re: [Pharo-dev] Apparently Zodiac plugin can crash VM on Linux

with a fresh image? i.e. you can also reprocude it with a fresh image, right? @embee yes On 15 Jan 2019, at 22:20, Max Leske wrote: Hi, I'm writing on behalf of Martin (eMBee) who's experiencing crashes when using SSL. You can find a VM crash stack trace here: http

Re: [Pharo-dev] A problem with latest image (64bit) ? (Please confirm)

Actually, I think it's rather a VM problem...? On 15 Jan 2019, at 12:30, Esteban Lorenzano wrote: Hello, I’m experiencing a problem with latest image (and latest vm) in Mac (Mojave). After doing Stdio stdout << ‘OK’ I’m having this stack: File class(ProtoObject)>>primitiveFailed: File

Re: [Pharo-dev] A problem with latest image (64bit) ? (Please confirm)

I've been seeing this in the early Pharo 7 builds. But it didn't occur with latest VM's, only with SmalltalkCI, so I ignored it. On 15 Jan 2019, at 12:30, Esteban Lorenzano wrote: Hello, I’m experiencing a problem with latest image (and latest vm) in Mac (Mojave). After doing Stdio stdout

Re: [Pharo-dev] Problem with zinc 2.9.2

Ancestors: Zinc-FileSystem-SvenVanCaekenberghe.16 Bugfix to ZnFileSystemUtils class>>#newBinaryFileNamed:do: we must ensure that the binaryStream opened here is closed as well (thx Max Leske for the bug hunting and fix) === The method in question now look as follows: newBinaryFileNamed: fi

Re: [Pharo-dev] Problem with zinc 2.9.2

by ZnClient after loading Zinc-HTTP-SvenVanCaekenberghe.472, which is being loaded by version 2.9.1 of ConfigurationOfZincHTTPComponents. Cheers, Max On 21 Jul 2018, at 17:21, Max Leske wrote: Just to be safe, I'll redo my experiment and get back to you. On 21 Jul 2018, at 16:59, Sven Van

Re: [Pharo-dev] Problem with zinc 2.9.2

there is nothing nothing to see here ... and I have the impression we are all talking about different things. On 21 Jul 2018, at 14:18, Max Leske wrote: On 21 Jul 2018, at 12:07, Norbert Hartl wrote: Max, what do you think will be a proper fix for this? I cannot see if this is a vm problem

Re: [Pharo-dev] Problem with zinc 2.9.2

a method or setting that allows the user to specify the expected behaviour. I do not think that this should be handled by the VM plugin or the stream class, as there are indeed different behaviours that make sense. Cheers, Max Norbert Am 14.07.2018 um 08:25 schrieb Max Leske : Hi Nicolas

Re: [Pharo-dev] ZnUnicodeComposingReadStream?

t 10:50:36PM +0200, Max Leske wrote: Hi Alistair, *nix systems usually come with the iconv[1] command line program that implements the normalization and denormalization algorithms, or Uconv 2, a library that does the same thing. These algorithms include a lot of black magic and I recom

Re: [Pharo-dev] Problem with zinc 2.9.2

/opensmalltalk-vm/pull/271 On 12 Jul 2018, at 23:19, Nicolas Cellier wrote: Isn't there a recent PR on opensmalltalk that address just this? Le jeu. 12 juil. 2018 à 23:16, Max Leske a écrit : Hi Norbert, I was able to reproduce the problem and then identify the culprit, although what I don't yet

Re: [Pharo-dev] ZnUnicodeComposingReadStream?

I realize I got things mixed up a bit: Uconv is a program akin to Iconv. What we interface with is libicu. Max On 13 Jul 2018, at 22:50, Max Leske wrote: Hi Alistair, *nix systems usually come with the iconv[1] command line program that implements the normalization and denormalization

Re: [Pharo-dev] ZnUnicodeComposingReadStream?

Hi Alistair, *nix systems usually come with the iconv[1] command line program that implements the normalization and denormalization algorithms, or Uconv [2] (from ICU [3]), a library that does the same thing. These algorithms include a lot of black magic and I recommend to not make your hands

Re: [Pharo-dev] Problem with zinc 2.9.2

On 13 Jul 2018, at 13:37, Norbert Hartl wrote: Sven, for me the problem is only on linux Yes, exactly. The problem doesn't exist on macOS. I tested on Ubuntu 17.04 (32-bit). Norbert Am 13.07.2018 um 13:26 schrieb Sven Van Caekenberghe : On 12 Jul 2018, at 23:15, Max Leske wrote

Re: [Pharo-dev] Problem with zinc 2.9.2

Hartl wrote: Am 12.07.2018 um 08:05 schrieb Max Leske : On 11 Jul 2018, at 22:44, Norbert Hartl wrote: Hi Max, I constructed a case that fails exactly like I experience it. Could you try? Just unpack the attachment on a linux, set PHARO_VM env to your executable and execute build.sh I will.

Re: [Pharo-dev] Problem with zinc 2.9.2

Am 10.07.2018 um 09:17 schrieb Max Leske : On 10 Jul 2018, at 8:48, Norbert Hartl wrote: Max, thanks for taking the effort. No worries. Am 10.07.2018 um 08:37 schrieb Max Leske : I did my best to reproduce the issue but didn't have any luck. I really need access to a Linux VM to debug

Re: [Pharo-dev] Problem with zinc 2.9.2

On 10 Jul 2018, at 8:48, Norbert Hartl wrote: Max, thanks for taking the effort. No worries. Am 10.07.2018 um 08:37 schrieb Max Leske : I did my best to reproduce the issue but didn't have any luck. I really need access to a Linux VM to debug this. So I'm praying that Apple fixes

Re: [Pharo-dev] Problem with zinc 2.9.2

a chance that something goes wrong during download of the zip archive and that something may be tied to a difference in the versions of Zinc (although I still think that's unlikely). Cheers, Max On 9 Jul 2018, at 19:43, Norbert Hartl wrote: > Am 09.07.2018 um 19:10 schrieb Max Leske :

Re: [Pharo-dev] Problem with zinc 2.9.2

moment because I'm on the macOS beta and it won't start... Max On 9 Jul 2018, at 18:31, Norbert Hartl wrote: Hi Max, Am 09.07.2018 um 18:18 schrieb Max Leske : Hi Norbert, This is a bit of a guess, but it's possible that the archive that is downloaded from github is in Zip64

Re: [Pharo-dev] Problem with zinc 2.9.2

Hi Norbert, This is a bit of a guess, but it's possible that the archive that is downloaded from github is in Zip64 format and that the libraries for extracting Zip64 are missing on your Linux. That would of course contradict the experience that the same operation appears to work in 6.1.

Re: [Pharo-dev] Need help to get a list of Pharo projects with tests

Fuel: https://github.com/theseion/Fuel Seaside: https://github.com/SeasideSt/Seaside On 5 Jul 2018, at 16:31, Serge Stinckwich wrote: On Thu, Jul 5, 2018 at 3:24 PM Julien wrote: Hello Pharo community, I am currently working on detecting rotten tests in Pharo projects. Rotten tests are

Re: [Pharo-dev] Problem with zinc 2.9.2

On 4 Jul 2018, at 23:00, Norbert Hartl wrote: Am 04.07.2018 um 17:52 schrieb Max Leske : Hi Norbert, Where can I get my hands on that image that you say has no sender of #newBinaryFileNamed:do: in it? I cannot give away the image, sorry. I can try to reproduce it somehow. Do you expect

Re: [Pharo-dev] Problem with zinc 2.9.2

Hi Norbert, Where can I get my hands on that image that you say has no sender of #newBinaryFileNamed:do: in it? Max On 4 Jul 2018, at 17:30, Norbert Hartl wrote: I tried to see how hard it would be to load my current project in pharo7. Cyril helped me to see that I load an old version of

Re: [Pharo-dev] Fuel Error in Latest Launcher

Thanks Sean. On 21 Jun 2018, at 18:08, Sean P. DeNigris wrote: > Max Leske wrote >>> Where should this bug be reported? >>> https://github.com/theseion/Fuel/issues ? >> >> Yes, please. > > https://github.com/theseion/Fuel/issues/234 > > >

Re: [Pharo-dev] Fuel Error in Latest Launcher

On 21 Jun 2018, at 15:34, Sean P. DeNigris wrote: Eliot Miranda-2 wrote Looks like the bug is that Fuel is… Ah, glad we identified it! Where should this bug be reported? https://github.com/theseion/Fuel/issues ? Yes, please. - Cheers, Sean -- Sent from:

Re: [Pharo-dev] Fuel Error in Latest Launcher

Good on you! I don't need the information for Fuel, but if you discovered a compiler bug it would help to post the information. Max On 21 Jun 2018, at 5:54, Sean P. DeNigris wrote: Eliot Miranda-2 wrote could you post some more information? Hey guys, I solved my problem by

Re: [Pharo-dev] Fuel Error in Latest Launcher

Hi Sean, Is it possible that your compiled method has been corrupted? It's the compiler that chokes when Fuel tries to read #endPC, and the compiler should not choke on a well formed compiled method... (or ever for that matter?), Max On 20 Jun 2018, at 15:07, Sean P. DeNigris wrote:

Re: [Pharo-dev] Why do we have SmallDictionary?

Well, I can answer my own question: SmallDictionary is a lot more space efficient. I think the class comment should clarify the use case for SmallDictionary and mention the performance trade off. Max On 8 Jun 2018, at 8:46, Max Leske wrote: Hi, I was messing around with SmallDictionary

Re: [Pharo-dev] DateAndTime Offset Bug Proposal

Hi Sean, On 8 April 2018 at 15:33:11, Sean P. DeNigris (s...@clipperadams.com) wrote: I was bitten by this very annoying bug again. As most of us probably know due to the steady stream of confused ML posts in the past, the bug in summary is that we have an incomplete timezone implementation

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

>> - but all tests were green :D >> >> So I'll introduce a new test to verify that monticello initializers are >> enabled by default and check what the problem is. >> Keep you updated. >> >> >> On Thu, Mar 29, 2018 at 9:18 AM, Max Leske <maxle...@gm

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

I can confirm that class side #initialization is broken. Don't know since when though. Cheers, Max On 29 March 2018 at 08:28:00, Martin McClure (mar...@hand2mouse.com) wrote: Good to know. In my case, however, I'm always loading code into a fresh image where these classes don't previously

Re: [Pharo-dev] Iceberg Loading issue

Hi Vincent, Possibly a problem with updating FETCH_HEAD. Does it work when you perform only the pull operation from Pharo (i.e., check out the branch on the command line)? Cheers, Max On 26 January 2018 at 00:43:40, vincent.blond...@lamresearch.com ( vincent.blond...@lamresearch.com) wrote:

Re: [Pharo-dev] [IMPORTANT] PHARO CONTRIBUTION PROCESS UPDATED! PLEASE READ!

Hi Martin, What I do is 1. update local pharo repository on branch 'development' 2. add repository to Iceberg 3. create branch for phogbugz issue 4. make changes (e.g. load stuff from your project) 5. Note that you will have to handle addition and removal of packages separately: 5.1 addition:

Re: [Pharo-dev] Fuel - FLPharo6Platform in Pharo 7

Thanks Torsten, I'll make the update tomorrow ( https://github.com/theseion/Fuel/issues/227). Cheers Max On 11 January 2018 at 22:32:09, Torsten Bergmann (asta...@gmx.de) wrote: There is a class FLPharo6Platform with FLPharo6Platform isResponsibleForCurrentPlatform returning false in Pharo

Re: [Pharo-dev] Hello, Im and a litle confused. Can you help me get started please?

Hi, welcome to Pharo! This is the development list for Pharo; your question is better suited for the users list ( http://lists.pharo.org/mailman/listinfo/pharo-users_lists.pharo.org). There's also a very active Discord community: http://discord.gg/Sj2rhxn. As for documentation, there are loads

Re: [Pharo-dev] 1.0 largeIdentityHash fails on 64-bit Linux

That seems to fix it. SmallFloat64 needs to implement #basicIdentityHash with primitive 171. Thanks Eliot. On 7 January 2018 at 06:19:18, Eliot Miranda (eliot.mira...@gmail.com) wrote: Hi Ben, On Sat, Jan 6, 2018 at 8:47 PM, Ben Coman wrote: > With Linux 64 bit image >

Re: [Pharo-dev] loading from github changes lgit classes?

Without taking a closer look, those are probably auto generated methods. Max On 10 December 2017 at 12:13:08, Nicolai Hess (nicolaih...@gmail.com) wrote: How come, loading a github project writes strange code change entries for classes like LGitFetchOptions LGitRemoteCallbacks ... For

Re: [Pharo-dev] [Calypso] Toolbar and Statusbar Look - voting time

Right On 13 September 2017 at 18:08:26, Torsten Bergmann (asta...@gmx.de) wrote: Hi all, as you know Denis Kudriashov does a fantastic job in implementing the new Calypso system browser. The plan is that at some point in time will be a replacement for Nautilus in the standard image. Even if

Re: [Pharo-dev] Fuel Materialization Error

Hi Sean, That cluster has been renamed. Of course, that change should be reflected in different version numbers. Unfortunately, the version number in 6.1 is not correct (thanks for finding that; I've logged it here:

Re: [Pharo-dev] poor state of fuel

Hannes, In general it doesn't matter "how much" two images differ. What is relevant are the changes to the graph of objects that are part of a snapshot, and that includes changes to classes that are either part of the graph or have instances that are part of the graph. It is possible to reshape

Re: [Pharo-dev] poor state of fuel

, but they don't really say), is readable on OS X 64bit . So it seems like you must have found something unusual. Tim Sent from my iPhone On 29 Aug 2017, at 11:13, Max Leske <maxle...@gmail.com> wrote: Hi Norbert, We still maintain Fuel. I was not aware of the problem you describe. Could yo

Re: [Pharo-dev] poor state of fuel

. So it seems like you must have found something unusual. Tim Sent from my iPhone On 29 Aug 2017, at 11:13, Max Leske <maxle...@gmail.com> wrote: Hi Norbert, We still maintain Fuel. I was not aware of the problem you describe. Could you open an issue on github (https://github.com/th

Re: [Pharo-dev] poor state of fuel

Hi Norbert, We still maintain Fuel. I was not aware of the problem you describe. Could you open an issue on github (https://github.com/theseion/Fuel/issues) with a detailed explanation and, if possible, steps to reproduce the problem? Cheers, Max On 29 August 2017 at 11:04:34, Norbert Hartl

Re: [Pharo-dev] Can we have subclasses of Process?

I've used subclasses of process for the debugger stuff without problems. Max On 17 August 2017 at 14:05:14, Denis Kudriashov (dionisi...@gmail.com) wrote: Hi. Is it allowed to subclass Process? I remember that there were some problems with it but I could not find any information. Generally

Re: [Pharo-dev] [Ann] libssh2 binding for Pharo

Very cool! On 11 August 2017 at 16:02:55, Denis Kudriashov (dionisi...@gmail.com) wrote: Hi I just want share my little experiments with libssh2. I think somebody can be interested with it and maybe will improve what I did which is now in very raw and initial state. Libssh2 library is now

Re: [Pharo-dev] ZnEasy question

Hi Milton, >From the URL RFC (http://tools.ietf.org/html/rfc3986, relevant grammar attached below) it seems that 'https://' in indeed a valid path component. ZnUrl seems to remove empty segments (which '//' would be) but that is not correct according to the RFC (empty segments appear to be valid

Re: [Pharo-dev] Lots of "UTF8InvalidText: Invalid utf8 input detected" from OMBU

On 25 July 2017 at 22:55:19, Mariano Martinez Peck (marianop...@gmail.com) wrote: Guys, I am getting "UTF8InvalidText: Invalid utf8 input detected" quite frequently on Pharo 6.0 which come from ombu background job. Has anything seen this too? Quite annoying... Yes, I've seen it a couple of

Re: [Pharo-dev] FileSystem file attributes and #isSymlink patch

Nice work Alistair! On 24 July 2017 at 10:10:09, Alistair Grant (akgrant0...@gmail.com) wrote: Hi All, I'm nearly ready to submit a patch that started with the goal of being able to retrieve the device id and fixing FileReference>>isSymlink and also follows Esteban's suggestion of splitting

Re: [Pharo-dev] Automatic Refactoring Disranging Seaside Rest Methods

As Gabriel notes, it looks like your missing the .sources file. I don't know what pharocloud supports, but you could try packaging your image and your .sources file into the same ZIP archive. Cheers, Max On 18 July 2017 at 02:21:54, lionelakue (lionela...@gmail.com) wrote: Now I can remember

Re: [Pharo-dev] The new implementation of current working directory

Thanks for the detailed explanation Rajula. I think it makes perfect sense to separate working and image directories from each other. What you didn't mention is how the current working directory is resolved when an image is not started from the command line but by using the operating systems

Re: [Pharo-dev] WebTester project

Are you aware of the work that Johan did on Parasol (https://github.com/SeasideSt/Parasol )? Max > On 25 Jun 2017, at 16:45, Nicolas Anquetil wrote: > > > Hi all, > > I developped a first version of a WebTestCase class. > >

Re: [Pharo-dev] Seaside Control Panel crashing

Hi Casimiro, We’re aware of the issue and already have a fix in the works. Please report Seaside issues to the Seaside github repository (https://github.com/SeasideSt/Seaside ) or on the Seaside mailing list. Cheers, Max > On 8 Jun 2017, at 22:17,

Re: [Pharo-dev] GitHub package management beta

Yes please! > On 7 Jun 2017, at 03:16, Eliot Miranda wrote: > > Hi All, > >I've been invited to participate in github's Bera test of their new > package management support. I don't know much, if anything, about the > software except that it supports RubyGems

Re: [Pharo-dev] Abstract test classes are not managed well in SUnit

> On 4 Jun 2017, at 02:50, Cyril Ferlicot D. wrote: > > Le 04/06/2017 à 02:26, monty a écrit : >> I've seen this before, and I'm not sure it's a bug. >> >> A testless, non-abstract subclass of a TestCase is useless unless it >> inherits test methods. But if it

Re: [Pharo-dev] Iceberg ?

ls -la ~/.ssh wil probably show you that you don’t have a key named “id_rsa”. You have to specify the correct file (e.g. my github key is named “github”). HTH, Max > On 22 May 2017, at 21:47, Stephane Ducasse wrote: > > I get > > ssh-add -K ~/.ssh/id_rsa > > Error

Re: [Pharo-dev] Can this regex be implemented in Pharo's one?

> On 22 May 2017, at 20:50, Mariano Martinez Peck wrote: > > Hi guys, > > I have this Javascript regex to prefix CSS rules to a given ID: > > css = css.replace(/([,|\}][\s$]*)([\.#]?-?[_a-zA-Z]+[_a-zA-Z0-9-]*)/g, "$1" > + "#myDiv" + " $2”);

Re: [Pharo-dev] Command line save and quit

> On 17 May 2017, at 15:23, Damien Pollet <damien.pol...@gmail.com> wrote: > > On 17 May 2017 at 14:34, Max Leske <maxle...@gmail.com > <mailto:maxle...@gmail.com>> wrote: > > (self hasOption: 'save') > > ifTrue: [ Smalltalk snapsh

Re: [Pharo-dev] Command line save and quit

> On 17 May 2017, at 14:24, K K Subbu <kksubbu...@gmail.com> wrote: > > On Wednesday 17 May 2017 05:12 PM, Max Leske wrote: >> Yes. #exitSuccess does a bit more: >> 1. return an exit code to the command line >> 2. print a message >> 3. check if the session

Re: [Pharo-dev] Command line save and quit

> On 17 May 2017, at 13:29, K K Subbu wrote: > > Hi, > > STCommandLineHandler>>#end is defined as: > --- > | quit | > quit := self commandLine hasOption: 'quit'. > (self commandLine hasOption: 'save') > ifTrue: [ Smalltalk snapshot: true

Re: [Pharo-dev] Does special delay scheduler class is still needed for OSSubprocess?

Great, thanks. > On 16 May 2017, at 17:32, Mariano Martinez Peck wrote: > > Denis, Max, > > On master you can find the scheduler change rollbacked. I will soon release a > new version 0.2.5 but not just yet. So as for testing purpose, give it a try > with master. >

Re: [Pharo-dev] Is there a way to know if I am in iTimer VM?

The --version command line option to the VM prints "ITHB" as part of the version for itimer VM's. Not sure whether that is accessible from within the image though. Cheers, Max > On 16 May 2017, at 15:35, Mariano Martinez Peck wrote: > > Guys, > > As you know,

Re: [Pharo-dev] Does special delay scheduler class is still needed for OSSubprocess?

Hi Denis Mariano is currently deciding what to do with it. See issue https://pharo.fogbugz.com/f/cases/20044/DelayMillisecondScheduler-leads-to-UI-lockup Cheers, Max > On 16 May 2017, at 14:29, Denis

Re: [Pharo-dev] Git breaks Monticello's version numbers

> On 12 May 2017, at 23:09, Oleksandr Zaytsev wrote: > > Hello > > Two days ago I was trying to send the slice with my fix to PolyMath using > Monticello. But the version number got set to 1494471195. Today I realized > that all the packages to which I commit are

Re: [Pharo-dev] [Zinc] How do I set the entry limit for ZnMultiValueDictionary?

y change how dynamic variables work, and I don't feel that this > justifies hacking around that. Sure, I can do that. I just thought that since there is an #unlimited configuration option it should be possible to use it. But I'm happy enough with the way it is now. Thanks! > >>

  1   2   3   4   5   6   7   8   >