| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
| |
| |
| | |
in #9904
|
|\ \
| | |
| | | |
Transparently upgrade signed cookies when setting secret_key_base
|
| | |
| | |
| | |
| | | |
signed cookies generated by Rails 3 to avoid invalidating them when upgrading to Rails 4
|
|/ /
| |
| |
| | |
v3 of pull request based on additional feedback from @jeremy
|
| |
| |
| |
| | |
completes https://github.com/rails/rails/commit/6f3f0f86332004fcee5c2f05d52bbff08c22f980
|
| | |
|
| |
| |
| |
| | |
String
|
|\ \
| | |
| | | |
Add #to_s method to VERSION modules
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
Use the "quit" command instead. This seems to prevents some weirdness on
OS X. See #9761.
|
|/ /
| |
| |
| |
| |
| | |
SIGTERM is the correct signal for a graceful exit.
This will hopefully resolve #9761.
|
| | |
|
| | |
|
| |
| |
| |
| | |
Check 862389c9537dbb6f65fd26c4325e07607ed437b5 for more background.
|
| |
| |
| |
| | |
Check pull request #9789 for more information.
|
| |
| |
| |
| | |
This reverts commit c24528fbc94dea9946a563be3bed9559583bdc57.
|
| | |
|
| |
| |
| |
| | |
v2 of pull request based on feedback from @rafaelfranca, @schneems, and @carlosantoniodasilva
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We used to pass the Rails::Application subclass to #run.
The Rails server then called #to_app to convert that class to the
actual Rack application.
if you surround `#run` with a call to `#map` the server no longer
convertes the class to the instance and we end up with unnecessary
delegation calls on every request.
|
| |
| |
| |
| | |
warning: assigned but unused variable - task_name
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* adds password_digest attribute to the migration
* adds has_secure_password to the model
* adds password and password_confirmation password_fields to _form.html
* omits password entirely from index.html and show.html
* adds password and password_confirmation to the controller
* adds unencrypted password and password_confirmation to the controller test
* adds encrypted password_digest to the fixture
|
| | |
|
| |
| |
| |
| | |
Cache the value of "super" in a variable and use it instead.
|
| |
| |
| |
| |
| |
| | |
Using regexps as arguments without parentheses end up raising:
warning: ambiguous first argument; put parentheses or even spaces
|
|\ \
| | |
| | | |
Make sure that the test case is run under test env
|
| | |
| | |
| | |
| | |
| | |
| | | |
* Unset $RAILS_ENV that got set by abstract_unit to trigger the default.
* split out environment setting since Ruby 1.9.3 doesn't support inline
ENV setting.
|
|/ /
| |
| |
| |
| |
| | |
https://github.com/rails/rails/pull/3180\#issuecomment-14705821 has
mention of rendering going from 1-2ms to 4 seconds with this on,
which seems reasonable: debugging is slow.
|
| |
| |
| |
| | |
I forgot to run the test suit after changing the task name. :bomb:
|
|\ \
| | |
| | | |
Add `rails test` command to run the test suite
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
Also, print out deprecation warning for other rake tasks except
`rake test` and `rake` (default)
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
* `rails test -f` will run the test suites with all fixtures loaded
* New application will now generated without `fixtures :all` line
enabled by default.
|
| | |
| | |
| | |
| | |
| | | |
Any flags that got set will be passed through to MiniTest::Unit.runner,
such as `-n`, `-s-, and `-v`.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
To run the whole test suite:
$ rails test
To run the test file(s):
$ rails test test/unit/foo_test.rb [test/unit/bar_test.rb ...]
To run the test suite
$ rails test [models,helpers,units,controllers,mailers,...]
For more information, see `rails test --help`.
This command will eventually replacing `rake test:*`, and `rake test`
command will actually invoking `rails test` instead.
|
| | | |
|
|/ / |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This should fix travis. For real this time! This is the one!
The readpartial(100) meant that an earlier assert_stdout could chomp up
the output that a later assert_stdout wants, meaning that the later
assertion fails.
Reading only 1 byte at a time ensure that we don't read any more than is
necessary to verify the assertion.
|
|/ |
|
|
|
|
|
|
| |
This should fix travis.
Also ensuring that we don't try to kill when pid is nil.
|
| |
|
|
|
| |
minor comment fix for consistency
|
|
|
|
| |
Introduced in be3e10cd26bc8ec29c6474d03a08a8e733108e7d.
|
|\
| |
| | |
Add rake test description
|
| |
| |
| |
| | |
No behavior change
|
| |
| |
| |
| | |
Thanks @neerajdotname for noticing this bug.
|
| |
| |
| |
| |
| |
| | |
I've also added a proper acceptance test which reproduced the issue.
Closes #9513, #9515.
|