- Python 3
- Pip 3
$ brew install python3
#!/bin/sh | |
# hook identifies jira ids in branch names, adds on more goodies if we are a hotifx or release branch and attempts to prevent blank commit messages...although this needs a bit more work... | |
COMMIT_FILE=$1 | |
COMMIT_MSG=$(cat $1) | |
#First and foremost check whether the commit message is blank. if so then abort the commit. strip any spaces out too | |
#this one only works at present when someone tries to do git commit -m "" or git commit -m " " | |
#if anyone uses tools such as sourcetree, then these GUIs typically present a prompt...eg. "do you want to commit wihtout a message" and pass in optional attributes to git commit to allow this. |
panel_custom: | |
- name: zwavegraph2 | |
sidebar_title: Z-Wave Graph | |
sidebar_icon: mdi:access-point-network | |
url_path: zwave |
Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.
Today (April 16th 2019 at noon) the first major clues to discover key #1 was set to be released in a few cities. A QR code with the words 'orbital' were found at these locations and looked like this: (https://imgur.com/a/6rNmz7T). If you read the QR code with your phone you will be directed to this url: https://satoshistreasure.xyz/k1
At this URL you are prompted to input a passphrase to decrypt the first shard. An obvious first guess was to try the word 'orbital' from the QR code. Not suprisingly this worked! This reveals a congratulations page and presents the first key shard:
ST-0001-a36e904f9431ff6b18079881a20af2b3403b86b4a6bace5f3a6a47e945b95cce937c415bedaad6c86bb86b59f0b1d137442537a8
.
Now, we were supposed to wait until April 17th to get clues from the other cities for keys #2 and #3 but that wouldn't stop me from digging around with all the new information we had. All that time "playing" notpron (http://notpron.org/notpron/) years ago was going to help me here.
The first thing I noticed was
const HomeAssistant = require( 'homeassistant' ); | |
const Pino = require( 'pino' ); | |
const config = require( 'config' ); | |
const hass = new HomeAssistant( config.get( 'home_assistant' ) ); | |
const imessage = require( 'osa-imessage' ); | |
const logger = Pino(); | |
// TODO package this better | |
const bridge = { |
$/
artifacts/
build/
docs/
lib/
packages/
samples/
src/
tests/
rem This program starts the minio batch. | |
@echo off | |
setlocal | |
path=C:\programs\minio;%path% | |
set MINIO_ACCESS_KEY=accountname1 | |
set MINIO_SECRET_KEY=secretForAccountName | |
call minio gateway azure --address=:9001 >c:\test\c1.out | |
endlocal |
Disclaimer: This piece is written anonymously. The names of a few particular companies are mentioned, but as common examples only.
This is a short write-up on things that I wish I'd known and considered before joining a private company (aka startup, aka unicorn in some cases). I'm not trying to make the case that you should never join a private company, but the power imbalance between founder and employee is extreme, and that potential candidates would
Customers periodically ask "Why am I getting errors when talking to Redis". The answer is complicated - it could be a client or server side problem. In this article, I am going to talk about client side issues. For server side issues, see here
Clients can see connectivity issues or timeouts for several reason, here are some of the common ones I see:
###Memory pressure