Antonio Terceiro
Antonio Terceiro
no, normal messages.
This doesn't seem related to the history api call. What is happening is that it gets called twice for each channel. Looking back at my logs from when this happened...
very much, happens to me all the time
to be fair, I hadn't updated localslackirc in a while (was running 148dab8). I just pulled the latest master (9582618) and will let you know
> very much, happens to me all the time I mean, it happens very frequently, but not *all* the time or on *all* channels.
I solved this by using [this tip](http://www.lgbmi.com/2013/07/two-column-for-latex-from-pandoc-add-twocolumn/): replacing `longtable` with `supertabular` made it work for me.
> A cheap way to do this is to spawn a thread that periodically dump the main thread backtrace: > > ```ruby > Thread.new { loop { File.write("/tmp/ruby-#{$$}.log", Thread.main.backtrace.join("\n")); sleep...
something else that feels weird is that temporary directories left over from those tests look quite big: ``` $ du -shc /tmp/bootsnap-test2022051* 12M /tmp/bootsnap-test20220510-20661-te6zrm 140M /tmp/bootsnap-test20220511-23438-zirpy5 140M /tmp/bootsnap-test20220511-25624-3o4l2o 140M /tmp/bootsnap-test20220511-25726-v7x5r1...
I maintain a platform of 30+ machines, which I'm migrating from chef to itamae. There are 3 packages that are developed for that platform, of which we always want the...
Also, if I add new machines to the platform, using `install` the new ones will get the new version of those packages, while the older ones would be stuck with...