November 2019 - Pharo-dev - lists.pharo.org

Recommendation for password encryption?
by Mariano Martinez Peck Sept. 30, 2022

Sept. 30, 2022

Hi guys. Some time ago I asked about the best way to encrypt a password. Some of the recommendations I got was: 1) Generally for passwords you do not write a decrypt method for security purposes (eg you do not want people to be able to reverse engineer the encrypted password easily) 2) put a little salt 3) There is http://www.squeaksource.com/Cryptography/PasswordHashingFFI 4) I should not decrypt password but instead I should compare both encrypted versions to see if they are equal. My scenario is the following. I need to store database passwords in text files. So I don't want to let them as plain text. And while I understand 4), I think it's a different scenario than mine. I know that some database driver may allow you to directly send the encrypted password. But still...I have another similar scenario in which I have to store a password and then send it (unencrypted)...so I kind of really need a bi-directional encryption. Now..I would try to avoid having an external library + FFI. Any ideas what is the best thing I can do? And how could I solve 1) if I want bidirectional like in my case? Thanks in advance, -- Mariano http://marianopeck.wordpress.com

9 26

Re: [Pharo-project] Parsing and navigating Html
by Paul DeBruicker July 16, 2020

July 16, 2020

On 12/05/2010 06:02 AM, pharo-project-request(a)lists.gforge.inria.fr wrote: > From: St?phane Ducasse<stephane.ducasse(a)inria.fr> > Subject: [Pharo-project] Parsing and navigating Html > To:"Pharo-project(a)lists.gforge.inria.fr Development" > <Pharo-project(a)lists.gforge.inria.fr> > Message-ID:<1C53DFD8-3021-4233-BC83-CE8C1EA8D103(a)inria.fr> > Content-Type: text/plain; charset=us-ascii > > Hi > > I would like extract partial information from HTML pages. > So I started to play and fix HTMLParser. > > Now does anybody know alternatives? > > Second, does anybody develop a lib to query HTML structure as with the XMLSupport package? > > Stef The Soup package on SqueakSource.com works OK.

3 4

Re: [Pharo-dev] Contribute to pharo8.0 ?
by Ritesh Saini Feb. 24, 2020

Feb. 24, 2020

Having the same issue. Canât fix! Tried everything :( Regards, Ritesh adsense high paying keywords <https://www.digitalkube.com/highest-paying-adsense-niches/>

3 2

Bugs still open on traits
by ducasse Dec. 4, 2019

Dec. 4, 2019

Hi andrei can you tell us the bug that you mentioned to me on traits and that skipped our radar? Stef

4 6

[Mm10s] 2019-11-25
by Esteban Lorenzano Dec. 2, 2019

Dec. 2, 2019

Hello, still working on enhance our communication, this week the core team will start informing our weekly todo. This is something we were using internally with success but now we will make it public, and it will include three points : last week work, this week work and what we have in our pipeline. (NOTE: This mail does not replaces the monthly report but complements it). So, I will start :) ### Last week: - [Spec2] Add search capability to lists/tables/trees. - [Spec2+Gtk3] Ensuring the parts that needs to run on main thread are correctly deferred there. - [VM] Adding ways to control whether we run the VM on main thread or worker thread. - [VM] Merging AIO interrupt branch, Worker thread branch and headless branch. - [VM] Preparing a linux machine to debug the vm and gtk3 spec2 backend there. ### This week (starting 2019-11-25): - [Spec2] Add search capability to lists/tables/trees. - [Spec2+Gtk3] Ensuring the parts that needs to run on main thread are correctly deferred there. - [VM] Verify some problems where AIO should interrupt and it does not doit, causing the vm to not respond to events. ### Pipeline - [Release] Prepare checklist to release of Pharo 8. - [Spec2] Search and filters on list/tables/trees. - [Spec2] Fix radio buttons. - [VM] debug AIO and worker thread VMs on linux and windows. - [NewTools] Create miller list paginator to make inspector panes more visible. - [NewTools] Enhance Inspector (several tasks here).

4 6

Erlang/OTP/Pony-style concurrency in Smalltalk
by Shaping Nov. 29, 2019

Nov. 29, 2019

