NameError: undefined method `configurations'

Steps to reproduce:
NameError: undefined method configurations' for class #<Class:0x236ec794>'
NoMethodError: undefined method configurations' for ActiveRecord::Base:Class`
$ cd rails/activerecord
$ git checkout 5-0-stable
$ bundle
$ bundle exec ruby -w -I"lib:test" --dev -I"/home/yahonda/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/rake-11.2.2/lib" "/home/yahonda/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/rake-11.2.2/lib/rake/rake_test_loader.rb" \
"test/cases/fixtures_test.rb" \
"test/cases/tasks/database_tasks_test.rb" \
"test/cases/connection_adapters/connection_handler_test.rb"

Result:
+ bundle exec ruby -w -Ilib:test --dev -I/home/yahonda/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/rake-11.2.2/lib /home/yahonda/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/rake-11.2.2/lib/rake/rake_test_loader.rb test/cases/fixtures_test.rb test/cases/tasks/database_tasks_test.rb test/cases/connection_adapters/connection_handler_test.rb
Using jdbcsqlite3
Run options: --seed 40645

# Running:

.........................................................................................................E............................................EEEEEE

Finished in 12.538000s, 12.4422 runs/s, 74.9721 assertions/s.

  1) Error:
ActiveRecord::DatabaseTasksCreateAllTest#test_creates_configurations_with_local_host:
NameError: undefined method `configurations' for class `#<Class:0x236ec794>'
    org/jruby/RubyModule.java:2701:in `public'
    org/jruby/RubyMethod.java:115:in `call'
    /home/yahonda/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/mocha-0.14.0/lib/mocha/class_method.rb:80:in `restore_original_method'
    /home/yahonda/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/mocha-0.14.0/lib/mocha/class_method.rb:22:in `unstub'
    /home/yahonda/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/mocha-0.14.0/lib/mocha/central.rb:20:in `unstub'
    /home/yahonda/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/mocha-0.14.0/lib/mocha/central.rb:27:in `unstub_all'
    /home/yahonda/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/mocha-0.14.0/lib/mocha/mockery.rb:74:in `teardown'
    /home/yahonda/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/mocha-0.14.0/lib/mocha/mockery.rb:25:in `teardown'
    /home/yahonda/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/mocha-0.14.0/lib/mocha/hooks.rb:39:in `mocha_teardown'
    /home/yahonda/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/mocha-0.14.0/lib/mocha/integration/mini_test/adapter.rb:48:in `after_teardown'
    /home/yahonda/git/rails/activesupport/lib/active_support/testing/setup_and_teardown.rb:46:in `after_teardown'
    /home/yahonda/git/rails/activerecord/lib/active_record/fixtures.rb:857:in `after_teardown'

  2) Error:
ActiveRecord::ConnectionAdapters::ConnectionHandlerTest#test_establish_connection_uses_spec_name:
NoMethodError: undefined method `configurations' for ActiveRecord::Base:Class
Did you mean?  configurations=
    org/jruby/RubyBasicObject.java:1655:in `method_missing'
    /home/yahonda/git/rails/activerecord/lib/active_record/dynamic_matchers.rb:21:in `method_missing'
    /home/yahonda/git/rails/activerecord/test/cases/connection_adapters/connection_handler_test.rb:8:in `setup'

  3) Error:
ActiveRecord::ConnectionAdapters::ConnectionHandlerTest#test_retrieve_connection:
NoMethodError: undefined method `configurations' for ActiveRecord::Base:Class
Did you mean?  configurations=
    org/jruby/RubyBasicObject.java:1655:in `method_missing'
    /home/yahonda/git/rails/activerecord/lib/active_record/dynamic_matchers.rb:21:in `method_missing'
    /home/yahonda/git/rails/activerecord/test/cases/connection_adapters/connection_handler_test.rb:8:in `setup'

  4) Error:
ActiveRecord::ConnectionAdapters::ConnectionHandlerTest#test_retrieve_connection_pool_with_invalid_id:
NoMethodError: undefined method `configurations' for ActiveRecord::Base:Class
Did you mean?  configurations=
    org/jruby/RubyBasicObject.java:1655:in `method_missing'
    /home/yahonda/git/rails/activerecord/lib/active_record/dynamic_matchers.rb:21:in `method_missing'
    /home/yahonda/git/rails/activerecord/test/cases/connection_adapters/connection_handler_test.rb:8:in `setup'

  5) Error:
ActiveRecord::ConnectionAdapters::ConnectionHandlerTest#test_connection_pools:
NoMethodError: undefined method `configurations' for ActiveRecord::Base:Class
Did you mean?  configurations=
    org/jruby/RubyBasicObject.java:1655:in `method_missing'
    /home/yahonda/git/rails/activerecord/lib/active_record/dynamic_matchers.rb:21:in `method_missing'
    /home/yahonda/git/rails/activerecord/test/cases/connection_adapters/connection_handler_test.rb:8:in `setup'

  6) Error:
ActiveRecord::ConnectionAdapters::ConnectionHandlerTest#test_active_connections?:
NoMethodError: undefined method `configurations' for ActiveRecord::Base:Class
Did you mean?  configurations=
    org/jruby/RubyBasicObject.java:1655:in `method_missing'
    /home/yahonda/git/rails/activerecord/lib/active_record/dynamic_matchers.rb:21:in `method_missing'
    /home/yahonda/git/rails/activerecord/test/cases/connection_adapters/connection_handler_test.rb:8:in `setup'

  7) Error:
ActiveRecord::ConnectionAdapters::ConnectionHandlerTest#test_retrieve_connection_pool:
NoMethodError: undefined method `configurations' for ActiveRecord::Base:Class
Did you mean?  configurations=
    org/jruby/RubyBasicObject.java:1655:in `method_missing'
    /home/yahonda/git/rails/activerecord/lib/active_record/dynamic_matchers.rb:21:in `method_missing'
    /home/yahonda/git/rails/activerecord/test/cases/connection_adapters/connection_handler_test.rb:8:in `setup'

156 runs, 940 assertions, 0 failures, 7 errors, 0 skips
[yahonda@li1037-113 activerecord (5-0-stable)]$

Environment:

AR-JDBC rails-5 branch
ActiveRecord 5-0-stable branch
JRuby version

$ ruby -v
jruby <IP_ADDRESS> (2.3.1) 2016-11-09 0150a76 OpenJDK 64-Bit Server VM 25.111-b16 on 1.8.0_111-b16 +jit [linux-x86_64]

Java version

openjdk version "1.8.0_111"
OpenJDK Runtime Environment (build 1.8.0_111-b16)
OpenJDK 64-Bit Server VM (build 25.111-b16, mixed mode)

These errors are affected by this test. Probably due to ActiveRecord::Base.stub(:configurations, {})
https://github.com/rails/rails/blob/5-0-stable/activerecord/test/cases/fixtures_test.rb#L262-L281
  def test_fixtures_are_set_up_with_database_env_variable
    db_url_tmp = ENV['DATABASE_URL']
    ENV['DATABASE_URL'] = "sqlite3::memory:"
    ActiveRecord::Base.stub(:configurations, {}) do
      test_case = Class.new(ActiveRecord::TestCase) do
        fixtures :accounts

        def test_fixtures
          assert accounts(:signals37)
        end
      end

      result = test_case.new(:test_fixtures).run

      assert result.passed?, "Expected #{result.name} to pass:\n#{result}"
    end
  ensure
    ENV['DATABASE_URL'] = db_url_tmp
  end

Since it does not reproduce with CRuby. I have reported it here.

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/39467182-nameerror-undefined-method-configurations?utm_campaign=plugin&utm_content=tracker%2F136963&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F136963&utm_medium=issues&utm_source=github).

@yahonda I am not seeing this problem but I am not executing through bundle exec and I am also using JRuby master.

Thanks for the update.

without bundle exec

Without bundle exec it gets the following LoadError. I do not know the cause of this LoadError. I usually use bundle exec for all ActiveRecord unit tests.
$ ruby -v
jruby <IP_ADDRESS> (2.3.1) 2016-11-09 0150a76 OpenJDK 64-Bit Server VM 25.111-b16 on 1.8.0_111-b16 +jit [linux-x86_64]
$ ruby -w -I"lib:test" --dev -I"/home/yahonda/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/rake-11.2.2/lib" "/home/yahonda/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/rake-11.2.2/lib/rake/rake_test_loader.rb" "test/cases/fixtures_test.rb" "test/cases/tasks/database_tasks_test.rb" "test/cases/connection_adapters/connection_handler_test.rb"
Using jdbcsqlite3
LoadError: Could not load 'active_record/connection_adapters/jdbcsqlite3_adapter'. Make sure that the adapter in config/database.yml is valid. If you use an adapter other than 'mysql2', 'postgresql' or 'sqlite3' add the necessary adapter gem to the Gemfile.

Also I need to run multiple ruby version then I use rbenv and ruby-build to swith ruby environments. It may be related with this error without bundle exec.
$ rbenv install jruby-<IP_ADDRESS>
$ rbenv global jruby-<IP_ADDRESS>

jruby-<IP_ADDRESS>-dev

It also reproduces with jruby <IP_ADDRESS>-SNAPSHOT. I think it is worthful to use it with rbenv and ruby-build, I'll open a pull request to install jruby <IP_ADDRESS>-SNAPSHOT.
$ ruby -v
jruby <IP_ADDRESS>-SNAPSHOT (2.3.1) 2016-11-28 40a90b1 OpenJDK 64-Bit Server VM 25.111-b16 on 1.8.0_111-b16 +jit [linux-x86_64]

$ bundle exec ruby -w -Ilib:test --dev -I/home/yahonda/.rbenv/versions/jruby-<IP_ADDRESS>-dev/lib/ruby/gems/shared/gems/rake-11.2.2/lib /home/yahonda/.rbenv/versions/jruby-<IP_ADDRESS>-dev/lib/ruby/gems/shared/gems/rake-11.2.2/lib/rake/rake_test_loader.rb test/cases/fixtures_test.rb test/cases/tasks/database_tasks_test.rb test/cases/connection_adapters/connection_handler_test.rb
Using jdbcsqlite3
Run options: --seed 46951

# Running:

.........................................................................................................E............................................EEEEEE

Finished in 16.019000s, 9.7384 runs/s, 58.6803 assertions/s.

  1) Error:
ActiveRecord::DatabaseTasksCreateAllTest#test_creates_configurations_with_local_host:
NameError: undefined method `configurations' for class `#<Class:0x44acce5d>'
    org/jruby/RubyModule.java:2703:in `public'
    org/jruby/RubyMethod.java:115:in `call'
    /home/yahonda/.rbenv/versions/jruby-<IP_ADDRESS>-dev/lib/ruby/gems/shared/gems/mocha-0.14.0/lib/mocha/class_method.rb:80:in `restore_original_method'
    /home/yahonda/.rbenv/versions/jruby-<IP_ADDRESS>-dev/lib/ruby/gems/shared/gems/mocha-0.14.0/lib/mocha/class_method.rb:22:in `unstub'
    /home/yahonda/.rbenv/versions/jruby-<IP_ADDRESS>-dev/lib/ruby/gems/shared/gems/mocha-0.14.0/lib/mocha/central.rb:20:in `unstub'
    /home/yahonda/.rbenv/versions/jruby-<IP_ADDRESS>-dev/lib/ruby/gems/shared/gems/mocha-0.14.0/lib/mocha/central.rb:27:in `unstub_all'
    /home/yahonda/.rbenv/versions/jruby-<IP_ADDRESS>-dev/lib/ruby/gems/shared/gems/mocha-0.14.0/lib/mocha/mockery.rb:74:in `teardown'
    /home/yahonda/.rbenv/versions/jruby-<IP_ADDRESS>-dev/lib/ruby/gems/shared/gems/mocha-0.14.0/lib/mocha/mockery.rb:25:in `teardown'
    /home/yahonda/.rbenv/versions/jruby-<IP_ADDRESS>-dev/lib/ruby/gems/shared/gems/mocha-0.14.0/lib/mocha/hooks.rb:39:in `mocha_teardown'
    /home/yahonda/.rbenv/versions/jruby-<IP_ADDRESS>-dev/lib/ruby/gems/shared/gems/mocha-0.14.0/lib/mocha/integration/mini_test/adapter.rb:48:in `after_teardown'
    /home/yahonda/git/rails/activesupport/lib/active_support/testing/setup_and_teardown.rb:46:in `after_teardown'
    /home/yahonda/git/rails/activerecord/lib/active_record/fixtures.rb:857:in `after_teardown'

  2) Error:
ActiveRecord::ConnectionAdapters::ConnectionHandlerTest#test_establish_connection_uses_spec_name:
NoMethodError: undefined method `configurations' for ActiveRecord::Base:Class
Did you mean?  configurations=
    org/jruby/RubyBasicObject.java:1654:in `method_missing'
    /home/yahonda/git/rails/activerecord/lib/active_record/dynamic_matchers.rb:21:in `method_missing'
    /home/yahonda/git/rails/activerecord/test/cases/connection_adapters/connection_handler_test.rb:8:in `setup'

  3) Error:
ActiveRecord::ConnectionAdapters::ConnectionHandlerTest#test_active_connections?:
NoMethodError: undefined method `configurations' for ActiveRecord::Base:Class
Did you mean?  configurations=
    org/jruby/RubyBasicObject.java:1654:in `method_missing'
    /home/yahonda/git/rails/activerecord/lib/active_record/dynamic_matchers.rb:21:in `method_missing'
    /home/yahonda/git/rails/activerecord/test/cases/connection_adapters/connection_handler_test.rb:8:in `setup'

  4) Error:
ActiveRecord::ConnectionAdapters::ConnectionHandlerTest#test_retrieve_connection_pool:
NoMethodError: undefined method `configurations' for ActiveRecord::Base:Class
Did you mean?  configurations=
    org/jruby/RubyBasicObject.java:1654:in `method_missing'
    /home/yahonda/git/rails/activerecord/lib/active_record/dynamic_matchers.rb:21:in `method_missing'
    /home/yahonda/git/rails/activerecord/test/cases/connection_adapters/connection_handler_test.rb:8:in `setup'

  5) Error:
ActiveRecord::ConnectionAdapters::ConnectionHandlerTest#test_connection_pools:
NoMethodError: undefined method `configurations' for ActiveRecord::Base:Class
Did you mean?  configurations=
    org/jruby/RubyBasicObject.java:1654:in `method_missing'
    /home/yahonda/git/rails/activerecord/lib/active_record/dynamic_matchers.rb:21:in `method_missing'
    /home/yahonda/git/rails/activerecord/test/cases/connection_adapters/connection_handler_test.rb:8:in `setup'

  6) Error:
ActiveRecord::ConnectionAdapters::ConnectionHandlerTest#test_retrieve_connection:
NoMethodError: undefined method `configurations' for ActiveRecord::Base:Class
Did you mean?  configurations=
    org/jruby/RubyBasicObject.java:1654:in `method_missing'
    /home/yahonda/git/rails/activerecord/lib/active_record/dynamic_matchers.rb:21:in `method_missing'
    /home/yahonda/git/rails/activerecord/test/cases/connection_adapters/connection_handler_test.rb:8:in `setup'

  7) Error:
ActiveRecord::ConnectionAdapters::ConnectionHandlerTest#test_retrieve_connection_pool_with_invalid_id:
NoMethodError: undefined method `configurations' for ActiveRecord::Base:Class
Did you mean?  configurations=
    org/jruby/RubyBasicObject.java:1654:in `method_missing'
    /home/yahonda/git/rails/activerecord/lib/active_record/dynamic_matchers.rb:21:in `method_missing'
    /home/yahonda/git/rails/activerecord/test/cases/connection_adapters/connection_handler_test.rb:8:in `setup'

156 runs, 940 assertions, 0 failures, 7 errors, 0 skips
$

Opened https://github.com/rbenv/ruby-build/pull/1028 to install jruby <IP_ADDRESS>-SNAPSHOT with ruby-build.

I am fairly certain 50.0 will fix this but I did not try.  @yahonda please try once released and re-open if so.  That is a little lame but we are very actively working on this now and many of these 5.x bugs were opened well before we started that work.

Great work to support Rails 5.0. I have tested it again and it still reproduces.
Here are steps to reproduce using rails-dev-box. It would be appreciated if you reopen it.

At Host

git clone -b runs_ar_jdbc https://github.com/yahonda/rails-dev-box.git
vagrant up
vagrant ssh

At Vagrant guest

git config --global url."https://".insteadOf git://
echo 'export ARJDBC=true' >> /home/ubuntu/.bashrc
. ./.bashrc
git clone https://github.com/rails/rails.git
cd rails/activerecord
git checkout 5-1-stable
bundle install
bin/test test/cases/fixtures_test.rb test/cases/tasks/database_tasks_test.rb test/cases/connection_adapters/connection_handler_test.rb --seed 40645

Output:

$ bin/test test/cases/fixtures_test.rb test/cases/tasks/database_tasks_test.rb test/cases/connection_adapters/connection_handler_test.rb
Using jdbcsqlite3
DEPRECATION WARNING: #table_exists? currently checks both tables and views. This behavior is deprecated and will be changed with Rails 5.1 to only check tables. Use #data_source_exists? instead. (called from <main> at bin/test:4)
/home/ubuntu/rails/activerecord/lib/active_record/internal_metadata.rb:26:in `table_exists?'
  /home/ubuntu/rails/activerecord/lib/active_record/internal_metadata.rb:31:in `create_table'
  /home/ubuntu/rails/activerecord/lib/active_record/schema.rb:55:in `define'
  /home/ubuntu/rails/activerecord/lib/active_record/schema.rb:44:in `define'
  /home/ubuntu/rails/activerecord/test/schema/schema.rb:1:in `<main>'
  /home/ubuntu/rails/activesupport/lib/active_support/dependencies.rb:1:in `load'
  /home/ubuntu/rails/activesupport/lib/active_support/dependencies.rb:1:in `block in (root)'
  /home/ubuntu/rails/activesupport/lib/active_support/dependencies.rb:258:in `load_dependency'
  /home/ubuntu/rails/activesupport/lib/active_support/dependencies.rb:286:in `load'
  /home/ubuntu/rails/activesupport/lib/active_support/dependencies.rb:286:in `load'
  /home/ubuntu/rails/activerecord/test/cases/helper.rb:139:in `<main>'
  /home/ubuntu/rails/activerecord/test/cases/helper.rb:148:in `require'
  /home/ubuntu/rails/activerecord/test/cases/helper.rb:148:in `<main>'
  /home/ubuntu/rails/activerecord/test/cases/fixtures_test.rb:1:in `require'
  /home/ubuntu/rails/activerecord/test/cases/fixtures_test.rb:1:in `block in (root)'
  /home/ubuntu/rails/activerecord/test/cases/fixtures_test.rb:1:in `each'
  /home/ubuntu/rails/activerecord/test/cases/fixtures_test.rb:1:in `(root)'
  /home/ubuntu/rails/railties/lib/rails/test_unit/runner.rb:1:in `(root)'
  /home/ubuntu/rails/railties/lib/rails/test_unit/runner.rb:50:in `<main>'
  /home/ubuntu/rails/railties/lib/rails/test_unit/runner.rb:50:in `require'
  /home/ubuntu/rails/railties/lib/rails/test_unit/runner.rb:50:in `load_tests'
  bin/test:4:in `<main>'
