clio / ten_years_rails Goto Github PK

View Code? Open in Web Editor NEW

167.0 167.0 43.0 72 KB

A companion gem for the "Ten Years of Rails Upgrades" talk

Home Page: https://www.youtube.com/watch?v=6aCfc0DkSFo

License: MIT License

Ruby 94.47% Shell 5.53%

ten_years_rails's People

Contributors

Stargazers

Watchers

Forkers

jasnow fastruby knappe akiokio pendletons bronzdoc 23years mctaylorpants lucasvel cristisomesan cliodanieljelenici arunguleria

ten_years_rails's Issues

bin/next command source code?

My friend @pcreux pinged me about your talk and I really liked it 👏

Would you be so kind to share bin/next command source code, or it only 1 bash script ?

It would be nice to have a way to Run Rails next on production or even better staging and see what CI did not catch :)

Can't install into Rails 3 project

I'm trying to add this to a Rails 3 project to start a Rails 4 upgrade, and ignoring #9 it won't even bundle. It seems ten_years_rails says it requires actionview for something, and that was only introduced as a standalone gem with rails 4 so the install fails:

Bundler could not find compatible versions for gem "activesupport":
  In snapshot (Gemfile.lock):
    activesupport (= 3.2.22.13)

  In Gemfile:
    ten_years_rails was resolved to 0.2.0, which depends on
      actionview was resolved to 4.1.0.beta1, which depends on
        activesupport (= 4.1.0.beta1)

    rails (~> 3.2.22.13) was resolved to 3.2.22.13, which depends on
      activesupport (= 3.2.22.13)

Running `bundle update` will rebuild your snapshot from scratch, using only
the gems in your Gemfile, which may resolve the conflict.

Dependency uses GPL 2.0 license - Replace Colorize

We are currently adding ten_years_rails in our app, and one of our security tools got a vulnerability on using this gem. Basically ten_years_rails is using colorized which is under GPL-2.0 license. The license enforces that "the source code of the work must be made available under the same license". As far as I could understand we shouldn't be using it on a private project, even if the ten_years_rails is under MIT license.

There is an issue on colorized regarding this, and there is also another gem that could replace colorize for this case. Gitlab CE had a similar issue and created this PR: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/4425.

Let me know if I can help with anything or if you have another interpretation for this.

CVE-2020-15169 - ActionView

A vulnerability has been opened against this repository. This vulnerability has been
assessed as medium. The deadline for remediation is ?.

The latest vulnerability details can be found at https://github.com/clio/security-vulnerabilities/issues/227

This ticket has been automatically generated. The entry in Overlord specifies as this repository's owner.

`next bundle` fails on version 0.2.0

Hi @jnraine,

I'm trying to use the next command but I keep running into this weird issue:

$ next bundle
The git source https://github.com/rails/sass-rails.git is not yet checked out. Please run `bundle install` before trying to start your application

What makes it weird is that running BUNDLE_GEMFILE=Gemfile.next bundle install actually works.

Here is the log from my console.