(I posted this earlier to the OS VM group (vm-dev(a)lists.squeakfoundation.org) but the message appeared as an attachment. I'm not sure that was the right place; so I'm reposting here.) Hi all. I was reading about the RoarVM, recently. The project seems to be at a standstill. Why, as in the RoarVM, would someone try to build a Smalltalk VM supporting concurrency, and not also resolve to use a strict actor model in which each process has its own, usually small heap that is very quickly and simply GCed? If I understand correctly, RoarVM still had one big heap for all processes. With one heap per process, many times no GC happens at all: the process finishes and the heap is discarded. This finer-grained memory-management dynamic gets us closer to deterministic latencies, which are needed in simulations (and almost anything graphical you want to render smoothly). The idea with the actor model (and the OTP-style work-stealing that accompanies it) is not only to use very continuously all cores in all CPUs in all machine-nodes on the network, all of the time (until the program exits or goes idle), but also to make using the usual synchronization devices (semaphores, mutexes, monitors, and the like) unnecessary. This is where all the complexity is and where the time and effort go when coding and debugging concurrent apps. No one wants to use these devices if he needn't. The actor model is an elegant way to solve the concurrent-programming problem, which mostly reduces to advancing program state with only asynchronous messaging, while causing no blocking and no idle cores if there is still work left to do. The actor model works if you are willing to build a proper state-machine for your app (I have some ideas for a GUI to help in this respect) and the asynchronous messaging is fast. It is very fast in Pony (https://www.ponylang.io/) (Smalltalk images linked by WS connections won't be fast enough.) I'm learning to use Pony these days. It's a good tool, and it's improving at a good pace with an enthusiastic community. It's statically compiled; so it's not speeding development/experimentation as much as it is the resulting program. However, Pony vastly reduces the amount of concurrency-related debugging you would otherwise do if you did not, after a successful compile, have a provably non-deadlocking/non-data racing program. This is the new thing that Pony gives you, and it's great. But I want a dynamic development environment and very efficient Erlang/OTP/Pony-style concurrency. How do we get that? Why wasn't this the path chosen by the RoarVM developers? What is happening in OpenSmalltalk VM regarding such concurrency? I'm considering using Pony somehow in a 5-pane browser (but that's some work), dumping compiler errors to the Transcript. I'm not fond of editing text files (scrolling/searching) even when the process is very graceful. That's too 20th-century. VS Code is a very nice tool with great extensions, but it does not replace what happens in a Smalltalk browser. Please share your thoughts on what is happening or what could be done to create Erlang/OTP/Pony-style concurrency in Smalltalk. Cheers, Shaping

1 0

[Pharo 8.0] Build #1026: 5190-Match-comments-should-turned-into-executable-comments
by ci-pharo-ci-jenkins2＠inria.fr Nov. 29, 2019

Nov. 29, 2019

There is a new Pharo build available! The status of the build #1026 was: SUCCESS. The Pull Request #5265 was integrated: "5190-Match-comments-should-turned-into-executable-comments" Pull request url: https://github.com/pharo-project/pharo/pull/5265 Issue Url: https://github.com/pharo-project/pharo/issues/5190 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

ECOOP'20 Berlin - Call for Papers
by Fabio Niephaus Nov. 29, 2019

Nov. 29, 2019

============================================================ The 34th Edition of ECOOP Call for Papers 13th-17th July 2020 Berlin, Germany https://2020.ecoop.org/ ============================================================ ECOOP is a conference about programming. Originally its primary focus was on object orientation, but now it looks at a much broader range of programming topics. Areas of interest include, at least, the design, implementation, optimization, analysis, and theory of programs, programming languages, and programming environments. It solicits both innovative and creative solutions to real problems as well as evaluations of existing solutionsâevaluations that provide new insights. It also encourages the submission of reproduction studies. ECOOP 2020 solicits high-quality submissions describing original, unpublished results. The program committee will evaluate the technical contribution of each submission as well as its general relevance and accessibility to the ECOOP audience according to the following criteria: - Originality. Papers must present new ideas and place them appropriately within the context established by previous research in the field. - Significance. The results in the paper must have the potential to add significantly to the state of the art or practice. - Evidence. The paper must present evidence supporting its claims. Examples of evidence include implemented systems, experimental results, statistical analyses, case studies, formalizations, and proofs. - Clarity. The paper must present its contributions and results clearly. On submission, authors will be asked to identify their paper with one of the following categories: - Research Paper. This is the most traditional category and solicits high quality research papers that demonstrate advances in the field. (As an alternative to being published in the conference proceedings, authors may wish to submit research papers to be considered for publication in ACM TOPLAS or Science of Computer Programming.) - Tool Insights Paper. These submissions focus on the practical details of the design and implementation of PL toolsâdetails that are often omitted from regular research papers, despite being fascinating and worthy of communication. A strong Tool Insights Paper should communicate engineering experience and insights that are likely to be useful to other members of the PL community, who may face similar problems in future. Examples of issues that Tool Insights Papers might focus on include, but are not limited to: performance, reliability, portability, inter-tool integration, infrastructure re-use, evaluation issues, theory/practice gaps, precision/efficiency, and soundness/efficiency trade-offs. - Reproduction Study. A Reproduction Study is an empirical evaluation. It reconstructs an already published experiment but in a different context (for example, using a different virtual machine or platform, or in a different class of applications) in order to validate or refute important results of earlier work. A good Reproduction Study includes thorough empirical evaluation as well as a detailed comparison with the previous results, providing reasons for possible disagreements. (A thoroughly-conducted Reproduction Study that perfectly replicates an existing experiment and reaches the same conclusions will be regarded as significant, so long as said experiment is significant enough to be worthy of reproduction.) - Experience Report. Such reports focus on noteworthy applications of known PL techniques, tools, and ideas in interesting domains and by other communities. Examples include, but are not limited to, applications of PL techniques in industry, open source, education, and other academic disciplines. We welcome reports on successful applications of PL ideas and reports that shed light on limitations and problems that may provide inspiration for future research. - Pearl. This category solicits articles that explain a known idea in a new and elegant way, to the benefit of the PL community. A Pearl may well be shorter than a regular research paper, but there is no hard requirement on this. - Brave New Idea. The Brave New Idea category solicits forward-looking articles on ideas in the field of PL that may take some time to substantiate, but for which early communication to the community is likely to be of benefit. For this category we welcome papers that are particularly conceptually novel or unconventional and that as a result may be harder to back up by traditional evaluation methods. A Brave New Idea paper may well be shorter than a regular research paper, but there is no requirement for it to be so. Paper Submission ================ Only papers that have not been published and are not under review for publication elsewhere may be submitted. Double submissions will be rejected without review. If major parts of an ECOOP submission have appeared elsewhere in any form, authors are required to notify the ECOOP program chair and explain the overlap and relationship. Authors are also required to inform the program chair about closely related work submitted to another conference while the ECOOP submission is under review. Papers must be no longer than 25 pages, excluding references. See below for information about appendices. Authors will not be penalized for papers that are shorter than the page limit. Submissions will be carried out electronically via the conference website [1]. ECOOP Proceedings are published by Dagstuhl LIPIcs. Papers must be written in English and follow the Dagstuhl LIPIcs LaTeX-style template [2]. Authors retain ownership of their content. Note: Submitted papers do not need to include the ACM classification or keywords. Also, please DO NOT put your name in either the \author or \Copyright macro, in order to maintain anonymity for double-blind reviewing (see below). Anonymity ========= ECOOP will use light double-blind reviewing: authorsâ identities are withheld until a reviewer submits his or her review (as usual, reviews are anonymous). To facilitate this, submitted papers must adhere to two rules: - Author names and institutions must be omitted. - References to authorsâ own other work should be in the third person (for example, not âWe build on our previous workâ¦â but rather âWe build on the work ofâ¦â). When in doubt, contact the Program Chair. Additional Material =================== Clearly marked additional appendices containing analyses, statistics, supporting proofs, etc. of possible value to reviewers but not published in the final publication, may be included beyond the page limit. The submission system provides an option to submit supplementary material; for example, a technical report including proofs, or web pages and repositories that cannot easily be anonymized. This supplementary material will be made available to reviewers after the initial reviews have been completed, when author names are revealed. Reviewers are under no obligation to examine such appendices and supplementary material. Therefore, the paper must be a stand-alone document - the appendices and supplementary material are a way of providing useful information that cannot fit in the page limit; they are not a means to extend the page limit. Authors of papers that have been submitted but not accepted by previous conferences may optionally submit a Note to Reviewers. The Note to Reviewers should provide the following information: - the identity of the previous venue(s) (for example, ESOP 2020, â¹Programmingâº 2020, POPL 2020, OOPSLA 2019) - a list the major issues identified by the reviews at those venues - a description of the changes made to the paper in response to those reviews These notes will be made available to reviewers after their initial reviews have been completed and author names have been revealed. Response Period =============== Authors will be given a three-day period to read and respond to the reviews of their papers before the program committee meeting. Responses have no formal length limit, but concision is likely to be effective. Artifact Evaluation =================== To reward the creation of artifacts and support replication of experiments, authors of accepted research papers may submit artifacts (such as tools, data, models, or videos) to be evaluated by an Artifact Evaluation Committee. Artifacts that pass muster will be recognized officially. Important Dates =============== - Paper submission: 10 January 2020 (Fri) - Author response: 16â18 March 2020 (Mon-Wed) - Author notification: 8 April 2020 (Wed) Journal First ============= We have Journal First arrangements with ACM Transactions on Programming Languages and Systems and Elsevier Science of Computer Programming. Common to both routes --------------------- Only new research papers are eligible for the Journal First routes to ECOOP 2020. That is, it is not acceptable to submit an extension of a previous conference paper, even if the associated journal solicits extended papers via its standard submission route. Authors of all accepted Journal First papers will be invited to submit a short abstract for their paper to appear in the ECOOP 2020 conference proceedings. Journal First papers will be included along with research papers submitted directly to the conference when a Distinguished Paper is selected. Science of Computer Programming route ------------------------------------- See this dedicated web page [3] for full details of how to submit to the ECOOP 2020 Science of Computer Programming (SCP) special issue. Submission deadline: December 2, 2019 (Mon) ACM Transactions on Programming Languages and Systems route ----------------------------------------------------------- See this announcement [4] for details of the TOPLAS scheme whereby papers submitted to TOPLAS can be presented at selected conferences. Authors interested in this route should submit their paper to TOPLAS via its usual submission system and mark it as an ECOOP 2020 submission. The ECOOP Program Chair will then be informed of this submission and will have some input into the review process. Submission deadline: October 10, 2019 (Thu) More Information ================ For additional information, please contact the ECOOP Program Chair, Robert Hirschfeld [5]. [1] https://2020.ecoop.org/track/ecoop-2020-papers [2] https://www.dagstuhl.de/en/publications/lipics/instructions-for-authors/ [3] https://www.journals.elsevier.com/science-of-computer-programming/call-for-… [4] https://toplas.acm.org/announcements.cfm#submit-a-paper-for-pldi-2016 [5] https://www.hpi.uni-potsdam.de/hirschfeld/people/hirschfeld/

1 0

[Pharo 8.0] Build #1025: CompletionFallBack
by ci-pharo-ci-jenkins2＠inria.fr Nov. 28, 2019

Nov. 28, 2019

There is a new Pharo build available! The status of the build #1025 was: SUCCESS. The Pull Request #5258 was integrated: "CompletionFallBack" Pull request url: https://github.com/pharo-project/pharo/pull/5258 Issue Url: https://github.com/pharo-project/pharo/issues/CompletionFallBack Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Re: [Pharo-dev] BlueInk removal
by Torsten Bergmann Nov. 28, 2019

Nov. 28, 2019

To me it certainly looks like a <before we freeze Pharo 8 we have to speed up with features> to get things in by all means. Have to admit I had this kind of "panic mode" myself several times in the past too ;) Stef writes he now does not have the time nor energy - which I guess (including his reactions) is a tribute to his workload. But then it would have been better to change to new Elumineire or getting rid of GTEventRecorder in Pharo 9 and now just marking them for later exclusion. Because often we all underestimate the depencies, side effects, migration costs - even the reactions. Meanwhile Pharo is not only the base image - it is the full ecosystem around it which is good and a positive sign and something we IMHO need to respect more and more. One has to understand that by just removing and not using deprecation the situation is getting worse and now pulling more time and energy from other parts of the community too. Because broken stuff like Spotter, Settings, Roassal, Moose, ... would need repair - either directly (to help contributors who use them in P8 alpha already to give quick feedback) - together with the Pharo 8 release so they can be used - after Pharo 8 is released (which would be very late and might include migration surprises) Depreaction would help us better managing such transitions and is something that is standard in other languages too. The alternative would be to say this is OPP (other peoples problem) and completely ignoring that projects are built on top of Pharo base. We all know removing leads to being incompatible and is not helpful in offering a transition path - therefore not a good option. Because then users would always need to start from scratch with each Pharo release and loose interest quickly. Users want to do both: use Pharo and move their projects without having to focus on changed infrastructure too often. Deprecation would give more room to fixing it- we have theses mechanisms like deprecations and we should really use them. In the past we were able to move more freely - but now we should really accept that with more users we have to follow certain backwards compatibility and more clear rules. This slows us down yes and requires more time and energy. But it is still a good thing because Pharo is actually used and the community can grow. We can not move Pharo into the "perfect" future with a crowbar as this would mean to loose users and especially trust into the system. We might then still come up with an improved (but still imperfect) system in a few years - but nobody would be interested anymore. If we fail to see things from the POV of the user then we will fail overall and loose them. I agree with Benoit that especially business users first have to solve the customers problems before they can juggle with migrations. So lets support the overall community and not being ignorant to it. So far we all managed it quite good: moving from Pharo 6 to 7 and even Pharo 8 is working because things over the last releases stabilized and also because we added more rules, depreactions, transformations and helping users. I personally would prefer to see that "Pharo is not perfect but strong and widely used" than "look how cool it could have been", so lets not get too impatient. Step by step - sometimes faster sometimes slower... Thanks T.

