September 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] issue with large file path on windows

by Nicolai Hess

Oh, no. Long path prefix can not work for relative paths! Since my latest additions for long path support for the windows vm, you can not open an image file if the supplied path is not an absolute path. If you start Pharo with "Pharo.exe Pharo.image" an open-file-dialog shows up and you have to choose the image in this dialog. (If you have only one image file in the current directory, this image *is* found, this is because the windows vm searches the current directory for a single .image file) Sorry for that, I'll fix it. nicolai 2015-09-04 22:19 GMT+02:00 Nicolai Hess <nicolaihess(a)web.de>: > Thank you all for your feedback. > @ben, > - yes malloca is not supported by mingw ( or I did not get it to work) > - and we don't have to consider recursive calls > I think we are save by using alloca. I did some tests with awfully long > path names. > > I made some more little changes for retrieving the file permissions. Don't > use the stat() function, because > this did not work for long path names ( and it doesn't worked well for > paths with non ascii characters). > > I created a pull request for the pharo-vm git project. > > nicolai > > > > 2015-08-25 8:35 GMT+02:00 HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> > : > >> >> >> 2015-08-24 4:31 GMT-03:00 Nicolai Hess <nicolaihess(a)web.de>: >> >>> Hi HernÃ¡n >>> Thanks for your feedback >>> >>> 2015-08-24 8:13 GMT+02:00 HernÃ¡n Morales Durand < >>> hernan.morales(a)gmail.com>: >>> >>>> Nicolai >>>> >>>> 2015-08-23 8:44 GMT-03:00 Nicolai Hess <nicolaihess(a)web.de>: >>>> >>>>> For those who had problems with pharo on windows and github based >>>>> repositories, >>>>> I built a windows vm with support for long paths: >>>>> >>>>> >>>>> https://drive.google.com/file/d/0B8yEahnuIem2bmxwdzJuUXFxVGM/view?usp=shari… >>>>> >>>>> >>>>> For browsing directories with large paths (FileList or Inspect), >>>>> you may need one additional change in the image (But I am not really >>>>> sure about that) : >>>>> >>>>> DiskStore>>initialize >>>>> super initialize. >>>>> maxFileNameLength := Smalltalk vm maxFilenameLength ifNil: [ 32767 >>>>> ]. >>>>> >>>>> >>>>> please test and give feedback. >>>>> >>>>> >>>> Using Win 8.1, I confirm FileList tree now is reading directories >>>> beyond 260 limit, without need to #initialize DiskStore. >>>> >>>> However there should be another concern with GitFileTree uncompression >>>> because loading Aconcagua/Chalten, etc with your new VM in a directory name >>>> with more characters, still signals File not found :( >>>> >>> >>> I tried Aconcagua from Catalogbrowser in pharo 5.0 and it worked for me. >>> Can you show what path is the base path, the working directory of your >>> pharo package-cache/github directory. Is there something special in your >>> path name or the disk? >>> >> >> Nicolai, the path is the one which I reported here >> http://forum.world.st/Loading-Chalten-amp-Aconcagua-error-td4844694.html >> I have nothing special in the path name, not special characters or so. >> >> I tried today again with your VM, same path, same image, but before >> loading the configuration I removed the whole github-cache/* contents, and >> it worked.... so I am confused. So I checked with old VM again and yep the >> FileDoesNotExists came back. Conclusion: Your VM actually fixes the issue, >> but cleaning github-cache did something, there could be another bug there... >> >> >> >>> >>> >>>> >>>> Is the VM using the "Unicode-aware API"? According to this guys >>>> http://serverfault.com/questions/163419/window-256-characters-path-name-lim… >>>> such Win Unicode API would let VM to use the 32767 bricks >>>> >>> >>> I am not sure, we are using all file/directory operations that should >>> use the unicode version with multibyte char (CreateFileW / FindFirstFileW / >>> ...) >>> >>> >> >> Ok, thanks for checking. >> >> >>> >>>> >>>> This wasn't as easy as I thought, and I had to make some more changes >>>>> for the file permissions (the stat-functions don't work for files with >>>>> long paths). >>>>> Please test other file/folder operations. >>>>> >>>>> >>>> Thank you Nicolai for your effort, I know it's hard to dive into depths >>>> with C. >>>> >>>> HernÃ¡n >>>> >>>> >>>>> nicolai >>>>> >>>>> >>>>> >>>>> >>>> >>> >> >

