Re: [Pharo-dev] Segmentation fault while installing Scale

Hi Andrey, Thanks for providing both a way to reproduce and the log so we can have you machine details. I see that the VM was compiled from build #589 on jenkins with VMMaker.oscog-eem.1855 and you're on Linux using x86 back-end. Scale works only on Linux and when I try the wget command from Mac

Re: [Pharo-dev] [QA] Debugger buttons explained

> On 7 Feb 2017, at 08:05, Stephane Ducasse wrote: > > Sven I do not get > > Step over the highlighted message, i.e. do not follow the sent message, > taking debugger control after the method invoked returns or whenever > execution should return inside a block used

Re: [Pharo-dev] Pharo 60 need help white-theme-color-for-button-is-not-good

No it is important. There is no point to have a supercool system that looks so bad and turn people off. But I do not get it your 13136 was integrated. On Mon, Feb 6, 2017 at 6:28 PM, p...@highoctane.be wrote: > I proposed that a while ago because these gradients are bad

Re: [Pharo-dev] [QA] Debugger buttons explained

Sven I do not get Step over the highlighted message, i.e. do not follow the sent message, taking debugger control after the method invoked returns or whenever execution should return inside a block used as an argument before that. in particular the taking debugger control may be give back

Re: [Pharo-dev] Debugger hang when step throught

tx for the report hilaire. Indeed I can reproduce your bug - I pasted it - I did debug it over over and through trhough and my system froze. On Mon, Feb 6, 2017 at 7:04 PM, Hilaire wrote: > Hello, > > The faulty code bellow when debugged and 'step through' cause the > debugger

Re: [Pharo-dev] Segmentation fault while installing Scale

