December 2018 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Pharo image don't restart

by Trussardi Dario Romano

Ciao, > Hi, > > The problem seems to come from: "no room in eden for allocateSmallNewSpaceSlots:format:classIndex:" > Eden is a part of the heap where new objects are allocated. > Basically, it appears that Pharo cannot create objects any more. > You can get information about gc and eden space here: https://clementbera.wordpress.com/2017/03/12/tuning-the-pharo-garbage-colle… > > Could you try to run your image in headless mode to see if it starts? > ex: > > I would try to start your image with a bigger size for the eden. > ClÃ©ment recommends to do: Smalltalk vm parameterAt: 45 put: (Smalltalk vm parameterAt: 44) * 4. > but it means you need an image that is started â¦ > > You can also set it as an argument to the VM: --eden <size>[mk] > > You could try with âeden 15207744 for example: > ~/Documents/Pharo/vms/70-x64/Pharo.app/Contents/MacOS/Pharo --eden 15207744 ~/Documents/Pharo/images/Pharo\ 7.0\ -\ 64bit\ $development\ version$/Pharo\ 7.0\ -\ 64bit\ $development\ version$.image After copy the pharoLauncher entry with the error into Pharo7.0-64DTRDevErr entry i do this: /opt/pharolauncher/pharo-vm$ ./pharo --eden 15207744 /home/party/Pharo/images/Pharo7.0-64DTRDevErr/Pharo7.0-64DTRDevErr.image the shell report: pthread_setschedparam failed: Operation not permitted ***** This VM uses a separate heartbeat thread to update its internal clock and handle events. For best operation, this thread should run at a higher priority, however the VM was unable to change the priority. The effect is that heavily loaded systems may experience some latency issues. If this occurs, please create the appropriate configuration file in /etc/security/limits.d/ as shown below: cat <<END | sudo tee /etc/security/limits.d/pharo.conf * hard rtprio 2 * soft rtprio 2 END and report to the pharo mailing list whether this improves behaviour. You will need to log out and log back in for the limits to take effect. For more information please see ...........r3732#linux Errore di segmentazione (core dump creato) Any idea about it? The ***** message required some action ? I need to configure some operating system value ? Thanks, Dario P.S. I have to conclude that there is no solution?

Dec. 13, 2018

Re: [Pharo-dev] Problem loading a branch of my pharo fork in an image

by Thomas Dupriez

I retried what I described below, but this time I cloned my pharo fork using the "Clone from github" option instead of the "Clone remote repository". It's better, but not perfect. here are the differences: - the pharo repo is marked as "Detached working Copy" instead of "Fetch required. Unknown 67dc1e8" - the changes to the WorldState class>>debugOn: were loaded this time - however, the package I had added to my branch (BreakpointBrowser) was not present, and not shown among the packages iceberg showed when double-clickig on the pharo repo Thomas Dupriez On 13/12/2018 16:18, Thomas Dupriez wrote: > Hello, > > I loaded a branch of my pharo fork in an image using iceberg, but the > method I was interested in did not change for some reason (my branch's > latest commit changes this method, but these changes were not visible > in the image I loaded my branch in). > > Does someone has an idea of what could have happened? Did I do > something wrong? > > Here's what I did step-by-step if that helps: > > - fresh pharo 7 image > - open iceberg > - repair repository "pharo" > - Clicked "Clone again this repository" > - Chose "Clone remote repository", and put the url of my pharo fork: > "https://github.com/dupriezt/pharo" > - ok > - wait for loading bar to complete > - pharo repo is marked as "Fetch required. Unknown 67dc1e8" > - repair repository "pharo" > - chose "Discard local changes and checkout an existing branch" > - chose the branch "BreakpointBrowser" from the "origin" remote > - Clicked "checkout" on the checkout preview window > - wait for loading bar to complete > - browse the method WorldState class>>debugOn: > - It is different from the last commit I made to this branch > (https://github.com/dupriezt/pharo/commit/ead94e32f138eb435a95cd889f77ca39d4…) > > Thomas Dupriez > >

Dec. 13, 2018

Re: [Pharo-dev] Application entrypoints