Sept. 10, 2015

Re: [Pharo-dev] Image and bootstrap dependencies

by Ben Coman

If your browser shows the web page source you will see the data being pulled from... bootstrap-dependency-report-graph-data.csv <https://ci.inria.fr/pharo/job/Pharo-5.0-DependencyAnalysis/ws/bootstrap-dep…> cheers -ben On Thu, Sep 10, 2015 at 5:32 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > Very interesting. > > Could you detail which information you use for building the edges? > > Cheers, > Doru > > > > On Wed, Sep 9, 2015 at 11:33 AM, Christophe Demarey < > Christophe.Demarey(a)inria.fr> wrote: > >> Hi, >> >> We now have a best overview of bootstrap dependencies. >> You can check the latest report at >> https://ci.inria.fr/pharo/job/Pharo-5.0-DependencyAnalysis/Dependencies_HTM… >> . >> With Max, we reused Dijkstra algo in Moose to help finding dependencies >> leading to Morphic and co. >> It is now possible to have a visualization that is usable (there is also >> a button to open it in the report): >> https://ci.inria.fr/pharo/job/Pharo-5.0-DependencyAnalysis/Dependencies_HTM… >> >> Next steps are to cut dependencies in red in the report table. >> >> Christophe. >> >> ps: by the way the dependency analyzer (with fixes asked) will be >> introduced soon in the image. >> >> >> Le 4 sept. 2015 Ã 15:13, Christophe Demarey a Ã©crit : >> >> Hi, >> >> I created a job to automatically generate a report of the Pharo image >> dependencies as well as current bootstrap dependencies. >> You can find them here: >> >> - >> https://ci.inria.fr/pharo/job/Pharo-5.0-DependencyAnalysis/Dependencies_HTM… >> - >> https://ci.inria.fr/pharo/job/Pharo-5.0-DependencyAnalysis/Dependencies_HTM… >> >> >> There are a lot (too many) dependencies but you can focus on some of them >> with the search field. >> Dependencies inside orange boxes are dependencies that are there but that >> we ignore (for example, an example method adds an extra-dependency). It >> should be fixed later but is not a problem for now. Ignored dependencies >> are declared in the package manifest in #ignoredDependencies. >> Dependencies inside red boxes are dependencies we want to remove for the >> bootstrap. For now, they are listed in the bootstrap dependency report. >> >> People that are willing to help to have a more modular Pharo could first >> take a look at the bootstrap dependency report and check dependencies that >> we should cut. >> Once we know, we can open issues on fogbugz in the 'bootstrap category' >> and update manifests accordingly. >> To investigate more deeply dependencies, you can use the >> DependencyAnalyzer (in the Pharo Catalog) to actually check dependencies >> (inheritance, reference, extension, traits, message send). >> >> Regards, >> Christophe. >> >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

Sept. 9, 2015

Disable focusing of FastTable

by Yuriy Tymchuk

Hi, is there a nice way to forbid a fast table to take focus? because #takesKeyboardFocus is implemented as: â^ self enabledâ. And #enabled is inherited from Morph and is always true. Do I really have to subclass the FTTableMorph just to get rid of focusing? Uko

Sept. 9, 2015

FastTable non-selectable, clickable

by Yuriy Tymchuk

Hi, Iâm trying to move QualityAssistant to FastTable and I really like it. Now as you may have noticed, you cannot select a list item in the QA plugin, but you can click on it to get the issue highlighted (if the rule allows). How can I mimic this with FT? Should I create a subclass of FTSelectionStrategy and redefine #selectRowIndex:event: not to do anything and just announce that there was a click on a list item? Or is there a better way? Uko

Sept. 9, 2015

Re: [Pharo-dev] Image and bootstrap dependencies

by Tudor Girba

Hi, Very interesting. Could you detail which information you use for building the edges? Cheers, Doru On Wed, Sep 9, 2015 at 11:33 AM, Christophe Demarey < Christophe.Demarey(a)inria.fr> wrote: > Hi, > > We now have a best overview of bootstrap dependencies. > You can check the latest report at > https://ci.inria.fr/pharo/job/Pharo-5.0-DependencyAnalysis/Dependencies_HTM… > . > With Max, we reused Dijkstra algo in Moose to help finding dependencies > leading to Morphic and co. > It is now possible to have a visualization that is usable (there is also a > button to open it in the report): > https://ci.inria.fr/pharo/job/Pharo-5.0-DependencyAnalysis/Dependencies_HTM… > > Next steps are to cut dependencies in red in the report table. > > Christophe. > > ps: by the way the dependency analyzer (with fixes asked) will be > introduced soon in the image. > > > Le 4 sept. 2015 Ã 15:13, Christophe Demarey a Ã©crit : > > Hi, > > I created a job to automatically generate a report of the Pharo image > dependencies as well as current bootstrap dependencies. > You can find them here: > > - > https://ci.inria.fr/pharo/job/Pharo-5.0-DependencyAnalysis/Dependencies_HTM… > - > https://ci.inria.fr/pharo/job/Pharo-5.0-DependencyAnalysis/Dependencies_HTM… > > > There are a lot (too many) dependencies but you can focus on some of them > with the search field. > Dependencies inside orange boxes are dependencies that are there but that > we ignore (for example, an example method adds an extra-dependency). It > should be fixed later but is not a problem for now. Ignored dependencies > are declared in the package manifest in #ignoredDependencies. > Dependencies inside red boxes are dependencies we want to remove for the > bootstrap. For now, they are listed in the bootstrap dependency report. > > People that are willing to help to have a more modular Pharo could first > take a look at the bootstrap dependency report and check dependencies that > we should cut. > Once we know, we can open issues on fogbugz in the 'bootstrap category' > and update manifests accordingly. > To investigate more deeply dependencies, you can use the > DependencyAnalyzer (in the Pharo Catalog) to actually check dependencies > (inheritance, reference, extension, traits, message send). > > Regards, > Christophe. > > > -- www.tudorgirba.com "Every thing has its own flow"

Sept. 9, 2015

Re: [Pharo-dev] FogBugz (Case [Issue]16520) CI and Bugtracker - Help topic for how to contribute to Pharo basecode

by Marcus Denker

It needs to be fixed but I *really* did not find any time yet. > On 09 Sep 2015, at 22:00, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > Maybe change the error message until it is resolved to something like "Timeout blablabla... this is CI issue, please tell the monkey to try again". > So people know it's not their error and it will also tell them what to do, so they (me last week, Alex this week, someone else next week) don't need to ask again and again. > > Peter > > > On Wed, Sep 9, 2015 at 9:57 PM, stepharo <stepharo(a)free.fr <mailto:stepharo@free.fr>> wrote: > yes in that case why not fixing that because this is really really annoying to always get a fix rejected with a bad feedback. > > Stef > > > Le 9/9/15 21:52, Marcus Denker a Ã©crit : > > On 09 Sep 2015, at 20:27, stepharo <stepharo(a)free.fr <mailto:stepharo@free.fr>> wrote: > > Not much mark it as fix to include. > The last where this was done added an undeclared. Quality goes down very fast when we add changes without running the tests. > > Marcus > > > >

Sept. 9, 2015

Re: [Pharo-dev] FogBugz (Case [Issue]16520) CI and Bugtracker - Help topic for how to contribute to Pharo basecode

by Peter UhnÃ¡k