Hi andrey can you tell us on which OS and version and which VM do you use (there is a System report browser where you can find the information. Tx On Mon, Feb 6, 2017 at 8:20 PM, Andrey Tykhonov wrote: > Hi all! > > While executing the following command: > > $ wget -O-

Re: [Pharo-dev] Pharo 6 update catalog entries

Fair point, I will make the changes. Glad you find it useful, is there any new feature you want ? On Mon, 6 Feb 2017 at 18:05, Sean P. DeNigris wrote: > kilon.alios wrote > > I see little reason to support individual pharo versions because I focus > > always on the

[Pharo-dev] Printing numbers in different bases

--- Begin Message --- Is there a reason why we allow printing numbers in bases greater than 36?  It makes no sense to me. For instance: 1406 printStringBase: 57.  "O]" - Benoît St-Jean "A standpoint is an intellectual horizon of radius zero".  (A. Einstein)--- End Message ---

Re: [Pharo-dev] WorkingSession UUID looks "sketchy"

On Tue, Feb 7, 2017 at 5:59 AM, Peter Uhnak wrote: > >> > On Windows (10) (with latest 6 image and VM) `Time microsecondClockValue` >> > returns microseconds, but (presumably the system) cannot give precision >> > beyond 1 second - this will imho need a VM fix; >> >> I find

Re: [Pharo-dev] [QA] Debugger buttons explained

> On 6 Feb 2017, at 21:25, Sean P. DeNigris wrote: > > How about... > > Into > > Step into the highlighted message, i.e. dive the debugger into the method > which handles it > > Over > > Step over the highlighted message, i.e. execute it, but keep the debugger >

Re: [Pharo-dev] WorkingSession UUID looks "sketchy"

> On 6 Feb 2017, at 23:01, werner kassens wrote: > > On 02/06/2017 09:00 PM, Sven Van Caekenberghe wrote: >> Regarding the poor seed at startup: >>> 1k outside runs of 'NeoUUIDGenerator new nextRandom16' (on a fresh image) >>> gives me only 116 unique values, compared to

Re: [Pharo-dev] WorkingSession UUID looks "sketchy"

> On 6 Feb 2017, at 22:59, Peter Uhnak wrote: > > >>> On Windows (10) (with latest 6 image and VM) `Time microsecondClockValue` >>> returns microseconds, but (presumably the system) cannot give precision >>> beyond 1 second - this will imho need a VM fix; >> >> I find

Re: [Pharo-dev] FileStreams and encoding ( opening a readStream on a FileRerefence)

> On 6 Feb 2017, at 22:33, Nicolai Hess wrote: > > > > 2017-02-04 13:40 GMT+01:00 Sven Van Caekenberghe : > > > On 4 Feb 2017, at 13:01, Nicolai Hess wrote: > > > > > > > > 2017-02-04 12:49 GMT+01:00 Sven Van Caekenberghe

Re: [Pharo-dev] WorkingSession UUID looks "sketchy"

On 02/06/2017 09:00 PM, Sven Van Caekenberghe wrote: Regarding the poor seed at startup: 1k outside runs of 'NeoUUIDGenerator new nextRandom16' (on a fresh image) gives me only 116 unique values, compared to the expected 990-1000 In the above it's already second run of the generator, for

Re: [Pharo-dev] WorkingSession UUID looks "sketchy"

> > On Windows (10) (with latest 6 image and VM) `Time microsecondClockValue` > > returns microseconds, but (presumably the system) cannot give precision > > beyond 1 second - this will imho need a VM fix; > > I find that quite hard to believe and I did not know that. Are you really > sure ?

Re: [Pharo-dev] FileStreams and encoding ( opening a readStream on a FileRerefence)

2017-02-04 13:40 GMT+01:00 Sven Van Caekenberghe : > > > On 4 Feb 2017, at 13:01, Nicolai Hess wrote: > > > > > > > > 2017-02-04 12:49 GMT+01:00 Sven Van Caekenberghe : > > Hi Nicolai, > > > > The FileSystem API is a bit inconsistent, yes. > > >

Re: [Pharo-dev] [QA] Debugger buttons explained

On Mon, Feb 6, 2017 at 9:14 PM, Hilaire wrote: > Thanks for the updated message. > > Le 06/02/2017 à 19:39, Sven Van Caekenberghe a écrit : > > That last one is not correct. It has nothing to do with specific > iteration selectors. It means: stop when execution returns in one

Re: [Pharo-dev] [QA] Debugger buttons explained

Ok, give a look to SpecDebugActionButton, this class has no user, only progma reference, not easy to track the logic. Never mind I test on a halt in its #update method. Nothing happen when opening the debugger. May be there is instance in memory, no idea under which name it is referenced, may be

Re: [Pharo-dev] [QA] Debugger buttons explained

How about... Into Step into the highlighted message, i.e. dive the debugger into the method which handles it Over Step over the highlighted message, i.e. execute it, but keep the debugger focused on the current method Through Like stepping "Over", except step through block contents when

Re: [Pharo-dev] [QA] Debugger buttons explained

Thanks for the updated message. Le 06/02/2017 à 19:39, Sven Van Caekenberghe a écrit : > That last one is not correct. It has nothing to do with specific iteration > selectors. It means: stop when execution returns in one of the argument > blocks. It also works for #on:error: #streamContents:

Re: [Pharo-dev] WorkingSession UUID looks "sketchy"

First, thanks for the discussion, I think this is good. The idea/reason behind NeoUUIDGenerator was to get an algorithm that is fully documented and clearly implemented with proper unit tests, all at the Smalltalk level, so that we can get rid of the plugin. > On 6 Feb 2017, at 18:54, Peter

[Pharo-dev] Segmentation fault while installing Scale

Hi all! While executing the following command: $ wget -O- https://raw.githubusercontent.com/guillep/Scale/master/setupScale.sh | sudo bash > stderr.log I got the Segmentation fault error. You can see it in the contents of stderr.log which is attached to the email. Here you can see the output of

Re: [Pharo-dev] [QA] Debugger buttons explained

> On 6 Feb 2017, at 18:55, Hilaire wrote: > > How will you describe these buttons in the debugger? > Here are proposals for tooltips, please fix it, I am sure there are > better way to write it. > > Proceed > Quit the debugger and resume the execution of the method. > >

[Pharo-dev] Debugger hang when step throught

Hello, The faulty code bellow when debugged and 'step through' cause the debugger to hang: self inform: '1'. #(2 3 4) select: [:i| i] thenDo: [:n| self inform: n printString ]. self inform: '5'. It seems trapped in an infinite loop, you can more or less get control back with Alt+[.] When step

[Pharo-dev] [QA] Debugger buttons explained

How will you describe these buttons in the debugger? Here are proposals for tooltips, please fix it, I am sure there are better way to write it. Proceed Quit the debugger and resume the execution of the method. Restart Reset the local variable and restart stepping at the beginning of the method.

Re: [Pharo-dev] WorkingSession UUID looks "sketchy"

1. Regarding WorkingSession The WS' comment claims "On each image startup the current session is invalidated and a new session is created.", but in reality WS is reset only save, and not on startup... isn't that odd? So if image crashes or I am running it headlessly without saving I am actually

Re: [Pharo-dev] Pharo 60 need help white-theme-color-for-button-is-not-good

I proposed that a while ago because these gradients are bad looking (especially in an age of flat design). https://pharo.fogbugz.com/f/cases/13132/Ugly-gradients-in-Pharo3Theme-Not-in-line-with-the-times Same for those ugly flat scrollbars.

Re: [Pharo-dev] Pharo 60 need help on Red-in-Dark-Theme-is-plain-bad

I'll check that. FWIW, all of this color thing + theme is annoying me and I started something to sort it out. Also have eye issues and one of the reasons I use Pharo is that I can customize it for my own ways. We need a real core palette on top of which we put logical color names for the themes.

Re: [Pharo-dev] Pharo 60 need help on When-coding-in-the-debugger-I-get-an-error-sourceNodeExecuted

Fixed 2017-02-06 17:55 GMT+01:00 Stephane Ducasse : > https://pharo.fogbugz.com/f/cases/19661/When-coding-in- > the-debugger-I-get-an-error-sourceNodeExecuted > > Then I got a really strange problem when I was doing the counter > execise using the debugger. > > > create

[Pharo-dev] Pharo 60 needs help on ooltips-of-the-class-button-does-not-changed

If you want to help pharo: https://pharo.fogbugz.com/f/cases/19659/Tooltips-of-the-class-button-does-not-changed

Re: [Pharo-dev] Seamless Error in GT-Inspector

Denis Kudriashov wrote > I fixed it. Thanks! Denis Kudriashov wrote > So old RemoteDebuggingTools project is also work on Pharo 5. > But remember that PharmIDE is only target Pharo 6 or later. No problem. I don't /need/ it to work in Pharo 5, but read that it was working, so I figured I'd let

[Pharo-dev] Pharo 60 need help white-theme-color-for-button-is-not-good

https://pharo.fogbugz.com/f/cases/19657/white-theme-color-for-button-is-not-good If we compare the selection color for the dark theme, the blue is stronger and much better to see. This is particularly true for class/instance side button, I would be good to have a better white theme with stronger

[Pharo-dev] Pharo 60 needs help on Broken-syntax-highlithing

I'm giving some lectures to siemens engineers and we found glitches. (bad impression). https://pharo.fogbugz.com/f/cases/19656/Broken-syntax-highlithing

[Pharo-dev] Pharo 60 needs help on shortcuts-are-wrongly-displayed

https://pharo.fogbugz.com/f/cases/19660/shortcuts-are-wrongly-displayed The system should display Ctrl + s and not Ctrl + S Because people are pressing Shift to get S and this is not working. We should distinguish between uppercase and lowercase. The reader cannot guess that S is not the same as

[Pharo-dev] Pharo 60 need help on Red-in-Dark-Theme-is-plain-bad

https://pharo.fogbugz.com/f/cases/19658/Red-in-Dark-Theme-is-plain-bad The black theme is not usable on certain screen because the red color cannot be distinguished. So when the white theme does not work for other reasons people cannot do much. They cannot read the errors. In addition since the

[Pharo-dev] Pharo 60 need help on When-coding-in-the-debugger-I-get-an-error-sourceNodeExecuted

https://pharo.fogbugz.com/f/cases/19661/When-coding-in-the-debugger-I-get-an-error-sourceNodeExecuted Then I got a really strange problem when I was doing the counter execise using the debugger. create a Test Case TestCase subclass: #CounterTest instanceVariableNames: ''

Re: [Pharo-dev] Seamless Error in GT-Inspector

I fixed it. Now Seamless is compatible with old Pharo (5 at least). Try new stable version. It was just little problem with one method. So old RemoteDebuggingTools project is also work on Pharo 5. But remember that PharmIDE is only target Pharo 6 or later. Thank's for feedback 2017-02-06 16:59

Re: [Pharo-dev] Pharo 6 update catalog entries

kilon.alios wrote > I see little reason to support individual pharo versions because I focus > always on the latest version. I'm not suggesting that you maintain compatibility ongoingly with various versions, but if you mark compatible versions as such in the catalog, users won't get an

Re: [Pharo-dev] Seamless Error in GT-Inspector

Denis Kudriashov wrote > Just check in latest Pharo 6. It works Thanks, I was in Pharo 5 - Cheers, Sean -- View this message in context: http://forum.world.st/Seamless-Error-in-GT-Inspector-tp4933050p4933167.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Re: [Pharo-dev] [QA] quality assurance

Ben Coman wrote > That seems appropriate. > A separate list makes it hard to draw new people in to help. +1 - Cheers, Sean -- View this message in context: http://forum.world.st/QA-quality-assurance-tp4933067p4933166.html Sent from the Pharo Smalltalk Developers mailing list archive at

Re: [Pharo-dev] Esteban's ChangeLog week of 30 January 2017

EstebanLM wrote > This is my weekly ChangeLog, from 30 January 2017 to 5 February 2017. Go, go, go, Esteban!!! EstebanLM wrote > the new process we are starting to create for Pharo, we need to be able to > do things like... Sounds great :) - Cheers, Sean -- View this message in

