- Pharo-dev - lists.pharo.org

[Pharo-project] Issue 3726 in pharo: Turn the orange corner into a real Morph object
by pharo＠googlecode.com March 21, 2011

March 21, 2011

Status: Fixed Owner: Benjamin...(a)gmail.com CC: siguc...(a)gmail.com New issue 3726 by Benjamin...(a)gmail.com: Turn the orange corner into a real Morph object http://code.google.com/p/pharo/issues/detail?id=3726 Gofer new squeaksource: 'PharoTaskForces'; package: 'AdorementMorph'; load Then add the attached cs. For now, it just cahnge the cursor into a hand ^^ But soon, we will attach behavior Attachments: Morphic-IgorStasenko.834.1.cs 1.8 KB

1 3

Re: [Pharo-project] [squeak-dev] Security Vunerability in SqueakSource
by Marcus Denker March 21, 2011

March 21, 2011

On Mar 21, 2011, at 12:23 PM, Sven Van Caekenberghe wrote: > > On 21 Mar 2011, at 11:20, Bert Freudenberg wrote: > >> SqueakSource is simply a WebDAV server. All the versioning logic is local, implemented in Monticello, so allowing overwrites is not really SqueakSource's "fault". Besides, even if SqueakSource disallowed overwriting a version (which it probably should) nothing would prevent somebody else to upload a *new* version that did something bad. > > Yes versioning/naming is local and distributed, that is a feature. One cannot rely on the name alone. > However, it is most certainly a bug that a server happily overwrites existing versions, a version control system should never do that. > > Your other points a valid, of course. > > I think that "security" was not meant in the sense of accidentally loading wrong code. More in the sense that one could just delete all your code. Even though we have backups of the SqueakSource filesystem, you don't want that, as it would be a mess to repair. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

2 1

[Pharo-project] Issue 3834 in pharo: Add support for Threaded VMs in Process
by pharo＠googlecode.com March 21, 2011

March 21, 2011

Status: Accepted Owner: siguc...(a)gmail.com Labels: Milestone-1.3 Type-RequestForEnhancement Importance-High New issue 3834 by siguc...(a)gmail.com: Add support for Threaded VMs in Process http://code.google.com/p/pharo/issues/detail?id=3834 By Eliot: To enable threading you have to modify the Process class definition to include threadId as its fourth inst var and tell the VM of that fact by setting a bit in the image via vmParameterAt: (the below, also attached). Link subclass: #Process instanceVariableNames: 'suspendedContext priority myList threadId errorHandler name island env' classVariableNames: '' poolDictionaries: '' category: 'Kernel-Processes'! SmalltalkImage methods for system attributes processHasThreadIdInstVar: aBoolean "The threaded VM needs to know if the 4th inst var of Process is threadId which it uses to control process-to-thread binding. This flag persists across snapshots, stored in the image header." aBoolean ifTrue: [self assert: (Process instVarNames at: 4) ='threadId']. self vmParameterAt: 48 put: ((self vmParameterAt: 48) bitClear: 1) + (aBoolean ifTrue: [1] ifFalse: [0]) e.g. "Ensure VM knows whether Process has threadId inst var or not." Smalltalk processHasThreadIdInstVar: (Process instVarNames includes: 'threadId'). Attachments: SmalltalkImage-processHasThreadIdInstVar.st 585 bytes

1 1

[Pharo-project] [update 1.3] #13099
by Marcus Denker March 21, 2011

March 21, 2011

13099 ----- Issue 3834: Add support for Threaded VMs in Process -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

Re: [Pharo-project] [squeak-dev] Security Vunerability in SqueakSource
by Marcus Denker March 21, 2011

March 21, 2011

On Mar 21, 2011, at 9:27 AM, Tobias Pape wrote: > Am 2011-03-21 um 03:24 schrieb Matthew Fulmer: > >> As demonstrated by the VMMaker team, SqueakSource has a rather >> serious security vunerability: >> >> http://bugs.squeak.org/view.php?id=7617 >> >> Below is the dialog that led to this discovery: >> > > > Note that SqueakSource 2 and 3 are unaffected of this bug. > Moreover, find attached a quick fix that is a backport of > the conflict handling in SqueakSource 2 to the original > SqueakSource. > Ok, we added the fix. We verified and versions are not overridden. The strange thing is that MC in the image thinks it was successful and gets confused. A restart of the image shows the correcnt data, so on the squeaksource side the meta data is ok. So as a first workaround, this is working but we should look into a correct error handling on the MC on the image side later. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] Issue 3839 in pharo: MC Browser refresh does not refresh everything
by pharo＠googlecode.com March 21, 2011

March 21, 2011

Status: Accepted Owner: marcus.d...(a)gmail.com New issue 3839 by marcus.d...(a)gmail.com: MC Browser refresh does not refresh everything http://code.google.com/p/pharo/issues/detail?id=3839 ... if you attempt to override a version on SqueakSourse, MC thinks it is successful. Restarting the image then shows the correct version of the package in the remote repository

1 0

[Pharo-project] Issue 3830 in pharo: [Failing Test] Autotes TestHitCounter.testHitCountIncrements
by pharo＠googlecode.com March 21, 2011

March 21, 2011

Status: Accepted Owner: marcus.d...(a)gmail.com Labels: Milestone-1.2-DevImage New issue 3830 by marcus.d...(a)gmail.com: [Failing Test] Autotes TestHitCounter.testHitCountIncrements http://code.google.com/p/pharo/issues/detail?id=3830 Why does this just like that start to fail after nunning for days without problems? Autotest.Tests.Core.AutotestTestHitCounter.testHitCountIncrements

1 8

Re: [Pharo-project] [ANN 1.2.1a] towards 1.2.1
by Marcus Denker March 21, 2011

March 21, 2011

On Mar 20, 2011, at 11:44 PM, Michael Roberts wrote: > Hi, a meta question... > > when i made changes to SystemVersion I put a comment in that method > thinking it would not make sense to use it. I did not know. I just did what we did when changing the version in the past. (copy and paste from the postscript... same as setting the version to 1.2) It worked... > You have published a use > for it ;-) > I just changed the version number the same way it was done before. It did not give an error message, the version looks good. If this is not correct, the method should react by telling me. How can I know else? Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

2 1

[Pharo-project] [ANN 1.2.1a] towards 1.2.1
by Marcus Denker March 20, 2011

March 20, 2011

Hi, With people now finally actually looking at 1.2Core, we need to start to collect bugfixes and do a 1.2.1... So if you want to update 1.2Core, you need to SystemVersion newVersion: 'Pharo1.2.1a'. or download it from https://gforge.inria.fr/frs/download.php/28391/PharoCore-1.2.1a-12342.zip This is *not* linked as stable core... as it can break anytime. And 1.2Core does not update withour changing the version number (We might want to rethink that... but that can only be done in 1.3) Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

3 3

[Pharo-project] [ANN] More on Keymappings
by Guillermo Polito March 20, 2011

March 20, 2011

What do we have now? - Can provide settings for a set of morphs - Can provide settings for a TextEditors (Smalltalk editor and related) - Settings integration I added some methods to the Settings Tree Builder in order to avoid references from the users code. - I ran Slint over it and cleaned it a lot more :). ( And learnt that Slint is there :P ) More info in here: http://guilleel3.blogspot.com/ Guille

7 29