1. 14 12月, 2019 1 次提交
  2. 10 12月, 2019 1 次提交
  3. 03 12月, 2019 2 次提交
  4. 02 12月, 2019 1 次提交
  5. 01 12月, 2019 1 次提交
  6. 27 11月, 2019 1 次提交
  7. 23 11月, 2019 2 次提交
  8. 16 11月, 2019 2 次提交
  9. 05 11月, 2019 1 次提交
  10. 01 11月, 2019 1 次提交
  11. 18 10月, 2019 1 次提交
  12. 10 10月, 2019 1 次提交
  13. 03 10月, 2019 1 次提交
  14. 02 10月, 2019 1 次提交
  15. 26 9月, 2019 1 次提交
  16. 21 9月, 2019 1 次提交
  17. 17 9月, 2019 1 次提交
  18. 09 9月, 2019 1 次提交
  19. 05 9月, 2019 1 次提交
  20. 17 8月, 2019 1 次提交
  21. 01 8月, 2019 1 次提交
  22. 28 7月, 2019 1 次提交
    • X
      Improves compatibility of require_dependency in zeitwerk mode [Closes #36774] · c701e0b8
      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.
      c701e0b8
  23. 27 7月, 2019 1 次提交
  24. 26 7月, 2019 1 次提交
  25. 25 7月, 2019 1 次提交
  26. 24 7月, 2019 1 次提交
  27. 23 7月, 2019 2 次提交
    • R
      Preparing for 6.0.0.rc2 release · 4f78062a
      Rafael Mendonça França 提交于
      4f78062a
    • A
      Omit marshal_dump & _dump from delegate_missing_to · 056414eb
      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
      056414eb
  28. 18 7月, 2019 1 次提交
  29. 17 7月, 2019 1 次提交
  30. 16 7月, 2019 3 次提交
  31. 17 6月, 2019 1 次提交
  32. 13 6月, 2019 1 次提交
  33. 05 6月, 2019 2 次提交