Re: [Pharo-dev] WorkingSession UUID looks "sketchy"

> On 6 Feb 2017, at 15:21, Yuriy Tymchuk wrote: > > Of course UUID is not guaranteed to be absolutely random. But it is > suspicious these similarities happen is a small timeframe, so I think that > the image got restarted a few times, but generated the same ID. If you

Re: [Pharo-dev] WorkingSession UUID looks "sketchy"

Of course UUID is not guaranteed to be absolutely random. But it is suspicious these similarities happen is a small timeframe, so I think that the image got restarted a few times, but generated the same ID. Uko > On 6 Feb 2017, at 14:35, Sven Van Caekenberghe wrote: > > >>

Re: [Pharo-dev] WorkingSession UUID looks "sketchy"

> On 6 Feb 2017, at 14:51, Peter Uhnak wrote: > > I had issues with Pharo not being random during the first startup: > http://forum.world.st/Random-is-not-random-at-startup-td4895905.html > > Even though the seed is different during startup, the mask trims the > randomness

Re: [Pharo-dev] WorkingSession UUID looks "sketchy"

I had issues with Pharo not being random during the first startup: http://forum.world.st/Random-is-not-random-at-startup-td4895905.html Even though the seed is different during startup, the mask trims the randomness away. Looking at NeoUUID, it actually makes it worse on Linux (and presumably

