https://wiki.postgresql.org/wiki/BDR_Quick_Start | |
curl -s "http://git.postgresql.org/gitweb/?p=2ndquadrant_bdr.git;a=blob_plain;f=contrib/bdr/scripts/bdr_quickstart.sh;hb=refs/heads/bdr-next" | bash | |
export PATH=$HOME/2ndquadrant_bdr/bdr/bin:$PATH | |
initdb -D $HOME/2ndquadrant_bdr/bdr5598 -A trust -U postgres |
def silencer | |
require 'java' | |
java_import 'java.io.PrintStream' | |
java_import 'java.io.ByteArrayOutputStream' | |
java_import 'java.lang.System' | |
sys_out_stream = System.out | |
my_output_stream = ByteArrayOutputStream.new |
require 'rake' | |
require 'rake/testtask' | |
Rake::TestTask.new do |t| | |
t.test_files = Dir.glob('spec/**/*_spec.rb') | |
end | |
task(default: :test) |
CentOS
wget https://raw.github.com/ksauzz/s3curl/master/s3curl.pl
curl -L http://cpanmin.us | perl - --sudo App::cpanminus
sudo cpanm YAML HTTP::Date Digest::HMAC_SHA1 URI::Escape
cpanminus https://github.com/miyagawa/cpanminus
Please see https://github.com/Mikayex/transmission
See my blog post.
This shows roughly similar configurations to distinguish message formats for different error levels in log4j version 2. I believe the yaml configuration is the easiert to read and maintain.
Create session using blackberry-connect, this tool resides inside your SDK dirs, the host dir i.e | |
$(BBSDK)/host_10_0_9_404/darwin/x86/usr/bin/blackberry-connect | |
$ blackberry-connect 169.254.0.1 -password <password> -sshPublicKey ~/.ssh/bb10/id_rsa | |
Then, | |
create a config file inside ~/.ssh folder | |
Host bb10 | |
HostName 169.254.0.1 |
body = MultipartBody.new(:field1 => 'test', :field2 => 'test2') | |
http = EventMachine::HttpRequest.new('http://example.com').post( | |
:head => {'content-type' => "multipart/form-data; boundary=#{body.boundary}"}, | |
:body => body.to_s | |
) | |
# Or with a file part included | |
part1 = Part.new('name', 'content', 'file.txt') |
The issue:
..mobile browsers will wait approximately 300ms from the time that you tap the button to fire the click event. The reason for this is that the browser is waiting to see if you are actually performing a double tap.
(from a new defunct https://developers.google.com/mobile/articles/fast_buttons article)
touch-action
CSS property can be used to disable this behaviour.
touch-action: manipulation
The user agent may consider touches that begin on the element only for the purposes of scrolling and continuous zooming. Any additional behaviors supported by auto are out of scope for this specification.