Basic specs dockerisation...

...specs are failing, unfortunately, locally (not for merge just yet, see comments).

Take 1:
root@3610c1870e37:/hyper-mesh# spec/test_app/bin/setup && bundle exec rake
== Installing dependencies ==
The Gemfile's dependencies are satisfied

== Preparing database ==
Database 'development_db_name' already exists
Database 'test_db_name' already exists
-- create_table("addresses", {:force=>:cascade})
   -> 0.1643s
-- create_table("child_models", {:force=>:cascade})
   -> 0.1536s
-- create_table("comments", {:force=>:cascade})
   -> 0.1597s
-- create_table("test_models", {:force=>:cascade})
   -> 0.1577s
-- create_table("todo_items", {:force=>:cascade})
   -> 0.1619s
-- create_table("todos", {:force=>:cascade})
   -> 0.1516s
-- create_table("users", {:force=>:cascade})
   -> 0.1583s
-- initialize_schema_migrations_table()
   -> 0.0034s
-- create_table("addresses", {:force=>:cascade})
   -> 0.1758s
-- create_table("child_models", {:force=>:cascade})
   -> 0.1537s
-- create_table("comments", {:force=>:cascade})
   -> 0.1570s
-- create_table("test_models", {:force=>:cascade})
   -> 0.1632s
-- create_table("todo_items", {:force=>:cascade})
   -> 0.1539s
-- create_table("todos", {:force=>:cascade})
   -> 0.1558s
-- create_table("users", {:force=>:cascade})
   -> 0.1830s
-- initialize_schema_migrations_table()
   -> 0.0021s

== Removing old logs and tempfiles ==

== Restarting application server ==
/usr/local/bin/ruby -I/usr/local/bundle/gems/rspec-core-3.5.4/lib:/usr/local/bundle/gems/rspec-support-3.5.0/lib /usr/local/bundle/gems/rspec-core-3.5.4/exe/rspec --pattern spec/\*\*\{,/\*/\*\*\}/\*_spec.rb
DEPRECATION WARNING: #tables currently returns both tables and views. This behavior is deprecated and will be changed with Rails 5.1 to only return tables. Use #data_sources instead. (called from needs_init? at /hyper-mesh/lib/synchromesh/connection.rb:4)
DEPRECATION WARNING: #tables currently returns both tables and views. This behavior is deprecated and will be changed with Rails 5.1 to only return tables. Use #data_sources instead. (called from needs_init? at /hyper-mesh/lib/synchromesh/connection.rb:4)
before :each blocks declared for steps are always treated as :all scope (it's possible you want before :step)
Run options:
  include {:focus=>true}
  exclude {:opal=>true}

All examples were filtered out; ignoring {:focus=>true}

reactive-record edge cases
Puma starting in single mode...
* Version 3.6.2 (ruby 2.3.3-p222), codename: Sleepy Sunday Serenity
* Min threads: 0, max threads: 4
* Environment: development
* Listening on tcp://<IP_ADDRESS>:32993
Use Ctrl-C to stop
  trims the association tree

many to many associations
  does not effect the base relationship count
  does not effect access to attributes in the base relationship
  can be followed directly

reverting records
  finds that the user Adam has not changed yet
  creates a new todo which should be changed (because its new)
  adds the todo to adam's todos and expects adam to change
  will show that the new todo is still changed
  the todo now has an owner
  can be reverted and the todo will not be changed
  will not have changed adam
  is time to test going the other way, lets give adam a todo again
  can be reverted
  finds the todo is still changed
  can change an attribute, revert, and make sure nothing else changes

updating associations
  a new model will have empty has_many assocation
  the push operator returns the collection
  the push operator adds 1 to the count
  will persist the new has_many association
  and will reconstruct the association and values on reloading
  the inverse belongs_to association will be set
  a model can be moved to a new owner, and will be removed from the old owner
  and will belong to the new owner
  and can be saved and it will remember its new owner
  and after saving will have been removed from original owners association
  a belongs to association can be set to nil and the model saved
  and it will update on the server
  and will not belong to the previous owner anymore
  but can be reassigned to the previous owner
  and it will update the server on saving
  and a model in a belongs_to relationship can be deleted
  will update the server properly
  and it won't exist after being destroyed
  an item in a belongs_to relationship can be created without belonging to anybody
  and can be reloaded
  and can be deleted
  and it will be won't exist the server

updating scopes
  will update .all and rerender after saving a record
  destroying records causes a rerender

HyperMesh::Connection
DEPRECATION WARNING: #tables currently returns both tables and views. This behavior is deprecated and will be changed with Rails 5.1 to only return tables. Use #data_sources instead. (called from needs_init? at /hyper-mesh/lib/synchromesh/connection.rb:4)
DEPRECATION WARNING: #tables currently returns both tables and views. This behavior is deprecated and will be changed with Rails 5.1 to only return tables. Use #data_sources instead. (called from needs_init? at /hyper-mesh/lib/synchromesh/connection.rb:4)
DEPRECATION WARNING: #tables currently returns both tables and views. This behavior is deprecated and will be changed with Rails 5.1 to only return tables. Use #data_sources instead. (called from block (2 levels) in <top (required)> at /hyper-mesh/spec/synchromesh/aaa-unit_tests/connection_spec.rb:15)
DEPRECATION WARNING: #tables currently returns both tables and views. This behavior is deprecated and will be changed with Rails 5.1 to only return tables. Use #data_sources instead. (called from block (2 levels) in <top (required)> at /hyper-mesh/spec/synchromesh/aaa-unit_tests/connection_spec.rb:16)
  creates the tables
  creates the messages queue
  can set the root path
  adding new connection
  new connections expire
  can send and read data from a channel
  will update the expiration time after reading
  will expire a polled connection
  after connecting to the transport
    will pass any pending data back
    will have the root path set for console access
    the channel will still be active even after initial connection time is expired
    will only effect the session being connected
    will begin refreshing the channel list
    refreshing will not effect channels not connected to the transport
    refreshing will not effect channels added during the refresh
    sends messages to the transport as well as open channels

DummyValue
  works with string interpolation (defines a JS .toString method)

column types on client
DEPRECATION WARNING: #tables currently returns both tables and views. This behavior is deprecated and will be changed with Rails 5.1 to only return tables. Use #data_sources instead. (called from needs_init? at /hyper-mesh/lib/synchromesh/connection.rb:4)
DEPRECATION WARNING: #tables currently returns both tables and views. This behavior is deprecated and will be changed with Rails 5.1 to only return tables. Use #data_sources instead. (called from needs_init? at /hyper-mesh/lib/synchromesh/connection.rb:4)
DEPRECATION WARNING: Time columns will become time zone aware in Rails 5.1. This
still causes `String`s to be parsed as if they were in `Time.zone`,
and `Time`s to be converted to `Time.zone`.

To keep the old behavior, you must add the following to your initializer:

    config.active_record.time_zone_aware_types = [:datetime]

To silence this deprecation warning, add the following:

    config.active_record.time_zone_aware_types = [:datetime, :time]
 (called from block in public_columns_hash at /hyper-mesh/lib/reactive_record/active_record/public_columns_hash.rb:14)
  transfers the columns hash to the client
  defines the server method with a default value
  loads the server method
  creates a dummy value of the appropriate type
  loads and converts the value (FAILED - 1)
  while loading the dummy value delegates the correct type with operators etc (FAILED - 2)
  converts a time string to a time on writing (FAILED - 3)
  converts a integer to a time on writing (FAILED - 4)
 ^CTerminating WebSocket Server
rake aborted!
Interrupt:
/usr/local/bundle/gems/rspec-core-3.5.4/lib/rspec/core/rake_task.rb:79:in `system'
/usr/local/bundle/gems/rspec-core-3.5.4/lib/rspec/core/rake_task.rb:79:in `run_task'
/usr/local/bundle/gems/rspec-core-3.5.4/lib/rspec/core/rake_task.rb:96:in `block (2 levels) in define'
/usr/local/bundle/gems/rspec-core-3.5.4/lib/rspec/core/rake_task.rb:94:in `block in define'
/usr/local/bin/bundle:22:in `load'
/usr/local/bin/bundle:22:in `<main>'
Tasks: TOP => default => spec
(See full trace by running task with --trace)
root@3610c1870e37:/hyper-mesh#
RSpec is shutting down and will print the summary report... Interrupt again to force quit.
  converts a float to a time on writing (FAILED - 5)

Failures:

  1) column types on client loads and converts the value
     Failure/Error:
       expect_promise do
         ReactiveRecord.load do
           TypeTest.columns_hash.collect do |attr, _info|
             [TypeTest.find(1).send(attr).class, TypeTest.find(1).send(attr)]
           end.flatten
         end
       end.to eq([
         'Number', 1,
         'NilClass', nil,
         'Boolean', true,

       expected: ["Number", 1, "NilClass", nil, "Boolean", true, "Date", "2003-02-01", "Time", "2003-02-01T00:00:00+00..."hello", "String", "goodby", "Time", "2000-01-01T00:00:00+0000", "Time", "2003-02-01T00:00:00+0000"]
            got: ["Number", 1, "NilClass", nil, "Boolean", true, "Date", "2003-02-01", "Time", "2003-02-01T00:00:00-00..."hello", "String", "goodby", "Time", "2000-01-01T00:00:00-0000", "Time", "2003-02-01T00:00:00-0000"]

       (compared using ==)
     # ./spec/synchromesh/column_types/column_type_spec.rb:185:in `block (2 levels) in <top (required)>'
     # /usr/local/bundle/gems/rspec-wait-0.0.9/lib/rspec/wait.rb:46:in `block (2 levels) in <top (required)>'

  2) column types on client while loading the dummy value delegates the correct type with operators etc
     Failure/Error:
       expect_evaluate_ruby do
         t = TypeTest.find(1)
         [
           !t.boolean, t.date+1, t.datetime+2.days, t.decimal + 5, t.float + 6, t.integer + 7,
           t.bigint + 8, t.string.length, t.text.length, t.time+3.days, t.timestamp+4.days
         ]
       end.to eq([
         true, "2001-01-02", (Timex.sqlmin+2.days).as_json, 5, 6, 7,
         8, 0, 0, (Timex.sqlmin+3.days).as_json, (Timex.sqlmin+4.days).as_json
       ])

       expected: [true, "2001-01-02", "2001-01-03T00:00:00+0000", 5, 6, 7, 8, 0, 0, "2001-01-04T00:00:00+0000", "2001-01-05T00:00:00+0000"]
            got: [true, "2001-01-02", "2001-01-03T00:00:00-0000", 5, 6, 7, 8, 0, 0, "2001-01-04T00:00:00-0000", "2001-01-05T00:00:00-0000"]

       (compared using ==)
     # ./spec/synchromesh/column_types/column_type_spec.rb:223:in `block (2 levels) in <top (required)>'
     # /usr/local/bundle/gems/rspec-wait-0.0.9/lib/rspec/wait.rb:46:in `block (2 levels) in <top (required)>'

  3) column types on client converts a time string to a time on writing
     Got 0 failures and 2 other errors:

     3.1) Failure/Error: JSON.parse(evaluate_script("[#{js}].$to_json()"), opts).first

          TypeError:
            no implicit conversion of nil into String
          # ./spec/support/component_helpers.rb:186:in `evaluate_ruby'
          # ./spec/support/component_helpers.rb:191:in `expect_evaluate_ruby'
          # ./spec/synchromesh/column_types/column_type_spec.rb:236:in `block (2 levels) in <top (required)>'
          # /usr/local/bundle/gems/rspec-wait-0.0.9/lib/rspec/wait.rb:46:in `block (2 levels) in <top (required)>'

     3.2) Failure/Error: Rails.cache.clear

          Errno::ENOTEMPTY:
            Directory not empty @ dir_s_rmdir - /hyper-mesh/spec/test_app/tmp/cache/assets
          # /usr/local/bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/cache/file_store.rb:32:in `clear'
          # /usr/local/bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/cache/strategy/local_cache.rb:82:in `clear'
          # ./spec/spec_helper.rb:100:in `block (2 levels) in <top (required)>'
          # /usr/local/bundle/gems/rspec-wait-0.0.9/lib/rspec/wait.rb:46:in `block (2 levels) in <top (required)>'
          # ------------------
          # --- Caused by: ---
          # Errno::ENOTEMPTY:
          #   Directory not empty @ dir_s_rmdir - /hyper-mesh/spec/test_app/tmp/cache/assets/test/sprockets/v3.0
          #   /usr/local/bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/cache/file_store.rb:32:in `clear'

  4) column types on client converts a integer to a time on writing
     Failure/Error:
       expect_evaluate_ruby do
         test = TypeTest.new
         test.datetime = 12
         test.datetime + 60.seconds
       end.to eq((Timex.at(12)+60.seconds).as_json)

       expected: "1970-01-01T00:01:12+0000"
            got: "1970-01-01T00:01:12-0000"

       (compared using ==)
     # ./spec/synchromesh/column_types/column_type_spec.rb:244:in `block (2 levels) in <top (required)>'
     # /usr/local/bundle/gems/rspec-wait-0.0.9/lib/rspec/wait.rb:46:in `block (2 levels) in <top (required)>'

  5) column types on client converts a float to a time on writing
     Got 0 failures and 3 other errors:

     5.1) Failure/Error: JSON.parse(evaluate_script("[#{js}].$to_json()"), opts).first

          TypeError:
            no implicit conversion of nil into String
          # ./spec/support/component_helpers.rb:186:in `evaluate_ruby'
          # ./spec/support/component_helpers.rb:191:in `expect_evaluate_ruby'
          # ./spec/synchromesh/column_types/column_type_spec.rb:252:in `block (2 levels) in <top (required)>'
          # /usr/local/bundle/gems/rspec-wait-0.0.9/lib/rspec/wait.rb:46:in `block (2 levels) in <top (required)>'

     5.2) Failure/Error: Rails.cache.clear

          Errno::ENOTEMPTY:
            Directory not empty @ dir_s_rmdir - /hyper-mesh/spec/test_app/tmp/cache/assets
          # /usr/local/bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/cache/file_store.rb:32:in `clear'
          # /usr/local/bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/cache/strategy/local_cache.rb:82:in `clear'
          # ./spec/spec_helper.rb:100:in `block (2 levels) in <top (required)>'
          # /usr/local/bundle/gems/rspec-wait-0.0.9/lib/rspec/wait.rb:46:in `block (2 levels) in <top (required)>'
          # ------------------
          # --- Caused by: ---
          # Errno::ENOTEMPTY:
          #   Directory not empty @ dir_s_rmdir - /hyper-mesh/spec/test_app/tmp/cache/assets/test/sprockets/v3.0
          #   /usr/local/bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/cache/file_store.rb:32:in `clear'

     5.3) Failure/Error: raise "Requests did not finish in 60 seconds"

          RuntimeError:
            Requests did not finish in 60 seconds
          # /usr/local/bundle/gems/capybara-2.11.0/lib/capybara/server.rb:93:in `rescue in wait_for_pending_requests'
          # /usr/local/bundle/gems/capybara-2.11.0/lib/capybara/server.rb:91:in `wait_for_pending_requests'
          # /usr/local/bundle/gems/capybara-2.11.0/lib/capybara/session.rb:113:in `reset!'
          # /usr/local/bundle/gems/capybara-2.11.0/lib/capybara.rb:335:in `block in reset_sessions!'
          # /usr/local/bundle/gems/capybara-2.11.0/lib/capybara.rb:335:in `reverse_each'
          # /usr/local/bundle/gems/capybara-2.11.0/lib/capybara.rb:335:in `reset_sessions!'
          # /usr/local/bundle/gems/capybara-2.11.0/lib/capybara/rspec.rb:21:in `block (2 levels) in <top (required)>'
          # /usr/local/bundle/gems/rspec-wait-0.0.9/lib/rspec/wait.rb:46:in `block (2 levels) in <top (required)>'
          # ------------------
          # --- Caused by: ---
          # Timeout::Error:
          #   execution expired
          #   /usr/local/bundle/gems/capybara-2.11.0/lib/capybara/server.rb:91:in `sleep'

