- Pharo-users - lists.pharo.org

Re: Is there an easy way to cherry pick methods from another branch in iceberg?

by Tim Mackinnon

Hi Guille - thanks for Chipping in on this - I have bookmarked the revert commands you have mentioned and see if that works better for me (rather than flailing around and making a mess of it). Possibly this scenario is one that could get its own menu option in the future - its a quite a common thing to want to just get bak to a safe point. For the cherry picking - I have raised an Issue (in Iceberg?) - https://github.com/pharo-vcs/iceberg/issues/1519 Tim > On 28 Jun 2021, at 13:12, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > Hi Tim, > >> El 22 jun 2021, a las 1:39, Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>> escribiÃ³: >> >> Hi guys - while I mostly get along with Iceberg and can do common stuff - there are still a few things that I'm not sure on the best way to work. >> >> A recent one, was that I created a branch for an experiment - decided not to use and then went back to master to try again. However if I want to cherry pick code (particularly a few methods) - is there nothing I can use to do this easily? I can browse the branch in the repo explorer and see diffs of methods to master - but why can't I load any of those methods (or am I missing something obvious here?) > > This seems to be a feature that was not migrated in the iceberg-to-spec2 migration. > Would you mind opening an issue? > >> >> The other item that still confuses me today - how can I easily revert back to previous point in time, essentially undo work I've commited and possible pushed to my git repo. I also struggle with this one - end up with a detached head and flail around. I don't understand why this is so hard to do - and can only think its because everything is based on graphs of graphs and so there is the potential that going back in time can break this? Anyway - what is the foolproof way to go back to the older point, and then start coding so that this becomes the new Head? > > There are two different questions in here. > > - How can you go back to some older commit? > > In iceberg this is done by creating a new branch from the commit youâre interested in. The âBranchâ¦â menu will open a pop-up to allow you creating a new branch from that point in time. > Then you can checkout that branch and work as with any other branch. > > <PastedGraphic-5.png> > > > - How can you undo some history (that was even pushed)? > > Iceberg does not support this scenario yet, as it could be very problematic when working in teams. > Undoing some history / removing some commit will produce undesired effects on people that had pulled that commit. > This is one of the scenarios that in git requires a `âforce` flag. > > If you want to do such a thing, you need for now to do it from the command line > > ```sh > $ git reset âhard THE_COMMIT_ID_YOU_WANT_TO_GO_BACK_TO > $ git push -f > ``` > > And then checkout the branch back from iceberg (which will show a detached working copy â see https://books.pharo.org/booklet-ManageCode/pdf/2020-05-12-ManageCode.pdf <https://books.pharo.org/booklet-ManageCode/pdf/2020-05-12-ManageCode.pdf>). > > G > >> >> Pointers on these two items greatly appreciate for my road to vcs greatness (and gosh I mess Envy - as I haven't asked about showing me deleted "available methods" and "classes") >> >> Tim >

June 29, 2021

Re: Communication between different images

by Sven Van Caekenberghe

Hi Esteban, > On 29 Jun 2021, at 04:55, Esteban Maringolo <emaringolo(a)gmail.com> wrote: > > Hi, > > I'm rearchitecting a web app to perform updates only when necessary > (instead of computing them all the time) on each request, I can have a > global announcer and subscribers to know when to update within an > image, but is there a way to have something like that but for > inter-image coordination? > > I'd only need to communicate the id and the class name (or a similar > identifier), so on other images they'll update accordingly, and if > there is an update in one image, it will notify the other images. The > common data is on the database, so this is just to avoid re-reading a > lot of things. > > Is a message queue a good fit for this? Pub/Sub? > What is available in Pharo that works without having to set up a lot of things? > > Thanks! > > Esteban A. Maringolo RabbitMQ (for which there is the STOMP client 'STAMP' https://github.com/svenvc/stamp) is one option, but it is a bit more complex. I guess Redis would work too (https://medium.com/concerning-pharo/quick-write-me-a-redis-client-5fbe4ddfb…) More recently I have been using MQTT (with the client https://github.com/svenvc/mqtt) which is much simpler. You post a message on a topic and have one or more listeners see it. You can even arrange for the broker to keep the messages you miss (within a reasonable window) - which is very nice for all kinds of reasons (especially operational). I have a system in production that uses this mechanism to coordinate different images (and handle ingress of data) for more than a year now. Sven

June 29, 2021

Communication between different images

by Esteban Maringolo

Hi, I'm rearchitecting a web app to perform updates only when necessary (instead of computing them all the time) on each request, I can have a global announcer and subscribers to know when to update within an image, but is there a way to have something like that but for inter-image coordination? I'd only need to communicate the id and the class name (or a similar identifier), so on other images they'll update accordingly, and if there is an update in one image, it will notify the other images. The common data is on the database, so this is just to avoid re-reading a lot of things. Is a message queue a good fit for this? Pub/Sub? What is available in Pharo that works without having to set up a lot of things? Thanks! Esteban A. Maringolo

June 29, 2021

Re: Is there an easy way to cherry pick methods from another branch in iceberg?

by Guillermo Polito

Hi Tim, > El 22 jun 2021, a las 1:39, Tim Mackinnon <tim(a)testit.works> escribiÃ³: > > Hi guys - while I mostly get along with Iceberg and can do common stuff - there are still a few things that I'm not sure on the best way to work. > > A recent one, was that I created a branch for an experiment - decided not to use and then went back to master to try again. However if I want to cherry pick code (particularly a few methods) - is there nothing I can use to do this easily? I can browse the branch in the repo explorer and see diffs of methods to master - but why can't I load any of those methods (or am I missing something obvious here?) This seems to be a feature that was not migrated in the iceberg-to-spec2 migration. Would you mind opening an issue? > > The other item that still confuses me today - how can I easily revert back to previous point in time, essentially undo work I've commited and possible pushed to my git repo. I also struggle with this one - end up with a detached head and flail around. I don't understand why this is so hard to do - and can only think its because everything is based on graphs of graphs and so there is the potential that going back in time can break this? Anyway - what is the foolproof way to go back to the older point, and then start coding so that this becomes the new Head? There are two different questions in here. - How can you go back to some older commit? In iceberg this is done by creating a new branch from the commit youâre interested in. The âBranchâ¦â menu will open a pop-up to allow you creating a new branch from that point in time. Then you can checkout that branch and work as with any other branch. - How can you undo some history (that was even pushed)? Iceberg does not support this scenario yet, as it could be very problematic when working in teams. Undoing some history / removing some commit will produce undesired effects on people that had pulled that commit. This is one of the scenarios that in git requires a `âforce` flag. If you want to do such a thing, you need for now to do it from the command line ```sh $ git reset âhard THE_COMMIT_ID_YOU_WANT_TO_GO_BACK_TO $ git push -f ``` And then checkout the branch back from iceberg (which will show a detached working copy â see https://books.pharo.org/booklet-ManageCode/pdf/2020-05-12-ManageCode.pdf) G > > Pointers on these two items greatly appreciate for my road to vcs greatness (and gosh I mess Envy - as I haven't asked about showing me deleted "available methods" and "classes") > > Tim

June 28, 2021

Re: Is there an easy way to cherry pick methods from another branch in iceberg?

by Clint Moore

+1 person who would like to know this so I don't have to do it from a terminal. On Sat, Jun 26, 2021 at 11:18 AM Tim Mackinnon <tim(a)testit.works> wrote: > > Just nudging this one - as Iâd like to improve my Iceberg foo - and cherry picking methods and reverting are things Iâd like to learn how to do better? > > > On 22 Jun 2021, at 00:39, Tim Mackinnon <tim(a)testit.works> wrote: > > > > Hi guys - while I mostly get along with Iceberg and can do common stuff - there are still a few things that I'm not sure on the best way to work. > > > > A recent one, was that I created a branch for an experiment - decided not to use and then went back to master to try again. However if I want to cherry pick code (particularly a few methods) - is there nothing I can use to do this easily? I can browse the branch in the repo explorer and see diffs of methods to master - but why can't I load any of those methods (or am I missing something obvious here?) > > > > The other item that still confuses me today - how can I easily revert back to previous point in time, essentially undo work I've commited and possible pushed to my git repo. I also struggle with this one - end up with a detached head and flail around. I don't understand why this is so hard to do - and can only think its because everything is based on graphs of graphs and so there is the potential that going back in time can break this? Anyway - what is the foolproof way to go back to the older point, and then start coding so that this becomes the new Head? > > > > Pointers on these two items greatly appreciate for my road to vcs greatness (and gosh I mess Envy - as I haven't asked about showing me deleted "available methods" and "classes") > > > > Tim

