Sebastian Webber sebawebber

Commit Message Guidelines

In the last few years, the number of programmers concerned about writing structured commit messages have dramatically grown. As exposed by Tim Pope in article readable commit messages are easy to follow when looking through the project history. Moreover the AngularJS contributing guides introduced conventions that can be used by automation tools to automatically generate useful documentation, or by developers during debugging process.

This document borrows some concepts, conventions and even text mainly from these two sources, extending them in order to provide a sensible guideline for writing commit messages.

Goals
Proposal
- Commit Message Format

Allowed ``

Common Options

-#, --progress-bar Make curl display a simple progress bar instead of the more informational standard meter.

-b, --cookie <name=data> Supply cookie with request. If no =, then specifies the cookie file to use (see -c).

-c, --cookie-jar <file name> File to save response cookies to.

Donation Button

#Wildfly Toolbelt

Deploy Related

Find domain deployments in filesystem

Basically, you need to open domain.xml under WILDFLY_HOME/domain/configuration and find the <deployments> session. In that session, each deployment contain a <content> tag. The attribute sha1 contains details where the file is storaged on the filesystem. EG:

<deployments>

# Install gosu.  https://github.com/tianon/gosu
ENV GOSU_VERSION=1.11
RUN gpg --keyserver ha.pool.sks-keyservers.net --recv-keys B42F6819007F00F88E364FD4036A9C25BF357DD4 \
    && curl -o /usr/local/bin/gosu -SL "https://github.com/tianon/gosu/releases/download/${GOSU_VERSION}/gosu-amd64" \
    && curl -o /usr/local/bin/gosu.asc -SL "https://github.com/tianon/gosu/releases/download/${GOSU_VERSION}/gosu-amd64.asc" \
    && gpg --verify /usr/local/bin/gosu.asc \
    && rm /usr/local/bin/gosu.asc \
    && rm -r /root/.gnupg/ \
 &amp;&amp; chmod +x /usr/local/bin/gosu \

memuse measures unique physical total memory taken by a process and its children, ignoring duplicate copy-on-write pages and shared memory.

This is a solution for http://serverfault.com/questions/676335/how-measure-memory-without-copy-on-write-pages

It's a quick and dirty utility, but feel free to fork & improve.

Example:

~ » sudo ./memuse.py 15897                                                                                                                         eugene@eugene-thinkpad

PID Commandline Frames (+unique) VMEM

	# switch the log level to DEBUG on console
	{wildfly}/bin/jboss-cli.sh --connect
	[standalone@localhost:9990 /] /subsystem=logging/console-handler=CONSOLE:write-attribute(name=level,value=DEBUG)
	[standalone@localhost:9990 /] /subsystem=logging/root-logger=ROOT:write-attribute(name=level,value=DEBUG)

	# switch it back to whatever it was initial configuration (here it is INFO)
	[standalone@localhost:9990 /] /subsystem=logging/console-handler=CONSOLE:write-attribute(name=level,value=INFO)
	[standalone@localhost:9990 /] /subsystem=logging/root-logger=ROOT:write-attribute(name=level,value=INFO)

	#!/bin/bash

	#
	# O pgbadger no modo incremental gera um indice (arquivos .bin)
	# para fazer o parser do log, e não possui um mecanismo interno
	# de limpeza de arquivos que não estão mais em uso.
	#
	# Este script efetua a limpeza dos .bin obsoletos, ou seja,
	# aqueles que são de dias anteriores aos correspondentes a
	# semana corrente.

	WITH btree_index_atts AS (
	SELECT nspname, relname, reltuples, relpages, indrelid, relam,
	regexp_split_to_table(indkey::text, ' ')::smallint AS attnum,
	indexrelid as index_oid
	FROM pg_index
	JOIN pg_class ON pg_class.oid=pg_index.indexrelid
	JOIN pg_namespace ON pg_namespace.oid = pg_class.relnamespace
	JOIN pg_am ON pg_class.relam = pg_am.oid
	WHERE pg_am.amname = 'btree'
	),

	// You can edit this code!
	// Click here and start typing.
	package main

	import "fmt"
	import "runtime"
	import "strings"

	func identifyPanic() string {
	var name, file string