3 2

[Pharo 8.0] Build #1024: CompletionFallBack
by ci-pharo-ci-jenkins2＠inria.fr Nov. 28, 2019

Nov. 28, 2019

There is a new Pharo build available! The status of the build #1024 was: FAILURE. The Pull Request #5258 was integrated: "CompletionFallBack" Pull request url: https://github.com/pharo-project/pharo/pull/5258 Issue Url: https://github.com/pharo-project/pharo/issues/CompletionFallBack Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #1023: 5102-FastTable-Horizontal-Scrolling-not-implemented
by ci-pharo-ci-jenkins2＠inria.fr Nov. 28, 2019

Nov. 28, 2019

There is a new Pharo build available! The status of the build #1023 was: SUCCESS. The Pull Request #5107 was integrated: "5102-FastTable-Horizontal-Scrolling-not-implemented" Pull request url: https://github.com/pharo-project/pharo/pull/5107 Issue Url: https://github.com/pharo-project/pharo/issues/5102 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[ANN] freezing Pharo 8.0 development
by Esteban Lorenzano Nov. 28, 2019

Nov. 28, 2019

Hi, After talk about current situation of P8 development, we decided we have already a version that is very stable (with some remaining problems, we know) and we think this is something we can release before start the new batch of breaking changes (move to headless vm by default, new object centric debugger, etc, etc, etc.) So, I am declaring the development status on âcode freezeâ and we will start working on stabilisation hoping to have a releasable version by end December, beginning of January (yes, this will be a short cycle, but that will allow us to make some iterations needed without the pressure of releasing on April). Enjoy, Esteban