$ next bundle install
The git source https://github.com/rails/sass-rails.git is not yet checked out. Please run `bundle install` before trying to start your application
$ BUNDLE_GEMFILE=Gemfile.next bundle install
Fetching https://github.com/rails/sass-rails.git
Fetching https://github.com/fastruby/blog.git
The dependency tzinfo-data (>= 0) will be unused by any of the platforms Bundler is installing for. Bundler is installing for ruby but the dependency is only for x86-mingw32, x86-mswin32, x64-mingw32, java. To add those platforms to the bundle, run `bundle lock --add-platform x86-mingw32 x86-mswin32 x64-mingw32 java`.
Fetching gem metadata from https://rubygems.org/..........
Fetching gem metadata from https://rubygems.org/.
Resolving dependencies.......
Using rake 12.3.2
Fetching concurrent-ruby 1.1.5
Using minitest 5.11.3
Using thread_safe 0.3.6
Using builder 3.2.3
Using erubi 1.8.0
Using mini_portile2 2.4.0
Using crass 1.0.4
Fetching rack 2.0.7
Installing rack 2.0.7
Installing concurrent-ruby 1.1.5
Using nio4r 2.3.1
Using websocket-extensions 0.1.3
Using mini_mime 1.0.1
Using arel 8.0.0
Using public_suffix 3.0.3
Fetching bindex 0.7.0
Fetching dotenv 2.7.2
Installing bindex 0.7.0 with native extensions
Installing dotenv 2.7.2
Using colorator 1.1.0
Using rb-fsevent 0.10.3
Using ffi 1.10.0
Using ruby_dep 1.5.0
Using kramdown 1.17.0
Using liquid 4.0.3
Using mercenary 0.3.6
Using forwardable-extended 2.6.0
Using rouge 2.2.1
Using safe_yaml 1.0.5
Using jekyll-paginate 1.1.0
Using titleize 1.4.1
Using multi_json 1.13.1
Using redcarpet 3.4.0
Using rspec-support 3.5.0
Using diff-lcs 1.3
Using bundler 2.0.1
Fetching byebug 11.0.1
Installing byebug 11.0.1 with native extensions
Fetching mime-types-data 3.2019.0331
Installing mime-types-data 3.2019.0331
Using colorize 0.8.1
Using connection_pool 2.2.2
Using unf_ext 0.0.7.5
Using method_source 0.9.2
Using thor 0.19.4
Using htmlentities 4.3.4
Using excon 0.62.0
Using execjs 2.7.0
Using multipart-post 2.0.0
Using flipper 0.16.1
Using formatador 0.2.5
Using ipaddress 0.8.3
Fetching json 2.2.0
Installing json 2.2.0 with native extensions
Using netrc 0.11.0
Using pg 0.21.0
Fetching puma 3.12.1
Installing puma 3.12.1 with native extensions
Using redis 4.1.0
Using rubyzip 1.2.2
Fetching tilt 2.0.9
Installing tilt 2.0.9
Using turbolinks-source 5.2.0
Using tzinfo 1.2.5
Using sitemap_generator 6.0.2
Fetching nokogiri 1.10.2
Fetching i18n 1.6.0
Installing i18n 1.6.0
Using websocket-driver 0.6.5
Using mail 2.7.1
Using addressable 2.6.0
Using rack-test 1.1.0
Using heroku-deflater 0.6.3
Using rack-protection 2.0.5
Fetching sprockets 3.7.2
Installing sprockets 3.7.2
Installing nokogiri 1.10.2 with native extensions
Using rb-inotify 0.10.0
Using childprocess 0.9.0
Fetching sassc 2.0.1
Installing sassc 2.0.1 with native extensions
Using pathutil 0.16.2
Using jekyll-titleize 0.1.0
Using pygments.rb 1.2.1
Using rspec-core 3.5.4
Using rspec-expectations 3.5.0
Using rspec-mocks 3.5.0
Using mime-types 3.2.2
Using unf 0.1.4
Using faraday 0.15.4
Using foreman 0.85.0
Using net-http-persistent 3.0.0
Using uglifier 4.1.20
Using turbolinks 5.2.0
Fetching recaptcha 4.14.0
Installing recaptcha 4.14.0
Fetching activesupport 5.1.7
Installing activesupport 5.1.7
Using launchy 2.4.3
Using sidekiq 5.2.5
Using sass-listen 4.0.0
Using listen 3.1.5
Using selenium-webdriver 3.141.0
Using loofah 2.2.3
Using xpath 2.1.0
Using rspec_junit_formatter 0.4.1
Using rspec 3.5.0
Fetching fog-core 2.1.2
Installing fog-core 2.1.2
Using domain_name 0.5.20180417
Fetching stripe 4.12.0
Installing stripe 4.12.0
Using rails-dom-testing 2.0.3
Using globalid 0.4.2
Fetching activemodel 5.1.7
Installing activemodel 5.1.7
Using jbuilder 2.8.0
Using shoulda-matchers 4.0.0.rc1
Using spring 2.0.2
Using email_spec 2.2.0
Fetching sass 3.7.4
Installing sass 3.7.4
Using jekyll-watch 1.5.1
Using rails-html-sanitizer 1.0.4
Using capybara 2.13.0
Using fog-json 1.2.0
Using fog-xml 0.1.3
Using http-cookie 1.0.3
Fetching activejob 5.1.7
Installing activejob 5.1.7
Fetching activerecord 5.1.7
Installing activerecord 5.1.7
Using carrierwave 1.3.1
Using spring-watcher-listen 2.0.1
Using jekyll-sass-converter 1.5.2
Fetching actionview 5.1.7
Installing actionview 5.1.7
Fetching fog-aws 3.4.0
Installing fog-aws 3.4.0
Using rest-client 2.0.2
Using flipper-active_record 0.16.1
Using jekyll 3.6.3
Fetching actionpack 5.1.7
Installing actionpack 5.1.7
Using ten_years_rails 0.2.0
Using jekyll-authors 0.0.3
Using jekyll-categories 0.0.2
Using jekyll-feed 0.11.0
Fetching actioncable 5.1.7
Installing actioncable 5.1.7
Fetching actionmailer 5.1.7
Installing actionmailer 5.1.7
Fetching railties 5.1.7
Installing railties 5.1.7
Using sprockets-rails 3.2.1
Using blog 1.0.0 from https://github.com/fastruby/blog.git (at master@52e5c27)
Fetching dotenv-rails 2.7.2
Using rspec-rails 3.5.2
Using web-console 3.7.0
Fetching rails 5.1.7
Installing rails 5.1.7
Installing dotenv-rails 2.7.2
Fetching sassc-rails 2.1.0
Installing sassc-rails 2.1.0
Using sass-rails 6.0.0.beta2 from https://github.com/rails/sass-rails.git (at master@ff54c20)
Bundle complete! 32 Gemfile dependencies, 136 gems now installed.
Use `bundle info [gemname]` to see where a bundled gem is installed.
Post-install message from i18n:

HEADS UP! i18n 1.1 changed fallbacks to exclude default locale.
But that may break your application.

Please check your Rails app for 'config.i18n.fallbacks = true'.
If you're using I18n (>= 1.1.0) and Rails (< 5.2.2), this should be
'config.i18n.fallbacks = [I18n.default_locale]'.
If not, fallbacks will be broken in your app by I18n 1.1.x.

For more info see:
https://github.com/svenfuchs/i18n/releases/tag/v1.1.0

Post-install message from sass:

Ruby Sass has reached end-of-life and should no longer be used.

* If you use Sass as a command-line tool, we recommend using Dart Sass, the new
  primary implementation: https://sass-lang.com/install

* If you use Sass as a plug-in for a Ruby web framework, we recommend using the
  sassc gem: https://github.com/sass/sassc-ruby#readme

* For more details, please refer to the Sass blog:
  https://sass-lang.com/blog/posts/7828841

I don't think I'm doing anything weird while using this script. These are the steps I followed:

next --init
next bundle install

This is the part of the Gemfile that is relevant to this issue:

source 'https://rubygems.org'

def next?
  File.basename(__FILE__) == "Gemfile.next"
end

git_source(:github) do |repo_name|
  repo_name = "#{repo_name}/#{repo_name}" unless repo_name.include?("/")
  "https://github.com/#{repo_name}.git"
end

# Bundle edge Rails instead: gem 'rails', github: 'rails/rails'
gem 'rails', '~> 5.1.0.rc1'
# Use postgresql as the database for Active Record
gem 'pg', '~> 0.18'
# Use Puma as the app server
gem 'puma', '~> 3.7'
# Use SCSS for stylesheets
gem 'sass-rails', github: "rails/sass-rails"

Do you know what could be the issue here?

BUNDLE_CACHE_PATH purpose?

Hi @jnraine! First of all, thanks for sharing your work. It has been tremendously helpful.

I was wondering what's use for setting a custom BUNDLE_CACHE_PATH in exe/next.sh? It looks like it is only useful if you use bundle package for your deployments? Could you provide some detail on how you use it?

Thanks!

Incompatible with Ruby < 2.3

Hey @jnraine,

It seems that the gem is incompatible with some versions of Ruby (< 2.3)

$ gem install ten_years_rails
Fetching: concurrent-ruby-1.1.5.gem (100%)
Successfully installed concurrent-ruby-1.1.5
Fetching: i18n-1.6.0.gem (100%)
ERROR:  Error installing ten_years_rails:
	The last version of i18n (>= 0.7, < 2) to support your Ruby & RubyGems was 1.5.1. Try installing it with `gem install i18n -v 1.5.1` and then running the current command again
	i18n requires Ruby version >= 2.3.0. The current ruby version is 2.2.0.

Everything works fine with Ruby >= 2.3.0:

$ rvm use 2.3.1
Using /Users/etagwerker/.rvm/gems/ruby-2.3.1
$ gem install ten_years_rails
Fetching: rest-client-2.0.2.gem (100%)
Successfully installed rest-client-2.0.2
Fetching: ten_years_rails-0.2.0.gem (100%)
Successfully installed ten_years_rails-0.2.0
Parsing documentation for rest-client-2.0.2
Installing ri documentation for rest-client-2.0.2
Parsing documentation for ten_years_rails-0.2.0
Installing ri documentation for ten_years_rails-0.2.0
Done installing documentation for rest-client, ten_years_rails after 4 seconds
2 gems installed

I see a couple of options to solve this problem:

Remove dependencies (maybe active_support and action_view are not really necessary and we can find alternative solutions)
Define spec.required_ruby_version in the .gemspec file

What do you think?

Missing dependencies in .gemspec

Hey @jnraine,

Thanks for publishing this gem and your talk at RailsConf! I just gave it a go and I found a couple of issues:

It seems that the colorize dependency is not listed in the gemspec file.

$ bundle_report outdated
/Users/etagwerker/.rvm/gems/ruby-2.4.3@ombu/gems/ten_years_rails_conf_2018-0.1.0/exe/bundle_report:49:in `block in <top (required)>': uninitialized constant BundleReport (NameError)
Did you mean?  Bundler
/Users/etagwerker/.rvm/gems/ruby-2.4.3@ombu/gems/ten_years_rails_conf_2018-0.1.0/exe/bundle_report:60:in `require': cannot load such file -- colorize (LoadError)
 from /Users/etagwerker/.rvm/gems/ruby-2.4.3@ombu/gems/ten_years_rails_conf_2018-0.1.0/exe/bundle_report:60:in `<top (required)>'
 from /Users/etagwerker/.rvm/gems/ruby-2.4.3@ombu/bin/bundle_report:23:in `load'
 from /Users/etagwerker/.rvm/gems/ruby-2.4.3@ombu/bin/bundle_report:23:in `<main>'
 from /Users/etagwerker/.rvm/gems/ruby-2.4.3@ombu/bin/ruby_executable_hooks:15:in `eval'
 from /Users/etagwerker/.rvm/gems/ruby-2.4.3@ombu/bin/ruby_executable_hooks:15:in `<main>'

Another dependency that is missing is rest-client:

 $ bundle_report outdated
 /Users/etagwerker/Projects/ombulabs/ten_years_rails_conf_2018/exe/bundle_report:49:in `block in <top (required)>': uninitialized constant BundleReport (NameError)
 Did you mean?  Bundler
 /Users/etagwerker/Projects/ombulabs/ten_years_rails_conf_2018/exe/bundle_report:64:in `require': cannot load such file -- rest-client (LoadError)
 	from /Users/etagwerker/Projects/ombulabs/ten_years_rails_conf_2018/exe/bundle_report:64:in `<top (required)>'
 	from /Users/etagwerker/.rvm/gems/ruby-2.4.3@ombu/bin/bundle_report:23:in `load'
 	from /Users/etagwerker/.rvm/gems/ruby-2.4.3@ombu/bin/bundle_report:23:in `<main>'
 	from /Users/etagwerker/.rvm/gems/ruby-2.4.3@ombu/bin/ruby_executable_hooks:15:in `eval'
 	from /Users/etagwerker/.rvm/gems/ruby-2.4.3@ombu/bin/ruby_executable_hooks:15:in `<main>'

I'm going to submit a PR for this. Adding it to the gemspec file solves this problem.

Thanks!

Tests are failing

Hey @jnraine,

It seems that the specs are failing right now. When I try to run them I get this:

$ bundle exec rspec spec

An error occurred while loading ./spec/deprecation_tracker_spec.rb.
Failure/Error: require_relative "../support/deprecation_tracker"

LoadError:
  cannot load such file -- /Users/etagwerker/Projects/fastruby/ten_years_rails_conf_2018/support/deprecation_tracker
# ./spec/deprecation_tracker_spec.rb:2:in `require_relative'
# ./spec/deprecation_tracker_spec.rb:2:in `<top (required)>'

Finished in 0.00023 seconds (files took 0.21704 seconds to load)
0 examples, 0 failures, 1 error occurred outside of examples

I'd like to start contributing more changes to your library but I wanted to make sure that I don't break anything in the process...

SyntaxError with Ruby 2.2.10