Maybe change the error message until it is resolved to something like "Timeout blablabla... this is CI issue, please tell the monkey to try again". So people know it's not their error and it will also tell them what to do, so they (me last week, Alex this week, someone else next week) don't need to ask again and again. Peter On Wed, Sep 9, 2015 at 9:57 PM, stepharo <stepharo(a)free.fr> wrote: > yes in that case why not fixing that because this is really really > annoying to always get a fix rejected with a bad feedback. > > Stef > > > Le 9/9/15 21:52, Marcus Denker a Ã©crit : > > On 09 Sep 2015, at 20:27, stepharo <stepharo(a)free.fr> wrote: >>> >>> Not much mark it as fix to include. >>> >> The last where this was done added an undeclared. Quality goes down very >> fast when we add changes without running the tests. >> >> Marcus >> >> > >

Sept. 9, 2015

Re: [Pharo-dev] FogBugz (Case [Issue]16520) CI and Bugtracker - Help topic for how to contribute to Pharo basecode

by Marcus Denker

Yes, I need to block some time to look why this happens. > On 09 Sep 2015, at 21:53, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > This is happening since last week (or maybe even earlier), you can also keep telling the monkey to try again until it succeeds. > > On Wed, Sep 9, 2015 at 8:27 PM, stepharo <stepharo(a)free.fr <mailto:stepharo@free.fr>> wrote: > Not much mark it as fix to include. > 4 > > Le 9/9/15 19:07, Alexandre Bergel a Ã©crit : >> Hi! >> >> Apparently the fix needs more work. But I am not sure how to proceed. The monkey says: >> a CIAndRule: Timeout (after 0:01:00:00) occured while loading "Help topic for how to contribute to Pharo basecode" >> What can I do? >> >> Alexandre >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/> >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >>> On Sep 9, 2015, at 4:45 AM, Pharo Issue Tracker <do-not-reply(a)pharo.fogbugz.com <mailto:do-not-reply@pharo.fogbugz.com>> wrote: >>> >>> >>> Ulysse The Galactic Monkey From Outer Spaceedited Case 16520: Help topic for how to contribute to Pharo basecode <https://pharo.fogbugz.com/f/cases/16520>: >>> >>> Bug in CI and Bugtracker: 1. Pharo Image >>> >>> Issue Validation Failed: <https://ci.inria.fr/pharo/job/Pharo-5.0-Issue-Validator/13183//artifact/val…>https://ci.inria.fr/pharo/job/Pharo-5.0-Issue-Validator/13183//artifact/val… <https://ci.inria.fr/pharo/job/Pharo-5.0-Issue-Validator/13183//artifact/val…> >>> Errors: 1 | >>> Status changed: >>> Resolved (Monkey is checking) Work Needed >>> >>> Priority: 5 â Fix If Time Status: Work Needed >>> Assigned to: Alexandre Bergel Milestone: Pharo5.0 >>> >>> Go to Case >>> >>> <https://pharo.fogbugz.com/f/cases/16520> >>> Don't want FogBugz notifications anymore? Update your preferences. <https://pharo.fogbugz.com/f/userPrefs> >> > >

Sept. 9, 2015

Re: [Pharo-dev] FogBugz (Case [Issue]16520) CI and Bugtracker - Help topic for how to contribute to Pharo basecode

by stepharo

yes in that case why not fixing that because this is really really annoying to always get a fix rejected with a bad feedback. Stef Le 9/9/15 21:52, Marcus Denker a Ã©crit : >> On 09 Sep 2015, at 20:27, stepharo <stepharo(a)free.fr> wrote: >> >> Not much mark it as fix to include. > The last where this was done added an undeclared. Quality goes down very fast when we add changes without running the tests. > > Marcus >

Sept. 9, 2015

Re: [Pharo-dev] Magritte-XMLBinding causes DNU when using Seaside editor example

by stepharo

Note that when we unloaded the xmlbinding (no idea what it is for) the same operation worked. I do not really understand why a xml binding would have such side effect. Le 9/9/15 17:51, Skip a Ã©crit : > Hello, > > Magritte-XMLBinding (loaded by MagritteAddons) appears to go bad when you use descriptions of descriptions. > Try to add a description using the MADescriptionEditor example in Seaside. I get the following: > > âMessageNotUnderstoord: MXXmlNamedElementTarget>>attributeNameâ. > > Is it just me? >

Sept. 9, 2015