matsukaz

npm install -g symlink

matsukaz

var AView = Backbone.View.extend({
    el: $("#main"),
    events: {
        "click button#btn1": "onBtn1Click"
    }
    ...
});
var BView = Backbone.View.extend({
    el: $("#main"),
    events: {

matsukaz

# To enable ProGuard in your project, edit project.properties
# to define the proguard.config property as described in that file.
#
# Add project specific ProGuard rules here.
# By default, the flags in this file are appended to flags specified
# in ${sdk.dir}/tools/proguard/proguard-android.txt
# You can edit the include path and order by changing the ProGuard
# include property in project.properties.
#
# For more details, see

matsukaz

protobuf
protobuf-2.6.0
protobuf-2.6.1
protobuf-master

matsukaz

XCODE_UUID=`defaults read /Applications/Xcode.app/Contents/Info.plist DVTPlugInCompatibilityUUID`
find ~/Library/Application\ Support/Developer/Shared/Xcode/Plug-ins -name Info.plist | xargs -IFILE defaults write FILE DVTPlugInCompatibilityUUIDs -array-add ${XCODE_UUID}

matsukaz

module Annotations
  @@__last_annotation__ = nil

  def annotations(meth=nil)
    return @@__annotations__[meth] if meth
    @@__annotations__
  end

  private

matsukaz

// see) https://github.com/rufuspollock/s3-bucket-listing

if (typeof S3BL_IGNORE_PATH == 'undefined' || S3BL_IGNORE_PATH!=true) {
  var S3BL_IGNORE_PATH = false;
}

if (typeof BUCKET_URL == 'undefined') {
  var BUCKET_URL = location.protocol + '//' + location.hostname;
}

matsukaz

### Keybase proof

I hereby claim:

  * I am matsukaz on github.
  * I am matsukaz (https://keybase.io/matsukaz) on keybase.
  * I have a public key ASCBEp_cERws8a9bgyJk6TWOlgQlpLEPq8atcv--G9Ynwwo

To claim this, I am signing this object:

matsukaz

module xxx
  class Application < Rails::Application

   #（中略）

    config.middleware.swap ActiveRecord::ConnectionAdapters::ConnectionManagement,
                           'ActiveRecord::ConnectionAdapters::ReconnectOnErrorManagement'
  end
end

matsukaz

This query is to find geolocation of an IP address including latitude, longitude, city and country.

Legacy SQL doesn't support range conditions such as BETWEEN when using JOIN, so we need to filter data by WHERE. This means if IP address does not match any of the data inside geolite_city_bq_b2b, records will not be able to receive.

Use Standard SQL if you want to receive records no matter you succeed to find geolocation or not.

Please refer to the following post for more detail.

https://cloudplatform.googleblog.com/2014/03/geoip-geolocation-with-google-bigquery.html