Hey @jnraine,

These are some issues that I ran into when testing the gem with Ruby 2.2.10. It's a follow up issue to #9.

SyntaxError: /Users/etagwerker/.rvm/gems/ruby-2.2.10@petitions/gems/ten_years_rails-0.2.0/lib/deprecation_tracker.rb:121: syntax error, unexpected '.'
    new_shitlist&.delete
                  ^
/Users/etagwerker/.rvm/gems/ruby-2.2.10@petitions/gems/activesupport-4.2.11.1/lib/active_support/dependencies.rb:274:in `require'
/Users/etagwerker/.rvm/gems/ruby-2.2.10@petitions/gems/activesupport-4.2.11.1/lib/active_support/dependencies.rb:274:in `block in require'
/Users/etagwerker/.rvm/gems/ruby-2.2.10@petitions/gems/activesupport-4.2.11.1/lib/active_support/dependencies.rb:240:in `load_dependency'
/Users/etagwerker/.rvm/gems/ruby-2.2.10@petitions/gems/activesupport-4.2.11.1/lib/active_support/dependencies.rb:274:in `require'
/Users/etagwerker/.rvm/gems/ruby-2.2.10@petitions/gems/ten_years_rails-0.2.0/lib/ten_years_rails.rb:2:in `<top (required)>'
/Users/etagwerker/Projects/fastruby/e-petitions/config/application.rb:7:in `<top (required)>'
/Users/etagwerker/Projects/fastruby/e-petitions/Rakefile:4:in `require'
/Users/etagwerker/Projects/fastruby/e-petitions/Rakefile:4:in `<top (required)>'
/Users/etagwerker/.rvm/gems/ruby-2.2.10@petitions/gems/rake-12.3.2/exe/rake:27:in `<top (required)>'
/Users/etagwerker/.rvm/gems/ruby-2.2.10@petitions/bin/ruby_executable_hooks:24:in `eval'
/Users/etagwerker/.rvm/gems/ruby-2.2.10@petitions/bin/ruby_executable_hooks:24:in `<main>'
(See full trace by running task with --trace)

Root cause: Ampersand operator was introduced in Ruby 2.3.0 (more here: http://mitrev.net/ruby/2015/11/13/the-operator-in-ruby/)

SyntaxError: /Users/etagwerker/.rvm/gems/ruby-2.2.10@petitions/gems/ten_years_rails-0.2.0/lib/deprecation_tracker.rb:88: syntax error, unexpected <<
      message = <<~MESSAGE.red
                  ^
/Users/etagwerker/.rvm/gems/ruby-2.2.10@petitions/gems/ten_years_rails-0.2.0/lib/deprecation_tracker.rb:95: syntax error, unexpected tIDENTIFIER, expecting keyword_do or '{' or '('
        To check your failures locally, you can run:
                ^
/Users/etagwerker/.rvm/gems/ruby-2.2.10@petitions/gems/ten_years_rails-0.2.0/lib/deprecation_tracker.rb:95: syntax error, unexpected tIDENTIFIER, expecting keyword_do or '{' or '('
        To check your failures locally, you can run:
                                               ^
/Users/etagwerker/.rvm/gems/ruby-2.2.10@petitions/gems/ten_years_rails-0.2.0/lib/deprecation_tracker.rb:97: dynamic constant assignment
        DEPRECATION_TRACKER=compare bundle exec rspec #{c...
                            ^
/Users/etagwerker/.rvm/gems/ruby-2.2.10@petitions/gems/ten_years_rails-0.2.0/lib/deprecation_tracker.rb:97: syntax error, unexpected tIDENTIFIER, expecting keyword_do or '{' or '('
...RECATION_TRACKER=compare bundle exec rspec #{changed_buckets...
...                               ^
/Users/etagwerker/.rvm/gems/ruby-2.2.10@petitions/gems/ten_years_rails-0.2.0/lib/deprecation_tracker.rb:103: syntax error, unexpected $undefined, expecting keyword_do or '{' or '('
        See \e[4;37mdev-docs/testing/depre...
             ^
/Users/etagwerker/.rvm/gems/ruby-2.2.10@petitions/gems/ten_years_rails-0.2.0/lib/deprecation_tracker.rb:103: syntax error, unexpected ';', expecting ']'
        See \e[4;37mdev-docs/testing/deprecati...
                 ^
/Users/etagwerker/.rvm/gems/ruby-2.2.10@petitions/gems/ten_years_rails-0.2.0/lib/deprecation_tracker.rb:103: syntax error, unexpected $undefined, expecting keyword_end
...testing/deprecation_tracker.md\e[0;31m for more information.
...                               ^
/Users/etagwerker/.rvm/gems/ruby-2.2.10@petitions/gems/ten_years_rails-0.2.0/lib/deprecation_tracker.rb:103: syntax error, unexpected ';', expecting ']'
...ing/deprecation_tracker.md\e[0;31m for more information.
...                               ^
/Users/etagwerker/.rvm/gems/ruby-2.2.10@petitions/gems/ten_years_rails-0.2.0/lib/deprecation_tracker.rb:103: syntax error, unexpected tIDENTIFIER, expecting keyword_do or '{' or '('
...md\e[0;31m for more information.
...                               ^
/Users/etagwerker/.rvm/gems/ruby-2.2.10@petitions/gems/ten_years_rails-0.2.0/lib/deprecation_tracker.rb:121: syntax error, unexpected '.'
    new_shitlist&.delete
                  ^
/Users/etagwerker/.rvm/gems/ruby-2.2.10@petitions/gems/activesupport-4.2.11.1/lib/active_support/dependencies.rb:274:in `require'
/Users/etagwerker/.rvm/gems/ruby-2.2.10@petitions/gems/activesupport-4.2.11.1/lib/active_support/dependencies.rb:274:in `block in require'
/Users/etagwerker/.rvm/gems/ruby-2.2.10@petitions/gems/activesupport-4.2.11.1/lib/active_support/dependencies.rb:240:in `load_dependency'
/Users/etagwerker/.rvm/gems/ruby-2.2.10@petitions/gems/activesupport-4.2.11.1/lib/active_support/dependencies.rb:274:in `require'
/Users/etagwerker/.rvm/gems/ruby-2.2.10@petitions/gems/ten_years_rails-0.2.0/lib/ten_years_rails.rb:2:in `<top (required)>'
/Users/etagwerker/Projects/fastruby/e-petitions/config/application.rb:7:in `<top (required)>'
/Users/etagwerker/Projects/fastruby/e-petitions/Rakefile:4:in `require'
/Users/etagwerker/Projects/fastruby/e-petitions/Rakefile:4:in `<top (required)>'
/Users/etagwerker/.rvm/gems/ruby-2.2.10@petitions/gems/rake-12.3.2/exe/rake:27:in `<top (required)>'
/Users/etagwerker/.rvm/gems/ruby-2.2.10@petitions/bin/ruby_executable_hooks:24:in `eval'
/Users/etagwerker/.rvm/gems/ruby-2.2.10@petitions/bin/ruby_executable_hooks:24:in `<main>'
(See full trace by running task with --trace)

