fair-ddtrace 0.8.2.a

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: 8d8406c22a52e0293d58c806768b921dfce85da1
+  data.tar.gz: 31b29c7a0af9d5bed73bc8670eb2646d6ee62d56
+SHA512:
+  metadata.gz: e01f435e62fedd4e295a2b62f14041aec9e524a5e908a0a7050bf7ca94133798d7d5fda30690cb4351dd6d58902331a58a7241f57651ddf24ca4bcc23364103a
+  data.tar.gz: a46d900f85f22b957858df467de8e8b6b62a47ad8ff188c3a0c421c29a2e14b945ddf47e8e7547e90e07b3a1af1822cb52c540ce3ccaa9c2f0b732ca765cd33e

data/.env

@@ -0,0 +1,11 @@
+TEST_POSTGRES_PORT=55432
+TEST_POSTGRES_USER=postgres
+TEST_POSTGRES_PASSWORD=postgres
+TEST_POSTGRES_DB=postgres
+TEST_MYSQL_PORT=53306
+TEST_MYSQL_ROOT_PASSWORD=root
+TEST_MYSQL_PASSWORD=mysql
+TEST_MYSQL_USER=mysql
+TEST_ELASTICSEARCH_REST_PORT=49200
+TEST_ELASTICSEARCH_NATIVE_PORT=49300
+TEST_REDIS_PORT=46379

data/.gitignore

