June 2017 - Pharo-dev - lists.pharo.org

Why allChildrenMatching: does not match extension?

by Stephane Ducasse

Why allChildrenMatching: does not match extension? allChildrenMatching: aPattern "Return all the files and folders recursively nested in the receiver and matching the pattern, aPattern" ^ self allChildren select: [ :each | aPattern match: each basename ] I would rename allChildrenMatching: aPattern into allChildrenNameMatching: aPattern

June 18, 2017

Re: [Pharo-dev] Doing a pull request

by Stephane Ducasse

HI juraj yes it would really cool. Stef On Sun, Jun 18, 2017 at 1:11 PM, Juraj Kubelka <juraj.kubelka(a)icloud.com> wrote: > >> El 16-06-2017, a las 19:27, Esteban Lorenzano <estebanlm(a)gmail.com> escribiÃ³: >> >> >>> On 16 Jun 2017, at 16:50, K K Subbu <kksubbu.ml(a)gmail.com> wrote: >>> >>> On Thursday 15 June 2017 08:14 PM, Esteban Lorenzano wrote: >>>> 2. work on fix/change >>>> 3. commit/push to your repo >>>> 4. do a Pull Request once finished. >>> >>> Esteban, >>> >>> Step 2 requires an issue to be created in Fogbugz. It would be nice to do this within Pharo itself. >> >> it would be, yes. >> I have even played with the idea of having a âreport bugâ button on debugger for years nowâ¦ > > Hi, I am currently playing with something like this :-) Well, I am reporting it to a Discord channel because someone may want to report and share troubles that are not related only with Pharo core, e.g., Roassal or other external projects. But we can have two buttons for sure. > > I will share it once it is ready for public review. > > Juraj > >> >> but then, someone has to program it :) >> >> Esteban >> >>> >>> When creating an issue FB requires every detail to be filled in. Most issues arise while testing or debugging, so it would be easy to get most of the details from a debug session or test failure and then file an issue. >>> >>> Regards .. Subbu >>> >>> >> >> > >

June 18, 2017

Re: [Pharo-dev] Doing a pull request

by Juraj Kubelka

> El 16-06-2017, a las 19:27, Esteban Lorenzano <estebanlm(a)gmail.com> escribiÃ³: > > >> On 16 Jun 2017, at 16:50, K K Subbu <kksubbu.ml(a)gmail.com> wrote: >> >> On Thursday 15 June 2017 08:14 PM, Esteban Lorenzano wrote: >>> 2. work on fix/change >>> 3. commit/push to your repo >>> 4. do a Pull Request once finished. >> >> Esteban, >> >> Step 2 requires an issue to be created in Fogbugz. It would be nice to do this within Pharo itself. > > it would be, yes. > I have even played with the idea of having a âreport bugâ button on debugger for years nowâ¦ Hi, I am currently playing with something like this :-) Well, I am reporting it to a Discord channel because someone may want to report and share troubles that are not related only with Pharo core, e.g., Roassal or other external projects. But we can have two buttons for sure. I will share it once it is ready for public review. Juraj > > but then, someone has to program it :) > > Esteban > >> >> When creating an issue FB requires every detail to be filled in. Most issues arise while testing or debugging, so it would be easy to get most of the details from a debug session or test failure and then file an issue. >> >> Regards .. Subbu >> >> > >

June 18, 2017

Re: [Pharo-dev] Doing a pull request

by Pavel Krivanek

You can just simply do them from Pharo 6 and place them into Pharo 6 inbox. We will then convert them to pull requests as we already did for most of prepared slices. Cheers, -- Pavel 2017-06-17 9:03 GMT+02:00 Stephane Ducasse <stepharo.self(a)gmail.com>: > Esteban > > what is the process for people to publish in the inbox of Pharo 70? > This is what we should add in the readme even if it changes. > I have enhancements waiting for a couple of months and I would like to > start pushing them. > > Stef > > > > On Sat, Jun 17, 2017 at 8:41 AM, Stephane Ducasse > <stepharo.self(a)gmail.com> wrote: > > What is the base branch? > > The master? > > > > On Thu, Jun 15, 2017 at 8:17 AM, K K Subbu <kksubbu.ml(a)gmail.com> wrote: > >> On Wednesday 14 June 2017 08:25 PM, Rajula Vineet wrote: > >>> > >>> Hi, > >>> > >>> I am a GSoC student working on enhancing pharo command line interface. > I > >>> was > >>> wondering if there is a procedure to make a pull request to the Github > >>> repo. > >>> It would be really helpful if someone can explain the right way of > doing a > >>> Pull Request. Thanks in advance. > >> > >> > >> Have you already forked the upstream project in github (aka base) and > >> created a topic branch in your fork (aka head) to hold your changes? > Please > >> post them here or in Discord chat if you need detailed help. Follow the > >> steps in : > >> > >> https://help.github.com/articles/creating-a-pull-request-from-a-fork/ > >> > >> Git jargon may be quite intimidating ;-) for first timers, but the > procedure > >> is really simple. Just remember to start with the "Pull Request" on the > >> *base branch* and not your fork. > >> > >> Regards .. Subbu > >> > >