1 0

MDLApplication
by Sven Van Caekenberghe Nov. 28, 2019

Nov. 28, 2019

Hi, I am trying to use MaterialDesignLite (master branch in Pharo 7). The demo works perfectly. Now, I thought I would start writing a small web app by subclassing MDLApplication, since that seems to set up things properly. Is that class finished ? How am I supposed to use it ? There are screens, but how are these rendered ? Do I have to do this myself ? Must there not be an idea of a current screen ? MDLScreen is in fact an empty class. Although there are units tests for MDLApplication, there is no subclass, so no actual user. It feels a bit as if the demo should/could use it. Sven

3 5

[Pharo 8.0] Build #1022: In bootstrap: Preparing heap before writing the image to shrink its size
by ci-pharo-ci-jenkins2＠inria.fr Nov. 28, 2019

Nov. 28, 2019

There is a new Pharo build available! The status of the build #1022 was: SUCCESS. The Pull Request #5255 was integrated: "In bootstrap: Preparing heap before writing the image to shrink its size" Pull request url: https://github.com/pharo-project/pharo/pull/5255 Issue Url: https://github.com/pharo-project/pharo/issues/Pharo8.0 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

BlueInk removal
by Cyril Ferlicot Nov. 28, 2019

Nov. 28, 2019

Hi, Can we revert the removal of blueink the time the new formatter is in the image please? (And maybe deprecate it instead of removing it). I ask this because: - If we work with Pharo 8 we need to format the code by hand because the format option is currently messing the code - The current formatter is removing all method comment - Currently removing it without deprecation is breaking the setting system (And since I push the setting system further than most people, I cannot even open an image with settings now...) I remind that the formatter is called by the refactorings. Imagine my surprise when I wanted to commit refactorings and I saw all the formatting messed up and all my method comments missing. I really do not appreciate to lose comments I spent time to write like this... -- Cyril Ferlicot https://ferlicot.fr

6 12

[Pharo 8.0] Build #1021: 5246--AST-Core-Tests-package-disappeared
by ci-pharo-ci-jenkins2＠inria.fr Nov. 27, 2019

Nov. 27, 2019

There is a new Pharo build available! The status of the build #1021 was: FAILURE. The Pull Request #5254 was integrated: "5246--AST-Core-Tests-package-disappeared" Pull request url: https://github.com/pharo-project/pharo/pull/5254 Issue Url: https://github.com/pharo-project/pharo/issues/5246 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #1020: Fix spotter openning bug
by ci-pharo-ci-jenkins2＠inria.fr Nov. 27, 2019

Nov. 27, 2019

There is a new Pharo build available! The status of the build #1020 was: SUCCESS. The Pull Request #5251 was integrated: "Fix spotter openning bug" Pull request url: https://github.com/pharo-project/pharo/pull/5251 Issue Url: https://github.com/pharo-project/pharo/issues/fix_spotter_bug Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #1019: Fix spotter openning bug
by ci-pharo-ci-jenkins2＠inria.fr Nov. 27, 2019

Nov. 27, 2019

There is a new Pharo build available! The status of the build #1019 was: FAILURE. The Pull Request #5251 was integrated: "Fix spotter openning bug" Pull request url: https://github.com/pharo-project/pharo/pull/5251 Issue Url: https://github.com/pharo-project/pharo/issues/fix_spotter_bug Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #1018: Fix spotter openning bug
by ci-pharo-ci-jenkins2＠inria.fr Nov. 27, 2019

Nov. 27, 2019

There is a new Pharo build available! The status of the build #1018 was: FAILURE. The Pull Request #5251 was integrated: "Fix spotter openning bug" Pull request url: https://github.com/pharo-project/pharo/pull/5251 Issue Url: https://github.com/pharo-project/pharo/issues/fix_spotter_bug Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #1017: [easyReview] correcting a small typo
by ci-pharo-ci-jenkins2＠inria.fr Nov. 27, 2019

Nov. 27, 2019

There is a new Pharo build available! The status of the build #1017 was: FAILURE. The Pull Request #5245 was integrated: "[easyReview] correcting a small typo" Pull request url: https://github.com/pharo-project/pharo/pull/5245 Issue Url: https://github.com/pharo-project/pharo/issues/typos Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #1016: Completion: EntryCleanup
by ci-pharo-ci-jenkins2＠inria.fr Nov. 27, 2019

Nov. 27, 2019

There is a new Pharo build available! The status of the build #1016 was: FAILURE. The Pull Request #5229 was integrated: "Completion: EntryCleanup" Pull request url: https://github.com/pharo-project/pharo/pull/5229 Issue Url: https://github.com/pharo-project/pharo/issues/CompletuonEntryCleanup Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #1015: 5223-Remove-blueInk-packages-from-repository
by ci-pharo-ci-jenkins2＠inria.fr Nov. 27, 2019

Nov. 27, 2019

There is a new Pharo build available! The status of the build #1015 was: FAILURE. The Pull Request #5243 was integrated: "5223-Remove-blueInk-packages-from-repository" Pull request url: https://github.com/pharo-project/pharo/pull/5243 Issue Url: https://github.com/pharo-project/pharo/issues/5223 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #1014: fixSystemDependenciesTests
by ci-pharo-ci-jenkins2＠inria.fr Nov. 27, 2019

Nov. 27, 2019

There is a new Pharo build available! The status of the build #1014 was: FAILURE. The Pull Request #5242 was integrated: "fixSystemDependenciesTests" Pull request url: https://github.com/pharo-project/pharo/pull/5242 Issue Url: https://github.com/pharo-project/pharo/issues/fixSystemDependenciesTests Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #1013: 5238-Checking-a-checkbox-in-Enluminer-setting-crash
by ci-pharo-ci-jenkins2＠inria.fr Nov. 26, 2019

Nov. 26, 2019

There is a new Pharo build available! The status of the build #1013 was: FAILURE. The Pull Request #5240 was integrated: "5238-Checking-a-checkbox-in-Enluminer-setting-crash" Pull request url: https://github.com/pharo-project/pharo/pull/5240 Issue Url: https://github.com/pharo-project/pharo/issues/5238 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #1012: 5232-Remove-GTEventRecorder-
by ci-pharo-ci-jenkins2＠inria.fr Nov. 26, 2019

Nov. 26, 2019

There is a new Pharo build available! The status of the build #1012 was: FAILURE. The Pull Request #5236 was integrated: "5232-Remove-GTEventRecorder-" Pull request url: https://github.com/pharo-project/pharo/pull/5236 Issue Url: https://github.com/pharo-project/pharo/issues/5232 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #1011: 5233-Integrate-EnlumineurFormatter
by ci-pharo-ci-jenkins2＠inria.fr Nov. 26, 2019

Nov. 26, 2019

