rsense-server 0.5.0

data/spec/rsense/server/command_spec.rb

@@ -0,0 +1,108 @@
+require "pathname"
+require "json"
+require_relative "../../spec_helper.rb"
+
+describe Rsense::Server::Command::Command do
+  before do
+    @json_path = Pathname.new("spec/fixtures/sample.json")
+    @json = JSON.parse(@json_path.read)
+    @options = Rsense::Server::Options.new(@json)
+  end
+
+  it "can be initialized" do
+    Rsense::Server::Command::Command.new(@options)
+  end
+
+  describe "finding dependencies" do
+    Dependency = Struct.new(:name, :full_name, :path)
+    Project = Struct.new(:load_path, :gem_path, :stubs)
+
+    before do
+      @dependencies = [
+        Dependency.new("foo", "foo.1.2", ["/foo/bar/baz"]),
+        Dependency.new("scooby", "scooby.1.2", ["/scooby/dooby/doo"])
+      ]
+      @loadpath = [
+        "spec/fixtures",
+        "/bada/bing/bang/boom"
+      ]
+      @gempath = [
+        "/fee/fi/fo/fum",
+        "/i/smell/the/blood/of/an/englishman"
+      ]
+      @stubs = Dir.glob(Rsense::BUILTIN.join("**/*.rb"))
+      @project = Project.new(@loadpath, @gempath, @stubs)
+      @command = Rsense::Server::Command::Command.new(@options)
+    end
+
+    it "finds the dependency" do
+      matches = @command.dependency_matches(@dependencies, "foo")
+      matches.first.to_s.must_match(/baz/)
+    end
+
+    it "does not find a dependency which is not there" do
+      @command.dependency_matches(@dependencies, "scoby").must_be_empty
+    end
+
+    it "finds the path in the load_path" do
+      @command.load_path_matches(@project, "def_sample").size.must_equal(1)
+    end
+
+    it "gathers the lib directory paths from the dependencies" do
+      deps = [
+        Dependency.new("foo", "foo.1.2", ["/foo/lib/foo.rb"]),
+        Dependency.new("scooby", "scooby.1.2", ["/scooby/lib/scooby.rb"])
+      ]
+      paths = @command.dependency_paths(deps)
+      paths.size.must_equal(2)
+      paths.first.to_s.must_match(/\/foo\/lib$/)
+    end
+
+    it "finds a deeply nested path" do
+      dep_paths = [Pathname.new("spec/fixtures/deeply"), Pathname.new("foo/bar/baz")]
+      matches = @command.deep_check(@gempath, dep_paths, "thing")
+      matches.first.must_match(/nested/)
+      matches.size.must_equal(1)
+    end
+
+    it "finds the stubs" do
+      matches = @command.stub_matches(@project, "_builtin")
+      matches.size.must_equal(1)
+    end
+
+    it "finds the _builtin" do
+      @command.builtin_path(@project).to_s.must_match(/_builtin/)
+    end
+  end
+
+  describe "completions" do
+    require 'json'
+
+    class Testscript
+      attr_accessor :json_path, :json, :options, :command, :name, :file, :project
+
+      def initialize
+        @json_path = Pathname.new("spec/fixtures/test_gem/test.json").expand_path
+        @json = JSON.parse(@json_path.read)
+        @options = Rsense::Server::Options.new(@json)
+        @command = Rsense::Server::Command::Command.new(@options)
+        @name = "sample"
+        @file = @options.project_path
+        @project = Rsense::Server::Project.new(@name, @file)
+      end
+
+      def code_complete
+        @command.code_completion(@options.file, @options.location)
+      end
+    end
+
+    before do
+      @test = Testscript.new
+    end
+
+    it "returns completions" do
+      @test.code_complete.size.must_equal(51)
+    end
+
+  end
+end

data/spec/rsense/server/config_spec.rb

@@ -0,0 +1,27 @@
+require "filetree"
+require_relative "../../spec_helper"
+
+describe Rsense::Server::Config do
+  before do
+    @path = "spec/fixtures/config_fixture"
+    @conf_path = FileTree.new("spec/fixtures/config_fixture/.rsense").expand_path
+    @config = Rsense::Server::Config.new
+  end
+
+  it "searches for a config file" do
+    search = @config.search(@path)
+    search.to_s.must_match(/spec\/fixtures\/config_fixture\/\.rsense/)
+    @config.searched.size.must_equal(1)
+  end
+
+  it "sets the port" do
+    options = @config.options(@conf_path)
+    @config.port.must_equal(123456)
+  end
+
+  it "sets ignores" do
+    options = @config.options(@conf_path)
+    @config.ignores.must_include(".foo")
+    @config.ignores.must_include(".bar")
+  end
+end

data/spec/rsense/server/gem_path_spec.rb

@@ -0,0 +1,16 @@
+require_relative "../../spec_helper.rb"
+
+describe Rsense::Server::GemPath do
+
+  it "returns the list of Gem paths" do
+    Rsense::Server::GemPath.stub :fetch, ["/path/to/the/gems"] do
+      Rsense::Server::GemPath.paths.first.must_match(/\/path\/to\/the\/gems/)
+    end
+  end
+
+  it "excludes paths inside jruby\'s jars" do
+    Rsense::Server::GemPath.stub :fetch, ["file: file in a jar"] do
+      Rsense::Server::GemPath.paths.wont_include("file: file in a jar")
+    end
+  end
+end

data/spec/rsense/server/load_path_spec.rb

@@ -0,0 +1,63 @@
+require "pathname"
+require_relative "../../spec_helper.rb"
+
+describe Rsense::Server::LoadPath do
+  it "lists loads paths" do
+    Rsense::Server::LoadPath.stub :fetch,["/some/path/to/load"] do
+      Rsense::Server::LoadPath.paths.first.must_match(/\/some\/path\/to\/load/)
+    end
+  end
+
+  it "does not list paths inside a jar" do
+    Rsense::Server::LoadPath.stub :fetch, ["file:path/in/jar"] do
+      Rsense::Server::LoadPath.paths.wont_include("file:path/in/jar")
+    end
+  end
+
+  describe "with project" do
+    ProjectMock = Struct.new(:path)
+
+    before do
+      @proj_path = "spec/fixtures/load_path_fixture"
+      @project = ProjectMock.new(@proj_path)
+    end
+
+    it "checks for a Gemfile.lock" do
+      Rsense::Server::LoadPath.find_gemfile(@project.path).to_s.must_match(/Gemfile/)
+    end
+
+    it "checks paths for correct version" do
+      fake_paths = ["1", "2", "3"]
+      checked = Rsense::Server::LoadPath.check_version(fake_paths, "2")
+      checked.size.must_equal(1)
+      checked.must_include("2")
+      checked.wont_include("1")
+      checked.wont_include("3")
+    end
+
+    it "returns a list of Gems" do
+      class SpecMock
+        def name
+          "mock"
+        end
+
+        def version
+          "2"
+        end
+      end
+
+      lfile = Object.new
+
+      def lfile.specs
+        [SpecMock.new]
+      end
+
+      Gem.stub :find_files, ["/stubbed/path-2"] do
+        ret_gems = Rsense::Server::LoadPath.gem_info(lfile).first
+        ret_gems.name.must_match(/mock/)
+        ret_gems.full_name.must_match(/mock-2/)
+        ret_gems.path.first.must_match(/stubbed/)
+      end
+    end
+  end
+end

data/spec/rsense/server/options_spec.rb

@@ -0,0 +1,33 @@
+require "pathname"
+require "json"
+require_relative "../../spec_helper"
+
+describe Rsense::Server::Options do
+  before do
+    @json_path = Pathname.new("spec/fixtures/sample.json")
+    @json = JSON.parse(@json_path.read)
+    @options = Rsense::Server::Options.new(@json)
+  end
+
+  it "has a command" do
+    @options.command.must_match(/code_completion/)
+  end
+
+  it "has a project path" do
+    @options.project_path.to_s.must_match(/code/)
+    @options.project_path.class.must_equal(Pathname)
+  end
+
+  it "has code" do
+    @options.code.must_match(/def/)
+  end
+
+  it "has a location" do
+    @options.location["row"].must_equal(2)
+    @options.location["column"].must_equal(10)
+  end
+
+  it "has a file" do
+    @options.file.to_s.must_match(/rsense\.rb/)
+  end
+end

data/spec/rsense/server/path_info_spec.rb

@@ -0,0 +1,11 @@
+require_relative "../../spec_helper.rb"
+
+describe Rsense::Server::PathInfo do
+  it "knows where its home is" do
+    Rsense::Server::PathInfo::RSENSE_SERVER_HOME.to_s.must_match(/rsense-server$/)
+  end
+
+  it "knows where to find the bin file" do
+    Rsense::Server::PathInfo.bin_path.to_s.must_match(/rsense-server\/bin\/_rsense.rb$/)
+  end
+end

data/spec/rsense/server/project_spec.rb

@@ -0,0 +1,18 @@
+require_relative "../../spec_helper"
+
+describe Rsense::Server::Project do
+  before do
+    @project = Rsense::Server::Project.new(__FILE__, File.dirname(__FILE__))
+  end
+
+  it "has stubs" do
+    stubs = @project.stubs.select { |e| e.to_s =~ /_builtin/ }
+    stubs.size.must_equal(1)
+  end
+
+  it "tracks loaded features" do
+    @project.loaded << "feature"
+    @project.loaded?("feature").must_equal(true)
+    @project.loaded?("different").must_equal(false)
+  end
+end

data/spec/rsense/server_spec.rb

@@ -0,0 +1,7 @@
+require_relative "../spec_helper"
+
+describe Rsense::Server do
+  it "loads" do
+    Rsense::Server.class.must_equal Module
+  end
+end

data/spec/spec_helper.rb

@@ -0,0 +1,16 @@
+require "minitest/autorun"
+require "minitest/reporters"
+Minitest::Reporters.use!
+
+require "rsense-core"
+
+require_relative "../lib/rsense/server/command.rb"
+require_relative "../lib/rsense/server/gem_path.rb"
+require_relative "../lib/rsense/server/load_path.rb"
+require_relative "../lib/rsense/server/options.rb"
+require_relative "../lib/rsense/server/code.rb"
+require_relative "../lib/rsense/server.rb"
+require_relative "../lib/rsense/server/path_info.rb"
+require_relative "../lib/rsense/server/command/special_meth.rb"
+require_relative "../lib/rsense/server/project.rb"
+require_relative "../lib/rsense/server/config.rb"

data/vendor/gems/puma-2.8.2-java/COPYING

@@ -0,0 +1,55 @@
+Mongrel Web Server (Mongrel) is copyrighted free software by Zed A. Shaw
+<zedshaw at zedshaw dot com> You can redistribute it and/or modify it under
+either the terms of the GPL or the conditions below:
+
+1. You may make and give away verbatim copies of the source form of the
+   software without restriction, provided that you duplicate all of the
+   original copyright notices and associated disclaimers.
+
+2. You may modify your copy of the software in any way, provided that
+   you do at least ONE of the following:
+
+     a) place your modifications in the Public Domain or otherwise make them
+     Freely Available, such as by posting said modifications to Usenet or an
+     equivalent medium, or by allowing the author to include your
+     modifications in the software.
+
+     b) use the modified software only within your corporation or
+        organization.
+
+     c) rename any non-standard executables so the names do not conflict with
+     standard executables, which must also be provided.
+
+     d) make other distribution arrangements with the author.
+
+3. You may distribute the software in object code or executable
+   form, provided that you do at least ONE of the following:
+
+     a) distribute the executables and library files of the software,
+     together with instructions (in the manual page or equivalent) on where
+     to get the original distribution.
+
+     b) accompany the distribution with the machine-readable source of the
+     software.
+
+     c) give non-standard executables non-standard names, with
+        instructions on where to get the original software distribution.
+
+     d) make other distribution arrangements with the author.
+
+4. You may modify and include the part of the software into any other
+   software (possibly commercial).  But some files in the distribution
+   are not written by the author, so that they are not under this terms.
+
+5. The scripts and library files supplied as input to or produced as 
+   output from the software do not automatically fall under the
+   copyright of the software, but belong to whomever generated them, 
+   and may be sold commercially, and may be aggregated with this
+   software.
+
+6. THIS SOFTWARE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR
+   IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED
+   WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+   PURPOSE.
+
+

data/vendor/gems/puma-2.8.2-java/DEPLOYMENT.md

