Skip to content

Instantly share code, notes, and snippets.


Peter Rabbitson ribasushi

View GitHub Profile
ribasushi / .lotusminer_config.toml
Last active Sep 29, 2020
Recommended miner settings
View .lotusminer_config.toml
# During space-race-1 we tuned the dealbots frequency to not overwhelm the miners
# With space-race-2 underway your miner will be negotiating deals with a number of
# clients, who lack coordination among themselves. Therefore it is *very strongly*
# recommended to tune your miner parameters based on the sealing capacity you already
# known from space-race-1
# The numbers below are the bare minimum for a single-box, non-gpu miner, and are
# very conservative safe numbers. No doubt your miner can do better so you can bring
# these numbers up. But! Do not dial them too high: if you lose sectors due to an
# unresponsive miner, your clients will be... sad.
View gist:06257eef7fbc5ba1b980385dd90c3f6d
# In your base Result class ( ...::Schema::BaseResult )
sub add_relationship {
my $self = shift;
my $opts = $_[3] || {};
# shut off all DBIC/perl-side cascading logic
$opts->{cascade_delete} = 0;
$opts->{cascade_update} = 0;
$opts->{cascade_copy} = 0;
View ELY5.txt
# As amply documented at:
perl -e '
ribasushi /
Last active Dec 7, 2016
Simple perl-centric git blame agregator
#!/usr/bin/env perl
use warnings;
use strict;
use File::Find qw/find/;
use Data::Dumper::Concise;
my $author_stats;
mst_20151207.log:[16:42:22] <mst> aight. what stuff are you going to want me to take on?
mst_20151207.log:[18:06:39] <ribasushi> um... we talked about this - I am not doing an orderly handover
mst_20151207.log:[18:06:45] <ribasushi> so.. nothing? :)
mst_20151207.log:[18:07:03] <ribasushi> am going to be @ LPW, can talk more then if you insist
mst_20151208.log:[15:54:23] <mst> you said on the blog post you'll be transferring maint bits. I'm not asking for orderly, just a heads up as to which things I'm going to wake up on boxing day owning, if anyway
mst_20151208.log:[16:39:12] <ribasushi> that bridge will be burning when I get to it
mst_20151208.log:[16:39:12] <ribasushi> don't worry - I will not land you in a Scwern-like situation
mst_20151208.log:[16:39:12] <ribasushi> but that's about it
mst_20151208.log:[16:44:55] <mst> so, basically "giving warning would stop it being the not-orderly thing you have in mind, but while you're trying to make a splash, you're going to do so without causing carnage" or so
View 2016-09-15_02-58-02_modules.txt
From: Peter Rabbitson <>
Subject: Upcoming PAUSE permissions dispute
Message-ID: <>
Date: Thu, 15 Sep 2016 04:58:02 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
View ~$ git reflog --date=rfc | head -n 6700
ca62a61 HEAD@{Thu, 28 Jul 2016 15:35:52 +0200}: commit (amend): Merging the ResultSource diagnostics rework
3220bf3 HEAD@{Thu, 28 Jul 2016 15:35:19 +0200}: commit (amend): Merging the ResultSource diagnostics rework
c169503 HEAD@{Thu, 28 Jul 2016 15:06:54 +0200}: checkout: moving from sssss to master
a71b078 HEAD@{Thu, 28 Jul 2016 15:03:45 +0200}: rebase -i (finish): returning to refs/heads/sssss
a71b078 HEAD@{Thu, 28 Jul 2016 15:03:45 +0200}: rebase -i (pick): (travis) Do not retry module installation when running single thread
a115f0d HEAD@{Thu, 28 Jul 2016 15:03:45 +0200}: rebase -i (pick): (travis) cPerl 5.24.0 has shipped
a6b1a4f HEAD@{Thu, 28 Jul 2016 15:03:34 +0200}: rebase -i (continue): Enable the schema SanChecks on 5.8 as well
db18e50 HEAD@{Thu, 28 Jul 2016 15:01:02 +0200}: rebase -i (edit): Enable the schema SanChecks on 5.8 as well
28dc870 HEAD@{Thu, 28 Jul 2016 15:01:02 +0200}: rebase -i (pick): Fix inexplicable 5.8.x C3 errors - roll back e6efde04
c169503 HEAD@{Thu, 28 Jul 2016 15:00:34 +0200}:
ribasushi / reflog.txt
Created May 25, 2016
git reflog --date=rfc | head -n 4000 | xclip
View reflog.txt
01c25aa HEAD@{Wed, 25 May 2016 14:42:16 +0200}: rebase -i (finish): returning to refs/heads/master
01c25aa HEAD@{Wed, 25 May 2016 14:42:15 +0200}: rebase -i (pick): grrrrr
a81471f HEAD@{Wed, 25 May 2016 14:19:27 +0200}: commit (amend): Move even more utils into DBIC::_Util (see next commit)
69815c3 HEAD@{Wed, 25 May 2016 14:19:13 +0200}: commit: Move even more utils into DBIC::_Util (see next commit)
890c012 HEAD@{Wed, 25 May 2016 14:13:38 +0200}: cherry-pick: fast-forward
140bcb6 HEAD@{Wed, 25 May 2016 14:13:38 +0200}: rebase -i (start): checkout HEAD^^^^
2774d1f HEAD@{Wed, 25 May 2016 13:03:02 +0200}: rebase -i (finish): returning to refs/heads/master
2774d1f HEAD@{Wed, 25 May 2016 13:03:02 +0200}: rebase -i (pick): grrrrr
890c012 HEAD@{Wed, 25 May 2016 12:54:31 +0200}: commit: Couple lines forgotten during 399b9455
140bcb6 HEAD@{Wed, 25 May 2016 12:53:48 +0200}: cherry-pick: fast-forward
ribasushi /
Created Apr 30, 2016
Note for the observers: "Coro's author refuses" is factually incorrect, here is the actual sequence of events:
  • A while ago Coro gets a bugreport about XS-level signal handlers and Perl-level signal handlers going out of sync
  • Coro's author reaches deep into perl internals to patch this up for the runtime, writes extensive tests for it, fixes the Coro-level manifestation
  • in 5.21.8 the hook interface is removed in order to (sic) save 4k of memory PER PROCESS:
  • A ticket is raised against 5.22.0-to-be, and dies after some discussion:
  • The issue is however acknowledged but not much is done to fixing it
  • As a result Coro as a toolkit can either
    • remove a part of its tests and continue being buggy under a known use scenario
    • refuse to build on 5.21.8+ until either P5#125439 is resolved or c910fead7893 is rolled back
  • The author chose the second option (which is exactly what I would do myself in his situation)
  • The "stableperl fork"
ribasushi / dbic_redocument.htm
Last active Feb 26, 2016
DBIC ReDocumentation
View dbic_redocument.htm
<p>I can not think of anything qualifying as <i>doesn't have to be a huge Perl project</i>* However, I have an idea which unquestionably will benefit the Perl community immensely, yet has a remarkably low barrier to entry (mainly one thing - patience). I propose that someone applies for a grant in the role of <b>DBIx::Class re-documentation project lead</b>.
<p>I have had inklings of "there got to be a better way to do things", but it wasn't until I read <a href="">this meditation by BrowserUK</a> that it dawned at me: Fixing up the better-than-most-but-still-terrible documentation of DBIC is a ~200 person-hour undertaking, which on top of that requires someones fresh eye. Given that DBIx::Class is a "staple-module" in the contemporary Perl ecosystem, I believe it is reasonable to expect for the TPF to "pick up the tab" if someone with the right qualifications steps up.
<p>What is wrong with DBIC's documentation anyway?
<ul><li>Lack of entry level architectural docu
You can’t perform that action at this time.