There is a new Pharo build available! The status of the build #1011 was: FAILURE. The Pull Request #5234 was integrated: "5233-Integrate-EnlumineurFormatter" Pull request url: https://github.com/pharo-project/pharo/pull/5234 Issue Url: https://github.com/pharo-project/pharo/issues/5233 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

VM crash investigations
by Alistair Grant Nov. 26, 2019

Nov. 26, 2019

Hi All, At the moment I'm spending pretty much all of my working time tracking down VM crashes. It sounds like there may be others working on the same issue (Guille?, Pablo?), if so it would be good to be able to exchange notes and hopefully reach a resolution a little earlier. So my status... I'm currently focusing on two corruptions that I've seen: 1. Frame Pointers aren't being updated when the receiver or rcvr/clsr they point to is moved during scavenging / compaction. 2. The current frame pointer (framePointer) contains an address that is in a free stack page. I'm doing all the investigation using a Pharo minimal image, so there's no FreeType, and from what I've seen FFI isn't being used. The script I'm using to reproduce the crash is at: https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/444#issuecomment-5… (the good part about this is that even the memory addresses are consistent across runs, so it is highly reproducible). For the Frame Pointers not being updated, what I'm seeing is that after a scavenge has finished copying all the referenced objects, but before the survivor spaces are exchanged, the call stack looks like: (gdb) call printCallStack() 0x7ffffffe3f70 I SessionManager>launchSnapshot:andQuit: 0x1508860: a(n) SessionManager 0x7ffffffe3fe0 I [] in SessionManager>snapshot:andQuit: 0x1508860: a(n) SessionManager 0x7ffffffe4020 I [] in INVALID RECEIVER>newProcess 0x118a728 0x118a728 is a forwarded object to 0x488fca0 of slot size 7 hdr8 ..... Once the survivor spaces have been exchanged: (gdb) call printCallStack() 0x7ffffffe3f70 I SessionManager>launchSnapshot:andQuit: 0x1508860: a(n) SessionManager 0x7ffffffe3fe0 I [] in SessionManager>snapshot:andQuit: 0x1508860: a(n) SessionManager 0x7ffffffe4020 I [] in INVALID RECEIVER>newProcess 0x118a728 is in new space For the framePointer containing an address in a free stack page: adding a check during the scavenge shows that the framePointer is in a free page. I'm assuming it is never valid for the framePointer to be in a free stack page, and that the receiver and rcvr/clsr should never be in new space. If my assumptions are wrong please let me know. If you'd like any more information, please let me know. Thanks, Alistair

3 3

[Pharo 8.0] Build #1010: 5212-Executable-comment-checker-problem
by ci-pharo-ci-jenkins2＠inria.fr Nov. 26, 2019

Nov. 26, 2019

There is a new Pharo build available! The status of the build #1010 was: FAILURE. The Pull Request #5224 was integrated: "5212-Executable-comment-checker-problem" Pull request url: https://github.com/pharo-project/pharo/pull/5224 Issue Url: https://github.com/pharo-project/pharo/issues/5212 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #1009: 5217-Remove-blueInk-to-introduce-Enlumineur
by ci-pharo-ci-jenkins2＠inria.fr Nov. 25, 2019

Nov. 25, 2019

There is a new Pharo build available! The status of the build #1009 was: FAILURE. The Pull Request #5218 was integrated: "5217-Remove-blueInk-to-introduce-Enlumineur" Pull request url: https://github.com/pharo-project/pharo/pull/5218 Issue Url: https://github.com/pharo-project/pharo/issues/5217 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #1008: Completion: Fix emebdded Browser
by ci-pharo-ci-jenkins2＠inria.fr Nov. 25, 2019

Nov. 25, 2019

There is a new Pharo build available! The status of the build #1008 was: FAILURE. The Pull Request #5220 was integrated: "Completion: Fix emebdded Browser" Pull request url: https://github.com/pharo-project/pharo/pull/5220 Issue Url: https://github.com/pharo-project/pharo/issues/CompletionFixBrowser Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

DrTest - strange UI effect and some feedback
by Torsten Bergmann Nov. 25, 2019

Nov. 25, 2019

Hi, DrTest is integrated into Pharo 8 now - but there seems to be a strange bug in overlapping widgets when one uses the grouping selection box. See attached screenshot. I opened an issue for that: https://github.com/pharo-project/pharo/issues/5205 for Pharo. Dont know if that is known bug or even already fixed in the original repo of DrTest. Would be good if the authors (Julien or Dayne) could check. Additional feedback: It's really a nice tool - but I see myself still switching back to old TestRunner again. Two reasons: 1. Compared to the regular TestRunner where one is able to see the failing tests directly in DrTest one always has to have additional clicks in the grouping tree on the left before getting the final results. So the default grouping of the results as a tree could be disturbing because it requires more clicking around. Would be a nice addition if there would be an additional "no grouping" mode as well so the results are just shown in a list like in reglar TestRunner. 2. The old TestRunner had (after filtering the package) an additional useful context menu with "Select all" and "Select none", "Select inversion", .... which allowed easier focusing on the test classes I want to check. Would be nice if a similar one could be added. Thanks T.

4 4

[ANN] Next Pharo Sprint: Nov 29
by Marcus Denker Nov. 25, 2019

Nov. 25, 2019