Finished in 18 minutes 50 seconds (files took 33.2 seconds to load)
65 examples, 5 failures

Failed examples:

rspec ./spec/synchromesh/column_types/column_type_spec.rb:169 # column types on client loads and converts the value
rspec ./spec/synchromesh/column_types/column_type_spec.rb:208 # column types on client while loading the dummy value delegates the correct type with operators etc
rspec ./spec/synchromesh/column_types/column_type_spec.rb:235 # column types on client converts a time string to a time on writing
rspec ./spec/synchromesh/column_types/column_type_spec.rb:243 # column types on client converts a integer to a time on writing
rspec ./spec/synchromesh/column_types/column_type_spec.rb:251 # column types on client converts a float to a time on writing

Take 2:
$ docker-compose build && docker-compose run spec
mysql uses an image, skipping
Building spec
Step 1/14 : FROM ruby
 ---> 936395c9ae10
Step 2/14 : RUN curl -sL https://deb.nodesource.com/setup_7.x | bash -
 ---> Using cache
 ---> 4b9d471bb983
Step 3/14 : RUN curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | apt-key add -
 ---> Using cache
 ---> 6b26150f5e75
Step 4/14 : RUN echo "deb https://dl.yarnpkg.com/debian/ stable main" | tee /etc/apt/sources.list.d/yarn.list
 ---> Using cache
 ---> 6af749ad04ec
Step 5/14 : RUN apt-get update -qq && apt-get install -y build-essential libpq-dev yarn
 ---> Using cache
 ---> cb7e2efac39e
Step 6/14 : RUN yarn global add phantomjs-prebuilt
 ---> Using cache
 ---> b3a623a62ab1
Step 7/14 : RUN mkdir /hyper-mesh
 ---> Using cache
 ---> d1af7a781765
Step 8/14 : WORKDIR /hyper-mesh
 ---> Using cache
 ---> 14a36a983629
Step 9/14 : ADD Gemfile.lock .
 ---> Using cache
 ---> 8fac6c7b9310
Step 10/14 : ADD Gemfile .
 ---> 9d4b1fa0c282
Removing intermediate container de1866f1e11a
Step 11/14 : ADD hyper-mesh.gemspec .
 ---> 4101e1a6fa94
Removing intermediate container b16d938d8fd7
Step 12/14 : ADD lib/hypermesh/version.rb lib/hypermesh/
 ---> 0849fee98a84
Removing intermediate container d4d388ebdf06
Step 13/14 : RUN bundle install --frozen
 ---> Running in 084a445fe0a6
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
Fetching gem metadata from https://rubygems.org/...........
Fetching version metadata from https://rubygems.org/...
Fetching dependency metadata from https://rubygems.org/..
Installing rake 10.5.0
Installing abstract_type 0.0.7
Installing concurrent-ruby 1.0.3
Installing i18n 0.7.0
Installing minitest 5.10.1
Installing thread_safe 0.3.5
Installing builder 3.2.2
Installing erubis 2.7.0
Installing mini_portile2 2.1.0
Installing rack 2.0.1
Installing nio4r 1.2.1 with native extensions
Installing websocket-extensions 0.1.2
Installing mime-types-data 3.2016.0521
Installing arel 7.1.4
Installing ice_nine 0.11.2
Installing public_suffix 2.0.4
Installing io-like 0.3.0
Installing ast 2.3.0
Installing babel-source 5.8.35
Installing execjs 2.7.0
Installing debug_inspector 0.0.2 with native extensions
Installing byebug 9.0.6 with native extensions
Installing ffi 1.9.14 with native extensions
Installing cliver 0.3.2
Installing coderay 1.1.1
Installing coffee-script-source 1.12.2
Installing equalizer 0.0.11
Installing connection_pool 2.2.1
Installing cookiejar 0.3.3
Installing daemons 1.2.4
Installing database_cleaner 1.5.3
Installing diff-lcs 1.2.5
Installing eventmachine 1.2.1 with native extensions
Installing http_parser.rb 0.6.0 with native extensions
Installing method_source 0.8.2
Installing thor 0.19.4
Installing hike 1.2.3
Installing httpclient 2.8.3
Installing sourcemap 0.1.1
Installing tilt 2.0.5
Installing hyper-trace 0.3.1
Installing interception 0.5 with native extensions
Installing libv8 <IP_ADDRESS>
Installing multi_json 1.12.1
Installing mysql2 0.4.5 with native extensions
Installing paggio 0.2.6
Using bundler 1.13.6
Installing procto 0.0.3
Installing slop 3.6.0
Installing puma 3.6.2 with native extensions
Installing pusher-signature 0.1.8
Installing ref 2.0.0
Installing rspec-support 3.5.0
Installing rubyzip 1.2.0
Installing websocket 1.2.3
Installing shoulda-context 1.2.2
Installing sqlite3 1.3.10 with native extensions
Installing timecop 0.8.1
Installing tzinfo 1.2.2
Installing memoizable 0.4.2
Installing nokogiri <IP_ADDRESS> with native extensions
Installing rack-test 0.6.3
Installing sprockets 3.7.1
Installing websocket-driver 0.6.4 with native extensions
Installing mime-types 3.1
Installing addressable 2.5.0
Installing archive-zip 0.7.0
Installing parser <IP_ADDRESS>
Installing babel-transpiler 0.7.0
Installing binding_of_caller 0.7.2 with native extensions
Installing childprocess 0.5.9
Installing em-socksify 0.3.1
Installing thin 1.7.0 with native extensions
Installing em-websocket 0.5.1
Installing pry 0.10.4
Installing pusher 1.3.0
Installing therubyracer 0.12.2 with native extensions
Installing rspec-core 3.5.4
Installing rspec-expectations 3.5.0
Installing rspec-mocks 3.5.0
Installing activesupport <IP_ADDRESS>
Installing adamantium 0.2.0
Installing loofah 2.0.3
Installing xpath 2.0.0
Installing opal 0.10.3
Installing mail 2.6.4
Installing chromedriver-helper 1.0.0
Installing selenium-webdriver 3.0.3
Installing em-http-request 1.1.5
Installing pry-byebug 3.4.2
Installing pry-rescue 1.4.4
Installing pry-stack_explorer <IP_ADDRESS>
Installing rspec-collection_matchers 1.1.2
Installing rspec-its 1.2.0
Installing rspec 3.5.0
Installing rails-dom-testing 2.0.1
Installing globalid 0.3.7
Installing activemodel <IP_ADDRESS>
Installing factory_girl 4.8.0
Installing shoulda-matchers 2.8.0
Installing spring 2.0.0
Installing concord 0.1.5
Installing rails-html-sanitizer 1.0.3
Installing capybara 2.11.0
Installing opal-activesupport 0.3.0
Installing opal-browser 0.2.0
Installing opal-jquery 0.4.2
Installing opal-sprockets <IP_ADDRESS>.<IP_ADDRESS>.0
Installing pusher-fake 1.7.0
Installing rspec-steps 2.1.1
Installing rspec-wait 0.0.9
Installing activejob <IP_ADDRESS>
Installing activerecord <IP_ADDRESS>
Installing shoulda 3.5.0
Installing spring-commands-rspec 1.0.4
Installing unparser 0.2.5
Installing actionview <IP_ADDRESS>
Installing poltergeist 1.12.0
Installing actionpack <IP_ADDRESS>
Installing actioncable <IP_ADDRESS>
Installing actionmailer <IP_ADDRESS>
Installing railties <IP_ADDRESS>
Installing sprockets-rails 2.3.3
Installing factory_girl_rails 4.8.0
Installing react-rails 1.10.0
Installing jquery-rails 4.2.1
Installing rspec-rails 3.5.2
Installing rails <IP_ADDRESS>
Installing hyper-react 0.11.0
Installing opal-rails 0.9.1
Installing reactrb-rails-generator 0.2.0
Using hyper-mesh 0.5.3 from source at `.`
Bundle complete! 40 Gemfile dependencies, 132 gems now installed.
Bundled gems are installed into /usr/local/bundle.
Post-install message from opal-rails:
BEWARE: Spec support is being extracted from `opal-rails` into `opal-rspec-rails`
        Please use `opal-rspec-rails` or the 0-8-stable branch.
 ---> b8f93b699e55