Re: [Pharo-dev] WorkingSession UUID looks "sketchy"

> On 6 Feb 2017, at 14:17, Yuriy Tymchuk wrote: > > Hi everyone, > > I’m using the session id (Smalltalk session id) for my data recording, so I > can distinguish if the recorded events came from the same session. The idea > is that each time an image is started a new

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/60375 Home: https://github.com/pharo-project/pharo-core

[Pharo-dev] [pharo-project/pharo-core] 394af1: 60375

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 394af1e72e16fd07e051c527b87418e41e00b848 https://github.com/pharo-project/pharo-core/commit/394af1e72e16fd07e051c527b87418e41e00b848 Author: Jenkins Build Server Date:

[Pharo-dev] WorkingSession UUID looks "sketchy"

Hi everyone, I’m using the session id (Smalltalk session id) for my data recording, so I can distinguish if the recorded events came from the same session. The idea is that each time an image is started a new session is created and assigned a new UUID. Now when I started to look on the data I

[Pharo-dev] [pharo-project/pharo-core] 1ef999: 60374

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 1ef999f0f762ee205eee21501a8001ca63416aaa https://github.com/pharo-project/pharo-core/commit/1ef999f0f762ee205eee21501a8001ca63416aaa Author: Jenkins Build Server Date:

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/60374 Home: https://github.com/pharo-project/pharo-core

[Pharo-dev] Esteban's ChangeLog week of 30 January 2017

Hello! This is my weekly ChangeLog, from 30 January 2017 to 5 February 2017. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=30/1/2017=5/2/2017 ChangeLog = 3 February 2017: *Still on