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

Re: Pharo-SQLite3: closing connections immediately and deleting the database file

by vinref＠gmail.com

Hi I double-check changes to the db by running the SQLite3 client in a terminal. The memory db is only accessible by the same client/session so it wonât work. I also run multiple processes doing different things in the same image so each process needs its own connection/handle to SQLite3 so that wont work either. I am using DROP TABLE IF NOT EXISTS to drop all tables before the main schema and it works perfectly. But I did think of using a SQLite3 memory db to hold session info - i.e, cookies. Or I could just use a Dictionary. I havenât implemented this yet but does anyone have any thoughts? Vince

Aug. 13, 2021

Re: Pharo-SQLite3: closing connections immediately and deleting the database file

by JuliÃ¡n Maestri

As far as I know you need to tell it to open a file called :memory: and in Pharo-SQLite3 you should be able to use: SQLite3Connection memory I've never done this before in Pharo, but it's worth trying, it should be faster and easier to set up. https://www.sqlite.org/inmemorydb.html https://github.com/pharo-rdbms/Pharo-SQLite3/blob/7614fe8d0ac03fc94ed6be7e6… On Fri, 13 Aug 2021 at 00:26, Esteban Maringolo <emaringolo(a)gmail.com> wrote: > After I set up the tests I knew that was possible, but never knew how > to actually do it. > > Regards! > > Esteban A. Maringolo > > On Thu, Aug 12, 2021 at 8:55 PM JuliÃ¡n Maestri <serpi90(a)gmail.com> wrote: > > > > Not exactly what you are asking for, but did you consider using sqlite > in memory? > > > > On Sat, 7 Aug 2021 at 23:23, Esteban Maringolo <emaringolo(a)gmail.com> > wrote: > >> > >> I've been doing exactly that. It is, creating a new DB file for each > >> test, and I was having the same problem as you. > >> > >> I suggested a change to the driver to cover that situation: > >> https://github.com/pharo-rdbms/Pharo-SQLite3/pull/22/files > >> > >> Try applying that change and see if that works. > >> > >> I still prefer to recreate the database, it will give you a full fresh > >> start, and if you want you can halt before the deletion of the db, to > >> analyze its internal state. > >> > >> Best regards! > >> > >> > >> Esteban A. Maringolo > >> > >> On Sat, Aug 7, 2021 at 11:13 PM <vinref(a)gmail.com> wrote: > >> > > >> > Hi > >> > > >> > Actually I will just do a bunch of > >> > > >> > DROP TABLE IF EXISTS > >> > > >> > instead of dropping the db altogether. > >> > > >> > Thanks, Vince >

Aug. 13, 2021

Re: Pharo-SQLite3: closing connections immediately and deleting the database file

by Esteban Maringolo

After I set up the tests I knew that was possible, but never knew how to actually do it. Regards! Esteban A. Maringolo On Thu, Aug 12, 2021 at 8:55 PM JuliÃ¡n Maestri <serpi90(a)gmail.com> wrote: > > Not exactly what you are asking for, but did you consider using sqlite in memory? > > On Sat, 7 Aug 2021 at 23:23, Esteban Maringolo <emaringolo(a)gmail.com> wrote: >> >> I've been doing exactly that. It is, creating a new DB file for each >> test, and I was having the same problem as you. >> >> I suggested a change to the driver to cover that situation: >> https://github.com/pharo-rdbms/Pharo-SQLite3/pull/22/files >> >> Try applying that change and see if that works. >> >> I still prefer to recreate the database, it will give you a full fresh >> start, and if you want you can halt before the deletion of the db, to >> analyze its internal state. >> >> Best regards! >> >> >> Esteban A. Maringolo >> >> On Sat, Aug 7, 2021 at 11:13 PM <vinref(a)gmail.com> wrote: >> > >> > Hi >> > >> > Actually I will just do a bunch of >> > >> > DROP TABLE IF EXISTS >> > >> > instead of dropping the db altogether. >> > >> > Thanks, Vince

Aug. 13, 2021

Re: Pharo-SQLite3: closing connections immediately and deleting the database file

by JuliÃ¡n Maestri

Not exactly what you are asking for, but did you consider using sqlite in memory? On Sat, 7 Aug 2021 at 23:23, Esteban Maringolo <emaringolo(a)gmail.com> wrote: > I've been doing exactly that. It is, creating a new DB file for each > test, and I was having the same problem as you. > > I suggested a change to the driver to cover that situation: > https://github.com/pharo-rdbms/Pharo-SQLite3/pull/22/files > > Try applying that change and see if that works. > > I still prefer to recreate the database, it will give you a full fresh > start, and if you want you can halt before the deletion of the db, to > analyze its internal state. > > Best regards! > > > Esteban A. Maringolo > > On Sat, Aug 7, 2021 at 11:13 PM <vinref(a)gmail.com> wrote: > > > > Hi > > > > Actually I will just do a bunch of > > > > DROP TABLE IF EXISTS > > > > instead of dropping the db altogether. > > > > Thanks, Vince >

Aug. 12, 2021

ABBench: Lightweight Microbenchmarking Library

by Evan Donahue

Hello, I've just released a utility I've been using for the past few years to help optimize Pharo code. It's a library that makes it easy to check whether an optimization has improved performance by wrapping the optimization and the old code in an if block and executing the optimized and unoptimized paths repeatedly under the same runtime conditions to determine which is faster. Basic usage is to wrap changes to the code in if blocks like so: ABBench a: [ ...existing code...] b: [...optimized code...] And then run the A/B test by printing: ABBench bench: [...some main method...] I have found it to make performance testing simple and quick enough that I actually do it. Perhaps someone else will find it useful. Install with: Metacello new githubUser: 'emdonahue' project: 'ABBench' commitish: 'master' path: ''; baseline: 'ABBench'; load. More details can be found here: https://github.com/emdonahue/ABBench Cheers, Evan

Aug. 12, 2021

Exercism v3 problems

by r.wobben＠home.nl

Hello, For the new version of exercism which is due in a few weeks, the pharo track needs a test-runner, a example of that can be found here : https://github.com/exercism/ruby-test-runner/tree/main/lib first question : Can this be easily be done in pharo? second question : can it also be standalone? Regards, Roelof

Aug. 10, 2021

Re: Logging Frameworks

by Esteban Maringolo

Hi Gabriel, I found this Beacon-Server [1] that could work, it would be a good use case in a docker environment where you have several worker images talking to a single beacon-server-container. Regards! [1] https://github.com/grype/Beacon-Server Esteban A. Maringolo On Mon, Aug 9, 2021 at 9:10 AM Gabriel Cotelli <g.cotelli(a)gmail.com> wrote: > > Beacon is integrated as part of Pharo now, but the repository includes more logger options. Maybe some option there allows forwarding the logs to a centralized place. I'm also interested in other's experiences regarding logging options because we want to settle on some option as the default for our Pharo components. > > On Sun, Aug 8, 2021 at 11:29 AM Esteban Maringolo <emaringolo(a)gmail.com> wrote: >> >> What are the current options for logging? >> >> Beacon seems to be the most modern one, but the Github repository >> doesn't seem very active (maybe it forked somewhere else). >> >> Given that the logs might come from different worker images, is there >> something that can work via HTTP or similar? (it is, forwarding the >> logged events to a server). >> >> Regards! >> >> ps: I think I've asked this before, but couldn't find my previous >> question about it. >> >> >> Esteban A. Maringolo

Aug. 9, 2021

Re: Logging Frameworks

by Esteban Maringolo

