- Pharo-dev - lists.pharo.org

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

Re: [Pharo-dev] Doing a pull request

by K K Subbu

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. 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

Re: [Pharo-dev] PharoDays17 Slides and some Videos

by Marcus Denker

Hi, The final video has been added, now we have all talks complete. > On 13 Jun 2017, at 15:53, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > We have now 9 more videos in the playlist: > > https://www.youtube.com/playlist?list=PL4actYd6bfnw7ous5We-XnWq0NZquP3gM > >> On 7 Jun 2017, at 16:24, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> Hi, >> >> I have uploaded the Slides and Videos of PharoDays2017. Slides are complete (minus those >> talks that were due demos). For the Videos we have right now 8 talks and the âShow Us Your >> Projectâ session. More might come in the future (I need to check). >> >> Slides: >> - https://www.slideshare.net/pharoproject/presentations >> - http://files.pharo.org/conferences/2017PharoDays/ >> >> PlayList: https://www.youtube.com/playlist?list=PL4actYd6bfnw7ous5We-XnWq0NZquP3gM >> >

June 16, 2017

Re: [Pharo-dev] Extra shortcut modifier opposite to #meta

by Denis Kudriashov

2017-06-14 17:09 GMT+02:00 Guillermo Polito <guillermopolito(a)gmail.com>: > But meta does also present problems in linux, doesn't it? I mean, meta in > linux and windows means Ctrl. That means that overriding meta+arrows will > break the Ctrl+arrows text navigation. What am I missing? > > I don't think that alternativeMeta means something useful. And I believe > in this topic that there are no magic solutions. Spotter should define for > each platform shortcuts that do not override text navigation, > alternativeMeta will provide reusable solution for such cases.

June 16, 2017

Re: [Pharo-dev] Doing a pull request

by Marcus Denker