June 27, 2021

Re: Is there an easy way to cherry pick methods from another branch in iceberg?

by Tim Mackinnon

Just nudging this one - as Iâd like to improve my Iceberg foo - and cherry picking methods and reverting are things Iâd like to learn how to do better? > On 22 Jun 2021, at 00:39, Tim Mackinnon <tim(a)testit.works> wrote: > > Hi guys - while I mostly get along with Iceberg and can do common stuff - there are still a few things that I'm not sure on the best way to work. > > A recent one, was that I created a branch for an experiment - decided not to use and then went back to master to try again. However if I want to cherry pick code (particularly a few methods) - is there nothing I can use to do this easily? I can browse the branch in the repo explorer and see diffs of methods to master - but why can't I load any of those methods (or am I missing something obvious here?) > > The other item that still confuses me today - how can I easily revert back to previous point in time, essentially undo work I've commited and possible pushed to my git repo. I also struggle with this one - end up with a detached head and flail around. I don't understand why this is so hard to do - and can only think its because everything is based on graphs of graphs and so there is the potential that going back in time can break this? Anyway - what is the foolproof way to go back to the older point, and then start coding so that this becomes the new Head? > > Pointers on these two items greatly appreciate for my road to vcs greatness (and gosh I mess Envy - as I haven't asked about showing me deleted "available methods" and "classes") > > Tim

June 26, 2021

Fwd: [vwnc] Exception in Regex11 1.4.6

by Steffen MÃ¤rcker

Hi! Does Pharo use the Regex11 package? If yes, has it already diverged from the version shipped with VisualWorks? The reason I am asking is that I just pushed an update to the public store. It addresses a bug that prevented $[ to be used in a character class. For details, see the excerpt below. Furthermore, you might have an opinion on allowing more escape sequences in character classes, don't you? Kind regards, Steffen ----- Weitergeleitete Nachricht ----- Von: Steffen MÃ¤rcker <merkste(a)web.de> An: 'VWNC' <vwnc(a)cs.uiuc.edu> Betreff: Re: [vwnc] Exception in Regex11 1.4.6 Datum: Thu Jun 24 2021 18:47:01 GMT+0200 (MitteleuropÃ¤ische Sommerzeit) Hi! I just published Regex11 version 1.4.7 with the following changes: 1. Fix: Character sets could not contain an opening bracket $[. 2. Fix: Character sets could not contain the characters '[:', e.g. as in '[[:something]' asRegex. I also provided additional tests for the improved functionality. I might tidy the code a bit later in a minor version bump. Just to note that Regex11 uses [[:xxx:]] as a special syntax, which might interfere with attempts to allow [[] and []]. Indeed. If I did no mistake, the new version does not break this. I agree with the idea to allow backslash escaping in character classes too, with the default being that backslash followed by any character is parsed as that character. I also like the idea of allowing more backslash escaping in character classes. However, I still have the bad feeling that this might change the semantics of existing code. Hence, I refrained from implementing this right away until I am more confident that this does not break other peoples stuff. Currently only a few explicitly defined backslash escapes are recognized, forcing the user to remember whether a given character can be used as-is in a given context, or must be escaped. A couple of gotchas (probably not applicable in a character set?): \< an empty string at the beginning of a word \> an empty string at the end of a word Thanks, I'll keep them in mind and consider them when I decide to implement the changes. OT: I also noticed that repetition, e.g. '.{5}' behaves strange. For instance, '.{{5}}' should match 'a{{{{{}' but it doesn't. Has anyone an opinion on that one? Best regards, Steffen -- Gesendet mit Vivaldi Mail. Laden Sie Vivaldi kostenlos von vivaldi.com herunter.

June 24, 2021

[ANN] Pharo Consortium New Academic Member: DGtal Aqua Lab

by Marcus Denker

The Pharo Consortium is very happy to announce that the DGtal Aqua Lab has joined the Consortium as an Academic Member. About ===== - DGtal Aqua Lab: https://wwp.shizuoka.ac.jp/dgtalaqualab/ - MOBYDIC: https://wwp.shizuoka.ac.jp/dgtalaqualab/mobydic/ - Pharo Consortium: http://consortium.pharo.org The goal of the Pharo Consortium is to allow companies and institutions to support the ongoing development and future of Pharo. Individuals can support Pharo via the Pharo Association: http://association.pharo.org/

June 24, 2021

UK Smalltalk User Group meeting - Wednesday June 30th

by Giovanni Corriga

The next meeting of the UK Smalltalk User Group will be on Wednesday, June 30th. Hernan Wilkinson ( https://twitter.com/HernanWilkinson ) will talk about his LiveTyping project. Currently, almost all mainstream dynamically typed languages support type annotation a la Strongtalk. Python calls it "type hints", TypeScript is JavaScript+type annotations, PHP calls it "type declarations" and Ruby does it through a tool called Sorbet. All of them annotate the types in the source code and it is the programmer who must write and maintain the annotation. In all cases, it is not mandatory for the system to correctly type check for it to run. LiveTyping ( https://github.com/hernanwilkinson/LiveTyping ) is a type system proposal for Smalltalk, that seeks similar objectives but implemented in a different way. First, it is the environment itself that collects and maintains the types based on the execution of the system, not the programmer. Second, the types are not interleaved in the source code, thus maintaining the syntax and simplicity of the language. And finally, the main objective is not to carry out a static type checking (although it supports it), but to augment the programmers experience increasing the usability of current tools such as searching for senders and implementers, and performing more accurate and safe refactorings. In this talk Hernan will briefly show how LiveTyping is implemented to later concentrate on the improvements made to the tools and the benefits it brings when developing software with Smalltalk. LiveTyping is currently implemented in Cuis Smalltalk ( https://cuis-smalltalk.org/ ) and has been successfully used for the last two years in three different universities in Argentina when teaching Object Oriented Programming and Design. Given the current COVID-19 restrictions, this will be an online meeting from home. If you'd like to join us, please sign up in advance on the meeting's Meetup page ( https://www.meetup.com/UKSTUG/events/cbklbryccjbfc/ ) to receive the meeting details. Donât forget to bring your laptop and drinks!

June 23, 2021

Is there an easy way to cherry pick methods from another branch in iceberg?

by Tim Mackinnon

Hi guys - while I mostly get along with Iceberg and can do common stuff - there are still a few things that I'm not sure on the best way to work. A recent one, was that I created a branch for an experiment - decided not to use and then went back to master to try again. However if I want to cherry pick code (particularly a few methods) - is there nothing I can use to do this easily? I can browse the branch in the repo explorer and see diffs of methods to master - but why can't I load any of those methods (or am I missing something obvious here?) The other item that still confuses me today - how can I easily revert back to previous point in time, essentially undo work I've commited and possible pushed to my git repo. I also struggle with this one - end up with a detached head and flail around. I don't understand why this is so hard to do - and can only think its because everything is based on graphs of graphs and so there is the potential that going back in time can break this? Anyway - what is the foolproof way to go back to the older point, and then start coding so that this becomes the new Head? Pointers on these two items greatly appreciate for my road to vcs greatness (and gosh I mess Envy - as I haven't asked about showing me deleted "available methods" and "classes") Tim

June 21, 2021