Root cause: The squiggly operator was introduced in Ruby 2.3.0 (more here: https://infinum.co/the-capsized-eight/multiline-strings-ruby-2-3-0-the-squiggly-heredoc)

I'm working on a PR for these issues. I'll submit it later today.

Thanks!

CVE-2020-26247 - nokogiri

Please note, currently the version with a fix for this vulnerability is in 1.11.0.rc4, and a new 1.11.0 version has not been released at the time of this ticket's creation. Due to the low risk of this vulnerability, the AppSec team believes it is safer to wait until version 1.11.0 is released before making the update

A vulnerability has been opened against this repository. This vulnerability has been
assessed as low. The deadline for remediation is ?.

The latest vulnerability details can be found at https://github.com/clio/security-vulnerabilities/issues/274

This ticket has been automatically generated. The entry in Overlord specifies as this repository's owner.

clio / ten_years_rails Goto Github PK

ten_years_rails's People

Contributors

Stargazers

Watchers

Forkers

ten_years_rails's Issues

bin/next command source code?

Can't install into Rails 3 project

Dependency uses GPL 2.0 license - Replace Colorize

CVE-2020-15169 - ActionView

`next bundle` fails on version 0.2.0

BUNDLE_CACHE_PATH purpose?

Incompatible with Ruby < 2.3

Missing dependencies in .gemspec

Tests are failing

SyntaxError with Ruby 2.2.10

CVE-2020-26247 - nokogiri

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent