June 2021 - Pharo-users - lists.pharo.org

Re: Communication between different images

by Sven Van Caekenberghe

> On 29 Jun 2021, at 15:50, Esteban Maringolo <emaringolo(a)gmail.com> wrote: > > Hi Sven, > > I thought about both RabittMQ and MQTT too. > > For RabittMQ I noticed you provide a docker config to get a container > running quickly. That was done for GitHub action testing, by Santiago, you could indeed (re)use part of that. > What is the easy-go solution for MQTT? Installing mosquitto is very simple, just apt install. See also the GitHub action. There is much to say about both, you can find lots of information on the internet on how to configure these services, getting started is quite easy. > Regards! > > Esteban A. Maringolo > > On Tue, Jun 29, 2021 at 3:15 AM Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> 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

Re: Communication between different images

by Esteban Maringolo

Hi Sven, I thought about both RabittMQ and MQTT too. For RabittMQ I noticed you provide a docker config to get a container running quickly. What is the easy-go solution for MQTT? Regards! Esteban A. Maringolo On Tue, Jun 29, 2021 at 3:15 AM Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > 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

SerialPort hangs image in combination with Raspberry Pico (Windows)

by Rob van Lopik

I have the following strange situation, where SerialPort>>nextPutAll: hangs when sending to a COM port that is (USB) connected to a Raspberry Pico (RP2040). The Pico contains a simple program (sketch) that echoes all input on it USB-serial port. This is written with the Arduino IDE. The echo function works OK with the Arduino Serial monitor, PuTTY and a simple Python progran. When I put the same echo program on another Arduino board (e.g. Uno or Adafruit Feather) Pharo's SerialPort does work fine. I have tested with 32 and 64 bits versions of Pharo 5, 7 and 8. All on Windows; on Raspbian there is no problem. So, there is something peculiar with the combination of the SerialPlugin and the USBserial implementation on the Pico (which uses TinyUSB), but I am at a loss as to where to search. Maybe somebody has a hint. I have seen problems with the Serial Plugin in the past. I ran into this when developing a driver for the Raspberry Pico, where the Pico runs the picod daemon (http://abyz.me.uk/picod/index.html) This code is in https://github.com/robvanlopik/picod-pharo and does not work on Windows. Rob van Lopik

June 29, 2021

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