DEPRECATION WARNING: #table_exists? currently checks both tables and views. This behavior is deprecated and will be changed with Rails 5.1 to only check tables. Use #data_source_exists? instead. (called from <main> at bin/test:4)
/home/ubuntu/rails/activerecord/lib/active_record/internal_metadata.rb:26:in `table_exists?'
  /home/ubuntu/rails/activerecord/lib/active_record/attribute_methods.rb:163:in `attribute_names'
  /home/ubuntu/rails/activerecord/lib/active_record/attribute_methods.rb:62:in `block in define_attribute_methods'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/stdlib/mutex_m.rb:74:in `synchronize'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/stdlib/mutex_m.rb:74:in `mu_synchronize'
  /home/ubuntu/rails/activerecord/lib/active_record/attribute_methods.rb:59:in `define_attribute_methods'
  /home/ubuntu/rails/activerecord/lib/active_record/core.rb:154:in `allocate'
  /home/ubuntu/rails/activerecord/lib/active_record/persistence.rb:69:in `instantiate'
  /home/ubuntu/rails/activerecord/lib/active_record/querying.rb:50:in `block in find_by_sql'
  /home/ubuntu/rails/activerecord/lib/active_record/result.rb:55:in `block in each'
  /home/ubuntu/rails/activerecord/lib/active_record/result.rb:55:in `each'
  /home/ubuntu/rails/activerecord/lib/active_record/result.rb:55:in `each'
  /home/ubuntu/rails/activerecord/lib/active_record/querying.rb:50:in `map'
  /home/ubuntu/rails/activerecord/lib/active_record/querying.rb:50:in `block in find_by_sql'
  /home/ubuntu/rails/activesupport/lib/active_support/notifications/instrumenter.rb:21:in `instrument'
  /home/ubuntu/rails/activerecord/lib/active_record/querying.rb:49:in `find_by_sql'
  /home/ubuntu/rails/activerecord/lib/active_record/relation.rb:678:in `exec_queries'
  /home/ubuntu/rails/activerecord/lib/active_record/relation.rb:546:in `load'
  /home/ubuntu/rails/activerecord/lib/active_record/relation.rb:255:in `records'
  /home/ubuntu/rails/activerecord/lib/active_record/relation/finder_methods.rb:508:in `find_take'
  /home/ubuntu/rails/activerecord/lib/active_record/relation/finder_methods.rb:100:in `take'
  /home/ubuntu/rails/activerecord/lib/active_record/relation/finder_methods.rb:78:in `find_by'
  /home/ubuntu/rails/activerecord/lib/active_record/relation.rb:233:in `find_or_initialize_by'
  /home/ubuntu/rails/activerecord/lib/active_record/querying.rb:6:in `find_or_initialize_by'
  /home/ubuntu/rails/activerecord/lib/active_record/internal_metadata.rb:18:in `[]='
  /home/ubuntu/rails/activerecord/lib/active_record/schema.rb:56:in `define'
  /home/ubuntu/rails/activerecord/lib/active_record/schema.rb:44:in `define'
  /home/ubuntu/rails/activerecord/test/schema/schema.rb:1:in `<main>'
  /home/ubuntu/rails/activesupport/lib/active_support/dependencies.rb:1:in `load'
  /home/ubuntu/rails/activesupport/lib/active_support/dependencies.rb:1:in `block in (root)'
  /home/ubuntu/rails/activesupport/lib/active_support/dependencies.rb:258:in `load_dependency'
  /home/ubuntu/rails/activesupport/lib/active_support/dependencies.rb:286:in `load'
  /home/ubuntu/rails/activesupport/lib/active_support/dependencies.rb:286:in `load'
  /home/ubuntu/rails/activerecord/test/cases/helper.rb:139:in `<main>'
  /home/ubuntu/rails/activerecord/test/cases/helper.rb:148:in `require'
  /home/ubuntu/rails/activerecord/test/cases/helper.rb:148:in `<main>'
  /home/ubuntu/rails/activerecord/test/cases/fixtures_test.rb:1:in `require'
  /home/ubuntu/rails/activerecord/test/cases/fixtures_test.rb:1:in `block in (root)'
  /home/ubuntu/rails/activerecord/test/cases/fixtures_test.rb:1:in `each'
  /home/ubuntu/rails/activerecord/test/cases/fixtures_test.rb:1:in `(root)'
  /home/ubuntu/rails/railties/lib/rails/test_unit/runner.rb:1:in `(root)'
  /home/ubuntu/rails/railties/lib/rails/test_unit/runner.rb:50:in `<main>'
  /home/ubuntu/rails/railties/lib/rails/test_unit/runner.rb:50:in `require'
  /home/ubuntu/rails/railties/lib/rails/test_unit/runner.rb:50:in `load_tests'
  bin/test:4:in `<main>'
Run options: --seed 27441

# Running:

......................................................................................................EDEPRECATION WARNING: #table_exists? currently checks both tables and views. This behavior is deprecated and will be changed with Rails 5.1 to only check tables. Use #data_source_exists? instead. (called from block in run at /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:106)
/home/ubuntu/rails/activerecord/lib/active_record/internal_metadata.rb:26:in `table_exists?'
  /home/ubuntu/rails/activerecord/lib/active_record/migration.rb:1272:in `last_stored_environment'
  /home/ubuntu/rails/activerecord/lib/active_record/tasks/database_tasks.rb:56:in `check_protected_environments!'
  /home/ubuntu/rails/activerecord/test/cases/tasks/database_tasks_test.rb:35:in `test_raises_an_error_when_called_with_protected_environment'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:106:in `block in run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:204:in `capture_exceptions'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:103:in `block in run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:256:in `time_it'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:102:in `block in run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:317:in `on_signal'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:276:in `with_info_handler'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:101:in `run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:759:in `run_one_method'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:293:in `run_one_method'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:287:in `block in run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:286:in `each'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:286:in `block in run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:317:in `on_signal'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:306:in `with_info_handler'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:285:in `run'
  /home/ubuntu/rails/railties/lib/rails/test_unit/line_filtering.rb:9:in `run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:149:in `block in __run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:149:in `map'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:149:in `__run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:126:in `run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:55:in `block in autorun'
DEPRECATION WARNING: #table_exists? currently checks both tables and views. This behavior is deprecated and will be changed with Rails 5.1 to only check tables. Use #data_source_exists? instead. (called from block in run at /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:106)
/home/ubuntu/rails/activerecord/lib/active_record/internal_metadata.rb:26:in `table_exists?'
  /home/ubuntu/rails/activerecord/lib/active_record/migration.rb:1272:in `last_stored_environment'
  /home/ubuntu/rails/activerecord/lib/active_record/migration.rb:1284:in `protected_environment?'
  /home/ubuntu/rails/activerecord/lib/active_record/tasks/database_tasks.rb:58:in `check_protected_environments!'
  /home/ubuntu/rails/activerecord/test/cases/tasks/database_tasks_test.rb:35:in `test_raises_an_error_when_called_with_protected_environment'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:106:in `block in run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:204:in `capture_exceptions'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:103:in `block in run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:256:in `time_it'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:102:in `block in run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:317:in `on_signal'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:276:in `with_info_handler'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:101:in `run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:759:in `run_one_method'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:293:in `run_one_method'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:287:in `block in run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:286:in `each'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:286:in `block in run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:317:in `on_signal'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:306:in `with_info_handler'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:285:in `run'
  /home/ubuntu/rails/railties/lib/rails/test_unit/line_filtering.rb:9:in `run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:149:in `block in __run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:149:in `map'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:149:in `__run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:126:in `run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:55:in `block in autorun'
DEPRECATION WARNING: #table_exists? currently checks both tables and views. This behavior is deprecated and will be changed with Rails 5.1 to only check tables. Use #data_source_exists? instead. (called from block in run at /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:106)
/home/ubuntu/rails/activerecord/lib/active_record/internal_metadata.rb:26:in `table_exists?'
  /home/ubuntu/rails/activerecord/lib/active_record/migration.rb:1272:in `last_stored_environment'
  /home/ubuntu/rails/activerecord/lib/active_record/migration.rb:1284:in `protected_environment?'
  /home/ubuntu/rails/activerecord/lib/active_record/tasks/database_tasks.rb:58:in `check_protected_environments!'
  /home/ubuntu/rails/activerecord/test/cases/tasks/database_tasks_test.rb:35:in `test_raises_an_error_when_called_with_protected_environment'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:106:in `block in run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:204:in `capture_exceptions'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:103:in `block in run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:256:in `time_it'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:102:in `block in run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:317:in `on_signal'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:276:in `with_info_handler'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:101:in `run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:759:in `run_one_method'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:293:in `run_one_method'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:287:in `block in run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:286:in `each'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:286:in `block in run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:317:in `on_signal'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:306:in `with_info_handler'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:285:in `run'
  /home/ubuntu/rails/railties/lib/rails/test_unit/line_filtering.rb:9:in `run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:149:in `block in __run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:149:in `map'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:149:in `__run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:126:in `run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:55:in `block in autorun'
DEPRECATION WARNING: #table_exists? currently checks both tables and views. This behavior is deprecated and will be changed with Rails 5.1 to only check tables. Use #data_source_exists? instead. (called from assert_raises at /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/assertions.rb:293)
/home/ubuntu/rails/activerecord/lib/active_record/internal_metadata.rb:26:in `table_exists?'
  /home/ubuntu/rails/activerecord/lib/active_record/migration.rb:1272:in `last_stored_environment'
  /home/ubuntu/rails/activerecord/lib/active_record/tasks/database_tasks.rb:56:in `check_protected_environments!'
  /home/ubuntu/rails/activerecord/test/cases/tasks/database_tasks_test.rb:39:in `block in test_raises_an_error_when_called_with_protected_environment'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/assertions.rb:293:in `assert_raises'
  /home/ubuntu/rails/activerecord/test/cases/tasks/database_tasks_test.rb:38:in `test_raises_an_error_when_called_with_protected_environment'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:106:in `block in run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:204:in `capture_exceptions'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:103:in `block in run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:256:in `time_it'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:102:in `block in run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:317:in `on_signal'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:276:in `with_info_handler'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:101:in `run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:759:in `run_one_method'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:293:in `run_one_method'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:287:in `block in run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:286:in `each'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:286:in `block in run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:317:in `on_signal'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:306:in `with_info_handler'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:285:in `run'
  /home/ubuntu/rails/railties/lib/rails/test_unit/line_filtering.rb:9:in `run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:149:in `block in __run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:149:in `map'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:149:in `__run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:126:in `run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:55:in `block in autorun'
DEPRECATION WARNING: #table_exists? currently checks both tables and views. This behavior is deprecated and will be changed with Rails 5.1 to only check tables. Use #data_source_exists? instead. (called from assert_raises at /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/assertions.rb:293)
/home/ubuntu/rails/activerecord/lib/active_record/internal_metadata.rb:26:in `table_exists?'
  /home/ubuntu/rails/activerecord/lib/active_record/migration.rb:1272:in `last_stored_environment'
  /home/ubuntu/rails/activerecord/lib/active_record/migration.rb:1284:in `protected_environment?'
  /home/ubuntu/rails/activerecord/lib/active_record/tasks/database_tasks.rb:58:in `check_protected_environments!'
  /home/ubuntu/rails/activerecord/test/cases/tasks/database_tasks_test.rb:39:in `block in test_raises_an_error_when_called_with_protected_environment'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/assertions.rb:293:in `assert_raises'
  /home/ubuntu/rails/activerecord/test/cases/tasks/database_tasks_test.rb:38:in `test_raises_an_error_when_called_with_protected_environment'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:106:in `block in run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:204:in `capture_exceptions'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:103:in `block in run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:256:in `time_it'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:102:in `block in run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:317:in `on_signal'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:276:in `with_info_handler'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:101:in `run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:759:in `run_one_method'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:293:in `run_one_method'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:287:in `block in run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:286:in `each'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:286:in `block in run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:317:in `on_signal'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:306:in `with_info_handler'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:285:in `run'
  /home/ubuntu/rails/railties/lib/rails/test_unit/line_filtering.rb:9:in `run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:149:in `block in __run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:149:in `map'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:149:in `__run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:126:in `run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:55:in `block in autorun'
DEPRECATION WARNING: #table_exists? currently checks both tables and views. This behavior is deprecated and will be changed with Rails 5.1 to only check tables. Use #data_source_exists? instead. (called from assert_raises at /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/assertions.rb:293)
/home/ubuntu/rails/activerecord/lib/active_record/internal_metadata.rb:26:in `table_exists?'
  /home/ubuntu/rails/activerecord/lib/active_record/migration.rb:1272:in `last_stored_environment'
  /home/ubuntu/rails/activerecord/lib/active_record/migration.rb:1284:in `protected_environment?'
  /home/ubuntu/rails/activerecord/lib/active_record/tasks/database_tasks.rb:58:in `check_protected_environments!'
  /home/ubuntu/rails/activerecord/test/cases/tasks/database_tasks_test.rb:39:in `block in test_raises_an_error_when_called_with_protected_environment'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/assertions.rb:293:in `assert_raises'
  /home/ubuntu/rails/activerecord/test/cases/tasks/database_tasks_test.rb:38:in `test_raises_an_error_when_called_with_protected_environment'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:106:in `block in run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:204:in `capture_exceptions'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:103:in `block in run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:256:in `time_it'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:102:in `block in run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:317:in `on_signal'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:276:in `with_info_handler'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:101:in `run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:759:in `run_one_method'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:293:in `run_one_method'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:287:in `block in run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:286:in `each'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:286:in `block in run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:317:in `on_signal'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:306:in `with_info_handler'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:285:in `run'
  /home/ubuntu/rails/railties/lib/rails/test_unit/line_filtering.rb:9:in `run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:149:in `block in __run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:149:in `map'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:149:in `__run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:126:in `run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:55:in `block in autorun'
......EE.......................DEPRECATION WARNING: #table_exists? currently checks both tables and views. This behavior is deprecated and will be changed with Rails 5.1 to only check tables. Use #data_source_exists? instead. (called from block in run at /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:106)
/home/ubuntu/rails/activerecord/lib/active_record/schema_migration.rb:20:in `table_exists?'
  /home/ubuntu/rails/activerecord/lib/active_record/schema_migration.rb:24:in `create_table'
  /home/ubuntu/rails/activerecord/lib/active_record/migration.rb:1125:in `initialize'
  /home/ubuntu/rails/activerecord/lib/active_record/migration.rb:1007:in `up'
  /home/ubuntu/rails/activerecord/lib/active_record/migration.rb:985:in `migrate'
  /home/ubuntu/rails/activerecord/lib/active_record/tasks/database_tasks.rb:171:in `migrate'
  /home/ubuntu/rails/activerecord/test/cases/tasks/database_tasks_test.rb:364:in `test_migrate_clears_schema_cache_afterward'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:106:in `block in run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:204:in `capture_exceptions'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:103:in `block in run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:256:in `time_it'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:102:in `block in run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:317:in `on_signal'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:276:in `with_info_handler'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:101:in `run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:759:in `run_one_method'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:293:in `run_one_method'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:287:in `block in run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:286:in `each'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:286:in `block in run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:317:in `on_signal'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:306:in `with_info_handler'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:285:in `run'
  /home/ubuntu/rails/railties/lib/rails/test_unit/line_filtering.rb:9:in `run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:149:in `block in __run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:149:in `map'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:149:in `__run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:126:in `run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:55:in `block in autorun'
DEPRECATION WARNING: #table_exists? currently checks both tables and views. This behavior is deprecated and will be changed with Rails 5.1 to only check tables. Use #data_source_exists? instead. (called from block in run at /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:106)
/home/ubuntu/rails/activerecord/lib/active_record/internal_metadata.rb:26:in `table_exists?'
  /home/ubuntu/rails/activerecord/lib/active_record/internal_metadata.rb:31:in `create_table'
  /home/ubuntu/rails/activerecord/lib/active_record/migration.rb:1126:in `initialize'
  /home/ubuntu/rails/activerecord/lib/active_record/migration.rb:1007:in `up'
  /home/ubuntu/rails/activerecord/lib/active_record/migration.rb:985:in `migrate'
  /home/ubuntu/rails/activerecord/lib/active_record/tasks/database_tasks.rb:171:in `migrate'
  /home/ubuntu/rails/activerecord/test/cases/tasks/database_tasks_test.rb:364:in `test_migrate_clears_schema_cache_afterward'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:106:in `block in run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:204:in `capture_exceptions'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:103:in `block in run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:256:in `time_it'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:102:in `block in run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:317:in `on_signal'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:276:in `with_info_handler'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest/test.rb:101:in `run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:759:in `run_one_method'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:293:in `run_one_method'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:287:in `block in run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:286:in `each'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:286:in `block in run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:317:in `on_signal'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:306:in `with_info_handler'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:285:in `run'
  /home/ubuntu/rails/railties/lib/rails/test_unit/line_filtering.rb:9:in `run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:149:in `block in __run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:149:in `map'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:149:in `__run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:126:in `run'
  /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/minitest-5.3.3/lib/minitest.rb:55:in `block in autorun'
......................EEEEEEEEE

Finished in 16.281029s, 10.1345 runs/s, 58.4115 assertions/s.

  1) Error:
ActiveRecord::DatabaseTasksUtilsTask#test_raises_an_error_if_no_migrations_have_been_made:
NameError: undefined method `current_version' for class `#<Class:0x2b3ba0a8>'
    org/jruby/RubyModule.java:2707:in `public'
    org/jruby/RubyMethod.java:115:in `call'
    /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/mocha-0.14.0/lib/mocha/class_method.rb:80:in `restore_original_method'
    /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/mocha-0.14.0/lib/mocha/class_method.rb:22:in `unstub'
    /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/mocha-0.14.0/lib/mocha/central.rb:20:in `unstub'
    /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/mocha-0.14.0/lib/mocha/central.rb:27:in `unstub_all'
    /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/mocha-0.14.0/lib/mocha/mockery.rb:74:in `teardown'
    /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/mocha-0.14.0/lib/mocha/mockery.rb:25:in `teardown'
    /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/mocha-0.14.0/lib/mocha/hooks.rb:39:in `mocha_teardown'
    /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/mocha-0.14.0/lib/mocha/integration/mini_test/adapter.rb:48:in `after_teardown'
    /home/ubuntu/rails/activesupport/lib/active_support/testing/setup_and_teardown.rb:46:in `after_teardown'
    /home/ubuntu/rails/activerecord/lib/active_record/fixtures.rb:856:in `after_teardown'

  2) Error:
ActiveRecord::DatabaseTasksDumpSchemaCacheTest#test_dump_schema_cache:
NoMethodError: undefined method `current_version' for ActiveRecord::Migrator:Class
Did you mean?  current_environment
    org/jruby/RubyBasicObject.java:1657:in `method_missing'
    /home/ubuntu/rails/activerecord/lib/active_record/connection_adapters/schema_cache.rb:29:in `encode_with'
    /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/stdlib/psych/visitors/yaml_tree.rb:562:in `dump_coder'
    /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/stdlib/psych/visitors/yaml_tree.rb:161:in `accept'
    /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/stdlib/psych/visitors/yaml_tree.rb:127:in `push'
    /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/stdlib/psych.rb:416:in `dump'
    /home/ubuntu/rails/activerecord/lib/active_record/tasks/database_tasks.rb:285:in `block in dump_schema_cache'
    org/jruby/RubyIO.java:1156:in `open'
    org/jruby/RubyKernel.java:306:in `open'
    /home/ubuntu/rails/activerecord/lib/active_record/tasks/database_tasks.rb:285:in `dump_schema_cache'
    /home/ubuntu/rails/activerecord/test/cases/tasks/database_tasks_test.rb:91:in `test_dump_schema_cache'

  3) Error:
ActiveRecord::DatabaseTasksCreateAllTest#test_creates_configurations_with_blank_hosts:
NameError: undefined method `configurations' for class `#<Class:0x14dbfdb1>'
    org/jruby/RubyModule.java:2707:in `public'
    org/jruby/RubyMethod.java:115:in `call'
    /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/mocha-0.14.0/lib/mocha/class_method.rb:80:in `restore_original_method'
    /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/mocha-0.14.0/lib/mocha/class_method.rb:22:in `unstub'
    /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/mocha-0.14.0/lib/mocha/central.rb:20:in `unstub'
    /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/mocha-0.14.0/lib/mocha/central.rb:27:in `unstub_all'
    /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/mocha-0.14.0/lib/mocha/mockery.rb:74:in `teardown'
    /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/mocha-0.14.0/lib/mocha/mockery.rb:25:in `teardown'
    /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/mocha-0.14.0/lib/mocha/hooks.rb:39:in `mocha_teardown'
    /home/ubuntu/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/shared/gems/mocha-0.14.0/lib/mocha/integration/mini_test/adapter.rb:48:in `after_teardown'
    /home/ubuntu/rails/activesupport/lib/active_support/testing/setup_and_teardown.rb:46:in `after_teardown'
    /home/ubuntu/rails/activerecord/lib/active_record/fixtures.rb:856:in `after_teardown'

  4) Error:
ActiveRecord::ConnectionAdapters::ConnectionHandlerTest#test_retrieve_connection_pool:
NoMethodError: undefined method `configurations' for ActiveRecord::Base:Class
Did you mean?  configurations=
    org/jruby/RubyBasicObject.java:1657:in `method_missing'
    /home/ubuntu/rails/activerecord/lib/active_record/dynamic_matchers.rb:22:in `method_missing'
    /home/ubuntu/rails/activerecord/test/cases/connection_adapters/connection_handler_test.rb:9:in `setup'

  5) Error:
ActiveRecord::ConnectionAdapters::ConnectionHandlerTest#test_establish_connection_using_3_levels_config:
NoMethodError: undefined method `configurations' for ActiveRecord::Base:Class
Did you mean?  configurations=
    org/jruby/RubyBasicObject.java:1657:in `method_missing'
    /home/ubuntu/rails/activerecord/lib/active_record/dynamic_matchers.rb:22:in `method_missing'
    /home/ubuntu/rails/activerecord/test/cases/connection_adapters/connection_handler_test.rb:9:in `setup'

  6) Error:
ActiveRecord::ConnectionAdapters::ConnectionHandlerTest#test_retrieve_connection_pool_with_invalid_id:
NoMethodError: undefined method `configurations' for ActiveRecord::Base:Class
Did you mean?  configurations=
    org/jruby/RubyBasicObject.java:1657:in `method_missing'
    /home/ubuntu/rails/activerecord/lib/active_record/dynamic_matchers.rb:22:in `method_missing'
    /home/ubuntu/rails/activerecord/test/cases/connection_adapters/connection_handler_test.rb:9:in `setup'

  7) Error:
ActiveRecord::ConnectionAdapters::ConnectionHandlerTest#test_establish_connection_using_top_level_key_in_two_level_config:
NoMethodError: undefined method `configurations' for ActiveRecord::Base:Class
Did you mean?  configurations=
    org/jruby/RubyBasicObject.java:1657:in `method_missing'
    /home/ubuntu/rails/activerecord/lib/active_record/dynamic_matchers.rb:22:in `method_missing'
    /home/ubuntu/rails/activerecord/test/cases/connection_adapters/connection_handler_test.rb:9:in `setup'

  8) Error:
ActiveRecord::ConnectionAdapters::ConnectionHandlerTest#test_retrieve_connection:
NoMethodError: undefined method `configurations' for ActiveRecord::Base:Class
Did you mean?  configurations=
    org/jruby/RubyBasicObject.java:1657:in `method_missing'
    /home/ubuntu/rails/activerecord/lib/active_record/dynamic_matchers.rb:22:in `method_missing'
    /home/ubuntu/rails/activerecord/test/cases/connection_adapters/connection_handler_test.rb:9:in `setup'

  9) Error:
ActiveRecord::ConnectionAdapters::ConnectionHandlerTest#test_establish_connection_uses_spec_name:
NoMethodError: undefined method `configurations' for ActiveRecord::Base:Class
Did you mean?  configurations=
    org/jruby/RubyBasicObject.java:1657:in `method_missing'
    /home/ubuntu/rails/activerecord/lib/active_record/dynamic_matchers.rb:22:in `method_missing'
    /home/ubuntu/rails/activerecord/test/cases/connection_adapters/connection_handler_test.rb:9:in `setup'

 10) Error:
ActiveRecord::ConnectionAdapters::ConnectionHandlerTest#test_establish_connection_using_two_level_configurations:
NoMethodError: undefined method `configurations' for ActiveRecord::Base:Class
Did you mean?  configurations=
    org/jruby/RubyBasicObject.java:1657:in `method_missing'
    /home/ubuntu/rails/activerecord/lib/active_record/dynamic_matchers.rb:22:in `method_missing'
    /home/ubuntu/rails/activerecord/test/cases/connection_adapters/connection_handler_test.rb:9:in `setup'

 11) Error:
ActiveRecord::ConnectionAdapters::ConnectionHandlerTest#test_active_connections?:
NoMethodError: undefined method `configurations' for ActiveRecord::Base:Class
Did you mean?  configurations=
    org/jruby/RubyBasicObject.java:1657:in `method_missing'
    /home/ubuntu/rails/activerecord/lib/active_record/dynamic_matchers.rb:22:in `method_missing'
    /home/ubuntu/rails/activerecord/test/cases/connection_adapters/connection_handler_test.rb:9:in `setup'

 12) Error:
ActiveRecord::ConnectionAdapters::ConnectionHandlerTest#test_connection_pools:
NoMethodError: undefined method `configurations' for ActiveRecord::Base:Class
Did you mean?  configurations=
    org/jruby/RubyBasicObject.java:1657:in `method_missing'
    /home/ubuntu/rails/activerecord/lib/active_record/dynamic_matchers.rb:22:in `method_missing'
    /home/ubuntu/rails/activerecord/test/cases/connection_adapters/connection_handler_test.rb:9:in `setup'

165 runs, 951 assertions, 0 failures, 12 errors, 0 skips
$


Add vcpkg installation instructions

liburing is available as a port in vcpkg, a C++ library manager that simplifies installation for liburing and other project dependencies. Documenting the install process here will help users get started by providing a single set of commands to build liburing, ready to be included in their projects.
We also test whether our library ports build in various configurations (dynamic, static) on various platforms (OSX, Linux, Windows: x86, x64) to keep a wide coverage for users.
I'm a maintainer for vcpkg, and here is what the port script looks like. We try to keep the library maintained as close as possible to the original library. :)

Please follow the pull request guidelines.

@JonLiu1993 Can you update the commit?

Closing due to inactivity.


Handling of follow-up scripts

It looks like we have special follow-up analysis scripting here for the error injection.
It would be nice to make such a thing more generic, either by moving this into the flow class as an extra analysis step, or being able to specify an analysis script in the yaml file.

Actually, I've added this as part of the code refactor in #360


Delay when switching to normal mode

Description
When I switch from normal mode to other modes(insert, visual etc.) the label and color in the mode component switches instantly but when I switch back to normal mode there's about a 500ms delay before the label and color changes in the mode component. Is this a bug or is it intentional?

Try set ttimeout ttimeoutlen=50 if it improves.

Yea, probably a delay after an , waiting to see if there any any more keystrokes arriving ?
As @itchyny said above you can adjust that some in vim.

yes that improved it, thank you.


Finished Headline section

Headline title
Headline description
social media icons

hey @mirouhml thanks for the heads up, fixed the readme file please have another look

hey @mirouhml, already did that


Edozwo 745 rev8

perfect & tested on edoweb

contains EDOZWO-745-rev8

minor points are addressed in a new ticket EDOZWO-753


Fix Deprecations for Symfony 4.2

Thank you for the PR.
Could you git squash yours commits.
Thanks

Like that? Never done this before.

No nott live that, I will do it :)

Closed in favor of : https://github.com/NAYZO/NzoUrlEncryptorBundle/pull/35


Crashes on Windows