by Tim Mackinnon

Actually - kind of related, how does one know how to reset a framework like Seaside, or Zinc etc. Iâve been thinking about proposing frameworks should have a #reset like pragma and then the system menu could find them and show the reset menu for all frameworks that provide it. I think applications could do a similar thing - have an #applicationStart pragma and then there could be an applications menu that listed them all in a convenient menu. Tim Sent from my iPhone > On 13 Dec 2018, at 08:38, nanqueti <nicolas.anquetil(a)inria.fr> wrote: > > > we could also use the "script:" annotation, and the system browser > could show it at the class level (it already shows at the method level) > > nicolas > >> On Thu, 2018-12-13 at 10:40 +0800, Ben Coman wrote: >> A question was asked on discord... "I know how to start the lights >> out example, >> and feed my objects test data with the testing framework, but how >> does one start >> something like ChineseCheckers? How does one find the entry point? >> Is there a convention on naming a starting place?" >> >> I remember having similar thoughts when starting in Pharo. >> >> One convention I have seen is that amongst all the classes presumably >> prefixed "CC" >> one class would stand out being named for the application without the >> prefix. >> e.g. class "ChineseCheckers". That is only a narrow chance for a >> namespace conflict, >> the the risk still remains. >> >> I suggested another path would have a package tag "Application" >> (i.e. "ChineseCheckers-Application") that contains a single class >> which has an #open method on the class-side. >> The tag "Application" sorts high up on the package-tags and is self- >> descriptive. >> But I've not seen that used before, so while I think its a good idea, >> its not really a convention. >> Conventions are only useful if they are broadly understood. >> >> So I'm wondering what other things people do to draw attention to >> their application entry points. >> >> cheers -ben > -- > Nicolas Anquetil > RMod team -- Inria Lille > >

Dec. 13, 2018

Problem loading a branch of my pharo fork in an image

by Thomas Dupriez