June 17, 2017

Re: [Pharo-dev] Doing a pull request

by Stephane Ducasse

Esteban what is the process for people to publish in the inbox of Pharo 70? This is what we should add in the readme even if it changes. I have enhancements waiting for a couple of months and I would like to start pushing them. Stef On Sat, Jun 17, 2017 at 8:41 AM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > What is the base branch? > The master? > > On Thu, Jun 15, 2017 at 8:17 AM, K K Subbu <kksubbu.ml(a)gmail.com> wrote: >> On Wednesday 14 June 2017 08:25 PM, Rajula Vineet wrote: >>> >>> Hi, >>> >>> I am a GSoC student working on enhancing pharo command line interface. I >>> was >>> wondering if there is a procedure to make a pull request to the Github >>> repo. >>> It would be really helpful if someone can explain the right way of doing a >>> Pull Request. Thanks in advance. >> >> >> Have you already forked the upstream project in github (aka base) and >> created a topic branch in your fork (aka head) to hold your changes? Please >> post them here or in Discord chat if you need detailed help. Follow the >> steps in : >> >> https://help.github.com/articles/creating-a-pull-request-from-a-fork/ >> >> Git jargon may be quite intimidating ;-) for first timers, but the procedure >> is really simple. Just remember to start with the "Pull Request" on the >> *base branch* and not your fork. >> >> Regards .. Subbu >>

June 17, 2017

Esteban clone, Pavel clone, Clement clone, Guillermo clone....

by Stephane Ducasse

Dear Pharoers there are many things that we would like to achieve to offer you a much better system but we cannot clone ourselves. Please let us know if you want to participate building better tools around for example Iceberg. Stef

June 17, 2017

Re: [Pharo-dev] Doing a pull request

by Stephane Ducasse

What is the base branch? The master? On Thu, Jun 15, 2017 at 8:17 AM, K K Subbu <kksubbu.ml(a)gmail.com> wrote: > On Wednesday 14 June 2017 08:25 PM, Rajula Vineet wrote: >> >> Hi, >> >> I am a GSoC student working on enhancing pharo command line interface. I >> was >> wondering if there is a procedure to make a pull request to the Github >> repo. >> It would be really helpful if someone can explain the right way of doing a >> Pull Request. Thanks in advance. > > > Have you already forked the upstream project in github (aka base) and > created a topic branch in your fork (aka head) to hold your changes? Please > post them here or in Discord chat if you need detailed help. Follow the > steps in : > > https://help.github.com/articles/creating-a-pull-request-from-a-fork/ > > Git jargon may be quite intimidating ;-) for first timers, but the procedure > is really simple. Just remember to start with the "Pull Request" on the > *base branch* and not your fork. > > Regards .. Subbu >

June 17, 2017

Re: [Pharo-dev] Doing a pull request

by K K Subbu

On Friday 16 June 2017 10:57 PM, Esteban Lorenzano wrote: >> Esteban, >> >> Step 2 requires an issue to be created in Fogbugz. It would be nice >> to do this within Pharo itself. > it would be, yes. I have even played with the idea of having a > âreport bugâ button on debugger for years nowâ¦ > > but then, someone has to program it:) Juraj has already demonstrated FogBugz integration in his PharoSprint app. Extending to debugging or slicemaker could a nice project for students or in hackathons. I have filed a case 20162 to track this: https://pharo.fogbugz.com/f/cases/20162 Regards .. Subbu

June 17, 2017

Reviving the Android VM

by Michael Rueger