That is my impression with Beacon, there was a lot of discussion about it and then never heard of it again. Is your code available somewhere? Regards! ps: There is also TinyLogger that works by means of a DynamicVariable, but I liked the idea of using objects instead of just strings for logging (which I'm manually doing now). Esteban A. Maringolo On Mon, Aug 9, 2021 at 9:16 AM Norbert Hartl <norbert(a)hartl.name> wrote: > > Beacon is a sad story. There was a lot of initiative and motivation for loggers which was killed. But it is still a good foundation to build something useful on top of it. I integrated a syslog option when I was working on beacon. In my projects Iâve done a sender to elasticsearch for logging. Beaconâs design allows all of that. After motivation died nobody put some love into it again. Thatâs all! > > Maybe time to pick it up again. But I personally have too much on my plate right now to take another attempt. > > Norbert > > > Am 09.08.2021 um 14:08 schrieb Gabriel Cotelli <g.cotelli(a)gmail.com>: > > Beacon is integrated as part of Pharo now, but the repository includes more logger options. Maybe some option there allows forwarding the logs to a centralized place. I'm also interested in other's experiences regarding logging options because we want to settle on some option as the default for our Pharo components. > > On Sun, Aug 8, 2021 at 11:29 AM Esteban Maringolo <emaringolo(a)gmail.com> wrote: >> >> What are the current options for logging? >> >> Beacon seems to be the most modern one, but the Github repository >> doesn't seem very active (maybe it forked somewhere else). >> >> Given that the logs might come from different worker images, is there >> something that can work via HTTP or similar? (it is, forwarding the >> logged events to a server). >> >> Regards! >> >> ps: I think I've asked this before, but couldn't find my previous >> question about it. >> >> >> Esteban A. Maringolo > >

Aug. 9, 2021

Re: Logging Frameworks

by Norbert Hartl

Beacon is a sad story. There was a lot of initiative and motivation for loggers which was killed. But it is still a good foundation to build something useful on top of it. I integrated a syslog option when I was working on beacon. In my projects Iâve done a sender to elasticsearch for logging. Beaconâs design allows all of that. After motivation died nobody put some love into it again. Thatâs all! Maybe time to pick it up again. But I personally have too much on my plate right now to take another attempt. Norbert > Am 09.08.2021 um 14:08 schrieb Gabriel Cotelli <g.cotelli(a)gmail.com>: > > Beacon is integrated as part of Pharo now, but the repository includes more logger options. Maybe some option there allows forwarding the logs to a centralized place. I'm also interested in other's experiences regarding logging options because we want to settle on some option as the default for our Pharo components. > > On Sun, Aug 8, 2021 at 11:29 AM Esteban Maringolo <emaringolo(a)gmail.com <mailto:emaringolo@gmail.com>> wrote: > What are the current options for logging? > > Beacon seems to be the most modern one, but the Github repository > doesn't seem very active (maybe it forked somewhere else). > > Given that the logs might come from different worker images, is there > something that can work via HTTP or similar? (it is, forwarding the > logged events to a server). > > Regards! > > ps: I think I've asked this before, but couldn't find my previous > question about it. > > > Esteban A. Maringolo

Aug. 9, 2021

Re: Logging Frameworks

by Gabriel Cotelli

Beacon is integrated as part of Pharo now, but the repository includes more logger options. Maybe some option there allows forwarding the logs to a centralized place. I'm also interested in other's experiences regarding logging options because we want to settle on some option as the default for our Pharo components. On Sun, Aug 8, 2021 at 11:29 AM Esteban Maringolo <emaringolo(a)gmail.com> wrote: > What are the current options for logging? > > Beacon seems to be the most modern one, but the Github repository > doesn't seem very active (maybe it forked somewhere else). > > Given that the logs might come from different worker images, is there > something that can work via HTTP or similar? (it is, forwarding the > logged events to a server). > > Regards! > > ps: I think I've asked this before, but couldn't find my previous > question about it. > > > Esteban A. Maringolo >

Aug. 9, 2021