We will organize a Pharo sprint / Moose dojo Nov 29, starting at 10:00am. (Local Time Paris). Goals of this sprint: - Pharo 8: Fix issues from tracker https://github.com/pharo-project/pharo/issues <https://github.com/pharo-project/pharo/issues> Remote Sprint: Remotely, you can join us on Discord. During the sprint, we synchronize local and remote Pharo sprinters: http://pharo.org/contribute-events <http://pharo.org/contribute-events> We have added a Board to coordinate the work: https://github.com/orgs/pharo-project/projects/9 <https://github.com/orgs/pharo-project/projects/9> Known Local Sprint meetings - Lille/France: It will be at the Inria Lille, Building B, third floor (RMoD offices). As the building is not open to the public, please contact us before if you plan to come A list of all Pharo Event of the year an be found here: https://association.pharo.org/events <https://association.pharo.org/events>

1 0

[Pharo 8.0] Build #1007: 5213-Little-pass-on-DrTests
by ci-pharo-ci-jenkins2＠inria.fr Nov. 24, 2019

Nov. 24, 2019

There is a new Pharo build available! The status of the build #1007 was: FAILURE. The Pull Request #5214 was integrated: "5213-Little-pass-on-DrTests" Pull request url: https://github.com/pharo-project/pharo/pull/5214 Issue Url: https://github.com/pharo-project/pharo/issues/5213 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #1006: Reflectivity: ASTCacheReset not needed
by ci-pharo-ci-jenkins2＠inria.fr Nov. 23, 2019

Nov. 23, 2019

There is a new Pharo build available! The status of the build #1006 was: FAILURE. The Pull Request #5210 was integrated: "Reflectivity: ASTCacheReset not needed" Pull request url: https://github.com/pharo-project/pharo/pull/5210 Issue Url: https://github.com/pharo-project/pharo/issues/ReflectivityNoASTCacheReset Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #175: Backport-5072-MCClassTraitDefinition-should-take-category-into-account-for-equality
by ci-pharo-ci-jenkins2＠inria.fr Nov. 23, 2019

Nov. 23, 2019

There is a new Pharo build available! The status of the build #175 was: FAILURE. The Pull Request #5075 was integrated: "Backport-5072-MCClassTraitDefinition-should-take-category-into-account-for-equality" Pull request url: https://github.com/pharo-project/pharo/pull/5075 Issue Url: https://pharo.fogbugz.com/f/cases/Backport Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #1005: Improve-AssertEquals-Rule
by ci-pharo-ci-jenkins2＠inria.fr Nov. 22, 2019

Nov. 22, 2019

There is a new Pharo build available! The status of the build #1005 was: FAILURE. The Pull Request #5197 was integrated: "Improve-AssertEquals-Rule" Pull request url: https://github.com/pharo-project/pharo/pull/5197 Issue Url: https://github.com/pharo-project/pharo/issues/Improve Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #1004: UseNecEntrySubclasses
by ci-pharo-ci-jenkins2＠inria.fr Nov. 22, 2019

Nov. 22, 2019

There is a new Pharo build available! The status of the build #1004 was: FAILURE. The Pull Request #5206 was integrated: "UseNecEntrySubclasses" Pull request url: https://github.com/pharo-project/pharo/pull/5206 Issue Url: https://github.com/pharo-project/pharo/issues/UseNecEntrySubclasses Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #1003: Rollback to setStrokePaint for issue: Remove use of StrokePaintCache #5199
by ci-pharo-ci-jenkins2＠inria.fr Nov. 22, 2019

Nov. 22, 2019

There is a new Pharo build available! The status of the build #1003 was: SUCCESS. The Pull Request #5201 was integrated: "Rollback to setStrokePaint for issue: Remove use of StrokePaintCache #5199" Pull request url: https://github.com/pharo-project/pharo/pull/5201 Issue Url: https://github.com/pharo-project/pharo/issues/Pharo8.0 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #1002: #flatCollect: implement using #streamContents:
by ci-pharo-ci-jenkins2＠inria.fr Nov. 22, 2019

Nov. 22, 2019

There is a new Pharo build available! The status of the build #1002 was: SUCCESS. The Pull Request #5204 was integrated: "#flatCollect: implement using #streamContents:" Pull request url: https://github.com/pharo-project/pharo/pull/5204 Issue Url: https://github.com/pharo-project/pharo/issues/flatcollectstreamcontents Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #1001: Cleanup #allClassVarNames
by ci-pharo-ci-jenkins2＠inria.fr Nov. 22, 2019

Nov. 22, 2019

There is a new Pharo build available! The status of the build #1001 was: SUCCESS. The Pull Request #5203 was integrated: "Cleanup #allClassVarNames" Pull request url: https://github.com/pharo-project/pharo/pull/5203 Issue Url: https://github.com/pharo-project/pharo/issues/ClassVarnamesCleanup Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #1000: Replace-assert-equals-from-non-test-methods
by ci-pharo-ci-jenkins2＠inria.fr Nov. 22, 2019

Nov. 22, 2019

There is a new Pharo build available! The status of the build #1000 was: SUCCESS. The Pull Request #5198 was integrated: "Replace-assert-equals-from-non-test-methods" Pull request url: https://github.com/pharo-project/pharo/pull/5198 Issue Url: https://github.com/pharo-project/pharo/issues/Replace Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

About dashed lines in Athens
by milton mamani Nov. 21, 2019

Nov. 21, 2019