Hi all, long time no see :-) Recently I spent a bit of time trying to piece together an Android VM using the up to date versions of AndroidStudio, SDK and NDK. Once things are building and running, I was planning to fold everything back into the proper build process. Current (somewhat messy) state of things here https://github.com/mrueger42/st-android It has been quite a long time since I looked at building VMs, so forgive me if I'm just being stupid here... I was able to get the original port from Andreas to build and run, but it is a very outdated version. Still nice to have it as a piece of history, I think (AndroidVM in the above repo). Some puzzle pieces later I have something running that is based on recent CogSpur opensmalltalk code and bits and pieces I found. Unfortunately CogSpur doesn't seem to play well with the setjmp/longjmp used in the code (CogDroid in the above repo). Plus, the VM is running on the UI thread, not something that is viewed well on mobile. Actually it makes Android just kill the app if you block the UI thread for too long. Trying to run the VM on a thread runs into a division by 0 exception (I think) and finds me way out of my league to track down why that would be. Crash below... I haven't really tried getting Dmitry's version to build/work in a current environment, partly because I'm not sure I'm looking at the most up to date version (see below). Any help, pointers, code snippets highly appreciated! Cheers Michael P.S. Sending this to vm-dev and pharo-dev, but should probably send any followup to vm-dev? -------- list of sources I looked at: -opensmalltalk -pharo -original port by Andreas git@github.com:timfel/squeak-android-vm.git -stack https://github.com/sbragagnolo/pharo-vm/ -dmitry gitorious is no longer, just an archival snapshot clicking on snapshot gives you the sources https://gitorious.org/cogvm/dmg-blessed?p=cogvm:dmg-blessed.git;a=summary non-functional jenkins setup https://ci.inria.fr/pharo-contribution/view/VM/job/CogDroid/configure-reado… ------------- The Cog VM crash when running on a Thread: D/jni-vm: Java_org_smalltalk_android_vm_VM_runVM D/jni-vm: runVM D/jni-vm: interpret A/libc: Fatal signal 8 (SIGFPE), code -6, fault addr 0x67db in tid 26636 (Thread-5) Revision: '6' ABI: 'arm' pid: 26587, tid: 26636, name: Thread-5 >>> org.smalltalk.android <<< signal 8 (SIGFPE), code -6 (SI_TKILL), fault addr 0x67db r0 00000000 r1 0000680c r2 00000008 r3 00000000 r4 e4f7f978 r5 00000008 r6 e4f7f920 r7 0000010c r8 e4f7ef60 r9 e3516400 sl e351648c fp e4f7ecb4 ip 00000002 sp e4f7ce30 lr efca84c7 pc efcaad30 cpsr 600e0010 backtrace: #00 pc 0004ad30 /system/lib/libc.so (tgkill+12) #01 pc 000484c3 /system/lib/libc.so (pthread_kill+34) #02 pc 0001dd99 /system/lib/libc.so (raise+10) #03 pc 000c54a3 /data/app/org.smalltalk.android-2/lib/arm/libStackVM.so #04 pc 00051507 /data/app/org.smalltalk.android-2/lib/arm/libStackVM.so #05 pc 0003d38b /data/app/org.smalltalk.android-2/lib/arm/libStackVM.so (interpret+238) #06 pc 000a4e6f /data/app/org.smalltalk.android-2/lib/arm/libStackVM.so (runVM+22) #07 pc 000a4a55 /data/app/org.smalltalk.android-2/lib/arm/libStackVM.so (Java_org_smalltalk_android_vm_VM_runVM+36) #08 pc 0031ec99 /data/app/org.smalltalk.android-2/oat/arm/base.odex (offset 0x302000)

June 16, 2017

Re: [Pharo-dev] Doing a pull request

by Esteban Lorenzano

> On 16 Jun 2017, at 16:50, K K Subbu <kksubbu.ml(a)gmail.com> wrote: > > On Thursday 15 June 2017 08:14 PM, Esteban Lorenzano wrote: >> 2. work on fix/change >> 3. commit/push to your repo >> 4. do a Pull Request once finished. > > Esteban, > > Step 2 requires an issue to be created in Fogbugz. It would be nice to do this within Pharo itself. it would be, yes. I have even played with the idea of having a âreport bugâ button on debugger for years nowâ¦ but then, someone has to program it :) Esteban > > When creating an issue FB requires every detail to be filled in. Most issues arise while testing or debugging, so it would be easy to get most of the details from a debug session or test failure and then file an issue. > > Regards .. Subbu > >

June 16, 2017