- Pharo-dev - lists.pharo.org

What, exactly, does `#=` mean?

by sean＠clipperadams.com

Anyone know of a book that goes in depth explaining \`#=\`? I've always wondered what "equal" is supposed to mean. For example, if I have two objects representing the same person, but one has their webpage cached as state, they represent the same entity, and are interchangeable in many contexts, but also have a difference that may be important in other contexts. Is âequalâ whatever you say it is in your domain, or is it a Smalltalk object system concept? If the latter, what is the exact expectation?

Aug. 23, 2022

Re: about object serialization and deserialization

by CÃ©drick BÃ©ler

Maybe a bit off topic, I found preserves from Tony Garnock-Jones who btw managed to run squeak on smartphone ;) * Preserves is a new data model and serialization format in many ways comparable to JSON, XML, S-expressions, CBOR, ASN.1 BER, and so on. https://preserves.dev/ https://git.syndicate-lang.org/tonyg/squeak-phone https://eighty-twenty.org/tag/squeak-phone/ Happy ESUG for those in Navi Sad, Cedrick > Le 16 aoÃ»t 2022 Ã 12:11, Sven Van Caekenberghe <sven(a)stfx.eu> a Ã©crit : > > ï»¿Hi Stef, > >> On 15 Aug 2022, at 20:25, stephane ducasse <stephane.ducasse(a)inria.fr> wrote: >> >> Hi guys >> >> It is interesting to think about the design and use of object deserializers. >> >> https://www.slideshare.net/frohoff1/deserialize-my-shorts-or-how-i-learned-… >> >> <2204.09388.pdf> > > Interesting, and indeed, a big problem (especially denial of service attacks). > > Step one is to be conscious of the problem (which exists across all language/formats). > > Step two could be to add some sanity checks (limits) to parsers. > > Would be a nice subject for a (student) project. > > Sven

Aug. 21, 2022

Re: Status update of Libgit2 and CI issues

by HernÃ¡n Morales Durand

Thank you for the update. I followed the thread and I imagine it was not easy to work on this problem. Best regards, HernÃ¡n El vie, 19 ago 2022 a las 16:45, Guillermo Polito (< guillermopolito(a)gmail.com>) escribiÃ³: > A couple of weeks ago we got reported a big recurrent failure on CI jobs > while cloning using iceberg/libgit > https://github.com/pharo-project/pharo/issues/11481. > > TL;DR; So far (Friday ~17h Paris time) we managed to get everything up and > running. A new VM is being released by our CI, all pull requests are issued > and we should have everything integrated by tonight. > > =-=-=-=-=-=-=-= > > More on the situation: Errors happened randomly with > > ``` > error reading from the zlib stream > ``` > > or > ``` > bad packet length > ``` > > Several people helped in getting a reliable script to reproduce the issue, > plus some instructions to produce a reproduction environment using a docker > container. With that in our hands, we managed to corner the issue to a new > incompatibility between old libgit2 versions, ssh2, OpenSSL, and (at least) > Github. > > After testing some configurations, we decided to upgrade the libgit and > related binaries to newer versions: > - libgit 1.4.4 > - libssh 1.9.0 > - OpenSSL 1.1.1k > > This was of course not as straightforward as we would have liked. > Libgit2 1.4.4 was not compatible with its older versions and broke our ffi > bindings. > We needed to provide new VM binaries for all our major platforms, make a > new VM release, upgrade the libgit2 bindings, and make releases of the > libgit2 bindings, iceberg, and backport to Pharo 10 and Pharo 9. > > TL;DR; So far (Friday ~17h Paris time) we managed to get everything up and > running. A new VM is being released by our CI, all pull requests are issued > and we should have everything integrated by tonight. > > Libgit+related compilation instructions are updated in the VM wiki > > https://github.com/pharo-project/pharo-vm/wiki/Building-OSX-ARM64-Third-Par… > > https://github.com/pharo-project/pharo-vm/wiki/Building-OSX-X86_64-Third-Pa… > > https://github.com/pharo-project/pharo-vm/wiki/Building-Linux-ARM64-Third-P… > > https://github.com/pharo-project/pharo-vm/wiki/Building-Linux-ARM32-Third-P… > > Libgit bindings Upgrade > changes: > https://github.com/pharo-vcs/libgit2-pharo-bindings/commit/0e0100f7d0f3a11c… > release: > https://github.com/pharo-vcs/libgit2-pharo-bindings/releases/tag/v2.2.6 > > Iceberg Upgrade > pr: https://github.com/pharo-vcs/iceberg/pull/1605 > release: https://github.com/pharo-vcs/iceberg/releases/tag/v2.0.7 > > Upgrading library dependencies in the VM > https://github.com/pharo-project/pharo-vm/pull/447 > Release VM 9.0.16 > https://github.com/pharo-project/pharo-vm/releases/tag/v9.0.16 > > Backports to Pharo > Pharo10 https://github.com/pharo-project/pharo/pull/11545 > Pharo9 https://github.com/pharo-project/pharo/pull/11546 > > We have left for later to upgrade library dependencies for the Windows VM > (x86-64, ARM64). > Of course, any help in this direction is welcome. > > Cheers, > G in behalf of the team

Aug. 19, 2022

Re: Status update of Libgit2 and CI issues

by Gabriel Cotelli

Thank you for the update. Once the new VM and image versions are built by the CI I will update also the ba-st docker Pharo images, so they start working flawlessly again. On Fri, Aug 19, 2022 at 11:45 AM Guillermo Polito <guillermopolito(a)gmail.com> wrote: > A couple of weeks ago we got reported a big recurrent failure on CI jobs > while cloning using iceberg/libgit > https://github.com/pharo-project/pharo/issues/11481. > > TL;DR; So far (Friday ~17h Paris time) we managed to get everything up and > running. A new VM is being released by our CI, all pull requests are issued > and we should have everything integrated by tonight. > > =-=-=-=-=-=-=-= > > More on the situation: Errors happened randomly with > > ``` > error reading from the zlib stream > ``` > > or > ``` > bad packet length > ``` > > Several people helped in getting a reliable script to reproduce the issue, > plus some instructions to produce a reproduction environment using a docker > container. With that in our hands, we managed to corner the issue to a new > incompatibility between old libgit2 versions, ssh2, OpenSSL, and (at least) > Github. > > After testing some configurations, we decided to upgrade the libgit and > related binaries to newer versions: > - libgit 1.4.4 > - libssh 1.9.0 > - OpenSSL 1.1.1k > > This was of course not as straightforward as we would have liked. > Libgit2 1.4.4 was not compatible with its older versions and broke our ffi > bindings. > We needed to provide new VM binaries for all our major platforms, make a > new VM release, upgrade the libgit2 bindings, and make releases of the > libgit2 bindings, iceberg, and backport to Pharo 10 and Pharo 9. > > TL;DR; So far (Friday ~17h Paris time) we managed to get everything up and > running. A new VM is being released by our CI, all pull requests are issued > and we should have everything integrated by tonight. > > Libgit+related compilation instructions are updated in the VM wiki > > https://github.com/pharo-project/pharo-vm/wiki/Building-OSX-ARM64-Third-Par… > > https://github.com/pharo-project/pharo-vm/wiki/Building-OSX-X86_64-Third-Pa… > > https://github.com/pharo-project/pharo-vm/wiki/Building-Linux-ARM64-Third-P… > > https://github.com/pharo-project/pharo-vm/wiki/Building-Linux-ARM32-Third-P… > > Libgit bindings Upgrade > changes: > https://github.com/pharo-vcs/libgit2-pharo-bindings/commit/0e0100f7d0f3a11c… > release: > https://github.com/pharo-vcs/libgit2-pharo-bindings/releases/tag/v2.2.6 > > Iceberg Upgrade > pr: https://github.com/pharo-vcs/iceberg/pull/1605 > release: https://github.com/pharo-vcs/iceberg/releases/tag/v2.0.7 > > Upgrading library dependencies in the VM > https://github.com/pharo-project/pharo-vm/pull/447 > Release VM 9.0.16 > https://github.com/pharo-project/pharo-vm/releases/tag/v9.0.16 > > Backports to Pharo > Pharo10 https://github.com/pharo-project/pharo/pull/11545 > Pharo9 https://github.com/pharo-project/pharo/pull/11546 > > We have left for later to upgrade library dependencies for the Windows VM > (x86-64, ARM64). > Of course, any help in this direction is welcome. > > Cheers, > G in behalf of the team

Aug. 19, 2022

Status update of Libgit2 and CI issues

by Guillermo Polito

A couple of weeks ago we got reported a big recurrent failure on CI jobs while cloning using iceberg/libgit https://github.com/pharo-project/pharo/issues/11481. TL;DR; So far (Friday ~17h Paris time) we managed to get everything up and running. A new VM is being released by our CI, all pull requests are issued and we should have everything integrated by tonight. =-=-=-=-=-=-=-= More on the situation: Errors happened randomly with ``` error reading from the zlib stream ``` or ``` bad packet length ``` Several people helped in getting a reliable script to reproduce the issue, plus some instructions to produce a reproduction environment using a docker container. With that in our hands, we managed to corner the issue to a new incompatibility between old libgit2 versions, ssh2, OpenSSL, and (at least) Github. After testing some configurations, we decided to upgrade the libgit and related binaries to newer versions: - libgit 1.4.4 - libssh 1.9.0 - OpenSSL 1.1.1k This was of course not as straightforward as we would have liked. Libgit2 1.4.4 was not compatible with its older versions and broke our ffi bindings. We needed to provide new VM binaries for all our major platforms, make a new VM release, upgrade the libgit2 bindings, and make releases of the libgit2 bindings, iceberg, and backport to Pharo 10 and Pharo 9. TL;DR; So far (Friday ~17h Paris time) we managed to get everything up and running. A new VM is being released by our CI, all pull requests are issued and we should have everything integrated by tonight. Libgit+related compilation instructions are updated in the VM wiki https://github.com/pharo-project/pharo-vm/wiki/Building-OSX-ARM64-Third-Par… https://github.com/pharo-project/pharo-vm/wiki/Building-OSX-X86_64-Third-Pa… https://github.com/pharo-project/pharo-vm/wiki/Building-Linux-ARM64-Third-P… https://github.com/pharo-project/pharo-vm/wiki/Building-Linux-ARM32-Third-P… Libgit bindings Upgrade changes: https://github.com/pharo-vcs/libgit2-pharo-bindings/commit/0e0100f7d0f3a11c… release: https://github.com/pharo-vcs/libgit2-pharo-bindings/releases/tag/v2.2.6 Iceberg Upgrade pr: https://github.com/pharo-vcs/iceberg/pull/1605 release: https://github.com/pharo-vcs/iceberg/releases/tag/v2.0.7 Upgrading library dependencies in the VM https://github.com/pharo-project/pharo-vm/pull/447 Release VM 9.0.16 https://github.com/pharo-project/pharo-vm/releases/tag/v9.0.16 Backports to Pharo Pharo10 https://github.com/pharo-project/pharo/pull/11545 Pharo9 https://github.com/pharo-project/pharo/pull/11546 We have left for later to upgrade library dependencies for the Windows VM (x86-64, ARM64). Of course, any help in this direction is welcome. Cheers, G in behalf of the team

Aug. 19, 2022

This week (33/2022) on the Pharo Issue Tracker

by Marcus Denker

We merged 13 PRs this week: Features ======== - SIMD bytecode support https://github.com/pharo-project/pharo/pull/11516 Fixes ===== - Fix senders/implementors of class variables and shared pools https://github.com/pharo-project/pharo/pull/11490 - Clean version of PR 11498: DrTests: Rerunning test https://github.com/pharo-project/pharo/pull/11510 - 11533-Ring-RGMethodDefinitionisDoIt-missing https://github.com/pharo-project/pharo/pull/11535 - Fix #11540: Selecting a string and pressing Implementors breaks in Calypso New Class pane https://github.com/pharo-project/pharo/pull/11542 - Fix isScripting for block contexts from DoIts https://github.com/pharo-spec/Spec/pull/1297 https://github.com/pharo-spec/NewTools/pull/401 - remove-broken-Fuel-inspector https://github.com/pharo-spec/NewTools/pull/397 - fix closing Spotter by Esc https://github.com/pharo-spec/NewTools/pull/410 Cleanup ======= - Delete .bintray.json https://github.com/pharo-project/pharo/pull/11522 - Fixes: #11514 Removing Refactoring Help package https://github.com/pharo-project/pharo/pull/11521 - Fix spurious creation of stream https://github.com/pharo-project/pharo/pull/11531 Pharo10 ======= - Backport visitWindowExposeEvent to redraw when windows are re-exposed https://github.com/pharo-project/pharo/pull/11484

Aug. 19, 2022

Weeks (30/31/32 ) on the Pharo Issue Tracker

by Marcus Denker

Holiday period, but we merged 15 PRs the last three weeks. Fixes ===== - fix the top and bottom of the rectangle of text input region so that â¦ #11474 https://github.com/pharo-project/pharo/pull/11474 - Fixes: #11342 added some tests to cover to methods that were not called. #11349 https://github.com/pharo-project/pharo/pull/11349 - 10774-FTP-clientgetDataInto-lost-returned-information #11466 https://github.com/pharo-project/pharo/pull/11466 - Improve protocol suggestions when creating method from debugger #11486 https://github.com/pharo-project/pharo/pull/11486 - Fix DoIt highlighting and debugIt in ProcessBrowser #11473 https://github.com/pharo-project/pharo/pull/11473 Test Runner =========== - Fix issue #11496: Executable comments checker of DrTests https://github.com/pharo-project/pharo/pull/11497 - Fixing issue #9545: DrTests should show 'expected failures' and 'passed unexpectedly' #11495 https://github.com/pharo-project/pharo/pull/11495 - NewTestRunner, NewCommandLineRunner #11469 https://github.com/pharo-project/pharo/pull/11469 - CoverageRunner deleted #11504 https://github.com/pharo-project/pharo/pull/11504 Features ======== - CloseAllWindows #11408 https://github.com/pharo-project/pharo/pull/11408 Cleanup ======= - [cleanup] naming consistency of bytecodeS #11488 https://github.com/pharo-project/pharo/pull/11488 - [improvement] add deprecation + transform to bytecode -> bytecodes #11502 https://github.com/pharo-project/pharo/pull/11502 - [cleanup] remove empty test classes #11508 https://github.com/pharo-project/pharo/pull/11508 - Adding comments to SUnit classes #11478 https://github.com/pharo-project/pharo/pull/11478

Aug. 17, 2022

Re: Inovation Technology Award Submission: Polyphemus

by Noury Bouraqadi

Thank you Pierre for the submission :-) Noury On Aug 16 2022, at 10:36 am, pmissech <pierre.misse-chanabier(a)inria.fr> wrote: > Hello, > > Although i will not be able to attend ESUG'22, a friend agreed to > present one of our projects to the innovation award. > **Polyphemus** is a VM related, but public aims at any kind of developers. > Particularly, the video submission talks about how to look at an image > and how to **recover** dead images. > Feel free to contact me if you have any questions ! > Enjoy (and vote for Polyphemus!). > > 5 minutes video, Innovation Technology Award submission: > https://youtu.be/zf3cCtNW830 > Repository: github.com/hogoww/Polyphemus/ > Additionnal information on image recovery: > https://github.com/hogoww/Polyphemus/blob/main/Documentation/ResurrectingDe… > > Cheers !

Aug. 16, 2022

Re: Pharo's syntax highlighter

by Marcus Denker

> On 6 Aug 2022, at 07:26, Pierre Misse Chanabier <pierre.misse-chanabier(a)inria.fr> wrote: > > I do not know the syntax highlighter, but I know the AST fairly well. > The first two points are fairly easy: > > Color method temp variables and block parameter variables differently. Currently they are identified too generally as just #variables. They are therefore always the same color. Can someone point me to the parser classes that extract these features? > > Color differently Classes and other globals? I'm trying to find this distinction as well in the parser classes. If someone familiar with the parsing and related GUI classes can give me some pointers, I'll do the work. > > Let the user assign colors to the first 7 levels of parentheses and first 7 levels of brackets. > > > 1) There is no differences in the AST about temporary / arguments declaration. > They are both at the level of the sequence node of the method/block (the body). > Thankfully we can ask for the parent and have a case for each. > You'd have to modify visitTemporaryDeclarationNode:. > > 2) There is no difference in the AST between classes / Globals. > Because Classes are in fact Globals. > You'd have to ask for the (self class environment classAt: aGlobal name) ifNotNil: [ class behavior ] ifNil: [ global behavior ]. > This is true, but kid of not: the AST does not distinguish kind of variables, as this is not Grammar but âSemanticsâ. That is, every variables use (definition, read, write) just gets one (new) instance of RBVariableNode. But: we do name analysis for the AST. This means that the AST that you have in hand is always annotated with semantic information. For Variables this means that every RBVariableNode instance has a âsemantic variableâ attached to it that models the Variable. (See Hierarchy of the class âVariableâ). Here now we get what we expect: for e.g. a temp there is *one* instance or a temp variable, and all the instances of RBVariableNode that are about that variable reference the one instance. With this, we can actually distinguish all the kinds of variables. (we pushed this so far that actually the compiler just asks the variable to generate bytecode, for example). For ease of use, we have added test methods to RBVariableNode lile isTempVariable, isClassVariable, isInstanceVariable and so on. > A quick look seem that the behavior of the syntax highlighter is in the IconStyler class. > (again, don't know it, just checking this out quickly). The main part of the syntax highlighter is class SHRBTextStyler. This is âjustâ a visitor on the AST (by including the trait TRBProgramNodeVisitor). For example, the method called via the #visitVariableNode: method is this: resolveStyleFor: aVariableNode aVariableNode binding ifNil: [^#default]. aVariableNode isArgumentVariable ifTrue: [ ^#methodArg]. aVariableNode isTempVariable ifTrue: [ ^#tempVar]. aVariableNode isGlobalVariable ifTrue: [ ^#globalVar]. "here we should add support for #classVar" aVariableNode isClassVariable ifTrue: [ ^#globalVar]. aVariableNode isInstanceVariable ifTrue: [ ^#instVar]. "for now we use temp variable here, we could now color them with their own color" aVariableNode isWorkspaceVariable ifTrue: [ ^#tempVar]. (self class formatIncompleteIdentifiers and: [ aVariableNode hasIncompleteIdentifier ]) ifTrue:[ ^#incompleteIdentifier] . "Note: if formatIncompleteIdentifiers is true, a non-exisiting variable might be incomplete" aVariableNode isUndeclaredVariable ifTrue: [ ^#undefinedIdentifier ]. ^#invalid. This shows that we, right now, do not distinguish globals from class variables, but all that would be very easy to add, as the annotated AST has all that information. (I always wanted to rewrite that method to just delegate to the aVariableNode and from there delatete to the Variable subclass and add a #styleSymbol method there, would make all that even simpler). Marcus

Aug. 16, 2022

Re: about object serialization and deserialization

by Sven Van Caekenberghe

Hi Stef, > On 15 Aug 2022, at 20:25, stephane ducasse <stephane.ducasse(a)inria.fr> wrote: > > Hi guys > > It is interesting to think about the design and use of object deserializers. > > https://www.slideshare.net/frohoff1/deserialize-my-shorts-or-how-i-learned-… > > <2204.09388.pdf> Interesting, and indeed, a big problem (especially denial of service attacks). Step one is to be conscious of the problem (which exists across all language/formats). Step two could be to add some sanity checks (limits) to parsers. Would be a nice subject for a (student) project. Sven

Aug. 16, 2022