@@ -0,0 +1,59 @@
+*.gem
+*.rbc
+/.config
+/coverage/
+/InstalledFiles
+/pkg/
+/spec/reports/
+/spec/examples.txt
+/test/tmp/
+/test/version_tmp/
+/tmp/
+/log/
+
+# Used by dotenv library to load environment variables.
+# .env
+
+## Specific to RubyMotion:
+.dat*
+.repl_history
+build/
+*.bridgesupport
+build-iPhoneOS/
+build-iPhoneSimulator/
+
+## Specific to RubyMotion (use of CocoaPods):
+#
+# We recommend against adding the Pods directory to your .gitignore. However
+# you should judge for yourself, the pros and cons are mentioned at:
+# https://guides.cocoapods.org/using/using-cocoapods.html#should-i-check-the-pods-directory-into-source-control
+#
+# vendor/Pods/
+
+## Documentation cache and generated files:
+/.yardoc/
+/_yardoc/
+/doc/
+/rdoc/
+/html/
+
+## Environment normalization:
+/.bundle/
+/vendor/bundle
+/lib/bundler/man/
+
+# for a library or gem, you might want to ignore these files since the code is
+# intended to run in multiple environments; otherwise, check them in:
+# Gemfile.lock
+# .ruby-version
+# .ruby-gemset
+
+# unless supporting rvm < 1.11.0 or doing something fancy, ignore this:
+.rvmrc
+
+# lock files
+Gemfile.lock
+gemfiles/*.lock
+
+# bundle config
+gemfiles/.bundle

data/.rubocop.yml

@@ -0,0 +1,61 @@
+AllCops:
+  TargetRubyVersion: 2.1
+
+# 80 characters is a nice goal, but not worth currently changing in existing
+# code for the sake of changing it to conform to a length set in 1928 (IBM).
+Metrics/LineLength:
+  Max: 124
+
+# These exceptions are good goals to attain, and probably will over time,
+# so periodic disabling and re-running to inspect values is suggested.
+
+Metrics/AbcSize:
+  Max: 50
+
+# TODO: As refactors continue, this should drop. However, the goal of
+# 10 lines in a method may be a little lofty.
+Metrics/MethodLength:
+  Max: 36
+
+# TODO: this is not compliant with the Ruby community style guide. We
+# should enable again this rule but it will change the public API because
+# we're using set_ methods. We should work on that because also Rails
+# honors this rule.
+Style/AccessorMethodName:
+  Enabled: false
+
+Style/MethodCallWithoutArgsParentheses:
+  Enabled: false
+
+Style/RescueModifier:
+  Enabled: false
+
+Style/NumericLiterals:
+  Enabled: false
+
+Metrics/ClassLength:
+  Max: 140
+
+Metrics/BlockLength:
+  Max: 42
+
+Metrics/ParameterLists:
+  Enabled: false
+
+Metrics/CyclomaticComplexity:
+  Max: 15
+
+Metrics/PerceivedComplexity:
+  Max: 15
+
+Lint/UnusedMethodArgument:
+    Enabled: false
+
+# Disabling advices that would lead to incompatible Ruby 1.9 code
+Style/SymbolArray:
+  Enabled: false
+
+# Simple conditionals are perfectly fine, and more readable for multiline
+# expressions.
+Style/GuardClause:
+  Enabled: false

data/.yardopts

@@ -0,0 +1,5 @@
+--readme docs/GettingStarted.md
+--main docs/GettingStarted.md
+-
+docs/GettingStarted.md
+LICENSE

data/Appraisals

@@ -0,0 +1,136 @@
+if RUBY_VERSION < '2.4.0' && RUBY_PLATFORM != 'java'
+  if RUBY_VERSION >= '1.9.1'
+    appraise 'rails32-mysql2' do
+      gem 'test-unit'
+      gem 'rails', '3.2.22.5'
+      gem 'mysql2', '0.3.21', platform: :ruby
+      gem 'activerecord-mysql-adapter', platform: :ruby
+      gem 'activerecord-jdbcmysql-adapter', platform: :jruby
+    end
+  end
+
+  if RUBY_VERSION >= '1.9.1'
+    appraise 'rails30-postgres' do
+      gem 'test-unit'
+      gem 'rails', '3.0.20'
+      gem 'pg', '0.15.1', platform: :ruby
+      gem 'activerecord-jdbcpostgresql-adapter', platform: :jruby
+    end
+
+    if RUBY_VERSION < '2.2.2'
+      appraise 'rails30-postgres-sidekiq' do
+        gem 'test-unit'
+        gem 'rails', '3.0.20'
+        gem 'pg', '0.15.1', platform: :ruby
+        gem 'activerecord-jdbcpostgresql-adapter', platform: :jruby
+        gem 'sidekiq', '4.0.0'
+      end
+    end
+
+    appraise 'rails32-postgres' do
+      gem 'test-unit'
+      gem 'rails', '3.2.22.5'
+      gem 'pg', '0.15.1', platform: :ruby
+      gem 'activerecord-jdbcpostgresql-adapter', platform: :jruby
+    end
+
+    appraise 'rails32-postgres-redis' do
+      gem 'test-unit'
+      gem 'rails', '3.2.22.5'
+      gem 'pg', '0.15.1', platform: :ruby
+      gem 'activerecord-jdbcpostgresql-adapter', platform: :jruby
+      gem 'redis-rails'
+    end
+
+    if RUBY_VERSION < '2.2.2'
+      appraise 'rails32-postgres-sidekiq' do
+        gem 'test-unit'
+        gem 'rails', '3.2.22.5'
+        gem 'pg', '0.15.1', platform: :ruby
+        gem 'activerecord-jdbcpostgresql-adapter', platform: :jruby
+        gem 'sidekiq', '4.0.0'
+      end
+    end
+  end
+
+  if RUBY_VERSION >= '2.1.10'
+    appraise 'rails4-mysql2' do
+      gem 'rails', '4.2.7.1'
+      gem 'mysql2', platform: :ruby
+      gem 'activerecord-jdbcmysql-adapter', platform: :jruby
+    end
+
+    appraise 'rails4-postgres' do
+      gem 'rails', '4.2.7.1'
+      gem 'pg', platform: :ruby
+      gem 'activerecord-jdbcpostgresql-adapter', platform: :jruby
+    end
+
+    appraise 'rails4-postgres-redis' do
+      gem 'rails', '4.2.7.1'
+      gem 'pg', platform: :ruby
+      gem 'activerecord-jdbcpostgresql-adapter', platform: :jruby
+      gem 'redis-rails'
+    end
+  end
+
+  if RUBY_VERSION >= '2.2.2'
+    appraise 'rails5-mysql2' do
+      gem 'rails', '5.0.1'
+      gem 'mysql2', platform: :ruby
+    end
+
+    appraise 'rails5-postgres' do
+      gem 'rails', '5.0.1'
+      gem 'pg', platform: :ruby
+    end
+
+    appraise 'rails5-postgres-redis' do
+      gem 'rails', '5.0.1'
+      gem 'pg', platform: :ruby
+      gem 'redis-rails'
+    end
+
+    appraise 'rails5-postgres-sidekiq' do
+      gem 'rails', '5.0.1'
+      gem 'pg', platform: :ruby
+      gem 'sidekiq'
+      gem 'activejob'
+    end
+
+    appraise 'rails4-postgres-sidekiq' do
+      gem 'rails', '4.2.7.1'
+      gem 'pg', platform: :ruby
+      gem 'activerecord-jdbcpostgresql-adapter', platform: :jruby
+      gem 'sidekiq'
+      gem 'activejob'
+    end
+  end
+end
+
+if RUBY_VERSION >= '2.2.2' && RUBY_PLATFORM != 'java'
+  appraise 'contrib' do
+    gem 'elasticsearch-transport'
+    gem 'grape'
+    gem 'rack'
+    gem 'rack-test'
+    gem 'redis'
+    gem 'hiredis'
+    gem 'sinatra'
+    gem 'sqlite3'
+    gem 'activerecord'
+    gem 'sidekiq'
+  end
+else
+  appraise 'contrib-old' do
+    gem 'elasticsearch-transport'
+    gem 'redis', '< 4.0.0'
+    gem 'hiredis'
+    gem 'rack', '1.4.7'
+    gem 'rack-test'
+    gem 'sinatra', '1.4.5'
+    gem 'sqlite3'
+    gem 'activerecord', '3.2.22.5'
+    gem 'sidekiq', '4.0.0'
+  end
+end

data/Gemfile

@@ -0,0 +1,3 @@
+source 'https://rubygems.org'
+
+gemspec

data/LICENSE

@@ -0,0 +1,24 @@
+Copyright (c) 2016, Datadog <info@datadoghq.com>
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+    * Redistributions of source code must retain the above copyright
+      notice, this list of conditions and the following disclaimer.
+    * Redistributions in binary form must reproduce the above copyright
+      notice, this list of conditions and the following disclaimer in the
+      documentation and/or other materials provided with the distribution.
+    * Neither the name of Datadog nor the
+      names of its contributors may be used to endorse or promote products
+      derived from this software without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL <COPYRIGHT HOLDER> BE LIABLE FOR ANY
+DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
+LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
+ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

data/README.md

@@ -0,0 +1,156 @@
+# dd-trace-rb
+
+[![CircleCI](https://circleci.com/gh/DataDog/dd-trace-rb/tree/master.svg?style=svg&circle-token=b0bd5ef866ec7f7b018f48731bb495f2d1372cc1)](https://circleci.com/gh/DataDog/dd-trace-rb/tree/master)
+
+## Why this Fork?
+The v0.8.2 version of dd-trace-rb has a bug whenever calling [send_traces on the worker](https://github.com/DataDog/dd-trace-rb/blob/v0.8.2/lib/ddtrace/workers.rb#L36). Ironically, this ends up blowing up on the log line and killing the worker.
+
+## Documentation
+
+You can find the latest documentation on [rubydoc.info][docs]
+
+[docs]: http://www.rubydoc.info/github/DataDog/dd-trace-rb/
+
+## Getting started
+
+### Install
+
+Install the Ruby client with the ``gem`` command:
+
+    gem install ddtrace
+
+If you're using ``Bundler``, just update your ``Gemfile`` as follows:
+
+```ruby
+    source 'https://rubygems.org'
+
+    # tracing gem
+    gem 'ddtrace'
+```
+
+To use a development/preview version, use:
+
+```ruby
+    gem 'ddtrace', :github => 'DataDog/dd-trace-rb', :branch => 'me/my-feature-branch'
+```
+
+### Quickstart (manual instrumentation)
+
+If you aren't using a supported framework instrumentation, you may want to to manually instrument your code.
+Adding tracing to your code is very simple. As an example, let’s imagine we have a web server and we want
+to trace requests to the home page:
+
+```ruby
+    require 'ddtrace'
+    require 'sinatra'
+    require 'active_record'
+
+    # a generic tracer that you can use across your application
+    tracer = Datadog.tracer
+
+    get '/' do
+      tracer.trace('web.request') do |span|
+        # set some span metadata
+        span.service = 'my-web-site'
+        span.resource = '/'
+        span.set_tag('http.method', request.request_method)
+
+        # trace the activerecord call
+        tracer.trace('posts.fetch') do
+          @posts = Posts.order(created_at: :desc).limit(10)
+        end
+
+        # trace the template rendering
+        tracer.trace('template.render') do
+          erb :index
+        end
+      end
+    end
+```
+
+### Quickstart (integration)
+
+Instead of doing the above manually, whenever an integration is available,
+you can activate it. The example above would become:
+
+```ruby
+    require 'ddtrace'
+    require 'sinatra'
+    require 'active_record'
+
+    Datadog::Monkey.patch_all # monkey patch all available integrations
+
+    # now write your code naturally, it's traced automatically
+    get '/' do
+      @posts = Posts.order(created_at: :desc).limit(10)
+      erb :index
+    end
+```
+
+This will automatically trace any app inherited from `Sinatra::Application`.
+To trace apps inherited from `Sinatra::Base`, you should manually register
+the tracer inside your class.
+
+```ruby
+    require "ddtrace"
+    require "ddtrace/contrib/sinatra/tracer"
+
+    class App < Sinatra::Base
+      register Datadog::Contrib::Sinatra::Tracer
+    end
+```
+
+To know if a given framework or lib is supported by our client,
+please consult our [integrations][contrib] list.
+
+[contrib]: http://www.rubydoc.info/github/DataDog/dd-trace-rb/Datadog/Contrib
+
+## Development
+
+### Testing
+
+Configure your environment through:
+
+    $ bundle install
+    $ appraisal install
+
+You can launch tests using the following Rake commands:
+
+    $ rake test:main                                      # tracer tests
+    $ appraisal rails<version>-<database> rake test:rails # tests Rails matrix
+    $ appraisal contrib rake test:redis                   # tests Redis integration
+    ...
+
+Run ``rake --tasks`` for the list of available Rake tasks.
+
+Available appraisals are:
+
+* ``contrib``: default for integrations
+* ``contrib-old``: default for integrations, with version suited for old Ruby (possibly unmaintained) versions
+* ``rails3-mysql2``: Rails3 with Mysql
+* ``rails3-postgres``: Rails 3 with Postgres
+* ``rails3-postgres-redis``: Rails 3 with Postgres and Redis
+* ``rails3-postgres-sidekiq``: Rails 3 with Postgres and Sidekiq
+* ``rails4-mysql2``: Rails4 with Mysql
+* ``rails4-postgres``: Rails 4 with Postgres
+* ``rails4-postgres-redis``: Rails 4 with Postgres and Redis
+* ``rails4-postgres-sidekiq``: Rails 4 with Postgres and Sidekiq
+* ``rails5-mysql2``: Rails5 with Mysql
+* ``rails5-postgres``: Rails 5 with Postgres
+* ``rails5-postgres-redis``: Rails 5 with Postgres and Redis
+* ``rails5-postgres-sidekiq``: Rails 5 with Postgres and Sidekiq
+
+The test suite requires many backing services (PostgreSQL, MySQL, Redis, ...) and we're using
+``docker`` and ``docker-compose`` to start these services in the CI.
+To launch properly the test matrix, please [install docker][2] and [docker-compose][3] using
+the instructions provided by your platform. Then launch them through:
+
+    $ docker-compose up -d
+
+We also enforce the Ruby [community-driven style guide][1] through Rubocop. Simply launch:
+
+    $ rake rubocop
+
+[1]: https://github.com/bbatsov/ruby-style-guide
+[2]: https://www.docker.com/products/docker
+[3]: https://www.docker.com/products/docker-compose