Hello, I loaded a branch of my pharo fork in an image using iceberg, but the method I was interested in did not change for some reason (my branch's latest commit changes this method, but these changes were not visible in the image I loaded my branch in). Does someone has an idea of what could have happened? Did I do something wrong? Here's what I did step-by-step if that helps: - fresh pharo 7 image - open iceberg - repair repository "pharo" - Clicked "Clone again this repository" - Chose "Clone remote repository", and put the url of my pharo fork: "https://github.com/dupriezt/pharo" - ok - wait for loading bar to complete - pharo repo is marked as "Fetch required. Unknown 67dc1e8" - repair repository "pharo" - chose "Discard local changes and checkout an existing branch" - chose the branch "BreakpointBrowser" from the "origin" remote - Clicked "checkout" on the checkout preview window - wait for loading bar to complete - browse the method WorldState class>>debugOn: - It is different from the last commit I made to this branch (https://github.com/dupriezt/pharo/commit/ead94e32f138eb435a95cd889f77ca39d4…) Thomas Dupriez

Dec. 13, 2018

â¹Programmingâº 2019 Combined Call for Workshop Submissions

by Fabio Niephaus

=========================================================================== â¹Programmingâº 2019 Combined Call for Workshop Submissions =========================================================================== To build a community and to foster an environment where participants can exchange ideas and experiences related to practical software development, â¹Programmingâº will host a number of workshops, during the days before the main conference. The workshops will provide a collaborative forum to exchange recent and/or preliminary results, to conduct intensive discussions on a particular topic, or to coordinate efforts between representatives of a technical community. They are intended as a forum for lively discussion of innovative ideas, recent progress, or practical experience on programming and applied software development in general for specific aspects, specific problems, or domain-specific needs. We also encourage practical, hands-on workshops in which participants actually experience one or several aspects of practical software development. The following workshops are co-located with â¹Programmingâº 2019. MoreVMsâ19: Workshop on Modern Language Runtimes, Ecosystems, and VMs --------------------------------------------------------------------------- MoreVMsâ19 aims to bring together industrial and academic programmers to discuss the design, implementation, and usage of modern languages and runtimes. Possible topics include reuse of language runtimes, modular implementation, language design, and compilation strategies. Call: https://2019.programming-conference.org/track/MoreVMs-2019 Extended Abstract Deadline: 11 Jan 2019 PX/19 5th Edition of the Programming Experience Workshop --------------------------------------------------------------------------- The Programming Experience (PX) Workshop is about what happens in that room when programmers sit down in front of computers and produce code, especially in an exploratory way. We are interested in this experience of programming and how to improve and evolve it. Call: https://2019.programming-conference.org/track/px-2019-papers Submission Deadline: 27 Jan 2019 VPT 2019: Seventh International Workshop on Program Transformation and Verification --------------------------------------------------------------------------- The aim of the workshop is to bring together researchers working in the fields of Program Verification and Program Transformation. There is a great potential for beneficial interactions between these two area. The workshop will provide a forum where researchers from these fields may interact and foster new developments. The workshop solicits research, position, application, and system description papers with a special emphasis on case studies, demonstrating viability of the interactions between the research fields of program transformation and program verification in a broad sense. Call: http://refal.botik.ru/vpt/vpt2019/ Submission Deadline: 8 Jan 2019 LANGETIâ19: Languages and Tools for Next Generation Testing --------------------------------------------------------------------------- The LANGETI workshop invites for submission of research papers and tool demonstrations developing new languages and tools that explore novel techniques to test next generation applications. We specially encourage new ideas on testing and its application domain that will spark discussion during the workshop. Call: https://2019.programming-conference.org/track/langeti-2019-papers Submission Deadline: 11 Jan 2019 PASSâ19: Workshop on Programming Across the System Stack (PASS) â19 --------------------------------------------------------------------------- PASSâ19 seeks contributions at the interaction of programming languages and computer systems, such as programming abstractions for emerging platforms, runtime performance and energy optimization, software tool support for systems, systems-level reasoning and verification, language-based security, and systems programming and debugging. Call: https://2019.programming-conference.org/home/PASS-2019 Submission Deadline: 15 Jan 2019 ICW 2019: Interconnecting Code Workshop --------------------------------------------------------------------------- Modern computer systems are often loosely coupled compositions of heterogeneous components. An important part of modern programming is the art, science, and engineering of interconnecting disparate code components to offer larger services in a reliable and scalable manner. The goal of this workshop is to facilitate an ongoing discussion, and advance the state of the art of interconnecting code. Call: https://2019.programming-conference.org/track/icw-2019-papers Initial Abstract Deadline: 11 Jan 2019 Salon des RefusÃ©s 2019 --------------------------------------------------------------------------- Salon des RefusÃ©s was an 1863 exhibition of artworks rejected from the official Paris Salon. We bring the same to programming research, creating a space for interesting ideas that are difficult to reduce to a proof or a naive measurement. Call: https://shift-society.org/salon/call-for-papers Submission Deadline: 7 Jan 2019 MiniPLoP 2019 --------------------------------------------------------------------------- Patterns are a systematic way to capture the experience of experts about good designs or best practices and document these nuggets of wisdom in an accessible way for peers. You can submit papers with 2-3 patterns for a discussion in a Writerâs Workshop session. Call: https://2019.programming-conference.org/track/PLOP-2019-papers Submission Deadline: 31 Jan 2019 ProWebâ19: 3rd International Workshop on Programming Technology for the Future Web --------------------------------------------------------------------------- ProWebâ19 is a forum for researchers and practitioners to share and discuss advances in programming technology (i.e., frameworks, libraries, programming languages, program analyses and development tools) for implementing web applications and for maintaining their quality over time, as well as experience reports about the use of state-of-the-art technology for the web. Call: https://2019.programming-conference.org/track/proweb-2019-papers Submission Deadline: 15 Jan 2019

Dec. 13, 2018

[Pharo 7.0] Build #36: 22762 Cleanup TextEditorTest

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #36 was: FAILURE. The Pull Request #2066 was integrated: "22762 Cleanup TextEditorTest" Pull request url: https://github.com/pharo-project/pharo/pull/2066 Issue Url: https://pharo.fogbugz.com/f/cases/22762 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Dec. 13, 2018

Re: [Pharo-dev] Pharo image don't restart

by Christophe Demarey

Hi, The problem seems to come from: "no room in eden for allocateSmallNewSpaceSlots:format:classIndex:" Eden is a part of the heap where new objects are allocated. Basically, it appears that Pharo cannot create objects any more. You can get information about gc and eden space here: https://clementbera.wordpress.com/2017/03/12/tuning-the-pharo-garbage-colle… <https://clementbera.wordpress.com/2017/03/12/tuning-the-pharo-garbage-colle…> Could you try to run your image in headless mode to see if it starts? ex: I would try to start your image with a bigger size for the eden. ClÃ©ment recommends to do: Smalltalk vm parameterAt: 45 put: (Smalltalk vm parameterAt: 44) * 4. but it means you need an image that is started â¦ You can also set it as an argument to the VM: --eden <size>[mk] You could try with âeden 15207744 for example: ~/Documents/Pharo/vms/70-x64/Pharo.app/Contents/MacOS/Pharo --eden 15207744 ~/Documents/Pharo/images/Pharo\ 7.0\ -\ 64bit\ $development\ version$/Pharo\ 7.0\ -\ 64bit\ $development\ version$.image Regards, Christophe > Le 13 dÃ©c. 2018 Ã 09:25, Trussardi Dario Romano <dario.trussardi(a)tiscali.it> a Ã©crit : > > Ciao, > > i have a Ubuntu system > where i defined a Pharo 7.0 - 64bit image managed with PharoLauncher. > > I work with it for a month and all work fine. > > Now after a save the image the system begin unstabled. > > When the mouse go on the windows summary bar ( at the bottom of the Pharo window ) the image go down. > > The first time i can launch the same image from the PharoLauncher, > > but after a new image save ( the image go down ) i can't relaunch the image. > > When i do the launch the pharoLauch shell report: > > <errorePharo.txt> > > I have some important work in the image ( and i don't have a backup ) > > Some consideration? > > Thanks, > Dario >

Dec. 13, 2018

[Pharo 7.0] Build #35: 22763 Tag classes in Text-Diff package

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #35 was: SUCCESS. The Pull Request #2067 was integrated: "22763 Tag classes in Text-Diff package" Pull request url: https://github.com/pharo-project/pharo/pull/2067 Issue Url: https://pharo.fogbugz.com/f/cases/22763 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Dec. 13, 2018

Re: [Pharo-dev] Pharo image don't restart

by Trussardi Dario Romano

Ciao, > Ciao, >> You don't mention that you rebooted, so just try that first. > > sorry but I do not understand what you mean. > > In any case i rebooted the system. ( restart ) > > Yes, thats what I meant. Always the easiest thing to try. > > > The PharoLauncher launch command on the Pharo 7.0 -64development image report the same error. >> I have some important work in the image ( and i don't have a backup ) >> >> Some consideration? > > > I'm not in a position to diagnose the error, but perhaps help you recover your work. Can someone help me? It's very important.....!!! > In PharoLauncher, if you right-click on the image you are trying to launch, > then choose "Show in folder" then browse to "pharo-local/ombu-sessions" > and you should see some files. If you create a fresh image and copy those to the same location there, > the go World menu > Tools > Code Changes and see if you find your work. > Check out the filters. Possibly useful... > * Show only latest changes > * Show only changes in this package Thanks. OK, i see the methods ..... ( i need to understand what i can do with these ..... ) But in the image i have the data base with real data...... and ...... Stupidly I lost the version that started with the launcher, saving it on itself after it began to have problems...... Thanks, Dario

Dec. 13, 2018

Re: [Pharo-dev] periodic auto actions on bug tracker

by Marcus Denker

> On 13 Dec 2018, at 03:35, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Marcus Denker-4 wrote >>> I support the auto-closing of old tickets to avoid bug bankruptcy >> ... >> Yes, that is a good idea. > > I thought we already did that. Don't we even have a stale/timeout tag to > distinguish from other reasons for closing and help find them again later if > needed? > We close them with a timeout tag. But we do not send a public mail âhey, these tickets will be closed next weekâ. Only the *owner* gets a message on closing. Marcus

Dec. 13, 2018