Hennadii Shymanskyi gendosua

Message pattern: `^\[(.*)\] (.+?)\.([A-Z]+): (.*)`
Message start pattern: `^\[`
Time format: `yyyy-MM-dd HH:mm:ss`
Time capture group: `1`
Severity capture group: `3`
Category capture group: `2`

Improving the Pact-JS DSL

(Thanks to Andras Bubics and Matt Fellows for many discussions leading to this proposal)

Test frameworks for Javascript are diverse - some run in parallel by default, some have different testing styles or expectations (eg BDD), and they all have different ways to configure and instrument the test framework.

The Pact workflow also includes a number of (necessary) assumptions and expectations - such as the need to keep

dyld: Symbol not found: __cg_jpeg_resync_to_restart
  Referenced from: /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO
  Expected in: /usr/local/lib/libJPEG.dylib
 in /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO
error: Process didn't exit successfully: `target/debug/main` (signal: 5, SIGTRAP: trace/breakpoint trap)

Similarly for libTIFF.dylib, etc.

Let's Encrypt on Ubuntu 14.04, nginx with webroot auth

This document details how I setup LE on my server. Firstly, install the client as described on http://letsencrypt.readthedocs.org/en/latest/using.html and make sure you can execute it. I put it in /root/letsencrypt.

As it is not possible to change the ports used for the standalone authenticator and I already have a nginx running on port 80/443, I opted to use the webroot method for each of my domains (note that LE does not issue wildcard certificates by design, so you probably want to get a cert for www.example.com and example.com).

Configuration

For this, I placed config files into etc/letsencrypt/configs, named after <domain>.conf. The files are simple:

When you declare a request and response using the traditional Pact DSL, ("uponReceiving" and "willRespondWith") you're building a structure that has three purposes -

it provides the concrete example request and response used in the tests
it specifies the contents of the contract which...
defines how to validate the the actual request/response against the expected request/response

The three different uses of this structure are hidden from you when using HTTP Pact because the mock service handles numbers 1 & 2 in the consumer tests, and the verification task handles number 3 for you in the provider tests. When using Pact in a non-HTTP scenario, there is no nice neat protocol layer to inject the code to do this for you, so you have to explicitly do each step.

The file expected_data_from_collector.rb declares an object graph using the Pact DSL. This is going to be used to create the concrete example and the contract. This could be declared inline, but for easier maintenance, and to allow the contr

	#!/bin/sh
	sed -i.default "s/^zend_extension=/;zend_extension=/" /usr/local/etc/php/7.1/conf.d/ext-xdebug.ini
	launchctl unload ~/Library/LaunchAgents/homebrew.mxcl.php71.plist
	launchctl load ~/Library/LaunchAgents/homebrew.mxcl.php71.plist
	sudo brew services restart php71
	echo "xdebug disabled"

	# UPDATED 17 February 2019
	# Redirect all HTTP traffic to HTTPS
	server {
	listen 80;
	listen [::]:80;
	server_name www.domain.com domain.com;
	return 301 https://$host$request_uri;
	}

	# SSL configuration

	#!/usr/bin/env ruby
	# make sure you the watir gem installed -> gem install watir
	require 'watir'
	def log (message) puts " #{message}" end
	def success (message) puts "+ #{message}" end
	def fail (message) puts "- #{message}" end
	def notify (message)
	success message.upcase
	system 'osascript -e \'Display notification Burgerbot with title "%s"\'' % message
	rescue StandardError => e

	#include <math.h>
	#include <algorithm>
	#include <string>
	#include <immintrin.h>
	using namespace std;typedef float R;
	#define _W 79
	#define _H 39
	#define EP 0.01f
	#define OP operator
	#define C const

	# The command finds the most recent tag that is reachable from a commit.
	# If the tag points to the commit, then only the tag is shown.
	# Otherwise, it suffixes the tag name with the number of additional commits on top of the tagged object
	# and the abbreviated object name of the most recent commit.
	git describe

	# With --abbrev set to 0, the command can be used to find the closest tagname without any suffix:
	git describe --abbrev=0

	# other examples