Hi to all I was playing with Athens and I found and error that you can reproduce with the next script in Pharo8x64 macOs ```Smalltalk AthensSurfaceExamples openViewOn: [ :can | can pathTransform restoreAfter: [ can pathTransform translateX: 30 Y: 30. can pathTransform rotateByDegrees: 35. can setPaint: Color red. can setStrokePaint: Color black. can setShape: (-20@ -20 corner: 20@ 20). can draw. ]. ]. AthensSurfaceExamples openViewOn: [ :can | can pathTransform restoreAfter: [ can pathTransform translateX: 30 Y: 30. can pathTransform rotateByDegrees: 35. can setPaint: Color red. (can setStrokePaint: Color black) width: 6; dashes: #(4) offset: 0. can setShape: (-20@ -20 corner: 20@ 20). can draw. ]. ]. AthensSurfaceExamples openViewOn: [ :can | can pathTransform restoreAfter: [ can pathTransform translateX: 30 Y: 30. can pathTransform rotateByDegrees: 35. can setPaint: Color red. can setStrokePaint: Color black. can setShape: (-20@ -20 corner: 20@ 20). can draw. ]. ]. ``` The previous examples opens 3 windows The first the line is normal The second the line is dashed The third one should be normal, but it is dashed Why because there is a cache for the color black in the methods `setStrokePaint:` I think that we need to fix this, Cheers, Milton

1 0

[Pharo 8.0] Build #999: ProtoObject: #mustBeBooleanDeOptimize
by ci-pharo-ci-jenkins2＠inria.fr Nov. 21, 2019

Nov. 21, 2019

There is a new Pharo build available! The status of the build #999 was: FAILURE. The Pull Request #5195 was integrated: "ProtoObject: #mustBeBooleanDeOptimize" Pull request url: https://github.com/pharo-project/pharo/pull/5195 Issue Url: https://github.com/pharo-project/pharo/issues/ProtoObjectmustBeBooleanDeOpt… Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

GildaVM - a Non-Blocking I/O Architecture for the Cog VM
by Ben Coman Nov. 21, 2019

Nov. 21, 2019

I saw an interesting tweet on "GildaVM: a Non-Blocking I/O Architecture for the Cog VM" [1] which shows the VM running multiple interpreter-threads. Where is the paper shown on page 23 available? Side thought, if "usually, 1% of objects survive their first scavenge" [2] as a "breadth-first traversal of objects from the remembered table (a table holding all old objects referencing new objects) and the stack" that implies only a small percentage object mutations were in old space (??) which makes wonder if each interpreter-thread had its "own" new-space, then scavenging each new-space could run independently in parallel-native-threads? Thus a global lock may only(?) be needed to mutate a shared old-space and minimize . This ignores the execution-engine needing to update method-lookup tables. Could native-threads start with their own copy of a warmed up JIT and then work independently? cheers -ben [1] https://www.slideshare.net/esug/gildavm-a-nonblocking-io-architecture-for-t… [2] https://clementbera.wordpress.com/2017/03/12/tuning-the-pharo-garbage-colle…

2 1

[Pharo 8.0] Build #992: 5085-Move-clap-into-BaselineOfBaseLibraries-2
by ci-pharo-ci-jenkins2＠inria.fr Nov. 20, 2019

Nov. 20, 2019

There is a new Pharo build available! The status of the build #992 was: SUCCESS. The Pull Request #5175 was integrated: "5085-Move-clap-into-BaselineOfBaseLibraries-2" Pull request url: https://github.com/pharo-project/pharo/pull/5175 Issue Url: https://github.com/pharo-project/pharo/issues/5085 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #174: Backport - Fix nextVersion for cases where an entry with basename only exists inâ¦
by ci-pharo-ci-jenkins2＠inria.fr Nov. 20, 2019

Nov. 20, 2019

There is a new Pharo build available! The status of the build #174 was: SUCCESS. The Pull Request #5122 was integrated: "Backport - Fix nextVersion for cases where an entry with basename only exists inâ¦" Pull request url: https://github.com/pharo-project/pharo/pull/5122 Issue Url: https://pharo.fogbugz.com/f/cases/fix Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #991: spellCheckAstCore
by ci-pharo-ci-jenkins2＠inria.fr Nov. 20, 2019

Nov. 20, 2019

There is a new Pharo build available! The status of the build #991 was: SUCCESS. The Pull Request #5176 was integrated: "spellCheckAstCore" Pull request url: https://github.com/pharo-project/pharo/pull/5176 Issue Url: https://github.com/pharo-project/pharo/issues/spellCheckAstCore Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #990: Replace-assert-equals-from-Morphic
by ci-pharo-ci-jenkins2＠inria.fr Nov. 19, 2019

Nov. 19, 2019

There is a new Pharo build available! The status of the build #990 was: SUCCESS. The Pull Request #5171 was integrated: "Replace-assert-equals-from-Morphic" Pull request url: https://github.com/pharo-project/pharo/pull/5171 Issue Url: https://github.com/pharo-project/pharo/issues/Replace Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #989: Replace-assert-equals-from-packages-starting-with-J-and-K
by ci-pharo-ci-jenkins2＠inria.fr Nov. 19, 2019

Nov. 19, 2019

There is a new Pharo build available! The status of the build #989 was: SUCCESS. The Pull Request #5170 was integrated: "Replace-assert-equals-from-packages-starting-with-J-and-K" Pull request url: https://github.com/pharo-project/pharo/pull/5170 Issue Url: https://github.com/pharo-project/pharo/issues/Replace Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0