| conn = pymysql.connect( | |
| host=os.environ['MYSQL_HOST'], | |
| user=os.environ['MYSQL_USERNAME'], | |
| password=os.environ['MYSQL_PASSWORD'], | |
| database='enwiki_p', | |
| charset='utf8', | |
| use_unicode=True | |
| ) |
| org.wikimedia.ssh-pkcs11-agent.plist -> ~/Library/LaunchAgents | |
| OPENSC_LIBS=/usr/local/Cellar/opensc/0.15.0/lib | |
| ssh-add -s $OPENSC_LIBS/opensc-pkcs11.so |
The standard way of understanding the HTTP protocol is via the request reply pattern. Each HTTP transaction consists of a finitely bounded HTTP request and a finitely bounded HTTP response.
However it's also possible for both parts of an HTTP 1.1 transaction to stream their possibly infinitely bounded data. The advantages is that the sender can send data that is beyond the sender's memory limit, and the receiver can act on
1Password 5.3 for OSX, 5.2 for iOS, and 4.1.0.538 for Windows support OTP. I've been using Authy for a while now, but the fact is, I haven't really been using 2FA for some time. As mentioned by 1Password in a recent blog post, having the OTP generator and password on the same device is very much not 2FA. It's just an expiring OTP, which can help, but let's not kid ourselves too much.
With that out of the way. One of the things that was interesting to me was moving my OTP out of Authy and into 1Password. I like the control I get with 1Password, but I didn't want to have to reset all my OTP right away, that would suck. So, I got to dissecting the Authy Chrome App to see what I could do.
Run the Authy Chrome app and make sure it's unlocked.
Now, enable Developer mode in Chrome. We'll need this to inspect the background application that stores al
| // ==UserScript== | |
| // @name Mailman Always Discard and Ban | |
| // @namespace https://bendechrai.com/ | |
| // @description Automatically selects "Discard" and ticks the "Add" and Ban" checkboxes on Mailman admin requests for pending messages | |
| // @downloadURL TBA | |
| // @match *://*/mailman/admindb/* | |
| // @match *://*/lists/admindb/* | |
| // @version 1 | |
| // @grant none | |
| // ==/UserScript== |
I like labs-vagrant, and I like it even better when I can run it on my own server.
Eight commands to get labs-vagrant on your own Ubuntu server, from scratch.
# apt-get install puppet git
# git clone https://git.wikimedia.org/git/operations/puppet.git
# cd puppet
# git checkout -B production origin/production
# cd ..
| #!/bin/bash | |
| # Example Script to forward ssh-agent socket into an unprivileged lxc | |
| # This allows access to the ssh-agent by commands executed with lxc-attach | |
| set -m | |
| CONTAINER=$1 # e.g., test-container | |
| REMOTE=$2 # e.g, [email protected] |
| from statistics import median, mean | |
| import time | |
| import re | |
| import requests | |
| import subprocess | |
| warmups = 15 | |
| trials = 15 | |
| hosts = ('osmium', 'mw1020') | |
| headers = {'host': 'en.wikivoyage.org'} |
| Category | State | SGE Letter Code |
|---|---|---|
| Pending | pending | qw |
| Pending | pending, user hold | qw |
| Pending | pending, system hold | hqw |
| Pending | pending, user and system hold | hqw |
| Pending | pending, user hold, re-queue | hRwq |
| Pending | pending, system hold, re-queue | hRwq |
| # The MIT License (MIT) | |
| # Copyright (c) 2014 Dave Clark | |
| # Permission is hereby granted, free of charge, to any person obtaining a copy | |
| # of this software and associated documentation files (the "Software"), to deal | |
| # in the Software without restriction, including without limitation the rights | |
| # to use, copy, modify, merge, publish, distribute, sublicense, and/or sell | |
| # copies of the Software, and to permit persons to whom the Software is | |
| # furnished to do so, subject to the following conditions: |