@@ -0,0 +1,92 @@
+# Deployment engineering for puma
+
+Puma is software that is expected to be run in a deployed environment eventually.
+You can centainly use it as your dev server only, but most people look to use
+it in their production deployments as well.
+
+To that end, this is meant to serve as a foundation of wisdom how to do that
+in a way that increases happiness and decreases downtime.
+
+## Specifying puma
+
+Most people want to do this by putting `gem "puma"` into their Gemfile, so we'll
+go ahead and assume that. Go add it now... we'll wait.
+
+
+Welcome back!
+
+## Single vs Cluster mode
+
+Puma was originally concieved as a thread-only webserver, but grew the ability to
+also use processes in version 2.
+
+Here are some rules of thumb:
+
+### MRI
+
+* Use cluster mode and set the number of workers to 1.5x the number of cpu cores
+  in the machine, minimum 2.
+* Set the number of threads to desired concurrent requests / number of workers.
+  Puma defaults to 8 and thats a decent number.
+
+#### Migrating from Unicorn
+
+* If you're migrating from unicorn though, here are some settings to start with:
+  * Set workers to half the number of unicorn workers you're using
+  * Set threads to 2
+  * Enjoy 50% memory savings
+* As you grow more confident in the thread safety of your app, you can tune the
+  workers down and the threads up.
+
+#### Worker utilization
+
+**How do you know if you're got enough (or too many workers)?**
+
+A good question. Due to MRI's GIL, only one thread can be executing at a time.
+But since so many apps are waiting on IO from DBs, etc., they can utilize threads
+to make better use of the process.
+
+The rule of thumb is you never want processes that are pegged all the time. This
+means that there is more work to do that the process can get through. On the other
+hand, if you have processes that sit around doing nothing, then they're just eating
+up resources.
+
+Watching your CPU utilization over time and aim for about 70% on average. This means
+you've got capacity still but aren't starving threads.
+
+## Daemonizing
+
+I prefer to not daemonize my servers and use something like `runit` or `upstrart` to
+monitor them as child processes. This gives them fast response to crashes and
+makes it easy to figure out what is going on. Additionally, unlike `unicorn`,
+puma does not require daemonization to do zero-downtime restarts.
+
+I see people using daemonization because they start puma directly via capistrano
+task and thus want it to live on past the `cap deploy`. To this people I said:
+You need to be using a process monitor. Nothing is making sure puma stays up in
+this scenario! You're just waiting for something weird to happen, puma to die,
+and to get paged at 3am. Do yourself a favor, at least the process monitoring
+your OS comes with, be it `sysvinit`, `upstart`, or `systemd`. Or branch out
+and use `runit` or hell, even `monit`.
+
+## Restarting
+
+You probably will want to deploy some new code at some point, and you'd like
+puma to start running that new code. Minimizing the amount of time the server
+is unavailable would be nice as well. Here's how to do it:
+
+1. Don't use `preload!`. This dirties the master process and means it will have
+to shutdown all the workers and re-exec itself to get your new code, which means
+much higher waiting around for things to load.
+
+1. Use `prune_bundler`. This makes it so that the cluster master will detach itself
+from a Bundler context on start. This allows the cluster workers to load your app
+and start a brand new Bundler context within the worker only. This means your
+master remains pristine and can live on between new releases of your code.
+
+1. Use phased-restart (`SIGUSR1` or `pumactl phased-restart`). This tells the master
+to kill off one worker at a time and restart them in your new code. This minimizes
+downtime and staggers the restart nicely. **WARNING** This means that both your
+old code and your new code will be running concurrently. Most deployment solutions
+already cause that, but it's worth warning you about it again. Be careful with your
+migrations, etc!

data/vendor/gems/puma-2.8.2-java/Gemfile

@@ -0,0 +1,17 @@
+source "http://rubygems.org"
+
+gem "hoe"
+gem "hoe-git"
+gem "hoe-ignore"
+gem "rdoc"
+gem "rake-compiler"
+gem "rack"
+
+gem 'minitest', '~> 4.0'
+
+gem "jruby-openssl", :platform => "jruby"
+
+platforms :rbx do
+  gem 'rubysl', '~> 2.0'
+end
+