Re: [Pharo-dev] WhatsUp from: 2013-05-20 until: 2013-05-31
Le 20 mai 2013 à 07:00, seas...@rmod.lille.inria.fr a écrit :
Hi! We're sending this automatic email twice a month, to give the community
an opportunity to easily know what's happening and to coordinate efforts.
Just answer informally, and feel free to spawn discussions thereafter!
### Here's what I've been up to since the last WhatsUp:
Work on Metacello with Dale :
- to include Pharo2 and Pharo3 as platforms to test on travis (Metacello is
tested with travis CI)
- to get MetacelloPreview working on Pharo2 and Pharo3 : we still need some
work but not so far!
**
Results for #('BaselineOfMetacello') Test Suite
737 run, 722 passes, 0 skipped, 0 expected failures, 0 failures, 7 errors, 8
unexpected passes
**
### What's next, until 2013-05-31 (*):
Include MetacelloPreview as default Metacello version in Pharo3
Get back on Versionner to use MetacelloPreview
smime.p7s
Description: S/MIME cryptographic signature
[Pharo-dev] you may need to update your configurations
Hello, Since the update #30205, Pharo 3.0 will not be recognized anymore as a Pharo 2.0 platform (from the metacello point of view). It means that if you have specific pharo 2.0 instructions in your configurations and you want to work on Pharo 3.0, you should add pharo 3.0 support in the configuration. For example: spec for: #'pharo1.4.x' version: '1.9'. spec for: #'pharo2.x' version: '1.10'. spec for: #'pharo3.x' version: '1.11'. or : spec for: #'pharo2.x' do: [ ... ] spec for: #'pharo3.x' do: [ ... ] Regards, Christophe. Le 19 juin 2013 à 07:49, Marcus Denker a écrit : 30205 - 10951 Debugger add new Method class choice dialog should show traits https://pharo.fogbugz.com/f/cases/10951 10958 Tabs model https://pharo.fogbugz.com/f/cases/10958 10959 metacelloPlatformAttributes not updated for Pharo3 https://pharo.fogbugz.com/f/cases/10959 10960 Pass on Tabs https://pharo.fogbugz.com/f/cases/10960 10961 Fix pluggableTextMorphWithLimits color https://pharo.fogbugz.com/f/cases/10961 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Tools-MarcusDenker.1147.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Tabs-MarcusDenker.16.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/System-Support-MarcusDenker.855.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Widgets-MarcusDenker.199.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Core-MarcusDenker.132.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Morphic-Base-MarcusDenker.15.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/DebuggerModel-MarcusDenker.39.diff smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] you may need to update your configurations
Le 19 juin 2013 à 14:45, Goubier Thierry a écrit : Cool. Side question: Christophe, are you working on utf8 support for the Monticello tools? I encountered encoding problems with ZipArchive. Not at all. There is some work from Nicolas integrated [1] but I'm not aware of other work on utf8 support. Christophe. [1] https://pharo.fogbugz.com/default.asp?10801 smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] you may need to update your configurations
Le 19 juin 2013 à 16:36, Goubier Thierry a écrit : By the way, why the change in MonticelloFileTree-Core-ChristopheDemarey.97 breaks Pharo 2.0 ? Because this change comes from the FileTree branch used fro Pharo3 [1]. This small change avoid to use a deprecated method in Pharo3. It should not be used in Pharo2. [1] https://github.com/demarey/filetree/commit/dbdbf30a00bc1f8816773dc1abe0bfa120f3 smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] filetree jenkins job
Hi Dale, The introduction of Opal as the new compiler has some side effects. The problem is reported here : https://pharo.fogbugz.com/default.asp?11141 Today, Camillo and I worked on this problem and we should come with a solution soon. Once integrated in the image, you should have the same kind of output you have on Pharo 2.0. Maybe you can trigger a new build for Pharo 3.0. There was also a bug related the new classBuilder introduction and it is now fixed. Le 8 juil. 2013 à 05:04, Dale K. Henrichs a écrit : When I am using travis, I am looking at the log file of the run just to see if the test passed or failed, so to have a dead stack trace right there in the log file that I am looking at is exactly what I WANT ... most of the time the stack trace is enough for me to debug the problem... | And exactly in the case you describe theses fuel files can save you a | lot of time since you can basically debug the same way you debug a | local application. Except that I rarely write code in Pharo3.0, but I am interested in running tests and seeing the results of tests and seeing stack traces for failures for the code when it is run against Pharo3.0 ... These days I do the bulk of my development for FileTree, Metacello, etc. using tODE in GemStone, so I don't usually even have a Pharo development image (especially a fresh one) available to do testing ... so a stack trace actually saves me a whole lot of time... Here Camillo just pointed you a very useful mechanism you can use to debug. At the end, you are free to check stack traces and try to fix from tODE/GemStone if you prefer this way. | In any case I see 4 failing tests on our jenkins build: | https://ci.inria.fr/pharo-contribution/job/FileTree/PHARO=30,VERSION=stable,VM=vm/lastCompletedBuild/testReport/ If you don't want to wait to have feedback from Travis with the error output fixed, this is the way to go. You can get the stack trace by clicking on each failed test. We should have the same failed tests on Travis. Christophe. smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] [update 3.0] #30296
Hello, This release breaks the right click on the mouse. The event is not handled anymore. I checked #30295 = ok, images = #30296 ko Christophe. Le 24 juil. 2013 à 14:46, Marcus Denker a écrit : 30296 - 10448 Smalltalk os should use instance of OSPlatform https://pharo.fogbugz.com/f/cases/10448 11225 fix DebuggerTesttestBasic for the new debugger https://pharo.fogbugz.com/f/cases/11225 11218 SettingDeclarationexportAction not send and returns self https://pharo.fogbugz.com/f/cases/11218 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/ToolsTest-MarcusDenker.denker.51.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Tools-MarcusDenker.1194.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Tests-MarcusDenker.597.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/System-Support-MarcusDenker.882.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/System-Platforms-MarcusDenker.43.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/System-Localization-MarcusDenker.69.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/System-Hashing-MarcusDenker.25.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/System-Clipboard-MarcusDenker.27.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/StartupPreferences-MarcusDenker.100.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Ring-Tests-Kernel-MarcusDenker.52.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Network-Kernel-MarcusDenker.89.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Multilingual-Languages-MarcusDenker.32.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Morphic-Base-MarcusDenker.52.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Keys-MarcusDenker.10.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Keymapping-KeyCombinations-MarcusDenker.16.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Keymapping-Core-MarcusDenker.154.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/KernelTests-MarcusDenker.537.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Kernel-MarcusDenker.1532.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/FreeType-MarcusDenker.621.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Files-MarcusDenker.ducasse.300.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/FileSystem-Disk-MarcusDenker.63.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/FileSystem-Core-MarcusDenker.104.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Compatibility-MarcusDenker.18.diff smime.p7s Description: S/MIME cryptographic signature
[Pharo-dev] Jenkins slaves
Hi all, An hypervisor used to host slaves for the continuous integration service is reaching its maximum storage capacity (primary storage used for running Virtual Machines). To avoid VM corruptions, we preventively stopped VMs running on this hypervisor. For the pharo ecosystem, following VMs are impacted: pharo linux-ubuntu-10-04 test2 pharo-contribution linux64-2 74 rmod windows-7-32 They will be restarted once the storage will be extended (probably in the beginning of the next week). If really needed, it is possible to create new slaves to substitute to these ones since they will be hosted on another hypervisor. Apologies for the inconvenience, Christophe.
Re: [Pharo-dev] [rmod] Jenkins slaves
We can also add a mac slave in our offices. We just have one for pharo / pharo-contribution / rmod. Le 22 août 2013 à 16:24, Stéphane Ducasse a écrit : Could we not use on of the mac machine lying around to have our own space? On Aug 22, 2013, at 2:15 PM, Christophe Demarey christophe.dema...@inria.fr wrote: Hi all, An hypervisor used to host slaves for the continuous integration service is reaching its maximum storage capacity (primary storage used for running Virtual Machines). To avoid VM corruptions, we preventively stopped VMs running on this hypervisor. For the pharo ecosystem, following VMs are impacted: pharo linux-ubuntu-10-04 test2 pharo-contribution linux64-2 74 rmod windows-7-32 They will be restarted once the storage will be extended (probably in the beginning of the next week). If really needed, it is possible to create new slaves to substitute to these ones since they will be hosted on another hypervisor. Apologies for the inconvenience, Christophe. smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] [update 3.0] #30359
Hi, This image seems broken. When I try to open the Monticello browser, I get PointPair(Object)doesNotUnderstand: #adaptToPoint:andSend: In the stack, it is sent by RectangleexpandBy:. So maybe the fix for the issue 2489 is not fully working. Christophe. Le 29 août 2013 à 22:22, Stéphane Ducasse a écrit : 30359 - - issue 2489 Strange Behavior of Rectangle Part Two https://pharo.fogbugz.com/default.asp?2489 - issue 11502 Override Class #setName: https://pharo.fogbugz.com/default.asp?11502 - issue 11505 Remove obsolete icons https://pharo.fogbugz.com/default.asp?11505 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Tools-StephaneDucasse.1230.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Polymorph-Widgets-StephaneDucasse.893.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/NautilusCommon-StephaneDucasse.164.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Nautilus-StephaneDucasse.524.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Morphic-Base-StephaneDucasse.82.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Kernel-StephaneDucasse.1585.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Graphics-Tests-StephaneDucasse.37.diff smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] CI Status
Hi, The problem with slaves on CloudStack is now solved. After a maintenance, the CloudStack controller was a bit lost and removed some iptables rules for running slaves. These slaves were up but without networking ... Slaves are now reachable. Christophe. Le 12 sept. 2013 à 20:32, Camillo Bruni a écrit : - http://ci.inria.fr/pharo continues to be critical. Slaves are still not reachable, the ci.inria.fr team should be working on a solution. - http://ci.inria.fr/pharo-contribution has a disk-size problem which I mitigated by deleting the workspace at the end of a build. - http://ci.inria.fr/rmod already lost 2 out of 4 slaves yours sincerely, the CI Janitor smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] Metacello2 now is part of Pharo3
Le 18 sept. 2013 à 17:25, Luc Fabresse a écrit : Hi, Cool. Is Versionner also integrated? Not yet, it is the next step ... smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] CI for OSWin
I got the problem, ZeroConf scripts use the find command and there was a PATH problem on the slave running your job. It used the windows find command and not the mingw one. It is now fixed and your job is now better ... but not yet green. It misses the test XML output file. It may be to a wrong regexp OSWindows.* for your test packages. Regards, Christophe. Le 20 sept. 2013 à 09:55, Christophe Demarey a écrit : Hello, To see what happens, you need to first click on a specific build in the matrix job, then you can browse a particular build and is console output. ex: https://ci.inria.fr/pharo-contribution/job/OSWindows/12/PHARO=30,VERSION=stable,VM=vm,Windows%20Slaves%20only=win/console Here the problem seems to come from the definition of the Windows Slaves label that generates a directory with this name. I would rather put a fixed value and replace export JOB_NAME=`dirname $JOB_NAME` by export JOB_NAME=OSWindows I did some changes and triggered a new build manually. But it also failed. It looks like the zeroConf script is broken on windows. We will take a look at it. Regards, Christophe. Le 20 sept. 2013 à 09:31, Torsten Bergmann a écrit : I created a CI project for OS-Windows according to the written steps on the creation page. It failed - and I checked the CI scripts. Since it was named OS-Windows and there was a $JOB_NAME variable in the script I better changed the script to use OSWindow for image name, ... (to avoid problems with character -. https://ci.inria.fr/pharo-contribution/job/OSWindows/ Still it fails - telling me something about no workspace. I now renamed it to OSWindows and situation is the same. Note that the tests should run only on Pharo 3.0 with a windows slave - that is how the configuration is currently setup. There is a ConfigurationOfOSWindows with #stable and #development, so ConfigurationOfOSWindows project version: #development ConfigurationOfOSWindows project version: #stable return something to load. Also the repo is correctly setup. Dont know what's missing - maybe someone with access can have a look. Thanks T. smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] About configuration of image projects
As we will very soon integrate a new version of Metacello, we already have this configuration. It will be: https://github.com/dalehenrich/metacello-work/blob/master/repository/BaselineOfMetacello.package/BaselineOfMetacello.class/instance/baseline..st Christophe. Le 2 oct. 2013 à 09:35, Stéphane Ducasse a écrit : yes! I add it to the list On Oct 2, 2013, at 9:19 AM, Pavel Krivanek pavel.kriva...@gmail.com wrote: what about start with this and only update packages and repositories? Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfMetacello'; load. 2013/10/2 Stéphane Ducasse stephane.duca...@inria.fr: On Oct 2, 2013, at 9:01 AM, Pavel Krivanek pavel.kriva...@gmail.com wrote: Please, can you create (update and put it to Pharo repositories) a ConfigurationOfMetacello? :-) That I do not know how to do it :) or I can simply create one based on what is in the image. We should sync with dale. Stef -- Pavel 2013/10/2 Stéphane Ducasse stephane.duca...@inria.fr: Done with ConfigurationOfAST (but could not really test it) ConfigurationOfAST-Interperter (tx for the configuration - so cool when it is already there. next ConfigurationOfEnvironment ConfigurationOfRefactoringEngine On Oct 1, 2013, at 9:25 PM, Stéphane Ducasse stephane.duca...@inria.fr wrote: Hi guys I started to work on creating configuration for all the projects inside the image RB Spec Zinc Ring OPAL AST Nautilus KeyMapping why because I want to be able to express the dependencies so that we get a modular system and that we can build it based on miniImage. So if you got some configuration in the past and your project got integrated in the image please let me know. - Pharo/ASMJit - Pharo/Fuel - Pharo/NativeBoost - Pharo/Athens Got them Stef smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] Issues interesting for the hangout
Le 2 oct. 2013 à 12:03, Esteban Lorenzano a écrit : Hi, Of course, that's not a exhaustive list, just some that I think are interesting to tackle :) https://pharo.fogbugz.com/f/cases/10821/Integrate-Metacello-2 For this one, there is still a missing fix to the metacello previewBootstrap version. I'm discussing with Dale to integrate this fix. Christophe. smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] Any visualisation for Metacello?
Gofer new url: 'http://www.smalltalkhub.com/mc/Moose/GToolkit/main'; package: 'ConfigurationOfGToolkit'; load. (Smalltalk at: #ConfigurationOfGToolkit) project development load. (Smalltalk at: #GTMetaceller) open. Le 2 oct. 2013 à 19:03, Stéphane Ducasse a écrit : metaceller in the moose image maybe On Oct 2, 2013, at 6:29 PM, Damien Cassou damien.cas...@gmail.com wrote: Hi, I have to deal with complex configurations involving Pier (and some of its plugins), Magritte, Voyage, Mongo and Seaside. There is a bug somewhere because I can't load all of that. Is there any tool that would show me a graph of the projects and their dependencies? If there is no graph, is there at least some place to get the information? I know the #record + #loadDirective combo, but I don't understand the result and it does not help. Best -- Damien Cassou http://damiencassou.seasidehosting.st Success is the ability to go from one failure to another without losing enthusiasm. Winston Churchill smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] Metacello preview in Pharo 2.0
Le 9 oct. 2013 à 13:25, Stéphane Ducasse a écrit : does it integrate for real? As you can see here: https://ci.inria.fr/rmod/view/Versions%20and%20Dependencies/job/MetacelloPreview-Pharo2/? are the other tests green? I created another test to run all tests in Pharo: https://ci.inria.fr/rmod/view/Versions%20and%20Dependencies/job/MetacelloPreview-Pharo2-all-tests/ They are a lot of tests failed in OSProcess but the OSProcess tests are already red: https://ci.inria.fr/pharo-contribution/job/OSProcess/PHARO=20,VERSION=stable,VM=vm/165/testReport/ To summarize, the problem is more on the OSProcess dependency that will come with MetacelloPreview. smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] [pharo-project/pharo-core] 4021f3: 30523
Why do we need to remove configurations of projects loaded into the image? I would say the opposite: all projects in the image should have their configuration loaded. It is part of the project. Le 25 oct. 2013 à 14:00, GitHub a écrit : 12005 unload BaselineOfFileTree, BaselineOfMetacello https://pharo.fogbugz.com/f/cases/12005 smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] Spec new release :)
Hi, I have some questions: 1/ Before the removal of morphic dependencies in spec, I used aNode selectedNode parentNode item to get the parent of the selected item. What is the new way to do that? 2/ I also defined specific nodes for a Tree model. These nodes overrode the childrenItems method to provide children elements. It looks like this method is not used anymore in TreeNodeModel. What should I now use to provide children elements in a TreeNodeModel? Thanks, Christophe. smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] Versionner CI?
Hi Sean, Le 3 déc. 2013 à 06:15, Sean P. DeNigris a écrit : I was surprised there was no job on community contributions... There is one job on the rmod ci server. I should move it to the community server. Thanks for pointing that, Christophe smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] Versionner CI?
I just moved the job to Pharo Contributions: https://ci.inria.fr/pharo-contribution/view/Versions%20and%20Dependencies/ I will also put Metacello job there. Le 3 déc. 2013 à 10:18, Clément Bera a écrit : The jobs's on Rmod: https://ci.inria.fr/rmod/job/Versionner/ 2013/12/3 Sean P. DeNigris s...@clipperadams.com I was surprised there was no job on community contributions... - Cheers, Sean -- View this message in context: http://forum.world.st/Versionner-CI-tp4726899.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] Versionner Impressions
Hi Sean, I made some progress on the following points: Le 3 déc. 2013 à 06:43, Sean P. DeNigris a écrit : Bugs: • I added BabyMock as a dependent project, Versionner showed (stable) in the UI, but when it added it to the baseline, it was loading bleeding edge Fixed • Added packages were a mixture of strings and symbols i.e. 'FMOD', #FMODSpecification, 'BabyMock-Core' For this one, I cannot reproduce. Can you give more information on what you did? • I added a main repository to Versionner, but it didn't appear in baseline when clicked update dev Fixed • If you accidentally navigate away from the version you're viewing, e.g. by clicking on another version, all changes are lost without warning Fixed. There is now a warning. I don't forget the point about repository selection (still in the to do). Cheers, Christophe. smime.p7s Description: S/MIME cryptographic signature
[Pharo-dev] files.pharo.org maintenance
Hello, A maintenance operation will be performed on files.pharo.org to add more storage. It will be performed Monday, December 23rd 2013 between 3:00 pm and 3:30 pm. Zero conf scripts and CI jobs will fail if used at this time. Regards, Christophe. smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] CI server account creation
Hello Alfredo, Le 8 janv. 2014 à 23:58, Alfredo Sanzo a écrit : Hello! I am trying to create an account for the CI server and I have bumped into several links and posts to this list and now that I've asked for help I've finally understood the process (I think). My question is... Can we have this written somewhere? (and corrected, if I'm wrong :) ) Steps to create a new user: a) Sign up for a user here: https://ci.inria.fr/users/new It gets processed manually, so you have to wait until your account is activated for you. = not true. There is no manual validation. Once you get registered, ci.inria.fr send you an email to validate your account. You need to click on the provided link. b) Go to: https://ci.inria.fr/project and look for pharo-contribution. Request to join it. (it also gets processed manually) Yes, an admin of this project has to accept the join request. c) Ask in pharo-dev@lists.pharo.org to be made an Admin, because if not you won't be able to create a Job. Also true. I updated Jenkins to add more permissions to members. All pharo-contibution members are now allowed to manage jobs. I see that Pharo-Contribution page redirects here: https://ci.inria.fr/pharo-contribution/job/JobTemplate/ Can we have that step 1 updated with what I wrote here? Good idea. Done! - Oh, and I can't get through part a) yet Apparently no one is accepting my user... Can somebody help? Maybe you should check your spams. If you cannot find the account activation email, tell me. I can force the account activation. Regards, Christophe. smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] Pharo3 and MetacelloPreview
Hi Johan, You should not do that because Metacello Preview is already loaded in Pharo 3.0. Loading the preview bootstrap is only needed to bootstrap the load of Metacello Preview. Regards, Christophe. Le 13 janv. 2014 à 09:22, Johan Brichau a écrit : Sorry, I meant the loading of the following: ((Smalltalk at: #ConfigurationOfMetacello) new project version: #previewBootstrap) load. On 13 Jan 2014, at 09:18, Johan Brichau jo...@inceptive.be wrote: Hi all, When I load the Metacello Preview in Pharo3, I get a very weird loading of the Phantom-Core-dgg.24 package (which yields a warning because of unexisting classes in the image). Nowhere in my image (thus all loaded configurations) I can find the name 'Phantom'. So where is this coming from? What I can make of the execution stack in Metacello is that 'Metacello-ProfStef-dkh.13' strangely resolves to a loading of 'Phantom-Core-dgg.24' Anyone using the Metacello Preview in Pharo3? Anyone experiencing the same? Johan smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] Strange Versionner behavior
Hi Sean, Le 14 janv. 2014 à 20:31, Sean P. DeNigris a écrit : Sean P. DeNigris wrote - Creating a new configuration adds fileSystemLegacy and fuelMetalevel as dependent projects Okay, I see that a baseline and version have been created with sample data. It is a side effect of this slice: https://pharo.fogbugz.com/f/cases/10578 It is not related to Versionner. Metacello ToolBox uses this template to create new configurations. It is wrong to add examples in this class. I will propose a fix. I thought Versionner was in a more usable state… I will be patient :) You and I pay the price that Pharo3.0 evolves fast. Versionner is a high level tool and is dependent on tools with a lot of updates (spec, komitter, metacello, etc). To focus on Versionner, I do not have a lot of users and I need users to improve it. :) That said, thank you for being a beta-tester ;) Cheers, Christophe. smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] Strange Versionner behavior
Le 14 janv. 2014 à 20:12, Sean P. DeNigris a écrit : - Creating a new configuration adds fileSystemLegacy and fuelMetalevel as dependent projects answered in a previous mail - How do you save changes without committing? After adding a dependent project to the baseline, Update de (sic, label cut-off) It works fine on my laptop. Can you send me a screenshot? doesn't seem to do anything. It should. It is the way to save changes. Maybe I should rename the button to Save Changes and just keep the release and commit buttons aside. Clicking away from the baseline warns me of losing changes but doesn't offer the opportunity to save. - If I select a project in Versionner, and then click the New prone button, the title of the window that pops is the name of the previously selected project, not the newly-created one. Where will the changes actually go? i.e. is it just a labeling error, or am I editing the wrong project? - I reported before, but Versionner needs a standard repositoryChooser that allows to select from known repos or create a new one from a template ( like MC Browser, but hopefully better ;) ) It looks like a Spec problem. It worked well some days ago. I will investigate. Thanks, Christophe smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] Strange Versionner behavior
Hi Norbert, Le 15 janv. 2014 à 00:38, Norbert Hartl a écrit : Am 14.01.2014 um 20:31 schrieb Sean P. DeNigris s...@clipperadams.com: Sean P. DeNigris wrote - Creating a new configuration adds fileSystemLegacy and fuelMetalevel as dependent projects Okay, I see that a baseline and version have been created with sample data. I thought Versionner was in a more usable state… I will be patient :) I was asking myself the same. I used it in 2.0 for months but in 3.0 it doesn’t seem to work. I need user feedback so I will be happy to know what does not work for you. Regards, Christophe. smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] Strange Versionner behavior
Le 15 janv. 2014 à 10:54, Christophe Demarey a écrit : Le 14 janv. 2014 à 20:12, Sean P. DeNigris a écrit : - Creating a new configuration adds fileSystemLegacy and fuelMetalevel as dependent projects answered in a previous mail - How do you save changes without committing? After adding a dependent project to the baseline, Update de (sic, label cut-off) It works fine on my laptop. Can you send me a screenshot? doesn't seem to do anything. It should. It is the way to save changes. Maybe I should rename the button to Save Changes and just keep the release and commit buttons aside. Clicking away from the baseline warns me of losing changes but doesn't offer the opportunity to save. - If I select a project in Versionner, and then click the New prone button, the title of the window that pops is the name of the previously selected project, not the newly-created one. Where will the changes actually go? i.e. is it just a labeling error, or am I editing the wrong project? It looks like a Spec problem. It worked well some days ago. I will investigate. I forgot to answer this one: - I reported before, but Versionner needs a standard repositoryChooser that allows to select from known repos or create a new one from a template ( like MC Browser, but hopefully better ;) ) I planned to do that friday. I extracted the repository chooser from Komitter to share it with Versionner. smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] Serializing Pharo Contribution CI jobs from one matrix
Hi Sven, Le 22 janv. 2014 à 18:24, Sven Van Caekenberghe a écrit : Hi, Is it possible to serialize (i.e. do not execute in parallel) the CI jobs of one matrix of Pharo Contributions ? The Zinc jobs occasionally fails because they interfere with each other (i.e. although they use random ports for servers during unit testing, sometimes they use a port that is already in use by a parallel running job, presumably from the built matrix). Matrix jobs are seen as individual jobs. Maybe you can just tick this option in the job configuration: Run each configuration sequentially There are other solutions: https://wiki.jenkins-ci.org/display/JENKINS/Port+Allocator+Plugin https://wiki.jenkins-ci.org/display/JENKINS/Lockable+Resources+Plugin https://wiki.jenkins-ci.org/display/JENKINS/Exclusion-Plugin Christophe. smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] pharo 3.0 versionner and creating a development version
Hi Norbert, Le 11 févr. 2014 à 11:05, Norbert Hartl a écrit : I try really hard to move to 3.0 at the moment. To me versionner became that important that this is a requirement for me to change the version. I’m testing the bleeding edge version of versionner in 3.0 and this looks really cool. But somehow I cannot create a development version of my project. Whatever I try the only thing I can achieve is that versionner is producing a new baseline method. I used all of the three buttons at the top and did also examine all of the menus (those that work). Any hints? I wrote a small documentation on Versionner: http://chercheurs.lille.inria.fr/~demarey/Tech/Versionner. With Versionner, a development version is always a baseline. If none is found, it will create one from the selected version. Why is it a baseline? because you don't want to update your configuration each time you publish new packages. When you are ready to release, Versionner creates: a numbered version with fixed packages revisions, and the next development version (a baseline). Tell me if you need more information. Regards, Christophe. smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] pharo 3.0 versionner and creating a development version
Le 11 févr. 2014 à 16:15, Norbert Hartl a écrit : Am 11.02.2014 um 14:48 schrieb Christophe Demarey christophe.dema...@inria.fr: Hi Norbert, Le 11 févr. 2014 à 11:05, Norbert Hartl a écrit : I try really hard to move to 3.0 at the moment. To me versionner became that important that this is a requirement for me to change the version. I’m testing the bleeding edge version of versionner in 3.0 and this looks really cool. But somehow I cannot create a development version of my project. Whatever I try the only thing I can achieve is that versionner is producing a new baseline method. I used all of the three buttons at the top and did also examine all of the menus (those that work). Any hints? I wrote a small documentation on Versionner: http://chercheurs.lille.inria.fr/~demarey/Tech/Versionner. With Versionner, a development version is always a baseline. If none is found, it will create one from the selected version. Why is it a baseline? because you don't want to update your configuration each time you publish new packages. When you are ready to release, Versionner creates: a numbered version with fixed packages revisions, and the next development version (a baseline). Tell me if you need more information. I’m not sure I understand. On the symbolic version front we have bleedingEdge that is loading a baseline without exact version information (it loads the newest packages). Then we have development versions that have specific package versions but are not released (not tagged stable). And we have releases that have a sense of to-be-published. Now we have only baselines/development and released versions? Yes. It is quite strange to have three levels of stability. A few users use that and we tried to find a simple process to manage configurations. As in many other languages, you develop, release, then develop again. In another way, I can also understand that you prefer another process or that you need an extra level. I liked to have the three levels because it matches all the requirements in my workflow. That is baseline = development, development = be used by other projects/collaborators before it is released, stable = ready to be released. your definition of the development version looks like a release-candidate. Why not publish (yes release ;) ) a RC version for this purpose? Anyway if it is the case that there is only baseline and released version I do not understand why the versions are having the blessing development. How are those supposed to be tagged stable? They shouldn't. I fixed that friday and it will be integrated soon. At the moment I find it quite confusing how it is. I need maybe one or two more hints. I understand. Versionner was thought to encourage people to follow a workflow that may be different of their current one. But there is still place to discussion, move and adding some other functionalities. Versionner needs feedback and will evolve from feedback. Thanks, Christophe. smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] CI Build Slaves ?
Hi, Le 12 févr. 2014 à 00:08, Sven Van Caekenberghe a écrit : Hi, Does anyone know when all CI Build Slaves will become available again ? Right now, I seems at least Windows is no longer there. It is a bit hard to do integrations like that. ah Windows ... Yes, they need to be restarted time to time. I just restarted Windows slaves but it will take a while before they are seen by Jenkins. If some of you want / need access to CloudStack to manage (at least stopt/start) slaves, I can give you access. you will be able to connect with the account you use with Jenkins. Thanks for pointing this problem, Christophe. smime.p7s Description: S/MIME cryptographic signature
[Pharo-dev] CI maintenance
Hi all, The build farm we use for continuous integration is powered by CloudStack. The version currently running is CloudStack 3.0. We will upgrade to CloudStack 4.2, a version supported by the apache community and fixing a lot of bugs. We hope to have a more reliable cloud with this upgrade. It will also allow, in a closed future, a storage extension (almost full at this time). This upgrade will have impacts on the service but we hope that they will be very short. At the end of the morning/beginning of the afternoon, you may notice: ci.inria.fr downtime (need to reboot some servers) cloudstack portal downtime (upgrade) maybe we will need to restart slaves after the upgrade. To summarize, the CI platform (jenkins, slaves) should be available as usual but there may be some downtimes. Thank you for your understanding, Christophe. smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] Versionner Suggestions
Thanks for the feeback Sean. Done in Versionner repo. Will be integrated soon. Le 13 févr. 2014 à 19:51, Sean P. DeNigris a écrit : 12877 Versionner: Make Project Editing More Prominent https://pharo.fogbugz.com/default.asp?12877 It wasn't immediately obvious to me that I had to double click on a project to edit the configuration. Maybe we should add a button? At minimum, it should be added to the context menu… 12878 Versionner: Filter Test Configurations https://pharo.fogbugz.com/default.asp?12878 Either test configs (e.g. VersionnerTestXMLWriter) should indicate their status, or Versionner should filter out known ones. Right now there seems to be half a dozen such entries shown in Versionner in a fresh Pharo 3.0. - Cheers, Sean -- View this message in context: http://forum.world.st/Versionner-Suggestions-tp4743390.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] Versionner in pharo 3.0
Hi Norbert, Le 19 févr. 2014 à 13:32, Norbert Hartl a écrit : Is anybody using Versionner in 3.0? I would be really interested in some success reports. In my case I cannot achieve much with it. People just start to use Versionner since it was integrated lately (vm problem). I really don’t get when it is creating a baseline version and when a static version. Releasing a valid baseline produces a static version that looks good but also it creates a new baseline. Why? baseline = dev version numbered version = release A project evolves or is ... dead (kind of). That's why a new development version is always generated after a release. I had a discussion with Damien this morning. He argued that Versionner should be able to able to reuse baselines until there is a change to this baseline ... and is right (need to work on that). To avoid problems, Versionner now always create a new baseline for the next development version. Because creating a baseline in any of my projects lead to a bogus configuration. Versionner rewrites project dependency wrongly (projects are named after configurations and not after names I give them. loads: directives are stripped off but references in the rest of the configuration are not changed accordingly). Yes, you reported this bug: https://pharo.fogbugz.com/f/cases/12903. I will work on this one tomorrow. In my current project it creates a baseline with the same version as a static version that already exists. static version = release baseline = new dev version It is a shame because it looks so good but all the funtionalities do not work in my projects except „commit the project“. I hope I’m doing something wrong but then I downloaded a fresh pharo 3.0 this morning and loaded my config and went from there. Are there some other bugs not reported? How to proceed? What kind of test case should I deliver. I think Versionner is pretty important and I should be usable in 3.0. Reporting bugs and provide a way to reproduce is a good start point. Thank you for taking time to test and to report problems, Christophe. smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] image traffic
Le 25 févr. 2014 à 17:37, Norbert Hartl a écrit : If you look at the hosts list than you can see that 75% of the overall traffic is generated by cloud-gw.inria.fr. The CI jobs download the vm with curl. What brings me to the next point. The „Hosts“ section in those states might break a data protection law. I don’t know how they are in france but in germany this would be illegal. We are not allowed to store IP addresses for a longer period. And making them public is really asking for trouble. I think we have some equivalent laws. For another project, we had to anonymize awstats results. Maybe raw statistics should be kept private and only use numbers for marketing. Christophe. smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] Pharo contribution CI: Email on failed build
Hello, Le 25 févr. 2014 à 16:53, Damien Cassou a écrit : On Tue, Feb 25, 2014 at 4:42 PM, Norbert Hartl norb...@hartl.name wrote: Is it possible to receive an email when the build of the project I registered turns to unstable? yes, just add a post build action Email notification and put your email address there. I would suggest to use the Editable email notification. It is a Jenkins plugin (already available on pharo-contribution) that is really better. With this one, you can customize recipients, the mail content, attach the build log, etc. The most important feature to me is that you can define specific triggers like: - on regression send a mail to RecipientsDevelopersRequestorCulprits - on failure, ... - etc. It is usable without configuring anything but the recipient list. The default template is already configured. More details here: https://wiki.jenkins-ci.org/display/JENKINS/Email-ext+plugin Christophe. smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] Versioneer docs?
Hi Phil, Le 1 mars 2014 à 16:50, p...@highoctane.be a écrit : I am now porting my code to 3.0 I am using Versioneer to look at my configuration as when I do load it in 3.0, it seems that there are some duplicate packages coming in my package-cache and I want to remove these dupes. (Mostly Seaside related). Versioneer is very helpful in representing the configuration. Now, is there any doc about its usage? You can find some documentation here: http://chercheurs.lille.inria.fr/~demarey/Tech/Versionner Don't hesitate to give feedback. Versionner gets better with feedbacks I got latest weeks. Maybe you already know but you can use the record directive with Metacello to see what will be loaded, i.e. resolved dependencies from the configuration: https://github.com/dalehenrich/metacello-work/blob/master/docs/MetacelloScriptingAPI.md#recording. It may help to debug. Best regards, Christophe. smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] Just found, i can compile this:
Why arguments should be read only? They are just temporary variables with an initial value. 2014-03-18 15:45 GMT+01:00 Nicolai Hess nicolaih...@web.de: similiar to issue 12419 block arguments should be read only 2014-03-18 15:21 GMT+01:00 Camille Teruel camille.ter...@gmail.com: Indeed, I can compile: Cfoo: arg ^ arg := 3 And 'C new foo: 1' returns 3... On 18 mars 2014, at 15:16, Igor Stasenko siguc...@gmail.com wrote: extent: newExtent vertical ifTrue: [ newExtent := self defaultWidth @ newExtent y ] ifFalse: [ newExtent := newExtent x @ self defaultWidth ]. super extent: newExtent Can you verify it? Arguments should be not assignable. -- Best regards, Igor Stasenko. smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] Just found, i can compile this:
Le 18 mars 2014 à 19:50, Eliot Miranda a écrit : On Tue, Mar 18, 2014 at 10:10 AM, Christophe Demarey christophe.dema...@inria.fr wrote: Why arguments should be read only? They are just temporary variables with an initial value. Read the blue book. It was a decision of the language designers to forbid assignment to arguments to allow debugging. The assignment to block arguments is a side-effect of the old BlockContext implementation of blocks where block arguments were mapped onto temporary variables of the home context. It is an anachronism and should be forbidden also. Thank you for the explanation. I'm just curious why it is so difficult to implement a debugger if arguments are assignable? If you need to restart the execution of a method, and so you need to get the initial value of the argument, I understand you cannot find the value anymore in the method context but it is available in the caller context, no? As I never implemented a debugger, I cannot figure out the difficulties. smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] Just found, i can compile this:
Hi Eliot, Le 19 mars 2014 à 16:25, Eliot Miranda a écrit : Hi Christophe, On Mar 19, 2014, at 1:45 AM, Christophe Demarey christophe.dema...@inria.fr wrote: Le 18 mars 2014 à 19:50, Eliot Miranda a écrit : On Tue, Mar 18, 2014 at 10:10 AM, Christophe Demarey christophe.dema...@inria.fr wrote: Why arguments should be read only? They are just temporary variables with an initial value. Read the blue book. It was a decision of the language designers to forbid assignment to arguments to allow debugging. The assignment to block arguments is a side-effect of the old BlockContext implementation of blocks where block arguments were mapped onto temporary variables of the home context. It is an anachronism and should be forbidden also. Thank you for the explanation. I'm just curious why it is so difficult to implement a debugger if arguments are assignable? If you need to restart the execution of a method, and so you need to get the initial value of the argument, I understand you cannot find the value anymore in the method context but it is available in the caller context, no? As I never implemented a debugger, I cannot figure out the difficulties. the args are no longer available; they get moved from the caller context to the callee. If you think about stack frames then what happens is that the slots containing the outgoing arguments are used as the slots for the incoming arguments. So if arguments are assigned to they are indeed lost. ok, I understand. Thank you for the explanation. But look at how many methods in the system (or in any system). The proportion of methods/functions/procedures that could be written to assign their arguments is very small so the Smalltalk trade off is a good one. I agree we don't really loose something. You can always assign arguments to temporary variables and update temporary variables. My point was just: if possible, why don't do it? Christophe. smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] List editor spec widget
Hello Did you check EditableList? Le 20 mars 2014 à 18:20, Benjamin a écrit : On 20 Mar 2014, at 18:13, Yuriy Tymchuk yuriy.tymc...@me.com wrote: Should this be an extension of List with buttons, of a buttons widget that has a setters for the list to modify and the block for retrieving the rest of items (during the addition action) Sorry I do not understand your question :) But I think the answer is Make a complete new widget, with one list and two buttons, and enough methods to tweak the buttons and the list :) You could even have a dedicated widget for the buttons, so one can replace them with a special new “buttons toolbar” widget Hope it helps, Ben smime.p7s Description: S/MIME cryptographic signature
[Pharo-dev] Versionner screencast
Hello, I made a small screencast on Versionner to explain how to use it: https://www.youtube.com/watch?v=S5Dbmmln8tA Regards, Christophe. smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] Pharo crashes
Yes it looks like there is a bug in the slot class builder. I also have a job failing since #30830 the stacktrace: [0mLayoutEmptyScope(Object)error: LayoutEmptyScope(LayoutAbstractScope)rebase:to: LayoutClassScoperebase:to: LayoutClassScoperebase:to: LayoutClassScoperebase:to: LayoutClassScoperebase:to: LayoutClassScoperebase:to: LayoutClassScoperebase:to: LayoutClassScoperebase:to: LayoutClassScoperebase:to: LayoutClassScoperebase:to: FixedLayout(ObjectLayout)reshapeFrom:to: ClassModificationPropagationpropagate:to: ClassModificationPropagation classpropagate:to: ClassModification(AbstractClassModification)propagate in Block: [ :subclass | propagations add: (ClassModification...etc... MetaclasssubclassesDo: in Block: [ :aSubclass | ... Array(SequenceableCollection)do: MCFileTreeFileUtils class(Class)subclassesDo: MetaclasssubclassesDo: ClassModification(AbstractClassModification)propagate SlotClassBuilderapplyAndUpdateSharedVariableOrSharedPool: in Block: [ :old :new | ... SlotClassBuildertrack:during: SlotClassBuilderapplyAndUpdateSharedVariableOrSharedPool: SlotClassBuilderapplySharedVariableOrPoolChange: SlotClassBuilderapply: SlotClassBuilderbuild PharoClassInstaller class(AbstractClassInstaller class)make: OldClassBuilderAdaptername:inEnvironment:subclassOf:type:instanceVariableNames:classVariableNames:poolDictionaries:category: MCClassDefinitioncreateClass in Block: [ ... BlockClosureon:do: Le 24 avr. 2014 à 13:59, Henrik Johansen a écrit : On 24 Apr 2014, at 1:48 , Marcus Denker marcus.den...@inria.fr wrote: On 24 Apr 2014, at 13:44, jannik laval jannik.la...@gmail.com wrote: Hi pharoers, I am trying to load Phratch in the latest Pharo3.0 Installer Mac (image+vm), and Pharo crashes during the install. Yes, and I have no clue why. Marcus The package I tried loads fine in 80829, but crashes in 80830, so there’s something in that update which needs to be revisited. Cheers, Henry smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] Versionner is even Coooler
Thanks a lot for all your nice words. You were right, there are other contributors to Versionner: first author Alexandre Bergel, then Juan Pablo Sandoval but also a lot of feedbacks from users (a mention to Sean for that) essential for such a tool. Le 20 mai 2014 à 10:10, kilon alios a écrit : can someone explain save to development ? When you do structural changes* in your configuration, it is done in memory. To keep theses changes, you need to save them in the configuration. It is always done in the development version (the only version you can edit is the development version) that is backed by a baseline. If you need to do structural changes, use Save to development to flush your changes. If you only need to generate a new version with packages numbers updated, then use the release version button. * structural change: basically a change made to a baseline: addition/removal of a package / project group, edition of requirements or includes directives. If it is not clear, don't hesitate to ask more explanation. Best regards, Christophe. smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] Versionner is even Coooler
Le 20 mai 2014 à 14:28, Ben Coman a écrit : Christophe Demarey wrote: Thanks a lot for all your nice words. You were right, there are other contributors to Versionner: first author Alexandre Bergel, then Juan Pablo Sandoval but also a lot of feedbacks from users (a mention to Sean for that) essential for such a tool. Le 20 mai 2014 à 10:10, kilon alios a écrit : can someone explain save to development ? When you do structural changes* in your configuration, it is done in memory. To keep theses changes, you need to save them in the configuration. It is always done in the development version (the only version you can edit is the development version) that is backed by a baseline. If you need to do structural changes, use Save to development to flush your changes. If you only need to generate a new version with packages numbers updated, then use the release version button. * structural change: basically a change made to a baseline: addition/removal of a package / project group, edition of requirements or includes directives. If it is not clear, don't hesitate to ask more explanation. Best regards, Christophe. So would Save to baseline mean the same as Save to development? Kind of. The idea is to hide the baseline complexity from the user point of view. The user only see releases (numbered version) and the development version where changes are possible. 'Save to baseline' is not clear about the baseline that will be used to save. In fact, development points to the latest baseline and creates new one if needed (ex: baseline used by a release that you need to edit). smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] Pharo contribution plot plugin update
Done! Le 20 mai 2014 à 16:55, Yuriy Tymchuk a écrit : Hi, I don’t have access to jenkins config, but it looks like the Plot Plugin[1] is not latest version. Can someone please update because they added support for matrix jobs. Uko [1] https://wiki.jenkins-ci.org/display/JENKINS/Plot+Plugin smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] String deduplication
Le 30 mai 2014 à 09:39, Philippe Marschall a écrit : Hi This is an idea I stole from somebody else. The assumption is that you have a lot of Strings in the image that are equal. We could therefore remove the duplicates and make all the objects refer to the same instance. I worked on a String optimisation for a Java virtual machine dedicated to small hardwares. A string was represented by an array of bytes (UTF8 or ASCII encoding), a start position, and the number of characters of the string. It allows to reuse the internal byte array for different strings but the String object was different for each String. With this approach, you are able to save a lot of memory (but with some CPU overhead) and you don't have a problems because you have different String objects for each String. ex: b1: 'Hello World! It's a sunny day' 'Hello World! It's a sunny day' : start = 0, count = 29, value b1 'Hello' : start = 0, count = 5, value b1 'Hello World!' : start = 0, count = 12, value b1 'World': start = 6, count = 5, value b1 I don't see how it may be applied to Smalltalk and it makes sense. Christophe. smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] Zero Conf in windows CI
Le 31 mai 2014 à 09:55, Guillermo Polito a écrit : Hi guys! I'm trying to configure a windows (7-32bits) slave to run DBXTalk tests :). I've had a lt of troubles already trying to configure right mingw and get it to compile C, but I succeeded. Now, I'm trying to get it run tests in Pharo, but I have problems with ZeroConf and probably temp directories. The log is here: https://ci.inria.fr/dbxtalk/job/DBXTalk-OpenDBXDriver-Mysql/PHARO_VERSION=30,Platform=dbxtalk-windows-32bit,VERSION=bleedingEdge/59/console In summary, I have the following output: Downloading the latest 30 Image: http://files.pharo.org/image/30/latest.zip Access denied - IMAGE.QGJEMX File not found - -NAME The access denied I think is from the rm -rf of the temp directory, because the temp directory is created in the workspace and the image file is there and unzipped. The File not found looks like coming from the find. Maybe I'm lacking some environment variables I didn't configure... I tried comparing my slaves with the ones used in Pharo and I didn't take it much further. Additionally, if I connect to the slave through remote desktop (:puke:), and try to execute the zero conf script with the same user, on the same folder from a msys console, I have no errors. Maybe someone has an idea? :) Indeed. Very strange. You can find all environment variables available to your jenkins job for this slave here: https://ci.inria.fr/dbxtalk/computer/dbxtalk-windows-32bit/systemInfo There are some other variable added on the fly, depending on your job config (values of axis in matrix jobs for example). I defined a test job to debug that: https://ci.inria.fr/dbxtalk/job/test-zeroconf/8/console The error comes from the http://get.pharo.org/vm. It looks like a permission problem to write in the workspace of your slave. Hope this helps, Christophe. smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] github metacello pero and jenkins matrix builds
Metacello implementation of the github protocol uses a zip file downloaded from github and then extracted in a temp folder. See https://github.com/dalehenrich/metacello-work/blob/master/repository/Metacello-Platform.pharo30.package/MetacelloPharo30Platform.class/instance/downloadFile.to..st Metacello code is not robust enough. It should check for a not-used temporary file name. Check MCGitHubRepositoryprojectDirectoryFrom: version: zipFileName := '/tmp/github-' , (downloadCacheKey select: [ :c | c isAlphaNumeric ]) , '.zip'. The problem is not related to Zinc. So, Metacello should be fixed. As a workaround, you can also specify to run only 1 instance of your job at a time. Christophe Le 6 juin 2014 à 08:39, Yuriy Tymchuk a écrit : Looks like ZnFileSystemUtils are doing this. As far as i understand, the problem occurs when two matrix lobs run at the same time and so one downloads thing into /tmp, and other one encounters a problem. Isn’t this some sort of bug in Zinc? Uko On 06 Jun 2014, at 11:54, Yuriy Tymchuk yuriy.tymc...@me.com wrote: On 06 Jun 2014, at 11:19, Max Leske maxle...@gmail.com wrote: On 06.06.2014, at 07:28, Yuriy Tymchuk yuriy.tymc...@me.com wrote: Sorry for bothering guys, but I really get random errors. For example last one I saw is: An attempt to use interactive tools detected, while in non-interactive mode FileDoesNotExistException: '/tmp/github-UkoVnaExportermaster.zip' Can anybody help me to localise the problem? Is the Jenkins configuration wrong? Or I should do things in a completely different way? Did you specigy /tmp as output folder? If so, you should use the working directory (which will be the build directory). You can not assume to have write permissions on /tmp. Yes, that’s the thing. I guess /tmp is used by something in metacello-filetree-github toolchain. That’s why I’m asking because I’ve never worked with is a lot. Uko Uko On 31 May 2014, at 14:40, Yuriy Tymchuk yuriy.tymc...@me.com wrote: Hi guys, So I’m using this fancy metacello github urls, like: github://user/project[:branch|tag|SHA][/path] and some of my Jenkins matrix builds are randomly failing with: Error: /tmp/github-UkoRenrakumaster.zip already exists anyone has an idea how to solve this? Uko smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] Spec list with checkboxes?
Did you check TreeModelbeCheckList ? Le 16 juin 2014 à 14:36, Yuriy Tymchuk a écrit : Hi everyone. I need to generate arbitrary number of checkboxes and I wander if there is something like a list with checkboxes or something similar. I know that I can use dynamic UI, but maybe there are some existing components that can help to solve the problem. Uko smime.p7s Description: S/MIME cryptographic signature
[Pharo-dev] about ~=
Hi, I would like to make a suggestion that may lead to a long debate but let's go: What do you think about deprecating ~= and replace it with != for example? Why? In mathematics the symbol ~ is used for equivalence. To me (and I think any newcomer to Smalltalk) the first guess of the meaning of ~= is equivalent to = missed. The meaning is totally different: Answer whether the receiver and the argument do not represent the same object. I never used this method because it is too confusing for me. I prefer to use (a = b) not or (a = b) ifFalse:. So, the discussion is open ... Christophe smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] about ~=
Le 26 juin 2014 à 12:46, Nicolas Cellier a écrit :
$! is not classified as a binary character right now, is it?
Of course it's possible but I'd just say why this particular symbol?
It does not look mathematical either. Or do you love C/C++ so much?
Of course not. It is just because it is something widely used but other names
could do the stuff like or /=
Note that ~= has same meaning in Matlab.
There are other possibilities like /= or (Fortran 95, ADA), even the long
form =/=.
But frankly, I don't buy this kind of change, for the sake of looking like
some {} language, making such a deep change is overkill.
Indeed it is a deep change but maybe at least we could have an alias and use it
for all new code. At a time, it will be less painful to do this change.
As expressed in another thread, Smalltalk code convention for method naming
strategy is intention revealing.
That said, I think ~= is not intention revealing and it will be good to fix or
propose a good alternative.
smime.p7s
Description: S/MIME cryptographic signature
Re: [Pharo-dev] Spec, groups and version-specific packages
Hi,
You can find useful information into the 'Deep into Pharo' book, chapter 9
(Managing projects with Metacello), section 9.12 (platform specific package).
Example:
ConfigurationOfCoolBrowserbaseline09: spec
version: '0.9-baseline'
spec for: #common do: [
spec blessing: #baseline.
spec repository: 'http://www.example.com/CoolBrowser'.
spec
package: 'CoolBrowser-Core';
package: 'CoolBrowser-Tests' with: [ spec requires:
'CoolBrowser-Core' ];
package: 'CoolBrowser-Addons' with: [ spec requires:
'CoolBrowser-Core' ];
package: 'CoolBrowser-AddonsTests' with: [
spec requires: #('CoolBrowser-Addons'
'CoolBrowser-Tests' ) ].
spec
group: 'default' with: #('CoolBrowser-Core'
'CoolBrowser-Addons' );
group: 'Core' with: #('CoolBrowser-Core' 'CoolBrowser-Platform'
);
group: 'Extras' with: #('CoolBrowser-Addon');
group: 'Tests' with: #('CoolBrowser-Tests'
'CoolBrowser-AddonsTests' );
group: 'CompleteWithoutTests' with: #('Core', 'Extras' );
group: 'CompleteWithTests' with: #('CompleteWithoutTests',
'Tests' )].
spec for: #gemstone do: [
spec package: 'CoolBrowser-Platform' with:
'CoolBrowser-PlatformGemstone'].
spec for: #pharo do: [
spec package: 'CoolBrowser-Platform' with: 'CoolBrowser-PlatformPharo'].
Le 26 juin 2014 à 13:43, Roberto Minelli a écrit :
Hi,
I have my project with my Configuration and I am using spec groups to load
different sets of packages (e.g., development and user groups).
With the porting to Pharo 4.0 I discovered that there are some
functionalities specific to Pharo 3.0 and others to Pharo 4.0, for example
the fact that MethodContext is no longer part of Pharo 4.0. but it has been
replaced by Context.
I moved such functionalities in a package, say 'MyProject-Extension30’ and
Pharo 4.0 specific functionalities in 'MyProject-Extension40’.
Now the question is, suppose that I have a group like
spec group: ‘User' with: #(‘A’ ‘B’ ‘C’).
and another one:
spec group: ‘Dev' with: #(‘A’ ‘B’ ‘C’ ‘D’ ‘E’).
Until now, the developer (i.e., me) would do something like
(self project version: #bleedingEdge) load: #('Dev’)
and a used of my project would do
(self project version: #bleedingEdge) load: #(‘User’)
How can I factor inside the dynamic load of the two Pharo-version specific
packages?
i.e., no matter if ‘User’ or ‘Dev’ group is loaded I need to load
'MyProject-Extension40’ if I am on Pharo 4.0 and 'MyProject-Extension30’ if
on Pharo 3.0.
Thanks for your help,
Roberto
smime.p7s
Description: S/MIME cryptographic signature
Re: [Pharo-dev] Spec, groups and version-specific packages
Le 26 juin 2014 à 14:49, Roberto Minelli a écrit : Hi Christophe, Thanks for the answer. I managed to do that! Am I interpreting something wrong or the CoolBrowser-Platform itself is an empty package? Some kind of. It is just a name you define that will then be bound to a real package. smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] Versioner
Hi Stephan, Le 30 juin 2014 à 20:50, Stephan Eggermont a écrit : Kilon wrote: I disagreed with this Stephan That being said, I am getting a bit nervous about how versioner is released. It should aim to improve the way people can work, and not to create a single workflow for all people working on pharo projects. I hope my fears are unfounded. this what I was replying to. Ok. The concrete problem we ran into with the current version of Versioner is that it wants to resolve dependencies to exact versions. For configurations depending on Seaside, Magritte or Grease, this is normally unwanted. They should depend on the symbolic release versions. With the high number of changes in Pharo, exact versions have a short lifetime. I don't think it is the problem because the solving to exact versions is an option (You have a check box). The real problem is the support of platform-specific sections. Dale wrote: In a programming language where the development environment allows script-based tools (as opposed to GUI-based tools) it is much easier to construct custom tools to support variations in workflow ... individual developers routinely copy/share scripts that routinely need to be customized for their environment ... In order to work together effectively in open source projects it is important that contributors know what workflow is used in a project. That is easier when the number of different workflows is limited. Because projects depend on other projects the number of combinations of workflow is very large. Scriptable tools can easily support these resulting combinations. Building a GUI tool that is both very flexible and very easy to use seems to be less easy. Yes but some part are reusable. For example, Versionner uses MetacelloToolBox that was not thinked to support the current Versionner workflow. Versionner has some classes (model, commands) aside the GUI that can be reused for other workflows. Christophe. smime.p7s Description: S/MIME cryptographic signature
[Pharo-dev] STON questions
Hi, I read the STON paper and the STON chapter in EnterprisePharo but I did not find answers to some questions: how do you tell STON to not serialize some variables of an object? is there a way to avoid the class tag? What I mean is that I would like a synthetic STON String. If a STON entry has a class tag, STON knows which class to instantiate. This class may also know which classes to instantiate for its i-var. In this case, the class tag may be omitted. Maybe I should redefine fromSton;, but in this case, is it possible to avoid a manual parsing of the string? is there a way to do an alias for an i-var (just like for the class name)? is there a way to skip the serialization of an i-var if its value is nil (or an empty collection)? Regards, Christophe. smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] Check multiple boxes in TreeModel
Le 28 août 2014 à 15:31, Yuriy Tymchuk a écrit : HI guys, is it possible? I’ve tried `autoDeselection: false`, `multiSelection: true`… and it continues to deselect selected items :(. Maybe there is any kind of example how to do a classic checkbox tree? For example if we have filesystem and want to select which items to backup. I did not check the code but at least Komitter do the thing you want to do. It should be easy to trigger out the way to configure your treeModel from there. Christophe smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] Jenkins builds not properly preserving artifacts?
Le 2 sept. 2014 à 12:53, Marcus Denker a écrit : On 02 Sep 2014, at 11:41, Tim Mackinnon tim@testit.works wrote: Marcus - how do you navigate to that view from the Build #890 of PharoLauncher? When I click on the link you show - thats that output I first saw in the console from the list of builds for Pharo Launcher (which is what I was looking for) - and when I click on “Back To Project” it takes me to the 890 build results page - however if I was looking at build 889 - where on that page do I click to see that output? It is not nice… Untitled 3.png But something is strange in the setup: it only runs on windows and does not show good names. The Pharo build looks better: https://ci.inria.fr/pharo/job/Pharo-4.0-Update-Step-2.1-Validation-A-L/ No idea, needs to be configures somehow… Jenkins is not that “nice” from the UI as it targets developers who get used to it somehow. The bad thing is that a matrix job is used instead of a standard job. Jenkins could manage that better but it would have been better to use the appropriate job. There is no reference to a windows build only. smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] How to see a Pharo job configuration - getting null pointer error?
Le 3 sept. 2014 à 17:59, Tim Mackinnon a écrit : Believe me, I understand the PIA part of CI ;) You are right about the account though. I do have an account - so I tried logging in to ci.inria.fr - and I get a dashboard to navigate down to Pharo-contributions, but clicking the jenkins button for that project gives me the https://ci.inria.fr/pharo-contribution/? link I’ve been used to. Pay attention that ci.inria.fr and ci.inria.fr/aproject don't point to the same web site / host. It means that even if you are logged in ci.inria.fr, you need to log in on ci.inria.fr/xxx to be able to manage jobs, see configurations, etc. It is a bit boring, but at least, it is the same user name / password. smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] Spec license
Le 3 sept. 2014 à 10:24, Torsten Bergmann a écrit : It is interesting that there is also a new Spec release [2] announced this week I can see in the announce: Adds SpecTableLayout, thanks @webwarrior-ws Removes hardcoded colors, thanks @Uko Do the authors of contribution (or their company if the contribution is done at work) agree on the new spec license? If not, it cannot be part of the new spec and could be integrated in Pharo spec. If so, we won't be able to integrate these fixes in Pharo. It woud be good that spec contributors clarify their position. Regards, Christophe. smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] Spec license
Yes, you should add a slice in the Pharo inbox with your contribution but ... it depends under which license you first published your contribution. If it was MIT, it is fine (and spec is out of law). If it was the double licensing, we will not be able to integrate it into Pharo. We should re-implement this functionality. I know these things are boring but we should take care to avoid potential problems in the future. Le 4 sept. 2014 à 11:13, Yuriy Tymchuk a écrit : Oh wow, it’s amazing how complicated things can get… What you I have to do to have fixes available in Pharo? Send a slice to Pharo inbox? I just want to use dark theme in pharo and don’t have ugly UI parts Uko On 04 Sep 2014, at 10:52, Christophe Demarey christophe.dema...@inria.fr wrote: Le 3 sept. 2014 à 10:24, Torsten Bergmann a écrit : It is interesting that there is also a new Spec release [2] announced this week I can see in the announce: Adds SpecTableLayout, thanks @webwarrior-ws Removes hardcoded colors, thanks @Uko Do the authors of contribution (or their company if the contribution is done at work) agree on the new spec license? If not, it cannot be part of the new spec and could be integrated in Pharo spec. If so, we won't be able to integrate these fixes in Pharo. It woud be good that spec contributors clarify their position. Regards, Christophe. smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] Spec license
Le 5 sept. 2014 à 09:38, Yuriy Tymchuk a écrit : I’ve made fixes long time ago before Ben left. + my change is in Pharo image. Is this enough? I think so. All code contributed to Pharo via Fogbugz is licensed under MIT. Problems may come if you did a pull request on the spec git repo after the re-licensing. smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] Pharo 4.0 Update Trigger
Le 11 sept. 2014 à 11:14, Yuriy Tymchuk a écrit : Hi FYI, I’ve added Pharo-4.0-Update-Trigger job on CI https://ci.inria.fr/pharo-contribution/job/Pharo-4.0-Update-Trigger/ so if you have a CI job for your project and it should run on Pharo4, you can re-run it after Update trigger is built to be sure that no changes broke your project. Good idea. Thanks smime.p7s Description: S/MIME cryptographic signature
[Pharo-dev] Zinc-rest URL matching
Hi,
I use Zinc-Rest and it works like a charm, really simple to quickly get
something working.
I have a question about URL pattern matching that is used to dispatch request
to the right handler.
I want to have following URLs:
/foo/*
/foo/latest
I defined 2 handlers with following patterns:
#('foo' '*')
#('foo' 'latest')
I was expecting that the more precise handler was chosen but it was the generic
handler (with '*'). Is there a way to do that?
It is not blocking because I can use the same handler to manage both patterns
but I would prefer to have them separated as the semantic is not the same.
Regards,
Christophe.
smime.p7s
Description: S/MIME cryptographic signature
Re: [Pharo-dev] Zinc-rest URL matching
Le 12 sept. 2014 à 10:50, Santiago Bragagnolo a écrit : You may want to check this thread. http://forum.world.st/ANN-Teapot-0-8-micro-web-framework-tp4774449.html Hope it solves your needs :) Thanks, nice framework. Interesting to know smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] Zinc-rest URL matching
Hi Sven,
Le 12 sept. 2014 à 11:59, Sven Van Caekenberghe a écrit :
Hi Christophe,
On 12 Sep 2014, at 10:28, Christophe Demarey christophe.dema...@inria.fr
wrote:
Hi,
I use Zinc-Rest and it works like a charm, really simple to quickly get
something working.
I have a question about URL pattern matching that is used to dispatch
request to the right handler.
I want to have following URLs:
/foo/*
/foo/latest
I defined 2 handlers with following patterns:
#('foo' '*')
#('foo' 'latest')
I was expecting that the more precise handler was chosen but it was the
generic handler (with '*'). Is there a way to do that?
It is not blocking because I can use the same handler to manage both
patterns but I would prefer to have them separated as the semantic is not
the same.
Regards,
Christophe.
My first answer would indeed also have been to handle both cases in one call
(I did similar things in my projects). But now that you mention it, I think
this can be fixed quite easily. Have a look at the following version:
===
Name: Zinc-REST-SvenVanCaekenberghe.16
Author: SvenVanCaekenberghe
Time: 12 September 2014, 11:55:02.020483 am
UUID: 6421d8be-c7c8-44fc-8958-121cc86ae93e
Ancestors: Zinc-REST-SvenVanCaekenberghe.15
ZnCallHierarchyRestUriSpace#match: now uses #order to sort auto matched
REST call subclasses - a lower order call will be matched before a higher
order call.
===
By default, calls inherit order 50, to make move one call earlier in the
matching process, override #order with a lower number.
Indeed, it does the trick with only a few changes :)
I wonder if it would be a good idea to give a default lower priority (ex: 20)
if the pattern ends with a '*'. It could be done in the order method. I think
you will never had to override priority this way but it has a little CPU
overhead.
Thanks for the quick feedback. It looks like functionality on-demand :)
Christophe
smime.p7s
Description: S/MIME cryptographic signature
Re: [Pharo-dev] Versioner does not work on Pharo 4
Hi Kilon, You error is strange. I use Versionner on Pharo 4.0 without any problem. If I take a closer look at the stack trace, the error comes from the MetacelloToolBox when Versionner asks for configuration classes. What is really strange is that after this message sent, the stack shows the execution goes through EphPyParser class(Object)mustBeBoolean. I don't get why. I tried in a fresh Pharo image to load Ephestos, create a config for it, and got no problem. Can you try to reproduce and give more information about the environment, what you did? Thanks, Christophe. Le 17 sept. 2014 à 16:57, kilon alios a écrit : So I tried today to open versioner to make a configuration for Ephestos and i got this error RBMethodNode(Object)doesNotUnderstand: #asSequenceNode EphPyParser class(Object)mustBeBooleanInMagic: EphPyParser class(Object)mustBeBoolean MetacelloProjectRegistration classExecuteUnOptimizedIn: EphPyParser class(Object)mustBeBooleanInMagic: EphPyParser class(Object)mustBeBoolean [ :cl | (answer includes: cl) ifFalse: [ (([ cl isMetacelloConfig ] on: Error do: [ :ex | ex return: false ]) and: [ cl name asString beginsWith: 'ConfigurationOf' ]) ifTrue: [ answer add: cl ] ] ] in MetacelloProjectRegistration classconfigurationClasses in Block: [ :cl | ... OrderedCollectiondo: MetacelloProjectRegistration classconfigurationClasses MetacelloToolBox classconfigurationClasses MBConfigurationRootconfigurationClasses MBConfigurationRootconfigurations VersionnerSpecBrowser classimageConfigurations VersionnerSpecBrowser classopen [ VersionnerSpecBrowser open ] in VersionnerSpecBrowser classmenuCommandOn: in Block: [ VersionnerSpecBrowser open ] BlockClosurecull: [ | selArgCount | show cursor in case item opens a new MVC window (selArgCount := selector numArgs) = 0 ifTrue: [ target perform: selector ] ifFalse: [ selArgCount = arguments size ifTrue: [ target perform: selector withArguments: arguments ] ifFalse: [ target perform: selector withArguments: (arguments copyWith: evt) ] ]. self changed ] in ToggleMenuItemMorph(MenuItemMorph)invokeWithEvent: in Block: [ ... BlockClosureensure: CursorWithMask(Cursor)showWhile: ToggleMenuItemMorph(MenuItemMorph)invokeWithEvent: ToggleMenuItemMorph(MenuItemMorph)mouseUp: ToggleMenuItemMorph(MenuItemMorph)handleMouseUp: MouseButtonEventsentTo: ToggleMenuItemMorph(Morph)handleEvent: MorphicEventDispatcherdispatchDefault:with: MorphicEventDispatcherdispatchEvent:with: ToggleMenuItemMorph(Morph)processEvent:using: MorphicEventDispatcherdispatchDefault:with: MorphicEventDispatcherdispatchEvent:with: MenuMorph(Morph)processEvent:using: smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] Versioner does not work on Pharo 4
Le 19 sept. 2014 à 11:21, kilon alios a écrit : Well to kepp you updated , because I did not bother replying to my own thread since none seemed to care or have the same issue as me. I was out of office last days ... I tried on windows again same error as macos on a fresh image by the way. So I know it must not be me. On which image? I just tried on a fresh 3.0 image and it also works for me. The only things I am doing with pharo is 1) use dark theme 2) use free type font Arial on windows and Monaco on macos 3) use filetree for working with a git directory. Maybe a side effect. Could you give me a script to help reproducing the problem? Maybe just your startup script. Does the problem appear the first time you open Versionner? Thanks, Christophe. smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] Interesting Date/Time Thread on Squeak Dev
Le 19 sept. 2014 à 14:59, Esteban A. Maringolo a écrit : Pharo Date/DateAndTime are incremental[1], then all this week/month/year operations will simply add/subtract the increment from epoch. The only way to do this in a deterministic way is to have a field based Date. Yes, it would be a good idea. Then, you may have today + 1 month, today + 1 financialMonth, ... smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] Exceptions chapter of Deep Into Pharo
Hello, Le 23 sept. 2014 à 04:36, Martin McClure a écrit : On 09/22/2014 09:43 AM, Damien Cassou wrote: On Mon, Sep 22, 2014 at 4:44 PM, Martin McClure mar...@hand2mouse.com wrote: OK, send me the SVN info and I'll work on the edits. please create an account on https://gforge.inria.fr and ask to join the project pharobooks. Argh. I stupidly mis-typed my email address during account registration, so I'm pending email confirmation and the email will never be delivered. Any way to fix this or do I need to try again with a different login name? My login name is martinmcclure. You can ask the forge admins to fix your email address. Send an email to help.et.gfo...@inria.fr. Regards, Christophe. smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] [Pharo-users] Versioneer. nice. mmMmmm...
Hi Ben, Le 22 sept. 2014 à 18:23, Ben Coman a écrit : While I had done the Versioneer tutorial some time ago, I had some inertial problem using it in anger. Now I'm happy to report using it just now to update the ConfigurationOfPharoLauncher was simple and smooth - which is great since I've never done a Configuration by hand. I thought it would be useful for others to see how simple it was... 1. Loaded latest ConfigurationOfPharoLauncher. 2. Loaded and tested newer PharoLauncher packages. 3. Opened World Tools Versioneer. 4. Selected PharoLauncher and Open Project. 5. Selected development list item. 6. Clicked Release Version and Ok to accept auto increment of version number. 7. Clicked Commit the project Now there is an updated ConfigurationOfPharoLauncher in its Smalltalkhub repository. Easy with Versioneer. mmM. nice. shiny. cheers -ben I'm happy to see that this tool is useful. Still improvable on many points but helps a lot for basic tasks. Christophe smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] is Kommiter working for you in 40 latest?
Le 1 oct. 2014 à 07:37, stepharo a écrit : is Kommiter working for you in 40 latest? yes, works fine for me smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] GTPlayground Play Button Semantics
Le 1 oct. 2014 à 16:55, Tudor Girba a écrit : Cmd+g sounds like fun :). The other thing could be to have cmd+i as a replacement for cmd+o when you are in the inspector. When outside, Cmd+i would spawn an inspector window if the surrounding browser does not support in-place inspection (like the playground). To force inspect in a new window we could use Cmd+Shift+i and this would be uniformly applied everywhere. What do you think? Yes, I like it. no need of a new shortcut. It was the first thing I tried in the Playground before seeing the arrow in the menu. Christophe. smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] Cmd-o is not opening a new pane?
Le 3 oct. 2014 à 08:26, Esteban Lorenzano a écrit : well, but that’s something that *now* you cannot do. what people will see now is “cmd+i does one thing in playground, and other thing in other parts of the system. Maybe it is me but what I see is cmd+i = inspect. I will be more confused to use cmd+o in GT and cmd+i everywhere else. My 2 cents, Christophe. smime.p7s Description: S/MIME cryptographic signature
[Pharo-dev] playground size
Hi, First I need to say, I love the new GT tools. It really goes a step further. I just wanted to say that I find the Playground window quite big (at least 1/4 of the whole Pharo window). I understand that the size is bigger than a simple workspace to be able to display panes after clicking play but if you just need to evaluate ()do-it, print-it) some code, it is over-sized. Would it be possible to have a default window size smaller and resize automatically if you need to display an inspector pane? Regards, Christophe. smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] gt issues
Hello, Le 4 oct. 2014 à 11:51, Tudor Girba a écrit : Pharo needs a centralised way to manage tabs and windows, its a system heavily wait that is wrong solely based on GUIs. So this is not a GT issue, its more a Pharo issue. The problem with GT because is such a detailed tool it exposes this Pharo weakness a lot more than other tools. The GTInspector problem will be solved by adding the possibility for each last tab to close. Please, add these feature for all tabs (maybe not for the first one but it does not matter). I often need to hide/close intermediates tabs that are just there because they were needed for the navigation. At the end, I just want to keep inspectors on objects I want to look at. Regards, Christophe. smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] gt issues
Hi Doru, Le 6 oct. 2014 à 23:33, Tudor Girba a écrit : Hi Christophe, We will start with adding the possibility of closing the last pane. It is unlikely that we will add closing of random panes in the inspector because the main purpose of those panes is to preserve the navigation path. For preserving inspectors on independent objects, we need another solution. I believe for this case, we could simply use a kind of a clipboard for objects that can be inspected at a later time. It may be an idea. I was just thinking on another possibility: if you want to keep the navigation history, just get a way to quickly identify valuable tabs and be able to navigate quickly between them. Maybe something like the star/unstar feature of GitHub. Anyway, the important thing to remember is that there is a need for a way to keep some objects that we would to inspect later, whatever the implementation is. Regards, Christophe. smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] BlockClosure source code
Le 15 oct. 2014 à 14:18, Ben Coman a écrit : Marcus Denker wrote: On 14 Oct 2014, at 16:42, Marcus Denker marcus.den...@inria.fr mailto:marcus.den...@inria.fr wrote: On 10 Oct 2014, at 12:29, Marcus Denker marcus.den...@inria.fr mailto:marcus.den...@inria.fr wrote: On 10 Oct 2014, at 10:57, Jan Kurš k...@iam.unibe.ch mailto:k...@iam.unibe.ch wrote: Hi All, Thank you for the replies. I see it is not an easy bug to fix. Do you have any idea, when this can be fixed? I will try to fix it next week... Or can you suggest me some other way/workaround, how to get/generate the source code of a block? The old compiler used a hack to decompile blocks for getting a textual representation… one could port the code from Pharo2 to the Package OpalDecompiler in Pharo4. (but I actually like the current scheme of using the byte code-offset-to-AST mapping more). step one: A nice tool… GTInspector view of the byte codes that highlights what is thinks is the corresponding code in the source. (This living Bytecode view replaces what before just printed out the #longPrintString of the CompiledMethod): This is now in 4.0 update 306. e.g. inspect OrderedCollection#do: then select the “SymbolicBC” tab, click on a byte code, then select in the second view the “Source” tab. == when moving around the byte code, the text highlights the code that generated the byte code. Marcus This is be great to pull more people into understanding (and helping) the dark depths. What about a tab in the second pane named Help that describes what each bytecode does? (half serious) For example, line 32, what is the 2 in pushTemp: 2, and 1 in pushConstant: 1. the index smime.p7s Description: S/MIME cryptographic signature
[Pharo-dev] Monticello package cache
Hello,
I find the implementation of MCCacheRepository(class)defaultDirectory a bit
strange:
defaultDirectory
| directories |
directories := {('package-cache' asFileReference). (FileLocator
temp). (FileLocator home)}.
directories
do: [ :directory |
[ ^ directory ensureCreateDirectory; yourself ]
on: Error do: [ ignore and try the next
directory ] ].
Error signal: 'Can''t create a package-cache'
We first search in the working directory (looks good), and then we try to use
the temporary directory or the home directory without creating any directory
hierarchy (e.g. pharo/package-cache).
I would like to, at least, add 'pharo/package-cache' directories for temp and
home.
Another problem is that it is not consistent with FileLocator(class)cache. It
points to the system cache directory that is not used by MCCacheRepository.
WDYT?
Christophe.
smime.p7s
Description: S/MIME cryptographic signature
Re: [Pharo-dev] VersionnerRepositoriesManager - Why clear okAction?
Hi Sean, Le 23 oct. 2014 à 23:16, Sean P. DeNigris a écrit : No class is safe from my wrath he he... VersionnerRepositoriesManager class#open | dialog | dialog := remotesUI openDialogWithSpec. dialog okAction: [ ] - why were we wiping the okAction? dialog okAction: [ ] does not reveal any intention. At minimum, a comment would be good I fully agree. I wrote the code some months ago and I forgot the reason ... I think the setting of the okAction is useless. I often put a comment but i miss this one. Thanks for the feedback. - it would be good to return something here so users can customize more easily. Even though this is tightly integrated with Versionner, a tiny bit of care makes the system more easily extensible. We should record some patterns here... Maybe what you need is RemotesManager. I extracted this component from Komitter. smime.p7s Description: S/MIME cryptographic signature
[Pharo-dev] Zinc running on privileged ports
Hello, I just tried to get a simple Zinc server running on the standard HTTP port (80) and it is not working. ZnServer startDefaultOn: 80 My image was run with a standard user. As the standard HTTP port is a privileged port (each port number 1024 is a privileged port), I tried to run it through sudo. It is not working with PharoLauncher (loss of permissions with the process fork?) but works by running the image directly. The thing that is strange to me is that if I try to run Zinc on a port with not enough permissions, I do not get an error. I saw a test of the socket validity in ZnNetworkingUtilsserverSocketOn: but I think it is not catching the permissions problem. Is it difficult to detect? If not, it would be good to have an exception if the specified port cannot be used. Christophe. smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] Zinc running on privileged ports
Le 31 oct. 2014 à 16:19, Sven Van Caekenberghe a écrit : Hi Christophe, On 31 Oct 2014, at 14:21, Christophe Demarey christophe.dema...@inria.fr wrote: Hello, I just tried to get a simple Zinc server running on the standard HTTP port (80) and it is not working. ZnServer startDefaultOn: 80 My image was run with a standard user. As the standard HTTP port is a privileged port (each port number 1024 is a privileged port), I tried to run it through sudo. It is not working with PharoLauncher (loss of permissions with the process fork?) but works by running the image directly. So basically, it works. Good. I never tried that. I/we always put a proxy in front for production deploys. The thing that is strange to me is that if I try to run Zinc on a port with not enough permissions, I do not get an error. I saw a test of the socket validity in ZnNetworkingUtilsserverSocketOn: but I think it is not catching the permissions problem. Is it difficult to detect? If not, it would be good to have an exception if the specified port cannot be used. There is ZnServer#isListening that tries to do that. In the end it comes down to what is available to the Socket API and how it behave across different platforms. You can access the server socket with #serverSocket. Yes, I think it is a limitation of the Socket API. smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] [Pharo-users] inria survey
Le 6 nov. 2014 à 12:21, Bernat Romagosa a écrit : What should I enter under Establishment? Is it the company/institution where one works/studies? Yes, your company/institution where one works/studies smime.p7s Description: S/MIME cryptographic signature
[Pharo-dev] playground history
In the latest Pharo4 (at least), the history of the text written in the Playground has gone! There is a nice publish icon but no way to get the history. Do I miss something or was it really removed? The history is very useful and I would like to get it back. Thanks, Christophe. smime.p7s Description: S/MIME cryptographic signature
[Pharo-dev] edit values in GTInspector
Hi, Is it planned to add the possibility to edit instances variables of an object directly from the inspector. I mean without evaluating code, just by clicking on the value and update it? Regards, Christophe. smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] Source code formatting guidelines
Hi I find the formatting chapter of the 'Smalltalk best practices pattern, Kent Beck' really nice but I cannot find a free pdf. I just found http://sdmeta.gforge.inria.fr/FreeBooks/WithStyle/SmalltalkWithStyle.pdf. There is also a chapter about formatting. Should also be a good reading. Regards, Christophe. Le 19 nov. 2014 à 12:06, Jan Vrany a écrit : Hi guys, is there any document I can read on how Pharo source code is/should be formatted? I mean things like - tabs/spaces? How many spaces if spaces? - encoding of the source string - trailing newlines - trailing spaces - ... I don't care much about things like whether there should be a space after ^, opening [ and so on (because there's a little I can do about it :-) Best, Jan smime.p7s Description: S/MIME cryptographic signature
[Pharo-dev] Fwd: [ci-announces] Storage maintenance planned tomorrow (2014/11/25)
Hello, Pleas find below an announce of a maintenance on the Inria CI infrastructure. It means we will have to shutdown our slaves this afternoon and no CI job run will be available before tomorrow. Regards, Christophe. Début du message réexpédié : De : Emmanuel Jeanvoine emmanuel.jeanvo...@inria.fr Date : 24 novembre 2014 09:47:56 HNEC À : ci-announ...@inria.fr Objet : [ci-announces] Storage maintenance planned tomorrow (2014/11/25) Répondre à : Emmanuel Jeanvoine emmanuel.jeanvo...@inria.fr Dear users, A maintenance of the storage infrastructure is planned on 2014/11/25 from 5pm to 11pm. In order to avoid issues, you are strongly encouraged to shut down the virtual machines of your project before 5pm. After that, the remaining virtual machines will be shut down by the IT team. If you are interested in following this maintenance you can have a look there: https://wiki.inria.fr/ciportal/Event_20141125_storage Thank you for your understanding, Emmanuel -- Emmanuel JeanvoineResearch Engineer Inria Nancy - Grand Est Office B118 http://www.inria.fr/nancy Tel +33 3 54 95 86 21 smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] Dependencies Analyzer
Le 25 nov. 2014 à 15:03, p...@highoctane.be a écrit : I installed it in my 3.0 but it crashes with a DNU on TreeNodeModelposition: I loaded it like this: Gofer it smalltalkhubUser: 'BaptisteQuide' project: 'PackageDependenciesAnalysis'; configuration; loadStable The article on http://www.baptistequide.fr/packagedependencies.php says that it loads on 3.0 but well, it doesn't say it works there. You're right. the latest version does not work on Pharo 30. It should not be a big deal to have it working. Most specific parts are related to Nautilus and spec changes. For example #updatePackageGroupAndClassList is bot implemented in PackageTreeNautilusUI in Pharo 30. Probably it was removed. I do not find a reference to #position: in the Package-Dependencies package, so it's difficult to guess the problem root. How to reproduce? smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] Dependencies Analyzer
If you do not care of the UI, it should work on both Pharo 30 and 40. You can use: (PDPackageAnalyzerTreeModel onPackagesMatch: 'AST*') relationGraph explore ... but it is hard to see directly the information you need. If you have graphviz installed, you could use PDGraphVizGenerator newWith: (PDPackageAnalyzerTreeModel onPackagesMatch: 'AST*') relationGraph named: 'ast' Le 25 nov. 2014 à 17:51, p...@highoctane.be a écrit : Can understand that. Will try with previous version. Now, 3.0 is what I use for production code, not 4.0. Is the version with 3.0 at the same location? Elsewhere? Phil On Tue, Nov 25, 2014 at 5:07 PM, stepharo steph...@free.fr wrote: it is to work on Pharo40. I did not want to maintain two versions. I loaded it like this: Gofer it smalltalkhubUser: 'BaptisteQuide' project: 'PackageDependenciesAnalysis'; configuration; loadStable The article on http://www.baptistequide.fr/packagedependencies.php says that it loads on 3.0 but well, it doesn't say it works there. You're right. the latest version does not work on Pharo 30. It should not be a big deal to have it working. Most specific parts are related to Nautilus and spec changes. For example #updatePackageGroupAndClassList is bot implemented in PackageTreeNautilusUI in Pharo 30. Probably it was removed. Yes probably Philippe if you take a version before it should load. I moved the repo to PharoExtras with the version for Pharo40. I do not find a reference to #position: in the Package-Dependencies package, so it's difficult to guess the problem root. How to reproduce? smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] GetOpt
See https://en.wikipedia.org/wiki/Getopt Le 2 déc. 2014 à 10:17, stepharo a écrit : Can you just tell me a bit more :) Le 2/12/14 08:45, p...@highoctane.be a écrit : I have made Ian Piumarta's GST GetOpt work in Pharo 3.0 See: http://www.smalltalkhub.com/#!/~philippeback/GetOpt http://www.smalltalkhub.com/#%21/%7Ephilippeback/GetOpt Nice tool even if we have some other support in CommandLineHandlers. But for a quick parameters setting in your own CommandLineHandler, it is fast to use and easy to debug. Phil smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] [Pharo-users] [ann] gtspotter: a moldable interface for spotting objects
Hi Doru and all, Great work. All these tools are really moving the development experience a step forward :) I will try it ASAP. At this time, I just wonder if it is possible to search text in method sources. It is often useful. Another related thing I don't know how to do, is to refactor a set of methods (could be some methods to 20 or more). In these methods, I send a specific message. Now, I just want to remove the message implementation (it is not a rename) and I have to update the code accordingly. Sometimes, I could do that by just a search/replace (text) functionality (would be cool to use patterns there) in methods source code but I cannot find a way do that for now. So I do it by hand. I wonder if it already exists a way to do that or if GTSpotter could address this issue. Christophe. Le 7 déc. 2014 à 14:14, Tudor Girba a écrit : Hi, Alex Syrel, Andrei Chis and I are happy to announce a new addition to the Glamorous Toolkit: GTSpotter, a novel interface for spotting objects. GTSpotter has two goals: - Provide a uniform yet moldable interface that can work on any object, and - Handle searching through arbitrary levels of object nesting. We think this will have a significant impact on the development workflow in Pharo. Here is a couple of screenshots: gtspotter-packages-classes.png gtspotter-dive-class-method-sender.png gtspotter-playground.png A trailer is available here: https://www.youtube.com/watch?v=PhSmjR3NOlU A detailed description is available here: http://www.humane-assessment.com/blog/introducing-gtspotter It works already in Pharo 3.0 and can be played with by following the instructions from: http://gt.moosetechnology.org Please let us know what you think. Enjoy, The Glamorous Team smime.p7s Description: S/MIME cryptographic signature
[Pharo-dev] servers maintenance
Hi, We will need to do some maintenance to Pharo servers this afternoon. It includes smalltalkhub, and all pharo-related web sites. That is likely that you may observe short downtimes. Regards, Esteban and Christophe. smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] jenkins and static analysis
Le 15 déc. 2014 à 12:17, Norbert Hartl a écrit : Am 15.12.2014 um 12:05 schrieb Yuriy Tymchuk yuriy.tymc...@me.com: Well… there is this job: https://ci.inria.fr/pharo/view/3.0-Analysis/job/Pharo-3.0-CodeCritics/plot/Pharo%20(Kernel%20only)%20analysis/ It’s a bit complicated, but in Pharo4 rule checking got much easier, so you can script something buy yourself, or I can help you. The main question is what do you want to obtain? Back then there was a mapping from lint warnings and errors to a checkstyle format file which can be feeded into the checkstyle plugin on jenkins. That would be fine. I wouldn't be sad if the categories of lint rules could be seen in the jenkins graph. That might be possible to do but that is hard to configure on the job. The missing thing is an output for the Jenkins Violations plugin (https://wiki.jenkins-ci.org/display/JENKINS/Violations). We could have our own type (critics) or just re-use one (ex: pmd). I also wanted to do that but did not get the time yet. I also want that critics are checked in the same time as tests in jenkins jobs. smime.p7s Description: S/MIME cryptographic signature
[Pharo-dev] GitFileTree - Git command not found (is which shell startup script is run when pharo launched from UI)
Hi, I wanted to give a try to gitfiletree but I got a 'Git command not found'. Indeed, the git command is not in the path Here is the code used by GitFileTree to run a git command: | c output | [ c := PipeableOSProcess command: 'export'. output := ReadStream on: c output. c succeeded ifFalse: [ self error: 'Git error: ' , c errorPipelineContents ] ] ensure: [ c closePipes ]. output I replaced the command to execute by 'export' to get all environment variables. I noticed that '/usr/local/bin' is not in the path (used by brew). To get my full environment (.profile executed), I need to run pharo from a shell with the same environment. The question is: how to run Pharo from the UI and get this environment? I tried with a .bashrc, bash_profile without success. Any idea? Thanks, Christophe. smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] GitFileTree - Git command not found (is which shell startup script is run when pharo launched from UI)
Hi Thierry, - Mail original - De: Thierry Goubier thierry.goub...@gmail.com À: Pharo Development List pharo-dev@lists.pharo.org Envoyé: Mardi 3 Février 2015 18:51:05 Objet: Re: [Pharo-dev] GitFileTree - Git command not found (is which shell startup script is run when pharo launched from UI) Hi Christophe, looks like that a configuration option for the path to the git command is necessary :) https://github.com/dalehenrich/filetree/issues/143 I'm planning a bit of a rewrite for GitFileTree (saw a few significant issues on Monticello to git integration pop-up recently) and I'll add that along with the others. Thanks. By the way, for this specific case (run Pharo from UI), I still think it should be configurable with the OS (from some profile file) but I did not find a solution yet. Another option could be to retrieve the content of path variable with NativeBoost and use it to run the git command. I will test. Christophe.
Re: [Pharo-dev] pharo-contribution CI out of space?
Le 19 janv. 2015 à 11:58, Yuriy Tymchuk a écrit : Hi, I’m getting this things in logs: Downloading PharoV20.sources: http://files.pharo.org/sources//PharoV20.sources.zip pharo-vm/PharoV20.sources: write error (disk full?). Continue? (y/n/^C) warning: pharo-vm/PharoV20.sources is probably truncated did we run out of space on pharo-contribution? No, it looks like the fils system of a slave is full. It may happen because a slave keep the last workspace for each job that has been run on it. smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] pharo-contribution CI out of space?
Le 20 janv. 2015 à 17:35, Stephan Eggermont a écrit : Who is dealing with CI? The queue is still growing and nothing seems to finish. I noticed that in the past. It may happen when no slave is available to execute a specific job. It happens if one or many slave go offline or if a build is stuck and no other executor is available for other jobs. I don't know if there is a good solution to manage that. My opinion is that we should just be sure that a timeout is set to every job. In addition, we could install these plugin: https://wiki.jenkins-ci.org/display/JENKINS/Purge+Build+Queue+Plugin that will ease our life if the queue grows quickly. smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] [Pharo CI] Jenkins down 10/11 Feb
Le 13 févr. 2015 à 08:31, Marcus Denker a écrit : On 13 Feb 2015, at 01:56, Yuriy Tymchuk yuriy.tymc...@me.com wrote: Are there any news on this? :) The update has been done. Now we need to - check why https://ci.inria.fr/pharo/ is not up - restart all slaves everywhere I just did that for pharo and pharo-contrib smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] CI Server still down...
Le 20 févr. 2015 à 11:22, Tudor Girba a écrit : Thank you for keeping an eye on this. Just a note: while the servers being down can induce some frustration we should remember that INRIA is very kind to offer this support for our community. So, thanks for all the hard work that happens behind the scene! And this upgrade is the first mandatory step to enable OS X slaves on the Inria CI service. smime.p7s Description: S/MIME cryptographic signature