> On 15 Jun 2017, at 18:00, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > Hi StÃ©phane, > > On Jun 15, 2017, at 7:44 AM, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: > >> Iâm sorry but I will need to intervine here :) >> While it may look complicated /now/, it is because we are still fixing Pharo7 to work, who has a problem right now because since is bootstrapped it does not keeps any version infoâ¦ then is complicated to calculate the diffs. But we are going to fix this. >> >> Now, this is how the process will work once released: >> >> 0. You will have to have a fork of pharo (this is like that and is âzeroâ because you doit once) >> 1. You will clone pharo, using iceberg. This can be achieved two ways >> a) by cloning if is first time. >> b) by adding it if you already have this clone. Most people will end using this option. >> 2. work on fix/change >> 3. commit/push to your repo >> 4. do a Pull Request once finished. >> >> done. As you can see, this is very easyâ¦ Pavel showed an overcomplicated process that is just a workaround until we fix the problem I mentioned :) > > From the website > Create a slice (group of packages): > Open the Monticello Browser. > Open the Slice Maker by clicking the "Slice" button. > In Slice Maker enter the Fogbugz issue number and "grab" the issue summary. > Select the dirty packages relevant to your bug fix. Dirty packages are prefixed by a start and are sorted to the top of the list of packages. > Verify your changes (click on changes button) > Select the Pharo60 repository > Select your slice > Press changes in the Monticello Browser and verify that your changes are the correct one. > Publish the slice to Pharo50Inbox: > Select the whole slice (not it's individual packages). > Select the SmalltalkHub Pharo Inbox repository. > Press the "Save" button to commit your slice to the inbox repository > Verify that your fix loads: take a fresh image and load the slice you published. > Update the bug entry to mention that you submitted a slice in the inbox. > In Fogzbugz, click on "Resolve" to Change the state of the issue to "Resolved: Fix Review Needed" and ensure that the milestone is set to the next release of Pharo. > Now you can feel good! > > Too many steps. This is the old process (for up to Pharo6). yes, too complex. Yes, we know that. Yes, it should have been better and simplerâ¦ Marcus

June 16, 2017

Re: [Pharo-dev] Pharo in a read-only environment survey

by Alexandre Bergel

Done! Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Jun 15, 2017, at 9:32 AM, JÃ©rÃ©mie Regnault <jeremie.regnault(a)outlook.com> wrote: > > Hi, I'm working on Pharo deployment in a read-only environment, and I > want to know what behavior you want Pharo to adopt. If you could take > 5-10 minutes to fill my survey, it would be nice : > https://goo.gl/forms/8S7w4079NDfBrsVu1 > > Thank you, > > -- > JÃ©rÃ©mie Regnault >

June 15, 2017

Re: [Pharo-dev] Doing a pull request

by Eliot Miranda

Hi StÃ©phane, > On Jun 15, 2017, at 7:44 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Iâm sorry but I will need to intervine here :) > While it may look complicated /now/, it is because we are still fixing Pharo7 to work, who has a problem right now because since is bootstrapped it does not keeps any version infoâ¦ then is complicated to calculate the diffs. But we are going to fix this. > > Now, this is how the process will work once released: > > 0. You will have to have a fork of pharo (this is like that and is âzeroâ because you doit once) > 1. You will clone pharo, using iceberg. This can be achieved two ways > a) by cloning if is first time. > b) by adding it if you already have this clone. Most people will end using this option. > 2. work on fix/change > 3. commit/push to your repo > 4. do a Pull Request once finished. > > done. As you can see, this is very easyâ¦ Pavel showed an overcomplicated process that is just a workaround until we fix the problem I mentioned :) >From the website Create a slice (group of packages): Open the Monticello Browser. Open the Slice Maker by clicking the "Slice" button. In Slice Maker enter the Fogbugz issue number and "grab" the issue summary. Select the dirty packages relevant to your bug fix. Dirty packages are prefixed by a start and are sorted to the top of the list of packages. Verify your changes (click on changes button) Select the Pharo60 repository Select your slice Press changes in the Monticello Browser and verify that your changes are the correct one. Publish the slice to Pharo50Inbox: Select the whole slice (not it's individual packages). Select the SmalltalkHub Pharo Inbox repository. Press the "Save" button to commit your slice to the inbox repository Verify that your fix loads: take a fresh image and load the slice you published. Update the bug entry to mention that you submitted a slice in the inbox. In Fogzbugz, click on "Resolve" to Change the state of the issue to "Resolved: Fix Review Needed" and ensure that the milestone is set to the next release of Pharo. Now you can feel good! Too many steps. Why is there still no integration with FogBugz? Then there's the dubiousdescign decision of making a slice a selection of dirty packages instead of a selection of changes (what if I work on two things at once and they touch the same package? => two Images). How old is the slice process and there's no integration with fogbugz, shifting between tools. When is iceberg going to be better integrated than the slice process? > > >> On 15 Jun 2017, at 15:40, Guillermo Polito <guillermopolito(a)gmail.com> wrote: >> >> Thanks pavel, I'll copy paste it in the README :) > > I will not copy and paste all that in the README. It will not remain... > > cheers, > Esteban > > >> >>> On Thu, Jun 15, 2017 at 10:43 AM, Rajula Vineet <Vineet.Reddy(a)iiitb.org> wrote: >>> @abergel I was looking for some basic guidelines for example: creating a new >>> branch with the issue name, having the issue number and name while >>> submitting a PR. Something like this. >>> >>> @Subbu I have forked it, but I haven`t made a new branch I will do it. >>> Thanks for the tips. >>> >>> @Pavel Thank you very much. This is what I was looking out for. >>> >>> Rajula >>> >>> >>> >>> >>> >>> >>> -- >>> View this message in context: http://forum.world.st/Doing-a-pull-request-tp4951443p4951485.html >>> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >>> >> >> >> >> -- >> >> Guille Polito >> >> Research Engineer >> French National Center for Scientific Research - http://www.cnrs.fr >> >> >> Web: http://guillep.github.io >> Phone: +33 06 52 70 66 13 >

June 15, 2017

Re: [Pharo-dev] Why don't the Zero Conf examples show how to launch Pharo?

by Alistair Grant

On Mon, Jun 12, 2017 at 07:27:06PM +0000, Alistair Grant wrote: > Hi Tim, > > On Mon, Jun 12, 2017 at 08:02:23PM +0100, Tim Mackinnon wrote: > > Actually - I think its as simple as just adding > > > > && ./pharo-ui Pharo.image > > > > To the shown command? > > > > (Although maybe showing it as 2 steps makes it clearer that you don?t need to > > download each time) > > > > Tim > > I'm currently putting together suggested text for the GNU/Linux download > page. In addition to showing how to launch Pharo, I'm also suggesting: > > - Putting 32 bit first (it's currently safer for a newcomer) > - Moving new platforms to the top and older platforms lower in order > - Removing reference to Ubuntu 12.04 since it is no longer supported. > > If you've got any other suggestions, please let me know and I'll be > happy to incorporate them. I've added the suggested text in: https://pharo.fogbugz.com/f/cases/20147/Suggested-text-for-http-pharo-org-g… > Cheers, > Alistair > > > > > On 12 Jun 2017, at 19:48, Tim Mackinnon <tim(a)testit.works> wrote: > > > > Hi - I was wondering why the command line section on the http://pharo.org/ > > web/download page, doesn?t show you how to then launch the app you have > > just downloaded? > > > > I?m not sure if there is a way to do it all on one line (I tried && ./ > > pharo-ui Pharo.image - but this doesn?t work). However I think the > > website example should at least have: > > > > # then run it > > ./pharo-ui Pharo.image > > > > > > Otherwise we make it harder for people to figure out what to do with the > > program we?ve pointed them to? > > > > Tim > > > >

June 15, 2017