- Pharo-dev - lists.pharo.org

Streaming problem in case of errors

by Damien Cassou

P Hi guys, when PharoDebug.log can't be created (e.g., when the image is in a non writeable directory like /usr/share), the errors are sent to the Transcript in the hope that they will be redirected to stdout or stderr. However, ContextPart>>errorReportOn: is called when an exception is signaled and this method assumes that the stream is positionable (which is not the case for transscript, stdin and stderr). I was planing on rewriting ContextPart>>errorReportOn: to make it independent of #position. What do you think? -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Feb. 28, 2014

Re: [Pharo-dev] git and metacello

by Goubier Thierry

This is because github: only works in Metacello, not in Monticello nor Gofer :( Thierry Le 28/02/2014 11:46, Yuriy Tymchuk a Ã©crit : > So far when I run > > ./pharo Pharo.image configgithub://User/Project:master ConfigurationOfProject --install=development > > > I get > > Error: No Monticello repository for URL scheme github > ZnUrl(Object)>>error: > ZnUrl>>mcRepositoryAsUser:withPassword: > Gofer>>url:username:password: > ConfigurationCommandLineHandler>>gofer > ConfigurationCommandLineHandler>>configuration > ConfigurationCommandLineHandler>>project > ConfigurationCommandLineHandler>>metacelloVersion: > > > > > On 28 Feb 2014, at 10:50, Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com > <mailto:Benjamin.VanRyseghem.Pharo@gmail.com>> wrote: > >> On 28 Feb 2014, at 10:23, Yuriy Tymchuk <yuriy.tymchuk(a)me.com >> <mailto:yuriy.tymchuk@me.com>> wrote: >> >>> Can you share a script? Because as far as I understand, You test on >>> read-only staff, and then link you "the oneâ repo on your machine. >> >> Exactly :) >> >> Here is the script to build spec: >> https://github.com/spec-framework/spec/blob/master/install_Spec.sh >> My preference to link Spec repo is: >> https://gist.github.com/BenjaminVanRyseghem/9268250 >> >> Ben > -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Feb. 28, 2014

Re: [Pharo-dev] git and metacello

by Yuriy Tymchuk

So far when I run ./pharo Pharo.image config github://User/Project:master ConfigurationOfProject --install=development I get Error: No Monticello repository for URL scheme github ZnUrl(Object)>>error: ZnUrl>>mcRepositoryAsUser:withPassword: Gofer>>url:username:password: ConfigurationCommandLineHandler>>gofer ConfigurationCommandLineHandler>>configuration ConfigurationCommandLineHandler>>project ConfigurationCommandLineHandler>>metacelloVersion: On 28 Feb 2014, at 10:50, Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: > On 28 Feb 2014, at 10:23, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > >> Can you share a script? Because as far as I understand, You test on read-only staff, and then link you "the oneâ repo on your machine. > > Exactly :) > > Here is the script to build spec: https://github.com/spec-framework/spec/blob/master/install_Spec.sh > My preference to link Spec repo is: https://gist.github.com/BenjaminVanRyseghem/9268250 > > Ben

Feb. 28, 2014

Re: [Pharo-dev] git and metacello

by Benjamin

On 28 Feb 2014, at 10:23, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > Can you share a script? Because as far as I understand, You test on read-only staff, and then link you "the oneâ repo on your machine. Exactly :) Here is the script to build spec: https://github.com/spec-framework/spec/blob/master/install_Spec.sh My preference to link Spec repo is: https://gist.github.com/BenjaminVanRyseghem/9268250 Ben

Feb. 28, 2014

Re: [Pharo-dev] git and metacello

by Yuriy Tymchuk

Can you share a script? Because as far as I understand, You test on read-only staff, and then link you "the oneâ repo on your machine. Uko On 28 Feb 2014, at 10:04, Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: > > On 28 Feb 2014, at 09:53, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: >> >> [1] Ok, still, maybe there is a point there: the path to the repository clone may well be encoded as an absolute path, and, therefore, moving the directory elsewhere could be tricky. This is something I can look into if you choose that git workflow. >> > > I use preferences for that. > It takes all the repo matching Spec* and add a repo pointing to my local git repo > > Ben

Feb. 28, 2014

Re: [Pharo-dev] git and metacello

by Goubier Thierry

Le 28/02/2014 10:04, Benjamin a Ã©crit : > > On 28 Feb 2014, at 09:53, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: >> >> [1] Ok, still, maybe there is a point there: the path to the repository clone may well be encoded as an absolute path, and, therefore, moving the directory elsewhere could be tricky. This is something I can look into if you choose that git workflow. >> > > I use preferences for that. > It takes all the repo matching Spec* and add a repo pointing to my local git repo You mean, inside your Pharo startup preferences? Yes, it would work. I'm testing at the moment non-absolute paths in gitfiletree and it seems to be ok. Until someone changes the working directory of the pharo process :(:( Or considering that non-absolute paths in gitfiletree are allways relative to the image path. Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Feb. 28, 2014

StartupLoader in Windows

by phil＠highoctane.be

I was looking at the comment in StartupLoader which appears to be plain wrong. First, "to know the read values, check FileDirectory preferencesGeneralFolder" Mmmh, no FileDirectory class of course. So, implementors give the StartupLoader itself. Where: StartupLoader class >> preferencesGeneralFolder ^ FileLocator preferences asFileReference / 'pharo'. Argh, no .config as mentioned. This gives an issue with ZeroConf as ZeroConf creates a pharo-ui et pharo scripts, which then make it impossible to have a pharo folder there as well. Now, the FileLocator preferences gets into the PreferencesHandler and there is a buildActionList there. buildActionList "All found files will be executed." | directories | directories := OrderedCollection new. directories add: [ self lookInGeneralPreferencesFolder ]. directories add: [ self lookInPreferencesVersionFolder ]. directories add: [ self lookInImageFolder ]. ^ directories So: preferencesVersionFolder ^ self preferencesGeneralFolder asFileReference / SystemVersion current dottedMajorMinor and lookInImageFolder ^ self lookInFolder: FileSystem workingDirectory forFilesMatching: StartupLoader startupScriptName. startupScriptName ^ 'startup.st' startupPreferencesVersionFolderScriptName ^ 'startupPharo',SystemVersion current dottedMajorMinor,'.st' startupGeneralPreferencesFolderScriptName ^ 'startupPharo.st' Well... this is weird. What is the intention really? So, wouldn't we have another thing than 'pharo' in there ? Like pharo-prefs? What does work for you? ------ "StartupLoader searches for and executes .st files from certain locations. To find these it searches for a '.config' folder in the folder next up from where the image file sits. Then it looks in the next folder up again and so on until reaching the root folder. When a '.config' folder is found, StartupLoader looks within this for a 'pharo' folder. This contains the startup scripts common to all versions of Pharo, and also optionally a folder per Pharo version holding startup scripts suitable for that version only. So a typical directory layout might be... .../some/folders/pharo/Content/Resources/pharo.image. .../some/folders/pharo/Content/Resources/startup.st .../some/folders/.config/pharo/author.st .../some/folders/.config/pharo/useSharedCache.st .../some/folders/.config/pharo/1.4/mystartupFor14only.st .../some/folders/.config/pharo/2.0/mystartupFor20only.st (**Note however that '.config' is an invalid filename on Windows, so '..config' is used instead) IMPORTANT: StartupLoader will search for a folder '.config' starting from the image directory until the root of the filesystem. What happens if no folder is found? It creates '.config' in the image folder. However, it is recommended that you create the '.config' following the standard, that is, in the $HOME. To know the real values for you... Print the result of "FileDirectory preferencesGeneralFolder" which holds the startup scripts common to all versions of Pharo. Print the result of "FileDirectory preferencesVersionFolder" which holds the startup scripts specific to the version of the current image." ----------- Phil

Feb. 28, 2014

Re: [Pharo-dev] git and metacello

by Benjamin

On 28 Feb 2014, at 09:53, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > > [1] Ok, still, maybe there is a point there: the path to the repository clone may well be encoded as an absolute path, and, therefore, moving the directory elsewhere could be tricky. This is something I can look into if you choose that git workflow. > I use preferences for that. It takes all the repo matching Spec* and add a repo pointing to my local git repo Ben

Feb. 28, 2014

Re: [Pharo-dev] git and metacello

by Goubier Thierry

Le 28/02/2014 09:30, Yuriy Tymchuk a Ã©crit : > Thank you Goubier. > > Iâm very sorry again for bothering, but I canât compose the workflow. > > Usually my workflow is like that: > 1. CI is building the image from the MC configuration testing and > zipping it. 1- Use a configuration which clones in read-write mode: that is ssh (prepare a ssh key for the CI that is just registered to the git repository as having read access is probably enough). After the tests, ask CI to zip the directory containing the image. > 2. I download the image and code the project. 2- Download the zip, extract the folder, open the image and code the project. > 3. I commit my stuff to the repository that is already available in the > image (because of CI) and it goes back to step 1. 3- Same. Don't forget to push at the end of the day[1]. > (I donât download the fresh image every time I commit, but I always > start a day from fresh image) > I donât really see how I can do that with git. With gitfiletree as it is now, I don't see how you wouldn't be able to do that :) To the condition that you don't zip only the image (and the changes and ...) but just directly the directory containing the image. Gitfiletree clones in there. But if you want or find another way, let me know :) [1] Ok, still, maybe there is a point there: the path to the repository clone may well be encoded as an absolute path, and, therefore, moving the directory elsewhere could be tricky. This is something I can look into if you choose that git workflow. Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Feb. 28, 2014

