| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
|\
| |
| |
| | |
Update to Turbolinks 5.0.0 final
|
| | |
|
|/ |
|
|
|
|
| |
per security release today --> https://groups.google.com/forum/#!topic/ruby-security-ann/RCHyF5K9Lbc
|
| |
|
|
|
|
| |
blade-sauce_labs_plugin gem
|
|
|
|
|
|
|
|
| |
Allow failures until test runs are consistently stable, not hanging.
Closes #24943.
Signed-off-by: Jeremy Daer <jeremydaer@gmail.com>
|
| |
|
|
|
|
|
|
|
|
|
| |
Apps that depend on Action Cable don't need Blade for app development,
so we can remove the gem dependency.
We do need Blade for Action Cable dev, so we bundle it in the Gemfile.
Signed-off-by: Jeremy Daer <jeremydaer@gmail.com>
|
| |
|
|\
| |
| |
| | |
Add prepared statements support for `Mysql2Adapter`
|
| | |
|
|/
|
|
|
|
|
|
|
| |
Without the `wdm` gem, it appears that `listen` keeps an open handle to
each of these files, causing them not to be removed when the tempdir
tries to clean iteslf up, and then directory to fail to unlink. In
addition to fixing that particular failure, we now construct OS agnostic
paths, and capture exceptions if the directory fails to unlink so that
minitest will report it rather than crash
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Uses latest precompiled JRuby so that
we don't spend time downloading versions Travis has
not already compiled. http://rubies.travis-ci.org/
Uses latest jdk: oraclejdk8
per
https://docs.travis-ci.com/user/build-environment-updates/2015-02-03/#Ruby-VM
and
https://docs.travis-ci.com/user/languages/ruby/#Supported-Ruby-Versions-and-RVM
Follows on work in https://github.com/rails/rails/pull/23927 which was reverted
https://github.com/rails/rails/commit/26fe5fa08d52384bcea09c4210e3b3baaf5e9b95
JRUBY_OPTS minimize GC, disable JIT, for max test speed
- https://github.com/rails/rails/pull/16613
- https://github.com/rails/rails/pull/17088
Have Rails use JRuby-compatible Rake 11.1
- The Rake task was passing --verbose, an invalid option, to contemporary JRuby
- https://github.com/ruby/rake/pull/120
- https://github.com/rails-api/active_model_serializers/pull/1585
- https://github.com/jruby/jruby/issues/3653#issuecomment-195883717
No advantage to directly mounting JRuby over installing from cache; both on S3
- https://github.com/rails/rails/pull/23499/commits/b2d5b336b5a812009444571b22eed90777cd9a8c
- https://github.com/rails/rails/pull/23499/commits/f4fad041b2755d81e82ee3fc66d96f334b4653db
|
| |
|
|
|
|
|
|
| |
This undoes https://github.com/rails/rails/commit/7241498e51120b9847a8bc16cf48551db0f3e216
https://github.com/codahale/bcrypt-ruby/issues/128 is fixed and closed.
|
|
|
| |
Changes "as has to be loaded" to "as it has to be loaded"
|
|
|
|
| |
Ref - https://github.com/turbolinks/turbolinks-rails/pull/3
|
| |
|
|
|
| |
All modern Rubies ship JSON as part of stdlib. Using the gem actually hurts multi-platform support due to build difficulties on Windows.
|
|
|
|
|
|
| |
This new adapter does get a little more intimate with the redis-rb gem's
implementation than I would like, but it's the least bad of the
approaches I've come up with.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
This PR includes two changes for 2.0.0:
- Breaking API change around `async.perform` --> `perform_async`
- New addition of `perform_in`, which now allows end users of the
adapter to use the `enqueued_at` public API method.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
It will make sure that the generated application in the tests get the
gem.
|
|\
| |
| |
| | |
Remove legacy mysql adapter
|
| | |
|
| |
| |
| |
| | |
Active Job
|
| |
| |
| |
| | |
Many CVEs released: https://groups.google.com/forum/#!topic/ruby-security-ann/aSbgDiwb24s
|
| | |
|
| | |
|
| | |
|
|/ |
|
| |
|
|\ |
|
| |\ |
|
| | | |
|
| |/
| |
| |
| |
| | |
"conditionals in the gemfile creates conditional code in the Gemfile.lock.
Since it is checked in the repository I think it is better to avoid it"
|
| |
| |
| |
| |
| |
| | |
bcrypt 3.1.0 doesn't load on Windows. See
https://github.com/codahale/bcrypt-ruby/issues/128
for details.
|
| |
| |
| |
| |
| | |
It appears that MRI on Windows can also appear as `:mingw`, if it was
installed via RubyInstaller.
|
| |
| |
| |
| |
| |
| |
| | |
platform `:ruby` is only MRI on Linux or Mac. Windows MRI shows up as
`:mswin` or `:mswin64` depending on if it was installed as 32 or 64 bit. I
am unsure if this will cause conflicts with JRuby on Windows, but I don't
have the means to test this at the moment.
|
| | |
|
|\ \
| |/
|/| |
|
| | |
|
| |
| |
| |
| | |
* Don't deep-require to AD::Http::Request since it misses Mime autoload
|
| | |
|