On Windows 10, 64-bit, GHC 8.10.7
If using formatting version 6.3.7 this small program works. It prints "Hello" and "Tre: 3".
{-# LANGUAGE OverloadedStrings #-}

module Main where

import qualified Formatting   as F
import  Formatting            ((%))

main :: IO ()
main = do
  putStrLn "Hello"
  F.fprint ("Tre: " % F.int) 3

If using formatting 7.0.0 or 7.1.3 it crashes. It doesn't write "Hello" or "Tre: 3".

This seems very surprising! Can you give any more information?
Is anyone else experiencing this problem?

Some more info
All versions runs in a REPL.

cabal repl
Resolving dependencies...
Build profile: -w ghc-8.10.7 -O1
In order, the following will be built (use -v for more details):

TestFormatting-<IP_ADDRESS> (exe:TestFormatting) (configuration changed)
Configuring executable 'TestFormatting' for TestFormatting-<IP_ADDRESS>..
Preprocessing executable 'TestFormatting' for TestFormatting-<IP_ADDRESS>..
GHCi, version 8.10.7: https://www.haskell.org/ghc/  :? for help
[1 of 1] Compiling Main             ( Main.hs, interpreted ) [Formatting changed]
Ok, one module loaded.
*Main> main
Hello, Haskell!
Tre: 3
*Main> :q
Leaving GHCi.

If using formatting 7.0.0 and GHC 8.10.7 this crashes without printing anything.
someFormatting :: IO ()
someFormatting = F.fprint ("Tre: " % F.int % "\n") (3::Int)

main :: IO ()
main = do
  putStrLn "Hello, Haskell!"

If using GHC 9.2.5 it still ends without any output.
It doesn't matter if I build with -O1 or -O2.
If I build with a function that is using formatting, e.g.
someFormatting = F.fprint ("Tre: " % F.int % "\n") (3::Int)

It ends with no output even if I don't call the function.
If I remove the function from the program it works OK.

If trying to run the executable inside the debugger WinDbg I get this error: The application was unable to start correctly (0xc000007b).

If looking at the dependencies of the executable I can see that "libstdc++-6.dll" is a dependency when when building against formatting 7.0.0 and not when building with 6.3.7. I have many versions of that dll on my system so I copied "C:\ghcup\ghc\8.10.7\mingw\bin\libstdc++-6.dll" to the same directory as the built executable but it still didn't work.

If building formatting with 'no-double-conversion' set to True  everything works fine.

I have now tested with double-conversion package and there is some strange linking problem. If using a MSYS2/MinGW64 shell I can get it to work on one of my machines. From Windows GUI or PowerShell it doesn't work. There are other reports of linking problems on Windows: https://gitlab.haskell.org/ghc/ghc/-/issues/20010.

@gussen You mentioned GHC 9.2.x. Note that versions 9.2 and before of GHC had problems on Windows, which is why everything was rewritten to use Clang. See release notes:

A complete overhaul of GHC’s Windows support. This includes a migration to a fully Clang-based C toolchain, a deep refactoring of the linker, and many fixes in WinIO.

It might work better on GHC 9.4. Note that to use double-conversion on 9.4, you need to use it from git, since a compatible release wasn't yet released.


Wrong SQL with preload and optional association? WHERE id IN ('', '')

I made a reproduction script below.
The last command runs the following SQL with IN ('<nil>'). Also see this with PostgreSQL.
SELECT * FROM "authors"  WHERE "authors".deleted_at IS NULL AND (("id" IN ('1','<nil>','<nil>','<nil>')))

I also see '<nil>' in the INSERT for DeletedAt:
INSERT INTO "authors" ("created_at","updated_at","deleted_at","name") VALUES ('2016-03-28T15:48:55-03:00','2016-03-28T15:48:55-03:00','<nil>','John Due')

The script:
package main

import (
	"database/sql"
	"os"

	"github.com/jinzhu/gorm"
	_ "github.com/jinzhu/gorm/dialects/sqlite"
)

type Author struct {
	gorm.Model
	Name string
}

type Post struct {
	gorm.Model
	Title    string
	AuthorId sql.NullInt64
	Author   Author
}

func main() {
	os.Remove("test.sqlite3")

	db, err := gorm.Open("sqlite3", "test.sqlite3")
	if err != nil {
		panic(err)
	}

	db.LogMode(true)

	db.AutoMigrate(&Author{})
	db.AutoMigrate(&Post{})

	db.Create(&Author{Name: "John Due"})
	db.Create(&Post{Title: "Post 1", AuthorId: sql.NullInt64{Int64: 1, Valid: true}})
	db.Create(&Post{Title: "Post 2"})
	db.Create(&Post{Title: "Post 3"})
	db.Create(&Post{Title: "Post 4"})

	db.Preload("Author").Find(&[]Post{})
}

The log:
[138.10ms]  CREATE TABLE "authors" ("id" integer primary key autoincrement,"created_at" datetime,"updated_at" datetime,"deleted_at" datetime,"name" varchar(255) )

[80.07ms]  CREATE INDEX idx_authors_deleted_at ON "authors"(deleted_at)

[78.07ms]  CREATE TABLE "posts" ("id" integer primary key autoincrement,"created_at" datetime,"updated_at" datetime,"deleted_at" datetime,"title" varchar(255),"author_id" bigint )

[79.06ms]  CREATE INDEX idx_posts_deleted_at ON "posts"(deleted_at)

[1.97ms]  INSERT INTO "authors" ("created_at","updated_at","deleted_at","name") VALUES ('2016-03-28T15:48:55-03:00','2016-03-28T15:48:55-03:00','<nil>','John Due')

[4.97ms]  INSERT INTO "posts" ("created_at","updated_at","deleted_at","title","author_id") VALUES ('2016-03-28T15:48:55-03:00','2016-03-28T15:48:55-03:00','<nil>','Post 1','1')

[2.00ms]  INSERT INTO "posts" ("created_at","updated_at","deleted_at","title","author_id") VALUES ('2016-03-28T15:48:55-03:00','2016-03-28T15:48:55-03:00','<nil>','Post 2',NULL)

[0.97ms]  INSERT INTO "posts" ("created_at","updated_at","deleted_at","title","author_id") VALUES ('2016-03-28T15:48:55-03:00','2016-03-28T15:48:55-03:00','<nil>','Post 3',NULL)

[2.00ms]  INSERT INTO "posts" ("created_at","updated_at","deleted_at","title","author_id") VALUES ('2016-03-28T15:48:55-03:00','2016-03-28T15:48:55-03:00','<nil>','Post 4',NULL)

[1.02ms]  SELECT * FROM "posts"  WHERE "posts".deleted_at IS NULL

[2.97ms]  SELECT * FROM "authors"  WHERE "authors".deleted_at IS NULL AND (("id" IN ('1','<nil>','<nil>','<nil>')))

duplicated with #854


adding bootstrap class support

Modified the scss in the formGroup.vue file to target elements that do not have a class that starts with 'col-' and set their width to 100%. Removed 'width:100%' from the form-group selector.

Please check if the PR fulfills these requirements

[ ] The commit message follows our guidelines
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

What is the current behavior? (You can also link to an open issue here)

What is the new behavior (if this is a feature change)?

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

Other information:

Hello @averagejoe77 , thank you for your PR !

Hello @averagejoe77 , thank you for your PR !

I am sorry I thought you guys would have tested and run the build before this got merged. I only updated the .vue file but did not run the build.
The latest branch (2.3.0) with this PR merged in does not contain the actual change in the css file.
Do you want me to create a new PR with the actual css files getting updated?

@averagejoe77 Travis CI should have handled that - looks like something went wrong.
@lionel-bijaoui have any thoughts?

@zoul0813 See https://github.com/vue-generators/vue-form-generator/issues/472#issuecomment-425822612

Yep - I’ll correct that with 2.3.1, sorry about that.


Admin Dashboard for GeotagX-sourcerer-sink

A admin dashboard for GeotagX-sourcerer-sink to let admins select which images go in and which do not.
And also, a neat way to look at all categories of sourced images.

Reference : https://github.com/geotagx/pybossa/commit/c64de59674718a2e74b4fbd3d6a62069b4ffac20
Important changes to the internal geotagx-sourcerer-sink redis data structure to facilitate support for the admin dashboard


[api] Simplify hash matching in specs

This was motivated by a couple of things:

Delete some code. Since RSpec 3 brings better support for hash
matching, we can just use its include and composable matchers instead
of traversing the hash and making multiple expectations on each pair.

Better failure messages. Before, missing keys resulted in a message
like "expected true, got false". An unmatched value would show up, but
may not be obvious what it was referring to. Now failures will show a
diff of actual and expected values.

Before:

After:

(Incidentally, the diff appears to be wrong here, but that could be an issue with RSpec)
@abellotti please review

Confirming the issue with the diff output: https://github.com/rspec/rspec-expectations/issues/887 (but still better than no diff)

Would prefer if the a_string_matching is done in expect_result_to_match_hash method so we don't have to change all the callers.  i.e. update the hash values for href and *_href before calling expect(...).to include(...).  So only one change needed and easier to change to something else later.

@abellotti incorporated your suggestion - let me know what you think and I'll squash everything

LGTM!! waiting for :white_check_mark:


Submitting an application should be simplified

Story
Parent Issue
Submitting an application should not spawn a process

We now use URLClassloader to submit an application.


The presence of "dark" key in checkout_options array throws error.

Lemon Squeezy for Laravel Version
1.6.2
Laravel Version
11.22.0
PHP Version
8.3.10
Description
The "dark" key in checkout_options array throws the error: "The checkout options field must be an array."
If I comment out this line : 'dark' =>  true,   it works.
I tried two other projects. Does the same.
Steps To Reproduce
In Checkout.php :
'checkout_options' => array_filter([
                        'embed' => $this->embed,
                        'logo' => $this->logo,
                        'media' => $this->media,
                        'desc' => $this->desc,
                        'discount' => $this->discount,
                        'dark' =>  true,  // this line causes the error
                        'subscription_preview' => $this->subscriptionPreview,
                        'button_color' => $this->buttonColor ?? null,
                    ], function ($value) {
                        return ! is_null($value);
                    }),

I don't get an error with:
$checkout = request()->user()->checkout('38223')->dark()->redirectTo(url('/'));

Works fine for me except the dark mode isn't showing. But it seems to be because it's a deprecated option:

So I think you should just avoid this one.

I'm sure it was an error on their side because it started working one hour later on all my sites after I tweeted about it.


Remove attribute types from account API

We are simplifying account API and removing the local attribute type.
This means it will only store what were previously cached attributes
(those provided by the IDP), and therefore aren't allowed to be changed
by any GOV.UK app.
Remove the pact test that tries to set an attribute in preparation for
this.

JIRA

You can see the pact tests passing against the updated branch of account API here: https://ci.integration.publishing.service.gov.uk/job/gds-api-adapters/job/GUA-122_remove_account_api_attribute_types/3/


Network Error while fetching from api

Hello there, i think i am as uptodate as possible but i still get network errors while trying to fetch my gems.
% bundle version
Bundler version 1.16.1 (2017-12-21 commit 0034ef341)
% gem update --system 2.6.14
Latest version currently installed. Aborting.
% bundle install
Fetching gem metadata from https://rails-assets.org/..
Retrying dependency api due to error (2/4): Bundler::HTTPError Network error while fetching https://rails-assets.org/api/v1/dependencies?gems=rails-assets-colorbox%2Crails-assets-jquery-fullscreen%2Crails-assets-jquery-ui%2Crails-assets-popper.js%2Crails-assets-strophe.js%2Crails-assets-strophejs%2Crails-assets-sualko--strophejs-plugins%2Crails-assets-tether (too many connection resets (due to Net::ReadTimeout - Net::ReadTimeout) after 7 requests on<PHONE_NUMBER>1360, last used 20.221591058 seconds ago)

i can curl against the api with success when i cut the request url down a bit just as being not uptodate enough (as i understood from reading).
being a bit out of ideas here so it may be a new bug?

I figured that the gems are now fetched after the network errors - dunno if this can be closed as there are still errors.

I think what's happening here is that bundler is having trouble connecting to the rails assets site, (too many connection resets (due to Net::ReadTimeout - Net::ReadTimeout) ...

I think the errors I get while running bundle install are related to this issue:
Fetching gem metadata from https://rails-assets.org/..
Retrying dependency api due to error (2/4): Bundler::HTTPError Network error while fetching https://rails-assets.org/api/v1/dependencies?gems=rails-assets-jquery-1.11.0%2Crails-assets-popper.js%2Crails-assets-tether (too many connection resets (due to Net::ReadTimeout - Net::ReadTimeout) after 3 requests on<PHONE_NUMBER>4720, last used 20.297687 seconds ago)
Retrying dependency api due to error (3/4): Bundler::HTTPError Network error while fetching https://rails-assets.org/api/v1/dependencies?gems=rails-assets-jquery-1.11.0%2Crails-assets-popper.js%2Crails-assets-tether (too many connection resets (due to Net::ReadTimeout - Net::ReadTimeout) after 0 requests on<PHONE_NUMBER>4720, last used 20.877113 seconds ago)
Retrying dependency api due to error (4/4): Bundler::HTTPError Network error while fetching https://rails-assets.org/api/v1/dependencies?gems=rails-assets-jquery-1.11.0%2Crails-assets-popper.js%2Crails-assets-tether (too many connection resets (due to Net::ReadTimeout - Net::ReadTimeout) after 0 requests on<PHONE_NUMBER>4720, last used 20.946988 seconds ago)

Fetching gem metadata from https://rubygems.org/........
Fetching git://github.com/ferhatsb/data-confirm-modal.git
Fetching gem metadata from https://rails-assets.org/..
Retrying dependency api due to error (2/4): Bundler::HTTPError Network error while fetching https://rails-assets.org/api/v1/dependencies?gems=rails-assets-jquery-1.11.0%2Crails-assets-popper.js%2Crails-assets-tether (too many connection resets (due to Net::ReadTimeout - Net::ReadTimeout) after 5 requests on<PHONE_NUMBER>4720, last used 20.298961 seconds ago)
Retrying dependency api due to error (3/4): Bundler::HTTPError Network error while fetching https://rails-assets.org/api/v1/dependencies?gems=rails-assets-jquery-1.11.0%2Crails-assets-popper.js%2Crails-assets-tether (too many connection resets (due to Net::ReadTimeout - Net::ReadTimeout) after 0 requests on<PHONE_NUMBER>4720, last used 21.260334 seconds ago)
Retrying dependency api due to error (4/4): Bundler::HTTPError Network error while fetching https://rails-assets.org/api/v1/dependencies?gems=rails-assets-jquery-1.11.0%2Crails-assets-popper.js%2Crails-assets-tether (too many connection resets (due to Net::ReadTimeout - Net::ReadTimeout) after 0 requests on<PHONE_NUMBER>4720, last used 20.934134 seconds ago)


Locale configuartion at dev and build time

This allows the developer to continue testing in all the locales available but the input get hidden when taken for production

Coverage remained the same at 55.002% when pulling 3f766a3b7e15afbbed6c10fa86b0649766622480 on ningosi:master into 1b023bd1f134e2148f7ed828ff7d14e984403ab8 on esaude:master.

 1.1.1. Make of Portuguese the defauld language, and desalow language change in the login page


[WIP] Add descriptions of source compatible and binary compatible changes

Fixes #3717
Changes in this PR:
Add article that defines source breaking change and binary breaking change when using new language features in a library.  This is ready for a thorough review to make sure I've expressed the concepts in the above issue correctly, and in a manner that is useful.
Add note about compatibility on some feature descriptions in what's new articles.  This is the second pass of the review, if the concepts are described correctly. I took the following strategy:

Only add a note on features that could be part of the public API surface for a type. Other feature descriptions have not been updated. My choice is somewhat subjective. For example, I did not say anything on the feature for new syntax for numeric literals. A numeric literal could be used for a default value of an argument, but that seemed a stretch, and not useful information to add. This PR adds notes when a new feature appears in a member's signature (except for expression bodied members where there have been customer questions).
I tried to be concise in calling this out, but still accurate. Question for reviewers: Does that make any of the notes misleading?

The discussion on the issue referenced has examples and details that will be helpful for reviewers.
/cc @jcouv @jaredpar @jonskeet (who wrote the comment for the original issue)
internal review link - new article
update - what's new in 6
update - what's new in 7
update - what's new in 7.2
update - what's new in 7.3
What's new in 7.1 was not updated.

Thanks @rpetrusha and @pkulikov
I've udpated with changes that address all the comments.


Fix missing plug-ins in audacity

Motivation for this change
The share/audacity/plug-ins directory was missing, because the audacity project changed to cmake.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Please match the PR title and the commit message title to something like:
audacity: use cmake to fix missing plugins

Result of nixpkgs-review pr 107465 run on x86_64-darwin 1

Result of nixpkgs-review pr 107465 run on x86_64-linux 1

1 package built:

audacity

Result of nixpkgs-review pr 107465 run on x86_64-linux 1

1 package built:

audacity

https://github.com/NixOS/nixpkgs/pull/97370


no_std + alloc Boilerplate

Mostly the error type
alloc via feature that extern crate alloc
heapless via feature that brings heapless types
std is usually a default feature (when needed) or usually non-default that can be activated for std error type
error type is making it's way into core though and there is also core-error crate

e.g.

https://github.com/khonsulabs/justjson/commit/968b7860d7263a283f87f104d14109cff33c371a
https://github.com/khonsulabs/justjson/commit/da7c03cf0719f052d562c0f691c27ed1c320d3d4
https://github.com/khonsulabs/justjson/commit/330dbd6e1c0aee775a4d527025dca3a381e4f17e
https://github.com/khonsulabs/justjson/commit/346548569b214138d4177d0e00960a752de27082
https://github.com/fission-codes/hexxo/commit/982ac3ceb44dc50abd4e7be96c34f75d589b0318

Also thiserror is simple to replace out

https://github.com/khonsulabs/justjson/commit/70765d9dd2465e20c808479c752b8591061c7da0

Yep. A no_std variant with heapless would be nice, via prompt.


Unknown websocket-related segfault

After HAL opened up websockets, the app started crashing way more often. No explicit logs were generated of why. Chall added a ton of debug statements to try and find what happened but we were unsuccessful. This led to users seeing a "Bad Gateway" error as the app restarted.

Was able to reproduce this with a websocket testing script I found. Had to fill in a session cookie and adjust the WS url to a valid seamail conversation.
#!/usr/bin/env python

import websocket

# https://pypi.org/project/websocket-client/

def on_message(ws, message):
    print(message)

def on_error(ws, error):
    print(error)

def on_close(ws, close_status_code, close_msg):
    print("### closed ###")

def on_open(ws):
    print("Opened connection")

if __name__ == "__main__":
    websocket.enableTrace(True)
    cookie = "swiftarr_session=Wcw4u2/NSdKmgYWzg9MjWroEEyNvGRg0uhzPjPz8BUM="
    ws = websocket.create_connection(
                              "ws://localhost:8081/fez/9B57F214-7269-4952-B40B-B126CB16FFB6/socket",
                              on_open=on_open,
                              on_message=on_message,
                              on_error=on_error,
                              on_close=on_close,
                              cookie=cookie)
    print(ws.recv())

Basically grab a valid cookie and seamail ID, throw that in a loop: for i in $(seq 1 300); do ./ws.py &; done
Then pkill -f ws.py when you're done or your CPU will cry.
For linux, to enable coredumps: sudo sysctl -w kernel.core_pattern="/tmp/%e_core_dump.%p"
That'll spit out a file akin to: /tmp/NIO-ELT-0-#1_core_dump.433172
My gut tells me it's Linux/NIO/Swift/something interaction that's at fault. But I have little evidence to back up that claim.
Process 440089 stopped
* thread #8, name = 'NIO-ELT-0-#6', stop reason = signal SIGSEGV: invalid address (fault address: 0x0)
    frame #0: 0x00007ffff74106fe libswiftCore.so`$sSD8_VariantV6lookupyq_SgxF + 14
libswiftCore.so`$sSD8_VariantV6lookupyq_SgxF:
->  0x7ffff74106fe <+14>: cmpq   $0x0, 0x10(%rsi)
    0x7ffff7410703 <+19>: je     0x7ffff7410745            ; <+85>
    0x7ffff7410705 <+21>: movq   %rsi, %r13
    0x7ffff7410708 <+24>: movq   %rdx, %rsi

via lldb .build/x86_64-unknown-linux-gnu/debug/Run

Got squirrely and did some further investigation. Will have  PR soon with a Locust test that reliably reproduces this issue based on the code above. When running on an x86_64 Mac Mini I get a variety of different crash points. I don't think the actual HTTP request is relevant since the logger is likely catching up.
[ INFO ] GET /api/v3/fez/8E910516-A83E-4D4A-80C9-EDDF467E4467 -> ok [request-id: E56204B3-C7F6-4972-90F7-29EE72B7D662]
Vapor/Core.swift:94: Fatal error: Core not configured. Configure with app.core.initialize()
zsh: illegal hardware instruction  swift run

[ INFO ] GET /fez/2E51B145-A47B-4774-934F-6313C82CD4F5/socket -> unauthorized [request-id: 1B92CC99-0ADE-43B5-B865-5CF9248CA320]
AsyncKit/EventLoopGroupConnectionPool.swift:296: Assertion failed: ConnectionPool.shutdown() was not called before deinit.
zsh: illegal hardware instruction  swift run

[ INFO ] GET /fez/85E9A123-317E-443F-8A72-07319BA386BB/socket -> switchingProtocols [request-id: 75C92119-9A73-427F-B0DB-3BE0079CD6E8]
Vapor/Application+Clients.swift:47: Fatal error: Clients not initialized. Initialize with app.clients.initialize()
zsh: illegal hardware instruction  swift run

[ INFO ] POST /api/v3/auth/login -> ok [request-id: A425D1E9-D8AD-4983-9FB2-F36D8E9F5DE9]
AsyncKit/EventLoopGroupConnectionPool.swift:296: Assertion failed: ConnectionPool.shutdown() was not called before deinit.
zsh: illegal hardware instruction  swift run

[ INFO ] POST /api/v3/auth/login -> ok [request-id: 23D32972-5B19-48E2-9D02-2D22A08DE089]
Redis/RedisStorage.swift:51: Fatal error: No redis found for id default, or the app may not have finished booting. Also, the eventLoop must be from Application's EventLoopGroup.
zsh: illegal hardware instruction  swift run

[ INFO ] GET /api/v3/fez/D6005383-07B4-4320-BAD2-450932A6E8FF -> ok [request-id: B30A0FAE-B23D-432C-A12A-EAF1FFAFCD53]
AsyncKit/EventLoopGroupConnectionPool.swift:296: Assertion failed: ConnectionPool.shutdown() was not called before deinit.
zsh: illegal hardware instruction  swift run

Apparently the default maximumActiveConnections in RedisConfiguration.PoolOptions is 2 which is pretty tiny. I played with bumping this to various values including 20, 300, 900 (I run my locust with 300 clients). Under the latter value I end up with different errors such as:
[ INFO ] GET /fez/A3CFE2B2-9271-428F-B723-7876DE786707/socket -> unauthorized [request-id: 31DC7448-C277-40FB-985E-0ACDE5611882]
Redis/RedisStorage.swift:51: Fatal error: No redis found for id default, or the app may not have finished booting. Also, the eventLoop must be from Application's EventLoopGroup.

[ INFO ] GET /fez/148E4596-3DD2-462C-BBB1-913BB1735277/socket -> switchingProtocols [request-id: BEDC9999-01D8-4FF4-B52B-B4440BDCEF46]
Redis/RedisStorage.swift:51: Fatal error: No redis found for id default, or the app may not have finished booting. Also, the eventLoop must be from Application's EventLoopGroup.

[ INFO ] POST /api/v3/auth/login -> ok [request-id: 95128172-0A1F-4EC8-ACDD-5F2EA8D5CF69]
Vapor/Core.swift:94: Fatal error: Core not configured. Configure with app.core.initialize()

[ INFO ] GET /api/v3/fez/14A3EC6A-34C6-412E-A9C1-7E2879B1C022 -> ok [request-id: 99C535E4-5F79-48CF-A086-2F0D3A3E9BF2]
AsyncHTTPClient/HTTPClient.swift:132: Fatal error: Client not shut down before the deinit. Please call client.syncShutdown() when no longer needed. Otherwise memory will leak.

My gut tells me that we're dealing with a Redis connection pool issue. I wonder what the relationship between WebSocket and Redis connection is since we store each session in Redis.

I take it all back. Got some more thread dumps on linux. They all start the same way.
* thread #1, name = 'Run', stop reason = signal SIGSEGV
  * frame #0: 0x00007fd5eb1c69ee libswiftCore.so`$sSD8_VariantV6lookupyq_SgxF + 14
    frame #1: 0x00007fd5eb3ffdf6 libswiftCore.so`$sSDyq_Sgxcig + 6
    frame #2: 0x0000557fc002bf50 Run`$s5Vapor7StorageV3gety5ValueQzSgxmAA0B3KeyRzlF at Storage.swift:44:39
    frame #3: 0x0000557fc002bdac Run`$s5Vapor7StorageVy5ValueQzSgxmcAA0B3KeyRzluig at Storage.swift:30:18
    frame #4: 0x000055aa7a0136be Run`$s5Vapor11ApplicationC6FluentEADV7storageAE7StorageCvg at FluentProvider.swift:125:44
    frame #5: 0x000055aa7a012fc5 Run`$s5Vapor11ApplicationC6FluentE9databases0C3Kit9DatabasesCvg at FluentProvider.swift:43:21
    frame #6: 0x000055aa7a012afb Run`$s5Vapor7RequestC6FluentE2dby0C3Kit8Database_pAF0F2IDVSgF at FluentProvider.swift:11:14
    frame #7: 0x000055aa7a012a70 Run`$s5Vapor7RequestC6FluentE2db0C3Kit8Database_pvg at FluentProvider.swift:6:14

* thread #1, name = 'Run', stop reason = signal SIGSEGV
  * frame #0: 0x00007f68bdc969ee libswiftCore.so`$sSD8_VariantV6lookupyq_SgxF + 14
    frame #1: 0x00007f68bdecfdf6 libswiftCore.so`$sSDyq_Sgxcig + 6
    frame #2: 0x00005587536c4f50 Run`$s5Vapor7StorageV3gety5ValueQzSgxmAA0B3KeyRzlF at Storage.swift:44:39
    frame #3: 0x00005587536c4dac Run`$s5Vapor7StorageVy5ValueQzSgxmcAA0B3KeyRzluig at Storage.swift:30:18
    frame #4: 0x00005587535bd815 Run`$s5Vapor11ApplicationC4HTTPV6ClientV6shared15AsyncHTTPClient0G0Cvg at Application+HTTP+Client.swift:23:55
    frame #5: 0x00005587535bd57d Run`$s5Vapor11ApplicationC7ClientsV8ProviderV4httpAGvgZyACcfU_AA6Client_pACcfU_ at Application+HTTP+Client.swift:5:32
    frame #6: 0x000055875356e10a Run`$s5Vapor11ApplicationC6clientAA6Client_pvg at Application+Clients.swift:10:16
    frame #7: 0x000055875357896a Run`$s5Vapor7RequestC6clientAA6Client_pvg at Request+Client.swift:3:26

* thread #1, name = 'Run', stop reason = signal SIGSEGV
  * frame #0: 0x00007f29b2dd09ee libswiftCore.so`$sSD8_VariantV6lookupyq_SgxF + 14
    frame #1: 0x00007f29b3009df6 libswiftCore.so`$sSDyq_Sgxcig + 6
    frame #2: 0x0000559a2c729f50 Run`$s5Vapor7StorageV3gety5ValueQzSgxmAA0B3KeyRzlF at Storage.swift:44:39
    frame #3: 0x0000559a2c729dac Run`$s5Vapor7StorageVy5ValueQzSgxmcAA0B3KeyRzluig at Storage.swift:30:18
    frame #4: 0x0000559a2c5374e1 Run`$s5Vapor11ApplicationC5RedisE12redisStorageAD0cE0Cvg at RedisStorage.swift:8:39
    frame #5: 0x0000559a2c527345 Run`$s5Vapor11ApplicationC5RedisEADV4pool3for9RediStack0C14ConnectionPoolC7NIOCore9EventLoop_p_tF at Application+Redis.swift:17:30
    frame #6: 0x0000559a2c53afbc Run`$s5Vapor7RequestC5RedisEADV4send7command4with7NIOCore15EventLoopFutureCy9RediStack9RESPValueOGSS_SayANGtF at Request+Redis.swift:31:14
    frame #7: 0x0000559a2c53bcc5 Run`$s5Vapor7RequestC5RedisEADV9RediStack0C6ClientAdfGP4send7command4with7NIOCore15EventLoopFutureCyAF9RESPValueOGSS_SayAPGtFTW at <compiler-generated>:0

* thread #1, name = 'Run', stop reason = signal SIGSEGV
  * frame #0: 0x00007fec204109ee libswiftCore.so`$sSD8_VariantV6lookupyq_SgxF + 14
    frame #1: 0x00007fec20649df6 libswiftCore.so`$sSDyq_Sgxcig + 6
    frame #2: 0x00005630e32e7f50 Run`$s5Vapor7StorageV3gety5ValueQzSgxmAA0B3KeyRzlF at Storage.swift:44:39
    frame #3: 0x00005630e32e7dac Run`$s5Vapor7StorageVy5ValueQzSgxmcAA0B3KeyRzluig at Storage.swift:30:18
    frame #4: 0x00005630e281000d Run`$s5Vapor11ApplicationC6FluentEADV10PaginationV13pageSizeLimitSiSgvg at Fluent+Pagination.swift:55:43
    frame #5: 0x00005630e2814e60 Run`$s5Vapor7RequestC6FluentE2dby0C3Kit8Database_pAF0F2IDVSgF at FluentProvider.swift:17:159
    frame #6: 0x00005630e2814a70 Run`$s5Vapor7RequestC6FluentE2db0C3Kit8Database_pvg at FluentProvider.swift:6:14
    frame #7: 0x00005630e19253e2 Run`$s3App13FezControllerV10fezHandleryAA0B4DataV5Vapor7RequestCYaKFTQ0_ at FezController.swift:236:65

So I dug into Storage.swift a bit. And in searching the issue tracker: https://github.com/vapor/vapor/issues/2330
That is VERY on point!

Load test put in via https://github.com/jocosocial/swiftarr/pull/79

Well, good news! We no longer seem to be suffering this bug. Not sure what changed since August (Storage.swift in Vapor hasn't) but something under the hood has. At elevated socket levels (>700-ish) we start to get Redis connection pool errors:
[ WARNING ] The operation could not be completed. (RediStack.RedisConnectionPoolError error 1.) [request-id: 63F589A2-CFAC-41A1-9E8D-EEC668AD7CD4]

By increasing the .maximumActiveConnections() from the current default of 2 to 4 (in configure.swift) I was able to make these mostly go away for a Locust user count of 1000. Also need to fix the SeamailWebsocketUser test to not close connections at the end, to ensure they stick around long enough to simulate a relevant real-world case. Anywho....
I was able to crank the websocket connection count up to north of 1500. No crashes. This bodes very well. I'd feel better if we knew what exactly fixed this glitch.

Fixed in https://github.com/jocosocial/swiftarr/commit/f49262eb5eb7205c615ce3b4c96a1b7e4d966538 back in September. Confirmed via above. Closing.


add report command to open issues easily

This PR is related to #40. At the moment, this is only the beginning of this command.
Currently, it only works for GitHub and GitLab. Custom services aren't possible at the moment.
If the selected modid is "minecraft", it will re-direct to the Minecraft issue tracker.
If the selected modid is "forge", it will open a new issue edit page on Forges issue tracker even if Forge doesn't provide a link.
There are 3 sections which will be added to the issue body:

"Mods information"

Minecraft version
Forge version
Mod version
All loaded dependencies (recursivly)

"Logs"

Includes a description how to provide logs

"Description"

Pre-filled with 2 numbers to see that you should describe how to reproduce the issue.

Things which still needs to be done:

[ ] Automatically upload log and add it to "Logs" section
[ ] Put git.io/mclogs to "Logs" section
[ ] Add API for custom handlings
[ ] Add config for handling modpacks

This is outdated and it seems best to start over.


OR term field

Add an "OR" ontology-term field to complement the "AND" and "NOT" fields.
Is this feature worth the interface-clutter that it would add?  Can we think of use cases?

Can we think of use cases for this?  @cndewey @mbernste

Perhaps the user interviews will help illuminate this; however, my hunch is that this is not a feature we should prioritize.  I feel that most "OR" queries can be done with multiple searches.


Implement std::iter::Step

I was surprised to discover that std::iter::Step was not implement on either IBig nor UBig. Implementing Step means that IBig and UBig could be used in Range, allowing:
for i in (ibig!(0)..limit) {
  // elided
}

I may be able to put together a PR if you are interested.

The Step API is not stable. This is desired but it will wait for stabilization.


Crouching while dying kicks you from the server (even in SSP)

BTW Version: 1.3.6
Multiplayer: No.  Only tested in SSP
Issue: No reason to kick me out of my game just for having the nerve to crouch while casting off this mortal coil.

Addons: Nope!  Not in this instance.
Log.txt

Lol well that's an interesting crash. I actually already know basically the exact issue, shouldn't be difficult to fix.


How to change the aspect ratio ?

@ekimual
The image derived from the camera, goes to the crop screen.
but the aspect ratio of the cropper is always square, how do i keep it free size ?

@coutlooters make the first 2 integers 0 to ignore aspect ratio, it will be square at first but you can adjust it.
Croperino.runCropImage(CroperinoFileUtil.getmFileTemp(), MainActivity.this, true, 0, 0, 0, 0);

@ekimual I  m very much impressed with the library, plus the immediate response given for the Issue which is solved by making the changes mentioned.
Thank you very much.

@coutlooters Very much appreciated and I will try to have this updated once I have a new device (Android 6+ ) and free time to do. :)


Unable to invoke social media.

Hi Guys,
I am trying to share content from cordova[phonegap] app to various social media platforms like facebook/whatsapp/hike/emails/and so on....
I tried with following plugin but was unsuccessful to implement it.
https://github.com/Telerik-Verified-P...
https://github.com/EddyVerbruggen/Soc...
I have added above plugin to my application and followed all the steps as instructed over there but its not working for my Android.
Steps I have done:

Created cordova application through CLI.
Added Android Platform
Added this socialSharing Plugin through CLI
pasted share sheet html in index.html
Build deployed but the buttons not working
tried with "Sharing directly to.." sheet but not working.

@EddyVerbruggen  Please help!

It's guessing without your code, so here's my first guess: do you have the whitelist plugin installed and is there a CSP metatag preventing inline scripts in your index.html?

Thanks! @EddyVerbruggen  for your prompt response.
Whitelist plugin is installed and CSP meta tag is also present in index.html.

Its working!!!!!
What a great plugin!!!!!
Thanks @EddyVerbruggen!!!!!

Awesome!


Embedding learning reference code

@fmassa PR for embedding learning reference code as discussed in #1042. I decided not to create a VGGFace2 dataset for now, since that would require more thought and planning. For now I'm using FMNIST.

Codecov Report

Merging #1101 into master will decrease coverage by 0.46%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1101      +/-   ##
==========================================
- Coverage   64.57%   64.11%   -0.47%
==========================================
  Files          68       68
  Lines        5411     5411
  Branches      831      831
==========================================
- Hits         3494     3469      -25
- Misses       1665     1679      +14
- Partials      252      263      +11

Impacted Files
Coverage Δ

torchvision/datasets/cifar.py
71.91% <0%> (-6.75%)
:arrow_down:

torchvision/datasets/folder.py
80% <0%> (-2.5%)
:arrow_down:

torchvision/datasets/lsun.py
18.47% <0%> (-2.18%)
:arrow_down:

torchvision/datasets/voc.py
20% <0%> (-2.11%)
:arrow_down:

torchvision/transforms/transforms.py
78.78% <0%> (-1.77%)
:arrow_down:

torchvision/transforms/functional.py
70.23% <0%> (-1.16%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3483342...0ca670f. Read the comment docs.

@fmassa I have made all the requested changes, other than the helper method change (I'm not sure which section you wanted to make a method).

@fmassa I have made the changes. Instead of expecting a targets attribute from the dataset, I elaborated further on the semantics and requirements from the targets data structure, which users can build during or after they have initialized their dataset. Will that be ok?

Renamed embedding to similarity to be more consistent with existing literature. Both are used, but similarity is more common.