mono0926

gitにおけるコミットログ/メッセージ例文集100の転載

例文を組み込んだAlfred Workflowを作りました: Alfred Git Commit Message Example

以下転載:

---

azu

flux-utils

facebook/flux 2.0.32.1.0で追加されたflux/utilsについて

see also 2015-08-17のJS: redux 1.0.0、flux-utils、Firefox 40 - JSer.info

はてなブックマーク検索を作りながらFlux Utilsについて学ぶ | Web Scratchにもっと具体的な解説を書きました

---

k-takata

Bash-completion is very slow on MSYS2

Bash-completion is very slow on MSYS2 when the current user is a domain user. This describes the cause and the solutions.

Cause

Expansion of ~* is very slow when you use a domain user. For example:

floriankraft

SQL2

All nodes with a specific name

SELECT * FROM [nt:unstructured] AS node
WHERE ISDESCENDANTNODE(node, "/search/in/path")
AND NAME() = "nodeName"

All pages below content path

anujbhatt

$ cat example.proto
message AMessage
{
    required int32 a=1;
    optional int32 b=2;
}

$ protoc example.proto --descriptor_set_out=example.pb
$ mono ProtoGen.exe example.pb
$ more Example.cs

branneman

Better local require() paths for Node.js

Problem

When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:

const Article = require('../../../../app/models/article');

Those suck for maintenance and they're ugly.

Possible solutions

hgfischer

Benchmarking Nginx with Go

There are a lot of ways to serve a Go HTTP application. The best choices depend on each use case. Currently nginx looks to be the standard web server for every new project even though there are other great web servers as well. However, how much is the overhead of serving a Go application behind an nginx server? Do we need some nginx features (vhosts, load balancing, cache, etc) or can you serve directly from Go? If you need nginx, what is the fastest connection mechanism? This are the kind of questions I'm intended to answer here. The purpose of this benchmark is not to tell that Go is faster or slower than nginx. That would be stupid.

So, these are the different settings we are going to compare:

• Go HTTP standalone (as the control group)
• Nginx proxy to Go HTTP
• Nginx fastcgi to Go TCP FastCGI
• Nginx fastcgi to Go Unix Socket FastCGI

kitak

コマンドによる「負荷」の原因切り分け

この文章では、Linuxコマンド、sar, top, psを使って、一般的に負荷といわれるものの原因を切り分けることを目的とする。

そもそも負荷とは

「複数のタスクによるサーバリソースの奪い合いの結果に生じる待ち時間」を一言で表した言葉。OSのチューニングとは負荷の原因を知り、それを取り除くことにほかならない。

ボトルネックの見極め作業の大まかな流れ

• ロードアベレージ（処理を実行したくても、実行できなくて待たされているプロセス（CPUの実行権限が与えられるのを待っている、またはディスクI/Oが完了するのを待っている）の数）を見る

paulirish

A timeline of the last four years of detecting good old window.localStorage.

---

Jan Lenhart, bless his heart contributed the first patch for support:

October 2009: 5059daa

SeanHayes

# -*- coding: utf-8 -*-
#Copyright (C) 2013 Seán Hayes

import my_project.settings as dj_settings
from fabric.api import local, run, sudo, env, prompt, settings, cd, parallel, execute
from fabric.contrib.files import exists
from fabric.decorators import hosts, roles, runs_once
import json
import logging
import os