Re: [Pharo-dev] git and metacello

by Yuriy Tymchuk

Thank you Goubier. Iâm very sorry again for bothering, but I canât compose the workflow. Usually my workflow is like that: 1. CI is building the image from the MC configuration testing and zipping it. 2. I download the image and code the project. 3. I commit my stuff to the repository that is already available in the image (because of CI) and it goes back to step 1. (I donât download the fresh image every time I commit, but I always start a day from fresh image) I donât really see how I can do that with git. If anyone can send me his workflow with git Iâd be great full. Uko On 28 Feb 2014, at 08:59, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > > > Le 27/02/2014 17:23, Yuriy Tymchuk a Ã©crit : >> Or wait. Do you have to have credentials also for reading? > > I'm not sure. I tried once and it asked for credentials; I tried another way and it didn't, so I can't confirm. > > A simple solution, available now without git support: > > - github: urls in Metacello > > From the comment in Metacello > > "self > parseLocation: 'github://dalehenrich/MetacelloRepository:master/monticello/repos/itory/path' > version: nil" > > It does everything you need in a read-only case over github. For example, to load SmaCC from github, using the following url in a configuration works: > > 'github://ThierryGoubier/SmaCC:master' > > So I'd say that there is no need for https support in Gitfiletree. > > Thierry > >> On 27 Feb 2014, at 17:22, Yuriy Tymchuk <yuriy.tymchuk(a)me.com >> <mailto:yuriy.tymchuk@me.com>> wrote: >> >>> Ok, is it possible to see with OSProcess if you are asked for input? >>> This way we can just abort the process and notify the user that we are >>> not working with credentials >>> >>> Uko >>> >>> >>> On 27 Feb 2014, at 17:16, Goubier Thierry <thierry.goubier(a)cea.fr >>> <mailto:thierry.goubier@cea.fr>> wrote: >>> >>>> >>>> >>>> Le 27/02/2014 17:00, Yuriy Tymchuk a Ã©crit : >>>>> Looks interesting. >>>>> >>>>> But can I use https? Like git clonehttps://github.com/User/Repo.git? >>>> >>>> Not at the moment. It used to, but then I encountered the >>>> authentification issue and removed it. >>>> >>>>> Because as far as I see it does git@github.com:User/Repo.git and >>>>> this is not fun. >>>> >>>> Well, interactive dialogs asking for a username and a password are >>>> tricky to handle through OSProcess. >>>> >>>>> As far as I know git protocol is read only and ssh requires a key. >>>>> With https you can read on CI and write on your machine where you >>>>> have a login and pass. >>>> >>>> Are you sure about the read-only thing? On github, you can git clone >>>> through ssh on a git repository you don't have a write access to (but >>>> your key must allow you ssh access). >>>> >>>> Thierry >>>> >>>>> Uko >>>>> >>>>> On 27 Feb 2014, at 13:45, Goubier Thierry <thierry.goubier(a)cea.fr >>>>> <mailto:thierry.goubier@cea.fr>> wrote: >>>>> >>>>>> Hi Uko, >>>>>> >>>>>> It's at >>>>>> >>>>>> http://forum.world.st/ANN-GitFileTree-with-no-git-command-line-at-all-td474… >>>>>> >>>>>> In short, have a look at either ConfigurationOfAltBrowser or >>>>>> ConfigurationOfSmaCC (baseline20). >>>>>> >>>>>> Thierry >>>>>> >>>>>> Le 27/02/2014 13:25, Damien Cassou a Ã©crit : >>>>>>> On Thu, Feb 27, 2014 at 1:22 PM, Yuriy Tymchuk >>>>>>> <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>> wrote: >>>>>>>> Sorry if I'm bothering you, but I wasn't able to find any >>>>>>>> workflow or so on with git. I've started to use file-tree, but >>>>>>>> for now on I don't understand how to make it work with metacello. >>>>>>>> Also is there some project like that built on jenkins, so I can >>>>>>>> set up similar job. >>>>>>> >>>>>>> >>>>>>> search for gitfiletree and Thierry Goubier on this mailing list. I >>>>>>> never used it though. >>>>>>> >>>>>> >>>>>> -- >>>>>> Thierry Goubier >>>>>> CEA list >>>>>> Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s >>>>>> 91191 Gif sur Yvette Cedex >>>>>> France >>>>>> Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >>>>>> >>>>> >>>>> >>>>> >>>>> >>>> >>>> -- >>>> Thierry Goubier >>>> CEA list >>>> Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s >>>> 91191 Gif sur Yvette Cedex >>>> France >>>> Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >>> >> > > -- > Thierry Goubier > CEA list > Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s > 91191 Gif sur Yvette Cedex > France > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Feb. 28, 2014