- 01 11月, 2019 1 次提交
-
-
由 George Claghorn 提交于
-
- 10 10月, 2019 1 次提交
-
-
由 Xavier Noria 提交于
-
- 21 9月, 2019 2 次提交
-
-
由 Carlos Antonio da Silva 提交于
-
由 Carlos Antonio da Silva 提交于
Fix issues with ActiveSupport Range extensions on boundless Ranges Closes #37177
-
- 09 9月, 2019 1 次提交
-
-
由 Ryuta Kamizono 提交于
Fix endless range include
-
- 05 9月, 2019 1 次提交
-
-
由 y-yagi 提交于
Don't use Process#clock_gettime CLOCK_PROCESS_CPUTIME_ID on Solaris
-
- 17 8月, 2019 1 次提交
-
-
由 Rafael Mendonça França 提交于
-
- 28 7月, 2019 1 次提交
-
-
由 Xavier Noria 提交于
Applications are not supposed to use require_dependency in their own code if running in zeitwerk mode, and require_dependency was initially aliased to require with that use case in mind. However, there are situations in which you cannot control the mode and need to be compatible with both. There, you might need require_dependency in case you are being executed in classic mode. Think about engines that want to support both modes in their parent applications, for example. Furthermore, Rails itself loads helpers using require_dependency. Therefore, we need better compatibility.
-
- 25 7月, 2019 1 次提交
-
-
由 Rafael França 提交于
Make ActiveSupport::Logger Fiber-safe
-
- 23 7月, 2019 2 次提交
-
-
由 Rafael Mendonça França 提交于
-
由 Aaron Lipman 提交于
Exclude missing marshal_dump and _dump methods from being delegated to an object's delegation target via the delegate_missing_to extension. This avoids unintentionally adding instance variables to an object during marshallization, should the delegation target be a method which would otherwise add them. In current versions of Ruby, a bug exists in the way objects are marshalled, allowing for instance variables to be added or removed during marshallization (see https://bugs.ruby-lang.org/issues/15968). This results in a corrupted serialized byte stream, causing an object's instance variables to "leak" into subsequent serialized objects during demarshallization. In Rails, this behavior may be triggered when marshalling an object that uses the delegate_missing_to extension, if the delegation target is a method which adds or removes instance variables to an object being marshalled - when calling Marshal.dump(object), Ruby's built in behavior will check whether the object responds to :marshal_dump or :_dump, which in turn triggers the delegation target method in the responds_to_missing? function defined in activesupport/lib/active_support/core_ext/module/delegation.rb While future versions of Ruby will resolve this bug by raising a RuntimeError, the underlying cause of this error may not be readily apparent when encountered by Rails developers. By excluding marshal_dump and _dump from being delegated to an object's target, this commit eliminates a potential cause of unexpected behavior and/or RuntimeErrors. Fixes #36522
-
- 15 5月, 2019 1 次提交
-
- 27 4月, 2019 1 次提交
-
-
由 Jordan Thomas 提交于
* Add test asserting truncate returns unfrozen string * Ensure strings returned from truncate are not frozen This fixes an issue where strings too short to be truncated were returned unfrozen, where as long-enough strings were returned frozen. Now retuned strings will not be frozen whether or not the string returned was shortened. * Update changelog w/ new truncate behavior description [Jordan Thomas + Rafael Mendonça França]
-
- 25 4月, 2019 1 次提交
-
-
由 Rafael Mendonça França 提交于
-
- 19 4月, 2019 2 次提交
-
-
由 Genadi Samokovarov 提交于
Actionable errors let's you dispatch actions from Rails' error pages. This can help you save time if you have a clear action for the resolution of common development errors. The de-facto example are pending migrations. Every time pending migrations are found, a middleware raises an error. With actionable errors, you can run the migrations right from the error page. Other examples include Rails plugins that need to run a rake task to setup themselves. They can now raise actionable errors to run the setup straight from the error pages. Here is how to define an actionable error: ```ruby class PendingMigrationError < MigrationError #:nodoc: include ActiveSupport::ActionableError action "Run pending migrations" do ActiveRecord::Tasks::DatabaseTasks.migrate end end ``` To make an error actionable, include the `ActiveSupport::ActionableError` module and invoke the `action` class macro to define the action. An action needs a name and a procedure to execute. The name is shown as the name of a button on the error pages. Once clicked, it will invoke the given procedure.
-
由 r7kamura 提交于
-
- 17 4月, 2019 1 次提交
-
-
由 Mauri Mustonen 提交于
-
- 09 4月, 2019 1 次提交
-
-
由 Xavier Noria 提交于
-
- 07 4月, 2019 1 次提交
-
-
由 Xavier Noria 提交于
-
- 31 3月, 2019 2 次提交
-
-
由 Ryuta Kamizono 提交于
* use backticks instead of `+` * and more (e.g. missed replacing `Array#excluding` and `Enumerable#excluding` in b89a3e7e)
-
由 Ryuta Kamizono 提交于
* add leading `#` before `=>` since hash rocket is valid Ruby code * add backticks * remove trailing spaces * and more
-
- 30 3月, 2019 1 次提交
-
-
由 Xavier Noria 提交于
-
- 28 3月, 2019 1 次提交
-
-
由 Owen Stephens 提交于
Before: ```ruby (1..10).cover?(1...11) => false ``` After: ```ruby (1..10).cover?(1...11) => true ``` See https://git.io/fjTtz for the commit against Ruby core that added support for Range arguments, with similar handling of this case.
-
- 26 3月, 2019 1 次提交
-
-
由 Edgars Beigarts 提交于
It allows anonymous subclasses to be garbage collected.
-
- 23 3月, 2019 1 次提交
-
-
由 Ali Ibrahim 提交于
-
- 22 3月, 2019 1 次提交
-
-
由 Ali Ibrahim 提交于
with change to ActiveSupport::Notifications::Instrumenter#instrument
-
- 19 3月, 2019 1 次提交
-
-
由 Andrew White 提交于
In #10634 the behavior of Time#advance was changed to maintain a proleptic gregorian calendar for dates before calendar reform. However it didn't full address dates a long time before calendar reform and they gradually drift away from the proleptic calendar the further you go back in time. Fix this by always converting the date to gregorian before calling advance which sets the reform date to -infinity.
-
- 16 3月, 2019 1 次提交
-
-
由 Xavier Noria 提交于
-
- 13 3月, 2019 1 次提交
-
-
由 Ryuta Kamizono 提交于
-
- 12 3月, 2019 1 次提交
-
-
由 Sharang Dashputre 提交于
-
- 11 3月, 2019 1 次提交
-
-
由 eileencodes 提交于
* Update RAILS_VERSION * Bundle * rake update_versions * rake changelog:header
-
- 06 3月, 2019 1 次提交
-
-
由 David Heinemeier Hansson 提交于
-
- 26 2月, 2019 1 次提交
-
-
由 Rafael Mendonça França 提交于
-
- 14 2月, 2019 1 次提交
-
-
由 Xavier Noria 提交于
There is too much to say about it for a CHANGELOG entry, and linking to the original PR could mislead if there are later changes as already happened with the gem dependency, so just a one-liner. For final we'll up to date documentation.
-
- 12 2月, 2019 1 次提交
-
-
由 zvkemp 提交于
-
- 09 2月, 2019 1 次提交
-
-
由 Guillermo Iguaran 提交于
-
- 31 1月, 2019 1 次提交
-
-
由 Akinori MUSHA 提交于
ActiveSupport overrides `` Kernel#` `` so that it would not raise `Errno::ENOENT` but return `nil` instead (due to the last statement `STDERR.puts` returning nil) if a given command were not found. Because of this, you cannot safely say somthing like `` `command`.chomp `` when ActiveSupport is loaded. It turns out that this is an outdated monkey patch for Windows platforms to emulate Unix behavior on an ancient version of Ruby, and it should be removed by now.
-
- 30 1月, 2019 2 次提交
-
-
由 Rosa Gutierrez 提交于
This is useful when we need to do some work associated to `Current.reset` but that work depends on the values of the current attributes themselves. This cannot be done in the supported `resets` callback because when the block is executed, CurrentAttributes's instance has already been reset. For symmetry, `after_reset` is defined as alias of `resets`.
-
由 Stefan Schüßler 提交于
-
- 19 1月, 2019 1 次提交
-
-
由 Rafael Mendonça França 提交于
-