Removing intermediate container 084a445fe0a6
Step 14/14 : ADD . .
 ---> a35bbd5a7bb9
Removing intermediate container e8af28c3042e
Successfully built a35bbd5a7bb9
Creating network "hypermesh_default" with the default driver
Creating hypermesh_mysql_1
== Installing dependencies ==
The following gems are missing
 * rake (11.3.0)
 * concurrent-ruby (1.0.2)
 * minitest (5.9.1)
 * coffee-script-source (1.10.0)
 * coffee-script (2.4.1)
 * thor (0.19.1)
 * coffee-rails (4.1.1)
 * connection_pool (2.2.0)
 * sprockets (3.7.0)
 * opal (0.10.2)
 * react-rails (1.4.2)
 * hyper-trace (0.3.0)
 * jbuilder (2.6.0)
 * jquery-ui-rails (5.0.5)
 * libv8 (<IP_ADDRESS>)
 * opal-rails (0.9.0)
 * puma (3.6.0)
 * rdoc (4.2.2)
 * react-router-rails (<IP_ADDRESS>)
 * reactrb (0.9.0)
 * reactrb-router (0.8.2)
 * sass (3.4.22)
 * sass-rails (5.0.6)
 * sdoc (0.4.2)
 * sqlite3 (1.3.12)
 * turbolinks-source (5.0.0)
 * turbolinks (5.0.1)
 * uglifier (3.0.3)
 * web-console (2.3.0)
Install missing gems with `bundle install`
Fetching gem metadata from https://rubygems.org/...........
Fetching version metadata from https://rubygems.org/...
Fetching dependency metadata from https://rubygems.org/..
Installing rake 11.3.0
Installing concurrent-ruby 1.0.2
Using i18n 0.7.0
Installing minitest 5.9.1
Using thread_safe 0.3.5
Using builder 3.2.2
Using erubis 2.7.0
Using mini_portile2 2.1.0
Using rack 2.0.1
Using nio4r 1.2.1
Using websocket-extensions 0.1.2
Using mime-types-data 3.2016.0521
Using arel 7.1.4
Using babel-source 5.8.35
Using execjs 2.7.0
Using debug_inspector 0.0.2
Using byebug 9.0.6
Using coderay 1.1.1
Installing coffee-script-source 1.10.0
Using method_source 0.8.2
Installing thor 0.19.1
Installing connection_pool 2.2.0
Using hike 1.2.3
Using sourcemap 0.1.1
Using tilt 2.0.5
Using bundler 1.13.6
Installing hyper-trace 0.3.0
Using multi_json 1.12.1
Using json 1.8.3
Installing libv8 <IP_ADDRESS>
Using mysql2 0.4.5
Using paggio 0.2.6
Using slop 3.6.0
Installing puma 3.6.0 with native extensions
Using ref 2.0.0
Installing sass 3.4.22
Installing sqlite3 1.3.12 with native extensions
Installing turbolinks-source 5.0.0
Using tzinfo 1.2.2
Using nokogiri <IP_ADDRESS>
Using rack-test 0.6.3
Installing sprockets 3.7.0
Using websocket-driver 0.6.4
Using mime-types 3.1
Using babel-transpiler 0.7.0
Installing uglifier 3.0.3
Using binding_of_caller 0.7.2
Installing coffee-script 2.4.1
Installing rdoc 4.2.2
Using pry 0.10.4
Using therubyracer 0.12.2
Installing turbolinks 5.0.1
Using activesupport <IP_ADDRESS>
Using loofah 2.0.3
Installing opal 0.10.2
Using mail 2.6.4
Installing sdoc 0.4.2
Using rails-dom-testing 2.0.1
Using globalid 0.3.7
Using activemodel <IP_ADDRESS>
Installing jbuilder 2.6.0
Using spring 2.0.0
Using rails-html-sanitizer 1.0.3
Using opal-activesupport 0.3.0
Using opal-browser 0.2.0
Using opal-jquery 0.4.2
Using activejob <IP_ADDRESS>
Using activerecord <IP_ADDRESS>
Using actionview <IP_ADDRESS>
Using actionpack <IP_ADDRESS>
Using actioncable <IP_ADDRESS>
Using actionmailer <IP_ADDRESS>
Using railties <IP_ADDRESS>
Using sprockets-rails 2.3.3
Installing coffee-rails 4.1.1
Using jquery-rails 4.2.1
Installing jquery-ui-rails 5.0.5
Using rails <IP_ADDRESS>
Installing sass-rails 5.0.6
Installing web-console 2.3.0
Installing react-rails 1.4.2
Installing opal-rails 0.9.0
Using reactrb-rails-generator 0.2.0
Using hyper-react 0.11.0
Installing react-router-rails <IP_ADDRESS>
Installing reactrb 0.9.0
Using hyper-mesh 0.5.3 from source at `../..`
Installing reactrb-router 0.8.2
Bundle complete! 25 Gemfile dependencies, 88 gems now installed.
Bundled gems are installed into /usr/local/bundle.
Post-install message from opal-rails:
BEWARE: Spec support is being extracted from `opal-rails` into `opal-rspec-rails`
        Please use `opal-rspec-rails` or the 0-8-stable branch.
Post-install message from rdoc:
Depending on your version of ruby, you may need to install ruby rdoc/ri data:

<= 1.8.6 : unsupported
 = 1.8.7 : gem install rdoc-data; rdoc-data --install
 = 1.9.1 : gem install rdoc-data; rdoc-data --install
>= 1.9.2 : nothing to do! Yay!

== Preparing database ==
Created database 'development_db_name'
Created database 'test_db_name'
-- create_table("addresses", {:force=>:cascade})
   -> 0.0986s
-- create_table("child_models", {:force=>:cascade})
   -> 0.1024s
-- create_table("comments", {:force=>:cascade})
   -> 0.1189s
-- create_table("test_models", {:force=>:cascade})
   -> 0.2667s
-- create_table("todo_items", {:force=>:cascade})
   -> 0.1410s
-- create_table("todos", {:force=>:cascade})
   -> 0.1546s
-- create_table("users", {:force=>:cascade})
   -> 0.1469s
-- initialize_schema_migrations_table()
   -> 0.1325s
-- create_table("addresses", {:force=>:cascade})
   -> 0.1513s
-- create_table("child_models", {:force=>:cascade})
   -> 0.1854s
-- create_table("comments", {:force=>:cascade})
   -> 0.1781s
-- create_table("test_models", {:force=>:cascade})
   -> 0.1799s
-- create_table("todo_items", {:force=>:cascade})
   -> 0.1730s
-- create_table("todos", {:force=>:cascade})
   -> 0.1053s
-- create_table("users", {:force=>:cascade})
   -> 0.1004s
-- initialize_schema_migrations_table()
   -> 0.1030s

== Removing old logs and tempfiles ==

== Restarting application server ==
/usr/local/bin/ruby -I/usr/local/bundle/gems/rspec-core-3.5.4/lib:/usr/local/bundle/gems/rspec-support-3.5.0/lib /usr/local/bundle/gems/rspec-core-3.5.4/exe/rspec --pattern spec/\*\*\{,/\*/\*\*\}/\*_spec.rb
DEPRECATION WARNING: #tables currently returns both tables and views. This behavior is deprecated and will be changed with Rails 5.1 to only return tables. Use #data_sources instead. (called from needs_init? at /hyper-mesh/lib/synchromesh/connection.rb:4)
DEPRECATION WARNING: #tables currently returns both tables and views. This behavior is deprecated and will be changed with Rails 5.1 to only return tables. Use #data_sources instead. (called from needs_init? at /hyper-mesh/lib/synchromesh/connection.rb:4)
before :each blocks declared for steps are always treated as :all scope (it's possible you want before :step)
Run options:
  include {:focus=>true}
  exclude {:opal=>true}

All examples were filtered out; ignoring {:focus=>true}

reactive-record edge cases
Puma starting in single mode...
* Version 3.6.2 (ruby 2.3.3-p222), codename: Sleepy Sunday Serenity
* Min threads: 0, max threads: 4
* Environment: development
* Listening on tcp://<IP_ADDRESS>:43557
Use Ctrl-C to stop
  trims the association tree

many to many associations
  does not effect the base relationship count
  does not effect access to attributes in the base relationship
  can be followed directly

reverting records
  finds that the user Adam has not changed yet
  creates a new todo which should be changed (because its new)
  adds the todo to adam's todos and expects adam to change
  will show that the new todo is still changed
  the todo now has an owner
  can be reverted and the todo will not be changed
  will not have changed adam
  is time to test going the other way, lets give adam a todo again
  can be reverted
  finds the todo is still changed
  can change an attribute, revert, and make sure nothing else changes

updating associations
  a new model will have empty has_many assocation
  the push operator returns the collection
  the push operator adds 1 to the count
  will persist the new has_many association
  and will reconstruct the association and values on reloading
  the inverse belongs_to association will be set
  a model can be moved to a new owner, and will be removed from the old owner
  and will belong to the new owner
  and can be saved and it will remember its new owner
  and after saving will have been removed from original owners association
  a belongs to association can be set to nil and the model saved
  and it will update on the server
  and will not belong to the previous owner anymore
  but can be reassigned to the previous owner
  and it will update the server on saving
  and a model in a belongs_to relationship can be deleted
  will update the server properly
  and it won't exist after being destroyed
  an item in a belongs_to relationship can be created without belonging to anybody
  and can be reloaded
  and can be deleted
  and it will be won't exist the server

updating scopes
  will update .all and rerender after saving a record
  destroying records causes a rerender

HyperMesh::Connection
DEPRECATION WARNING: #tables currently returns both tables and views. This behavior is deprecated and will be changed with Rails 5.1 to only return tables. Use #data_sources instead. (called from needs_init? at /hyper-mesh/lib/synchromesh/connection.rb:4)
DEPRECATION WARNING: #tables currently returns both tables and views. This behavior is deprecated and will be changed with Rails 5.1 to only return tables. Use #data_sources instead. (called from needs_init? at /hyper-mesh/lib/synchromesh/connection.rb:4)
DEPRECATION WARNING: #tables currently returns both tables and views. This behavior is deprecated and will be changed with Rails 5.1 to only return tables. Use #data_sources instead. (called from block (2 levels) in <top (required)> at /hyper-mesh/spec/synchromesh/aaa-unit_tests/connection_spec.rb:15)
DEPRECATION WARNING: #tables currently returns both tables and views. This behavior is deprecated and will be changed with Rails 5.1 to only return tables. Use #data_sources instead. (called from block (2 levels) in <top (required)> at /hyper-mesh/spec/synchromesh/aaa-unit_tests/connection_spec.rb:16)
  creates the tables
  creates the messages queue
  can set the root path
  adding new connection
  new connections expire
  can send and read data from a channel
  will update the expiration time after reading
  will expire a polled connection
  after connecting to the transport
    will pass any pending data back
    will have the root path set for console access
    the channel will still be active even after initial connection time is expired
    will only effect the session being connected
    will begin refreshing the channel list
    refreshing will not effect channels not connected to the transport
    refreshing will not effect channels added during the refresh
    sends messages to the transport as well as open channels

DummyValue
  works with string interpolation (defines a JS .toString method)

column types on client
DEPRECATION WARNING: #tables currently returns both tables and views. This behavior is deprecated and will be changed with Rails 5.1 to only return tables. Use #data_sources instead. (called from needs_init? at /hyper-mesh/lib/synchromesh/connection.rb:4)
DEPRECATION WARNING: #tables currently returns both tables and views. This behavior is deprecated and will be changed with Rails 5.1 to only return tables. Use #data_sources instead. (called from needs_init? at /hyper-mesh/lib/synchromesh/connection.rb:4)
DEPRECATION WARNING: Time columns will become time zone aware in Rails 5.1. This
still causes `String`s to be parsed as if they were in `Time.zone`,
and `Time`s to be converted to `Time.zone`.

To keep the old behavior, you must add the following to your initializer:

    config.active_record.time_zone_aware_types = [:datetime]

To silence this deprecation warning, add the following:

    config.active_record.time_zone_aware_types = [:datetime, :time]
 (called from block in public_columns_hash at /hyper-mesh/lib/reactive_record/active_record/public_columns_hash.rb:14)
  transfers the columns hash to the client
  defines the server method with a default value
  loads the server method
  creates a dummy value of the appropriate type
  loads and converts the value (FAILED - 1)
  while loading the dummy value delegates the correct type with operators etc (FAILED - 2)
2016-12-20 20:23:44 +0000: Rack app error handling request { GET /react_test/1 }
#<ActionView::Template::Error: No such file or directory @ rb_file_s_rename - (/hyper-mesh/spec/test_app/tmp/cache/assets/test/sprockets/v3.0/nB/nB2JBCP9Mq04xKAlzvmLsgcXo1Mc5wYShOKm2uQ2bwA.cache.69880504180100.320.805324, /hyper-mesh/spec/test_app/tmp/cache/assets/test/sprockets/v3.0/nB/nB2JBCP9Mq04xKAlzvmLsgcXo1Mc5wYShOKm2uQ2bwA.cache)>
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/path_utils.rb:282:in `rename'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/path_utils.rb:282:in `atomic_write'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/cache/file_store.rb:107:in `set'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/cache.rb:212:in `set'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/cache.rb:136:in `set'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/loader.rb:243:in `store_asset'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/loader.rb:185:in `load_from_unloaded'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/loader.rb:60:in `block in load'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/loader.rb:317:in `fetch_asset_from_dependency_cache'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/loader.rb:44:in `load'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/cached_environment.rb:20:in `block in initialize'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/cached_environment.rb:47:in `load'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/bundle.rb:23:in `block in call'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/utils.rb:200:in `dfs'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/bundle.rb:24:in `call'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/processor_utils.rb:75:in `call_processor'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/processor_utils.rb:57:in `block in call_processors'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/processor_utils.rb:56:in `reverse_each'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/processor_utils.rb:56:in `call_processors'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/loader.rb:134:in `load_from_unloaded'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/loader.rb:60:in `block in load'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/loader.rb:317:in `fetch_asset_from_dependency_cache'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/loader.rb:44:in `load'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/cached_environment.rb:20:in `block in initialize'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/cached_environment.rb:47:in `load'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/base.rb:66:in `find_asset'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/environment.rb:30:in `find_asset'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/base.rb:92:in `[]'
/usr/local/bundle/gems/sprockets-rails-2.3.3/lib/sprockets/rails/helper.rb:123:in `asset_digest_path'
/usr/local/bundle/gems/sprockets-rails-2.3.3/lib/sprockets/rails/helper.rb:76:in `compute_asset_path'
/usr/local/bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/helpers/asset_url_helper.rb:144:in `asset_path'
/usr/local/bundle/gems/sprockets-rails-2.3.3/lib/sprockets/rails/helper.rb:91:in `asset_path'
/usr/local/bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/helpers/asset_url_helper.rb:254:in `javascript_path'
/usr/local/bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/helpers/asset_tag_helper.rb:61:in `block in javascript_include_tag'
/usr/local/bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/helpers/asset_tag_helper.rb:59:in `map'
/usr/local/bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/helpers/asset_tag_helper.rb:59:in `javascript_include_tag'
/usr/local/bundle/gems/sprockets-rails-2.3.3/lib/sprockets/rails/helper.rb:148:in `javascript_include_tag'
/usr/local/bundle/gems/opal-rails-0.9.1/app/helpers/opal_helper.rb:14:in `javascript_include_tag'
inline template:6:in `_inline_template__2090653715659524586_69880505484740'
/usr/local/bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/template.rb:158:in `block in render'
/usr/local/bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications.rb:166:in `instrument'
/usr/local/bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/template.rb:348:in `instrument'
/usr/local/bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/template.rb:156:in `render'
/usr/local/bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/renderer/template_renderer.rb:54:in `block (2 levels) in render_template'
/usr/local/bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/renderer/abstract_renderer.rb:42:in `block in instrument'
/usr/local/bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications.rb:164:in `block in instrument'
/usr/local/bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications/instrumenter.rb:21:in `instrument'
/usr/local/bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications.rb:164:in `instrument'
/usr/local/bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/renderer/abstract_renderer.rb:41:in `instrument'
/usr/local/bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/renderer/template_renderer.rb:53:in `block in render_template'
/usr/local/bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/renderer/template_renderer.rb:61:in `render_with_layout'
/usr/local/bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/renderer/template_renderer.rb:52:in `render_template'
/usr/local/bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/renderer/template_renderer.rb:14:in `render'
/usr/local/bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/renderer/renderer.rb:42:in `render_template'
/usr/local/bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/renderer/renderer.rb:23:in `render'
/usr/local/bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/rendering.rb:103:in `_render_template'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/streaming.rb:217:in `_render_template'
/usr/local/bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/rendering.rb:83:in `render_to_body'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/rendering.rb:52:in `render_to_body'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/renderers.rb:144:in `render_to_body'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/abstract_controller/rendering.rb:26:in `render'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/rendering.rb:36:in `render'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/instrumentation.rb:44:in `block (2 levels) in render'
/usr/local/bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/core_ext/benchmark.rb:12:in `block in ms'
/usr/local/lib/ruby/2.3.0/benchmark.rb:308:in `realtime'
/usr/local/bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/core_ext/benchmark.rb:12:in `ms'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/instrumentation.rb:44:in `block in render'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/instrumentation.rb:87:in `cleanup_view_runtime'
/usr/local/bundle/gems/activerecord-<IP_ADDRESS>/lib/active_record/railties/controller_runtime.rb:25:in `cleanup_view_runtime'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/instrumentation.rb:43:in `render'
/hyper-mesh/spec/support/component_helpers.rb:149:in `block (2 levels) in build_test_url_for'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/basic_implicit_render.rb:4:in `send_action'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/abstract_controller/base.rb:188:in `process_action'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/rendering.rb:30:in `process_action'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/abstract_controller/callbacks.rb:20:in `block in process_action'
/usr/local/bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:126:in `call'
/usr/local/bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:506:in `block (2 levels) in compile'
/usr/local/bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:455:in `call'
/usr/local/bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:101:in `__run_callbacks__'
/usr/local/bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:750:in `_run_process_action_callbacks'
/usr/local/bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:90:in `run_callbacks'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/abstract_controller/callbacks.rb:19:in `process_action'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/rescue.rb:20:in `process_action'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/instrumentation.rb:32:in `block in process_action'
/usr/local/bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications.rb:164:in `block in instrument'
/usr/local/bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications/instrumenter.rb:21:in `instrument'
/usr/local/bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications.rb:164:in `instrument'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/instrumentation.rb:30:in `process_action'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/params_wrapper.rb:248:in `process_action'
/usr/local/bundle/gems/activerecord-<IP_ADDRESS>/lib/active_record/railties/controller_runtime.rb:18:in `process_action'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/abstract_controller/base.rb:126:in `process'
/usr/local/bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/rendering.rb:30:in `process'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal.rb:190:in `dispatch'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal.rb:262:in `dispatch'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/routing/route_set.rb:50:in `dispatch'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/routing/route_set.rb:32:in `serve'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/journey/router.rb:39:in `block in serve'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/journey/router.rb:26:in `each'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/journey/router.rb:26:in `serve'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/routing/route_set.rb:725:in `call'
/usr/local/bundle/gems/rack-2.0.1/lib/rack/etag.rb:25:in `call'
/usr/local/bundle/gems/rack-2.0.1/lib/rack/conditional_get.rb:25:in `call'
/usr/local/bundle/gems/rack-2.0.1/lib/rack/head.rb:12:in `call'
/usr/local/bundle/gems/rack-2.0.1/lib/rack/session/abstract/id.rb:222:in `context'
/usr/local/bundle/gems/rack-2.0.1/lib/rack/session/abstract/id.rb:216:in `call'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/cookies.rb:613:in `call'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/callbacks.rb:38:in `block in call'
/usr/local/bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:97:in `__run_callbacks__'
/usr/local/bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:750:in `_run_call_callbacks'
/usr/local/bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:90:in `run_callbacks'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/callbacks.rb:36:in `call'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/executor.rb:12:in `call'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/remote_ip.rb:79:in `call'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/debug_exceptions.rb:49:in `call'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/show_exceptions.rb:31:in `call'
/usr/local/bundle/gems/railties-<IP_ADDRESS>/lib/rails/rack/logger.rb:36:in `call_app'
/usr/local/bundle/gems/railties-<IP_ADDRESS>/lib/rails/rack/logger.rb:24:in `block in call'
/usr/local/bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/tagged_logging.rb:70:in `block in tagged'
/usr/local/bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/tagged_logging.rb:26:in `tagged'
/usr/local/bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/tagged_logging.rb:70:in `tagged'
/usr/local/bundle/gems/railties-<IP_ADDRESS>/lib/rails/rack/logger.rb:24:in `call'
/hyper-mesh/lib/synchromesh/synchromesh_controller.rb:25:in `call'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/request_id.rb:24:in `call'
/usr/local/bundle/gems/rack-2.0.1/lib/rack/method_override.rb:22:in `call'
/usr/local/bundle/gems/rack-2.0.1/lib/rack/runtime.rb:22:in `call'
/usr/local/bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/cache/strategy/local_cache_middleware.rb:28:in `call'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/executor.rb:12:in `call'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/static.rb:136:in `call'
/usr/local/bundle/gems/rack-2.0.1/lib/rack/sendfile.rb:111:in `call'
/usr/local/bundle/gems/railties-<IP_ADDRESS>/lib/rails/engine.rb:522:in `call'
/usr/local/bundle/gems/rack-2.0.1/lib/rack/urlmap.rb:68:in `block in call'
/usr/local/bundle/gems/rack-2.0.1/lib/rack/urlmap.rb:53:in `each'
/usr/local/bundle/gems/rack-2.0.1/lib/rack/urlmap.rb:53:in `call'
/usr/local/bundle/gems/capybara-2.11.0/lib/capybara/server.rb:43:in `call'
/usr/local/bundle/gems/puma-3.6.2/lib/puma/configuration.rb:225:in `call'
/usr/local/bundle/gems/puma-3.6.2/lib/puma/server.rb:578:in `handle_request'
/usr/local/bundle/gems/puma-3.6.2/lib/puma/server.rb:415:in `process_client'
/usr/local/bundle/gems/puma-3.6.2/lib/puma/server.rb:275:in `block in run'
/usr/local/bundle/gems/puma-3.6.2/lib/puma/thread_pool.rb:116:in `block in spawn_thread'
  converts a time string to a time on writing (FAILED - 3)
  converts a integer to a time on writing (FAILED - 4)
  converts a float to a time on writing (FAILED - 5)
  converts a 0, "false" false and nil to a boolean false, everything else is true (FAILED - 6)
2016-12-20 20:42:33 +0000: Rack app error handling request { GET /react_test/1 }
#<ActionView::Template::Error: No such file or directory @ rb_file_s_rename - (/hyper-mesh/spec/test_app/tmp/cache/assets/test/sprockets/v3.0/fY/fY2bD1_SiMAq2IERgxwPIwsyZVnDQPHnVtFAlYBZG6g.cache.69880512341180.320.429901, /hyper-mesh/spec/test_app/tmp/cache/assets/test/sprockets/v3.0/fY/fY2bD1_SiMAq2IERgxwPIwsyZVnDQPHnVtFAlYBZG6g.cache)>
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/path_utils.rb:282:in `rename'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/path_utils.rb:282:in `atomic_write'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/cache/file_store.rb:107:in `set'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/cache.rb:212:in `set'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/cache.rb:136:in `set'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/legacy.rb:128:in `cache_set'
/usr/local/bundle/gems/opal-0.10.3/lib/opal/sprockets/source_map_server.rb:58:in `set_map_cache'
/usr/local/bundle/gems/opal-0.10.3/lib/opal/sprockets/processor.rb:53:in `evaluate'
/usr/local/bundle/gems/tilt-2.0.5/lib/tilt/template.rb:102:in `render'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/legacy_tilt_processor.rb:25:in `call'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/processor_utils.rb:75:in `call_processor'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/processor_utils.rb:57:in `block in call_processors'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/processor_utils.rb:56:in `reverse_each'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/processor_utils.rb:56:in `call_processors'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/loader.rb:134:in `load_from_unloaded'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/loader.rb:60:in `block in load'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/loader.rb:317:in `fetch_asset_from_dependency_cache'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/loader.rb:44:in `load'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/cached_environment.rb:20:in `block in initialize'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/cached_environment.rb:47:in `load'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/bundle.rb:23:in `block in call'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/utils.rb:200:in `dfs'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/bundle.rb:24:in `call'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/processor_utils.rb:75:in `call_processor'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/processor_utils.rb:57:in `block in call_processors'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/processor_utils.rb:56:in `reverse_each'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/processor_utils.rb:56:in `call_processors'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/loader.rb:134:in `load_from_unloaded'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/loader.rb:60:in `block in load'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/loader.rb:317:in `fetch_asset_from_dependency_cache'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/loader.rb:44:in `load'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/cached_environment.rb:20:in `block in initialize'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/cached_environment.rb:47:in `load'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/base.rb:66:in `find_asset'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/environment.rb:30:in `find_asset'
/usr/local/bundle/gems/sprockets-3.7.1/lib/sprockets/base.rb:92:in `[]'
/usr/local/bundle/gems/sprockets-rails-2.3.3/lib/sprockets/rails/helper.rb:123:in `asset_digest_path'
/usr/local/bundle/gems/sprockets-rails-2.3.3/lib/sprockets/rails/helper.rb:76:in `compute_asset_path'
/usr/local/bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/helpers/asset_url_helper.rb:144:in `asset_path'
/usr/local/bundle/gems/sprockets-rails-2.3.3/lib/sprockets/rails/helper.rb:91:in `asset_path'
/usr/local/bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/helpers/asset_url_helper.rb:254:in `javascript_path'
/usr/local/bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/helpers/asset_tag_helper.rb:61:in `block in javascript_include_tag'
/usr/local/bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/helpers/asset_tag_helper.rb:59:in `map'
/usr/local/bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/helpers/asset_tag_helper.rb:59:in `javascript_include_tag'
/usr/local/bundle/gems/sprockets-rails-2.3.3/lib/sprockets/rails/helper.rb:148:in `javascript_include_tag'
/usr/local/bundle/gems/opal-rails-0.9.1/app/helpers/opal_helper.rb:14:in `javascript_include_tag'
inline template:6:in `_inline_template__2090653715659524586_69880520489540'
/usr/local/bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/template.rb:158:in `block in render'
/usr/local/bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications.rb:166:in `instrument'
/usr/local/bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/template.rb:348:in `instrument'
/usr/local/bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/template.rb:156:in `render'
/usr/local/bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/renderer/template_renderer.rb:54:in `block (2 levels) in render_template'
/usr/local/bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/renderer/abstract_renderer.rb:42:in `block in instrument'
/usr/local/bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications.rb:164:in `block in instrument'
/usr/local/bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications/instrumenter.rb:21:in `instrument'
/usr/local/bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications.rb:164:in `instrument'
/usr/local/bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/renderer/abstract_renderer.rb:41:in `instrument'
/usr/local/bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/renderer/template_renderer.rb:53:in `block in render_template'
/usr/local/bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/renderer/template_renderer.rb:61:in `render_with_layout'
/usr/local/bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/renderer/template_renderer.rb:52:in `render_template'
/usr/local/bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/renderer/template_renderer.rb:14:in `render'
/usr/local/bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/renderer/renderer.rb:42:in `render_template'
/usr/local/bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/renderer/renderer.rb:23:in `render'
/usr/local/bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/rendering.rb:103:in `_render_template'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/streaming.rb:217:in `_render_template'
/usr/local/bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/rendering.rb:83:in `render_to_body'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/rendering.rb:52:in `render_to_body'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/renderers.rb:144:in `render_to_body'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/abstract_controller/rendering.rb:26:in `render'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/rendering.rb:36:in `render'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/instrumentation.rb:44:in `block (2 levels) in render'
/usr/local/bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/core_ext/benchmark.rb:12:in `block in ms'
/usr/local/lib/ruby/2.3.0/benchmark.rb:308:in `realtime'
/usr/local/bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/core_ext/benchmark.rb:12:in `ms'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/instrumentation.rb:44:in `block in render'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/instrumentation.rb:87:in `cleanup_view_runtime'
/usr/local/bundle/gems/activerecord-<IP_ADDRESS>/lib/active_record/railties/controller_runtime.rb:25:in `cleanup_view_runtime'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/instrumentation.rb:43:in `render'
/hyper-mesh/spec/support/component_helpers.rb:149:in `block (2 levels) in build_test_url_for'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/basic_implicit_render.rb:4:in `send_action'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/abstract_controller/base.rb:188:in `process_action'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/rendering.rb:30:in `process_action'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/abstract_controller/callbacks.rb:20:in `block in process_action'
/usr/local/bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:126:in `call'
/usr/local/bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:506:in `block (2 levels) in compile'
/usr/local/bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:455:in `call'
/usr/local/bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:101:in `__run_callbacks__'
/usr/local/bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:750:in `_run_process_action_callbacks'
/usr/local/bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:90:in `run_callbacks'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/abstract_controller/callbacks.rb:19:in `process_action'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/rescue.rb:20:in `process_action'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/instrumentation.rb:32:in `block in process_action'
/usr/local/bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications.rb:164:in `block in instrument'
/usr/local/bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications/instrumenter.rb:21:in `instrument'
/usr/local/bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications.rb:164:in `instrument'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/instrumentation.rb:30:in `process_action'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/params_wrapper.rb:248:in `process_action'
/usr/local/bundle/gems/activerecord-<IP_ADDRESS>/lib/active_record/railties/controller_runtime.rb:18:in `process_action'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/abstract_controller/base.rb:126:in `process'
/usr/local/bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/rendering.rb:30:in `process'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal.rb:190:in `dispatch'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal.rb:262:in `dispatch'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/routing/route_set.rb:50:in `dispatch'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/routing/route_set.rb:32:in `serve'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/journey/router.rb:39:in `block in serve'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/journey/router.rb:26:in `each'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/journey/router.rb:26:in `serve'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/routing/route_set.rb:725:in `call'
/usr/local/bundle/gems/rack-2.0.1/lib/rack/etag.rb:25:in `call'
/usr/local/bundle/gems/rack-2.0.1/lib/rack/conditional_get.rb:25:in `call'
/usr/local/bundle/gems/rack-2.0.1/lib/rack/head.rb:12:in `call'
/usr/local/bundle/gems/rack-2.0.1/lib/rack/session/abstract/id.rb:222:in `context'
/usr/local/bundle/gems/rack-2.0.1/lib/rack/session/abstract/id.rb:216:in `call'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/cookies.rb:613:in `call'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/callbacks.rb:38:in `block in call'
/usr/local/bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:97:in `__run_callbacks__'
/usr/local/bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:750:in `_run_call_callbacks'
/usr/local/bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:90:in `run_callbacks'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/callbacks.rb:36:in `call'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/executor.rb:12:in `call'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/remote_ip.rb:79:in `call'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/debug_exceptions.rb:49:in `call'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/show_exceptions.rb:31:in `call'
/usr/local/bundle/gems/railties-<IP_ADDRESS>/lib/rails/rack/logger.rb:36:in `call_app'
/usr/local/bundle/gems/railties-<IP_ADDRESS>/lib/rails/rack/logger.rb:24:in `block in call'
/usr/local/bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/tagged_logging.rb:70:in `block in tagged'
/usr/local/bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/tagged_logging.rb:26:in `tagged'
/usr/local/bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/tagged_logging.rb:70:in `tagged'
/usr/local/bundle/gems/railties-<IP_ADDRESS>/lib/rails/rack/logger.rb:24:in `call'
/hyper-mesh/lib/synchromesh/synchromesh_controller.rb:25:in `call'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/request_id.rb:24:in `call'
/usr/local/bundle/gems/rack-2.0.1/lib/rack/method_override.rb:22:in `call'
/usr/local/bundle/gems/rack-2.0.1/lib/rack/runtime.rb:22:in `call'
/usr/local/bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/cache/strategy/local_cache_middleware.rb:28:in `call'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/executor.rb:12:in `call'
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/static.rb:136:in `call'
/usr/local/bundle/gems/rack-2.0.1/lib/rack/sendfile.rb:111:in `call'
/usr/local/bundle/gems/railties-<IP_ADDRESS>/lib/rails/engine.rb:522:in `call'
/usr/local/bundle/gems/rack-2.0.1/lib/rack/urlmap.rb:68:in `block in call'
/usr/local/bundle/gems/rack-2.0.1/lib/rack/urlmap.rb:53:in `each'
/usr/local/bundle/gems/rack-2.0.1/lib/rack/urlmap.rb:53:in `call'
/usr/local/bundle/gems/capybara-2.11.0/lib/capybara/server.rb:43:in `call'
/usr/local/bundle/gems/puma-3.6.2/lib/puma/configuration.rb:225:in `call'
/usr/local/bundle/gems/puma-3.6.2/lib/puma/server.rb:578:in `handle_request'
/usr/local/bundle/gems/puma-3.6.2/lib/puma/server.rb:415:in `process_client'
/usr/local/bundle/gems/puma-3.6.2/lib/puma/server.rb:275:in `block in run'
/usr/local/bundle/gems/puma-3.6.2/lib/puma/thread_pool.rb:116:in `block in spawn_thread'
^Crake aborted!
Interrupt:
/usr/local/bundle/gems/rspec-core-3.5.4/lib/rspec/core/rake_task.rb:79:in `system'
/usr/local/bundle/gems/rspec-core-3.5.4/lib/rspec/core/rake_task.rb:79:in `run_task'
/usr/local/bundle/gems/rspec-core-3.5.4/lib/rspec/core/rake_task.rb:96:in `block (2 levels) in define'
/usr/local/bundle/gems/rspec-core-3.5.4/lib/rspec/core/rake_task.rb:94:in `block in define'
/usr/local/bin/bundle:22:in `load'
/usr/local/bin/bundle:22:in `<main>'
Terminating WebSocket Server
Tasks: TOP => spec
(See full trace by running task with --trace)

so I'm a little confused by #19. does the PR fix this problem?

@catmando No, unfortunately, not as such. I was just hoping someone (more experienced with the project) could take a quick look and see if there's a major environment problem or something (since I'm getting a lot of failures). I'm re-running the specs as we speak and I'll hopefully attach the full log when it's done.

@catmando ok, it's not as bad as I thought it was, I can probably fix most of the errors easily, one run yields:
Failures:

  1) column types on client loads and converts the value
     Failure/Error:
       expect_promise do
         ReactiveRecord.load do
           TypeTest.columns_hash.collect do |attr, _info|
             [TypeTest.find(1).send(attr).class, TypeTest.find(1).send(attr)]
           end.flatten
         end
       end.to eq([
         'Number', 1,
         'NilClass', nil,
         'Boolean', true,

       expected: ["Number", 1, "NilClass", nil, "Boolean", true, "Date", "2003-02-01", "Time", "2003-02-01T00:00:00+00..."hello", "String", "goodby", "Time", "2000-01-01T00:00:00+0000", "Time", "2003-02-01T00:00:00+0000"]
            got: ["Number", 1, "NilClass", nil, "Boolean", true, "Date", "2003-02-01", "Time", "2003-02-01T00:00:00-00..."hello", "String", "goodby", "Time", "2000-01-01T00:00:00-0000", "Time", "2003-02-01T00:00:00-0000"]

       (compared using ==)
     # ./spec/synchromesh/column_types/column_type_spec.rb:185:in `block (2 levels) in <top (required)>'
     # /usr/local/bundle/gems/rspec-wait-0.0.9/lib/rspec/wait.rb:46:in `block (2 levels) in <top (required)>'

  2) column types on client while loading the dummy value delegates the correct type with operators etc
     Failure/Error:
       expect_evaluate_ruby do
         t = TypeTest.find(1)
         [
           !t.boolean, t.date+1, t.datetime+2.days, t.decimal + 5, t.float + 6, t.integer + 7,
           t.bigint + 8, t.string.length, t.text.length, t.time+3.days, t.timestamp+4.days
         ]
       end.to eq([
         true, "2001-01-02", (Timex.sqlmin+2.days).as_json, 5, 6, 7,
         8, 0, 0, (Timex.sqlmin+3.days).as_json, (Timex.sqlmin+4.days).as_json
       ])

       expected: [true, "2001-01-02", "2001-01-03T00:00:00+0000", 5, 6, 7, 8, 0, 0, "2001-01-04T00:00:00+0000", "2001-01-05T00:00:00+0000"]
            got: [true, "2001-01-02", "2001-01-03T00:00:00-0000", 5, 6, 7, 8, 0, 0, "2001-01-04T00:00:00-0000", "2001-01-05T00:00:00-0000"]

       (compared using ==)
     # ./spec/synchromesh/column_types/column_type_spec.rb:223:in `block (2 levels) in <top (required)>'
     # /usr/local/bundle/gems/rspec-wait-0.0.9/lib/rspec/wait.rb:46:in `block (2 levels) in <top (required)>'

  3) column types on client converts a time string to a time on writing
     Failure/Error:
       expect_evaluate_ruby do
         test = TypeTest.new
         test.datetime = "1/1/2001"
         (test.datetime + 1.minute)
       end.to eq((Timex.parse("1/1/2001") + 1.minute).as_json)

       expected: "2001-01-01T00:01:00+0000"
            got: "2001-01-01T00:01:00-0000"

       (compared using ==)
     # ./spec/synchromesh/column_types/column_type_spec.rb:236:in `block (2 levels) in <top (required)>'
     # /usr/local/bundle/gems/rspec-wait-0.0.9/lib/rspec/wait.rb:46:in `block (2 levels) in <top (required)>'

  4) column types on client converts a integer to a time on writing
     Failure/Error:
       expect_evaluate_ruby do
         test = TypeTest.new
         test.datetime = 12
         test.datetime + 60.seconds
       end.to eq((Timex.at(12)+60.seconds).as_json)

       expected: "1970-01-01T00:01:12+0000"
            got: "1970-01-01T00:01:12-0000"

       (compared using ==)
     # ./spec/synchromesh/column_types/column_type_spec.rb:244:in `block (2 levels) in <top (required)>'
     # /usr/local/bundle/gems/rspec-wait-0.0.9/lib/rspec/wait.rb:46:in `block (2 levels) in <top (required)>'

  5) column types on client converts a float to a time on writing
     Failure/Error:
       expect_evaluate_ruby do
         test = TypeTest.new
         test.datetime = 12.2
         test.datetime + 60.9
       end.to eq((Timex.at(12.2)+60.9).as_json)

       expected: "1970-01-01T00:01:13+0000"
            got: "1970-01-01T00:01:13-0000"

       (compared using ==)
     # ./spec/synchromesh/column_types/column_type_spec.rb:252:in `block (2 levels) in <top (required)>'
     # /usr/local/bundle/gems/rspec-wait-0.0.9/lib/rspec/wait.rb:46:in `block (2 levels) in <top (required)>'

  6) column types on client converts other dates just like time
     Failure/Error:
       expect_evaluate_ruby do
         [:datetime, :time, :timestamp].collect do |attr|
           TypeTest.new(attr => 12).send(attr)
         end.uniq
       end.to eq([Timex.at(12).as_json])

       expected: ["1970-01-01T00:00:12+0000"]
            got: ["1970-01-01T00:00:12-0000"]

       (compared using ==)
     # ./spec/synchromesh/column_types/column_type_spec.rb:268:in `block (2 levels) in <top (required)>'
     # /usr/local/bundle/gems/rspec-wait-0.0.9/lib/rspec/wait.rb:46:in `block (2 levels) in <top (required)>'

  7) column types on client uses the default value if specified for the dummy value
     Failure/Error:
       expect_evaluate_ruby do
         t = DefaultTest.find(1)
         [t.string, t.date, t.datetime]
       end.to eq(["I'm a string!", r.date.as_json, Timex.new(r.datetime.localtime).as_json])

       expected: ["I'm a string!", "2016-12-29", "2016-12-29T17:51:24+0000"]
            got: ["I'm a string!", "2016-12-29", "2016-12-29T17:51:24-0000"]

       (compared using ==)
     # ./spec/synchromesh/column_types/column_type_spec.rb:295:in `block (2 levels) in <top (required)>'
     # /usr/local/bundle/gems/rspec-wait-0.0.9/lib/rspec/wait.rb:46:in `block (2 levels) in <top (required)>'

  8) authorization integration will only synchronize the connected channels
     Failure/Error:
       model1.attributes_on_client(page).should eq({
         id: 1,
         created_at: model1.created_at.localtime.strftime('%Y-%m-%dT%H:%M:%S%z'),
         updated_at: model1.updated_at.localtime.strftime('%Y-%m-%dT%H:%M:%S%z')
       })

       expected: {:id=>1, :created_at=>"2016-12-29T17:55:06+0000", :updated_at=>"2016-12-29T17:55:07+0000"}
            got: {:id=>1, :updated_at=>"2016-12-29T17:55:07-0000", :created_at=>"2016-12-29T17:55:06-0000"}

       (compared using ==)

       Diff:

       @@ -1,4 +1,4 @@
       -:created_at => "2016-12-29T17:55:06+0000",
       +:created_at => "2016-12-29T17:55:06-0000",
        :id => 1,
       -:updated_at => "2016-12-29T17:55:07+0000",
       +:updated_at => "2016-12-29T17:55:07-0000",

     # ./spec/synchromesh/integration/authorization_spec.rb:75:in `block (2 levels) in <top (required)>'
     # /usr/local/bundle/gems/rspec-wait-0.0.9/lib/rspec/wait.rb:46:in `block (2 levels) in <top (required)>'

  9) authorization integration will fail on illegal class connections
     Failure/Error: model1.attributes_on_client(page).should eq({id: 1})

       expected: {:id=>1}
            got: {:id=>2}

       (compared using ==)

       Diff:
       @@ -1,2 +1,2 @@
       -:id => 1,
       +:id => 2,

     # ./spec/synchromesh/integration/authorization_spec.rb:98:in `block (2 levels) in <top (required)>'
     # /usr/local/bundle/gems/rspec-wait-0.0.9/lib/rspec/wait.rb:46:in `block (2 levels) in <top (required)>'

  10) authorization integration will fail on illegal instance connections
      Failure/Error: model1.attributes_on_client(page).should eq({id: 1})

        expected: {:id=>1}
             got: {:id=>3}

        (compared using ==)

        Diff:
        @@ -1,2 +1,2 @@
        -:id => 1,
        +:id => 3,

      # ./spec/synchromesh/integration/authorization_spec.rb:108:in `block (2 levels) in <top (required)>'
      # /usr/local/bundle/gems/rspec-wait-0.0.9/lib/rspec/wait.rb:46:in `block (2 levels) in <top (required)>'

  11) default_scope client tests a default scope can be added server side using either a block or proc
      Failure/Error: page.should have_content("0 unscoped items")
        expected #has_content?("0 unscoped items") to return true, got false
      # ./spec/synchromesh/integration/default_scope_spec.rb:56:in `block (3 levels) in <top (required)>'
      # /usr/local/bundle/gems/rspec-wait-0.0.9/lib/rspec/wait.rb:46:in `block (2 levels) in <top (required)>'

  12) default_scope client tests a default scope can be added client side
      Failure/Error: page.should have_content("0 unscoped items")
        expected #has_content?("0 unscoped items") to return true, got false
      # ./spec/synchromesh/integration/default_scope_spec.rb:96:in `block (3 levels) in <top (required)>'
      # /usr/local/bundle/gems/rspec-wait-0.0.9/lib/rspec/wait.rb:46:in `block (2 levels) in <top (required)>'

Finished in 20 minutes 18 seconds (files took 6.76 seconds to load)
219 examples, 12 failures, 6 pending

Quick look would indicate that the test environment is reporting GMT as -000 instead of expected +000
Failures 10 and 11 are worrisome as they in the auth spec
The last one is tough, as it's against the rendered output which u can't see!
I'll see if there is a way to fix the GMT problem first

for times showing +0000 -0000: This is ruby specifically, see:
https://bugs.ruby-lang.org/issues/691
https://codedump.io/share/jcuvHuHfBsbF/1/forcing-quot0000quot-timezone-for-rfc2822-times-in-ruby
Setting the Timezone will eliminate the problem of +0000 -0000
for tests done in PR#40


Added Discord Rich Presence in Baklava 🚀🌌

This feature adds Discord rich presence support (#1549) in the Electron wrapper/Baklava. Currently uses my own application but a future official DogeHouse discord application for things like OAuth would be attached here instead (and requires an icon to be added in the portal).
Preview
In Menus/Dashboard

In a room

The current problem is that fetching information about a room or all rooms requires you to sign in via either your own account or via a bot account. Ben will add an endpoint for fetching metadata from a room to be used in the header tags in Kibbeh. Once he has done that it allows for things like this:

Any contribution and reviews of this pull request would be highly appreciated. :)

@amitojsingh366 If you would like to add in room specific information in the In Room Discord presence in this pr you are more than welcome to.

Thanks for the PR, this is a great feature, but it seems that @amitojsingh366 has implemented full rpc in #1888


Administration page UI implementation

Contact Details
No response
GSSoC-22
yes
Type of Issue
UI Related
Description
Administration page UI should be implemented according to the UI. for now use the dummy data.
@chayan-dev will give you the Figma access.

Error Logs
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

I would like to work on this issue. Please assign me

@sitamadex11 could you give me Figma access

@Vibhuti2002 here is the figma link:   if you haven't got the link yet, otherwise ignore it.

@Vibhuti2002 can you give your email so to invite you figma file for Gssoc

@Vibhuti2002 can you give your email so to invite you to figma file for Gssoc

<EMAIL_ADDRESS>

invitation send.
feel free to reach out if you have any doubt.

any update @Vibhuti2002 ?

yeah i am working on the issue

Great. Take your time
On Fri, 18 Mar 2022, 6:28 pm vibhuti patil, @.***>
wrote:

yeah i am working on the issue
—
Reply to this email directly, view it on GitHub
https://github.com/ByteMonk-GCECT/GCECT-APP/issues/47#issuecomment-1072385833,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASIF5UG7VENP55PTO5CBWNLVAR4YRANCNFSM5QWEHB6A
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

Should i hard code the list below governing body text or should i use list view

yeah you can. Just put the text to string.


Minor refactor and comments

Merge #45 first because this PR includes changes from that branch. Will rebase this to tidy the diff
Clarifies what's going on with the coverage hack. No actual change.
Open to opinions on this, as these changes are opinionated based on what I found hard to understand from that code and what I find easier to read.

I think these are good additions. Thanks for doing this <3

Ready for review!


Carbon-Spec test writing requirements

@shinytoyrobots @joshblack
Hey Robin,
This is a draft of the requirements of two portions of the Carbon Spec initiative:

Test writing
Requirements writing

I can separate them into two separate RFC's if you'd like them to be discussed in isolation.
thanks!
Scott

Should support unit and end-to-end tests

Could you define these more concretely? Unit tests feel in scope, as do integration tests if we want to add those, but end-to-end seem to encroach on product teams and I'm not sure if that's a shared requirement for spec.

JavaScript executed on the DOM is separate from the assertions

This requirement seems to stem from the ability to supply tests to browser executors (like selenium). Should we instead state that the runner, or environment in which tests are run, supports a generic interface?

Tests accept window and optional DOM fragment

What's the underlying requirement here? Naively, it seems that tests must support being run in environments that can supply browser globals differently, either as a global or some other mechanism. Or, perhaps more abstractly, they are test framework agnostic?

Assertions do not have any dependencies outside of assertion definition

Would we instead want to state that the spec supports being run in any execution context? This seems like it could capture this idea, alongside the idea that we don't depend on any kind of test framework solution or internals in order to function as intended.

Tests are grouped by functionality

What underlying requirement is this addressing?

Tests should be exported and nest-able

100% agreed on exportable, what does nest-able mean in this context?


Incorrect indentation after loop with comment

Description
Having an end-of-line comment on the same line as a loop header appears to break indentation for subsequent lines. This didn't happen with the 1.4 line of code, but apparently got introduced with 1.5. I bisected the problem and identified 035363bb1fe240655bb3b9508a47ab7eae48becc as the culprit.
Input and Expected Output
The code looked like this before beautification, and should have looked like this after beautification as well:
for (var i = 0; i < 20; ++i) // loop
    if (i % 3) {
        console.log(i);
    }

Actual Output
The  code actually looked like this after beautification:
for (var i = 0; i < 20; ++i) // loop
    if (i % 3) {
    console.log(i);
}

Steps to Reproduce
I first observed this using the<EMAIL_ADDRESS>npm package.
But I can reproduce this on http://jsbeautifier.org/ right now, with default settings.

This problem has become more severe recently, namely since 21fac820c7a2605b674e69e9dca1a8500d4b63b0. Before that, a statement after the loop would somehow cause correct indentation for the block in question. Now this is no longer the case. So the input
for (var i = 0; i < 20; ++i) // loop
    if (i % 3) {
        console.log(i);
    }
console.log("done");

would stay in that form in versions up to 1.6.4, but 1.6.5 would turn it into
for (var i = 0; i < 20; ++i) // loop
    if (i % 3) {
    console.log(i);
}
console.log("done");


ERROR exit status 1

I'm running into an issue that isn't explained in the logs. I can't find the cause. The web interface works fine, and I've tried restarting it. It just refuses to scan, it has worked fine in the past. I don't know what's broken it.
> sudo journalctl -xeu watchyourlan | tail
Dec 09 18:03:45 nas watchyourlan[17210]: 2024/12/09 18:03:45 ERROR exit status 1
Dec 09 18:04:47 nas watchyourlan[17210]: 2024/12/09 18:04:47 ERROR exit status 1
Dec 09 18:05:51 nas watchyourlan[17210]: 2024/12/09 18:05:51 ERROR exit status 1
Dec 09 18:06:54 nas watchyourlan[17210]: 2024/12/09 18:06:54 ERROR exit status 1
Dec 09 18:07:58 nas watchyourlan[17210]: 2024/12/09 18:07:58 ERROR exit status 1
Dec 09 18:09:02 nas watchyourlan[17210]: 2024/12/09 18:09:02 ERROR exit status 1
Dec 09 18:10:06 nas watchyourlan[17210]: 2024/12/09 18:10:06 ERROR exit status 1
Dec 09 18:11:09 nas watchyourlan[17210]: 2024/12/09 18:11:09 ERROR exit status 1
Dec 09 18:12:12 nas watchyourlan[17210]: 2024/12/09 18:12:12 ERROR exit status 1
Dec 09 18:13:14 nas watchyourlan[17210]: 2024/12/09 18:13:14 ERROR exit status 1

❯ sudo systemctl restart watchyourlan.service

❯ sudo journalctl -xeu watchyourlan | tail
Dec 09 18:24:03 nas watchyourlan[6815]: 2024/12/09 18:24:03 INFO ARP_STRS_JOINED:
Dec 09 18:24:03 nas watchyourlan[6815]: 2024/12/09 18:24:03 INFO Log level=INFO
Dec 09 18:24:03 nas watchyourlan[6815]: 2024/12/09 18:24:03 INFO Using DB type=sqlite
Dec 09 18:24:03 nas watchyourlan[6815]: 2024/12/09 18:24:03 INFO Config dir path=/etc/watchyourlan/
Dec 09 18:24:03 nas watchyourlan[6815]: 2024/12/09 18:24:03 INFO ===================================
Dec 09 18:24:03 nas watchyourlan[6815]: 2024/12/09 18:24:03 INFO Web GUI at http://<IP_ADDRESS>:8840
Dec 09 18:24:03 nas watchyourlan[6815]: 2024/12/09 18:24:03 INFO ===================================
Dec 09 18:24:03 nas watchyourlan[6815]: 2024/12/09 18:24:03 ERROR exit status 1
Dec 09 18:24:04 nas watchyourlan[6815]: 2024/12/09 18:24:04 INFO Removing all History before date="2024-12-09 06:24:03"
Dec 09 18:24:04 nas watchyourlan[6815]: 2024/12/09 18:24:04 INFO Removed records from History n=110

What ever this is, it's stopping the package from scanning. I'm using the flag --ouifile=/usr/share/arp-scan/ieee-oui.txt.
❯ ls /usr/share/arp-scan/
ieee-oui.txt  ieee-oui.txt.bak

❯ sudo which arp-scan
/usr/sbin/arp-scan

❯ uname -a
Linux nas 6.6.62-v8+ #1817 SMP PREEMPT Wed Nov 20 13:34:18 GMT 2024 aarch64 GNU/Linux

❯ apt show watchyourlan
Package: watchyourlan
Version: 2.0.4
Status: install ok installed
Priority: optional
Section: utils
Maintainer: aceberg<EMAIL_ADDRESS>Installed-Size: 18.3 MB
Depends: arp-scan, tzdata
Homepage: https://github.com/aceberg/watchyourlan
License: MIT
Download-Size: unknown
APT-Manual-Installed: yes
APT-Sources: /var/lib/dpkg/status
Description: Lightweight network IP scanner with web GUI

❯ sudo arp-scan --version
arp-scan 1.10.0

❯ sudo arp-scan <IP_ADDRESS>
Interface: end0, type: EN10MB, MAC: d8:3a:dd:e7:7e:29, IPv4: <IP_ADDRESS>
Starting arp-scan 1.10.0 with 1 hosts (https://github.com/royhills/arp-scan)
<IP_ADDRESS>	3c:52:a1:xx:xx:xx	(Unknown)

56 packets received by filter, 0 packets dropped by kernel
Ending arp-scan 1.10.0: 1 hosts scanned in 0.355 seconds (2.82 hosts/sec). 1 responded

The error should have been "Network interface not found"


Security Manager org-level role - cloud beta

Summary
We are creating an org-level "Security Manager" role. Users will be able to apply the security manager role to any team. When applied it will grant the team's members the following permissions:

Read permission on all repositories in the organisation
Write permission on all security alerts in the organisation (i.e., the ability to resolve them)
Access to Security Center in the org Security tab
Write permission on security settings at the organisation level (including the ability to enable/disable GHAS)
Write permission on security settings at the repository level (including the ability to enable/disable GHAS)

Intended Outcome
This new role is intended to be used by members of a security team. It will remove the need for security team members to be organisation owners, which is a common workaround but provides these team members with more permissions than they would like (such as the ability to delete any repository).
How will it work?
Organisation owners and security managers will be able to grant the security manager role to teams. The team's members will then gain the permissions described above. If the security manager role is removed from a team its members will lose those permissions (unless they have them by virtue of another role, such as being an organisation owner, or a repository admin).

https://github.blog/changelog/2021-10-21-introducing-the-organization-level-security-manager-role/


Sudo for Bazel Install

The script fails on my system when trying to installed Bazel with a Permission Denied error. By using sudo on the copy and chmod the process succeeds.

Thanks for your contribution.
For example, in my case, I compile as root and without sudo in the docker. You can test if directory have permission:
chmod +x output/bazel
if [ -w /usr/local/ ]; then
cp output/bazel /usr/local/bin/
else
sudo cp output/bazel /usr/local/bin/
fi

Thanks!


Work with Relative Path in Shared Directory Events

Currently there are 2 events fired by SharedDirectory which contain paths and keys.
1.) "containedValueChanged": This event is fired by SubDirectory whose key is changed/deleted. The info provided on this event is:
export interface IValueChanged {
    key: string;
    previousValue: any;
}

2.) "valueChanged": This event is fired by SharedDirectory whose any key is changed/deleted. The info provided on this event is:
export interface IDirectoryValueChanged extends IValueChanged {
    path: string;
}

The path here is the absolute path for the directory firing the event. Not sure how useful it is since nobody might be interested in full absolute paths and knowing how deep they are in tree structure. If they want to, they can construct from the absolute path of the object they are working with and the relative path provided on the event.

We can change the IValueChanged to be:
interface IValueChanged {     path: string,     previousValue: any, }
where path represents the relative path from the object firing the event to the key that is modified/deleted. So, if we have directory structure:
root->A->B->c(key), and we change the value for key c,
1.) The path will be /A/B/c for "valueChanged" event.
2.) The path will be c for "containedValueChanged" event.

IValueChanged should definitely not add a path.  Both for the reasons Vlad describes ("reaching" via path frequently maps to violating encapsulation), but also because it is used by the map DDS where path is not a concept.
Could you describe the problem you're trying to solve?  I'm not certain what the motivation for this would be.

For IValueChanged, since it is fired by the parent directory only, key and relative path from object firing to value is changed is same. So, key === relative path for IValueChanged.

Here is a written proposal for the same:
https://microsoft-my.sharepoint-df.com/:w:/p/jatgarg/EVUL5BHmTkxBkqWtYds2O5kBdkRjdzE6kO8lIUhw_gVcJg?e=ak2D4U


Test Coverage X25519

Implement all tests for X25519 specified in RFC 7748, chapter 5.2 .

The missing tests runs are for factor 10^6, which does not terminate with the current implementation (#4).


Program arguments not yellow after ///

Sometimes people list arguments for a program after ///, which allows you to quickly explain the argument after the ///. The package does not highlight these arguments yellow.

This may be impossible to fix. The program applies tags to text inside the syntax command, but that's currently set as starting with syntax and ending with a newline. Ideally, to have this environment wrap over multiple lines, you'd want the environment to only end on a line that doesn't have a ///. But to do that, I think you'd need something like (?<!///[^\\n]+)\\n, i.e. the environment wouldn't end if it saw /// then any amount of text and then the end of the line.
However the regex engine that Atom uses doesn't allow look-behinds to be of variable length. There's no way to do this without having a regex match of variable length, because I don't know how much text would occur after the ///.

Success!
I realized that you could say begin with syntax and end with a newline \n, and then if you have comments inside that start with /// and end with a newline \n, then any comment will 'push' the end of the environment to the next line!
I'm super happy I figured this out. This will go out in an update sometime today.


Training with Visual Genome

When trying to train with the train/val splits and Visual Genome
python main.py --config config/butd_vqa.json --seed 1 --use_both --use_vg
I got this error
nParams=        41192896
optim: adamax lr=0.0010, decay_step=2, decay_rate=0.25,grad_clip=0.25
LR decay epochs: 15,17,19
gradual warmup lr: 0.0005
Traceback (most recent call last):
File "main.py", line 289, in
train(model, train_loader, eval_loader, args, device)
File "train.py", line 91, in train
sem_adj_matrix) in enumerate(train_loader):
File "python3.7/site-packages/torch/utils/data/dataloader.py", line 637, in next
return self._process_next_batch(batch)
File "python3.7/site-packages/torch/utils/data/dataloader.py", line 658, in _process_next_batch
raise batch.exc_type(batch.exc_msg)
TypeError: Traceback (most recent call last):
File "python3.7/site-packages/torch/utils/data/dataloader.py", line 138, in _worker_loop
samples = collate_fn([dataset[i] for i in batch_indices])
File "utils.py", line 172, in trim_collate
return [trim_collate(samples) for samples in transposed]
File "utils.py", line 172, in
return [trim_collate(samples) for samples in transposed]
File "utils.py", line 161, in trim_collate
return torch.LongTensor(batch)
TypeError: an integer is required (got type str)
I think the problem is in the process of encoding Genome questions. Do you have any ideas?

Sorry for the late reply. Are you still facing the same issue? I don't see similar error when training with Visual Genome.

The problem remains unsolved for me

I suspect is the question id. But to further debug, you can set the num_workers in data loader to 0 and use ipdb. Let me know if it helps.

I suspect is the question id. But to further debug, you can set the num_workers in data loader to 0 and use ipdb. Let me know if it helps.

I have the same problem in use VG, in your code, the return values of VGFeatureDataset is that return features, normalized_bb, question, target, raw_question,
image_id, bb, spatial_adj_matrix, semantic_adj_matrix,
I think the problem is from return value(raw_question)
in the VQAFeatureDataset, the return values is that return features, normalized_bb, question, target,
question_id, image_id, bb, spatial_adj_matrix,
semantic_adj_matrix
so I use (question_id) instead of (raw_question) in the return values of VGFeatureDataset, but there get the error:
/pytorch/aten/src/THC/THCTensorIndex.cu:362: void indexSelectLargeIndex(TensorInfo<T, IndexType>, TensorInfo<T, IndexType>, TensorInfo<long, IndexType>, int, int, IndexType, IndexType, long) [with T = float, IndexType = unsigned int, DstDim = 2, SrcDim = 2, IdxDim = -2, IndexIsMajor = true]: block: [20,0,0], thread: [39,0,0] Assertion srcIndex < srcSelectDimSize failed.
Traceback (most recent call last):
File "main.py", line 276, in
train(model, train_loader, eval_loader, args, device)
File "/media/xatu/83fce006-3950-4630-8a4d-d5db0016f6cf2/zpr/media/xatu/83fce006-3950-4630-8a4d-d5db0016f6cf2/zpr/VQA_reGAT/train.py", line 113, in train
spa_adj_matrix, target)
File "/home/xatu/anaconda2/envs/zpr/lib/python3.6/site-packages/torch/nn/modules/module.py", line 489, in call
result = self.forward(*input, **kwargs)
File "/home/xatu/anaconda2/envs/zpr/lib/python3.6/site-packages/torch/nn/parallel/data_parallel.py", line 143, in forward
outputs = self.parallel_apply(replicas, inputs, kwargs)
File "/home/xatu/anaconda2/envs/zpr/lib/python3.6/site-packages/torch/nn/parallel/data_parallel.py", line 153, in parallel_apply
return parallel_apply(replicas, inputs, kwargs, self.device_ids[:len(replicas)])
File "/home/xatu/anaconda2/envs/zpr/lib/python3.6/site-packages/torch/nn/parallel/parallel_apply.py", line 83, in parallel_apply
raise output
File "/home/xatu/anaconda2/envs/zpr/lib/python3.6/site-packages/torch/nn/parallel/parallel_apply.py", line 59, in _worker
output = module(*input, **kwargs)
File "/home/xatu/anaconda2/envs/zpr/lib/python3.6/site-packages/torch/nn/modules/module.py", line 489, in call
result = self.forward(*input, **kwargs)
File "/media/xatu/83fce006-3950-4630-8a4d-d5db0016f6cf2/zpr/media/xatu/83fce006-3950-4630-8a4d-d5db0016f6cf2/zpr/VQA_reGAT/model/regat.py", line 51, in forward
q_emb_seq = self.q_emb.forward_all(w_emb)  # [batch, q_len, q_dim]
File "/media/xatu/83fce006-3950-4630-8a4d-d5db0016f6cf2/zpr/media/xatu/83fce006-3950-4630-8a4d-d5db0016f6cf2/zpr/VQA_reGAT/model/language_model.py", line 111, in forward_all
output, hidden = self.rnn(x, hidden)
File "/home/xatu/anaconda2/envs/zpr/lib/python3.6/site-packages/torch/nn/modules/module.py", line 489, in call
result = self.forward(*input, **kwargs)
File "/home/xatu/anaconda2/envs/zpr/lib/python3.6/site-packages/torch/nn/modules/rnn.py", line 179, in forward
self.dropout, self.training, self.bidirectional, self.batch_first)
RuntimeError: CUDA error: device-side assert triggered
can you give me some suggestions for thr error? looking forward your reply, think you very much!

Closing this due to no further activities.


Bug: When I delete a partner that has opportunities, then search for opportunities, I get a 500 error.

I predict this error occurs because when a partner is deleted, all of it's opportunities are NOT deleted.

A temporary fix I can do is to disable the delete button on the front-end. Let me know your thoughts.


Jansson crashed when receiving emptied sub-object

I got a segmentation fault from my device when testing with the following emptied sub-object
{
"deviceIdentifier": "1B35D979",
"timestamp": "2022-10-24T14:09:57Z",
"payload": {}
}
Probably it failed from json_object_foreach() function.

The issue resolved,
Because of the payload was emptied, the "value" that from json_object_foreach() called function was return NULL.
json_object_foreach(obj, key, value);
Using the value for next called function caused sytem to crash.
I was calling: parse_json_aux(value); while value was NULL.


Fix bug #40: string.sub broken for j=0 or j<i

Hi,
This is great, thank you. I don't suppose you could also add the failing examples from the bug report to the test files for sub() in the following file?
https://github.com/gamesys/moonshine/blob/master/test/scripts/lib-string.lua
Many thanks

Great! Thank you for the very fast response. I've just added (and tested) the test cases. Hope it works.
PS: I haven't updated the built versions in the repository ("test-package.json", "moonshine{.min}.js").

Thank you for this PR. Sorry it took so long to test and resolve.


[Bug] Client: lobby join list

When logging to server sometimes the client list does not show some users, investigate and fix

When joining an empty server, the username does not always show up (username of current joining user)


Provisioned RKE1 Clusters are being marked as Custom on dashboard view

Setup

Rancher version: 2.7.2-rc7
Browser type & version:

Chrome v111.0.5563.147
Chrome v<IP_ADDRESS>
Vivaldi v5.5.2805.35

Describe the bug
If the user has a provisioned cluster, it will appear as a "Custom RKE1" cluster instead. If the user navigates to Cluster Management it will be labelled properly, and if they then move to the dashboard view it will be labelled as a provisioned nodedriver cluster as well. After any reloads, moving to the dashboard page will label it as a "Custom RKE1" cluster again.
To Reproduce

Login to Rancher
Provision a Linode, AWS or other nodedriver RKE1 cluster
Reload and navigate to the Dashboard page
Observe that the cluster is labelled as "Custom RKE1"
Navigate to Cluster Management
Observe that the cluster is labelled as "[Cloud Provider name] RKE1"
Navigate back to the Dashboard page
Observe that the cluster is labelled as "[Cloud Provider name] RKE1"

Result
The cluster is incorrectly labelled as a Custom cluster on the Dashboard page.
Expected Result
It should be labelled as a provisioned nodedriver [Cloud Providername ] cluster on the Dashboard page.
Screenshots
https://user-images.githubusercontent.com/85186645/229616280-4c53bac7-35c8-412c-8f9c-0c0c33f8a40f.mp4
Additional Context

Tested via provisioning with the rancher2 provider as well as manually
Verified against AWS and Linode provisioned RKE1 clusters
Verified this same behavior was present in Rancher v2.7.0

This issues requires an RKE1 cluster to test, so can't easily be automated at the moment

Test Environment:
Rancher version: v2.7-head 5334be3
Rancher cluster type: HA
Docker version: 20.10
Downstream cluster type: rke1 node driver cluster

Testing:
Tested this issue with the following steps:

Login to Rancher
Provision a Linode, AWS or other nodedriver RKE1 cluster
Reload and navigate to the Dashboard page
Observe that the cluster is labelled as "Custom RKE1"

Result
Now the cluster is labelled with the correct provider instead of Custom


ReferenceError: 'Symbol' is undefined in IE 11

Everything works fine in all the browsers including Edge. In IE 11 (and possibly more versions) I'm getting the error:
ReferenceError: 'Symbol' is undefined
I haven't changed the gulp and webpack files. is the bable transpiling working or do I have to do something for him to work?
Thank you.

Solved:
https://babeljs.io/docs/usage/polyfill/

@ranbuch closing this. Feel free to ask more related questions about polyfills.

Still getting the issue


Allow Istio to work with Cassandra and encrypt native connections

This PR removes Intranode and JMX ports from the Service, this way they are not proxyfied by Istio. When Istio proxyfies internodes ports it prevents local connections which is needed by Gossip protocol
HOST:PORT                                                           STATUS       SERVER      CLIENT           AUTHN POLICY                                 DESTINATION RULE
cassandra-e2e-exporter-jmx.cassandra-e2e.svc.cluster.local:9500     OK           STRICT      ISTIO_MUTUAL     /default                                     istio-system/default
cassandra-e2e.cassandra-e2e.svc.cluster.local:9042                  OK           STRICT      ISTIO_MUTUAL     /default                                     istio-system/default
cassandra-reaper.cassandra-e2e.svc.cluster.local:8080               OK           STRICT      ISTIO_MUTUAL     /default                                     istio-system/default

The proxy configuration that shows the TLS context can be found at https://pastebin.com/raw/jEmxXpwv

Question: if we remove the jmx port from the service, will we be able to:

have C* Reaper connect to the nodes?
have the operator contact the nodes for jolokia commands?

Question: if we remove the jmx port from the service, will we be able to:

have C* Reaper connect to the nodes?
have the operator contact the nodes for jolokia commands?
Ports on pods are still exposed to the outside world