How do I avoid the circular argument reference warning in activesupport

后端 未结 9 978
既然无缘
既然无缘 2020-12-17 07:56

How do I avoid the circular argument reference warning in activesupport. Happens on ruby 2.2.0

/home/ec2-user/apps/foo_prod/shared/bundle/ruby/2.2.0/gems/act         


        
相关标签:
9条回答
  • 2020-12-17 08:38

    Well, Here is a solution to this: Try doing all these changes in your .rbenv/.rvm folder and change in these files:

    https://github.com/tmm1/rails/commit/8fd52705eda6a2cd7e9a8a5bc723fa094e359eb7

    0 讨论(0)
  • 2020-12-17 08:40

    here is what i did to resolve that, i had the latest ruby and the gems are not compatible with that, so after having a fight for nearly a day i switched to older ruby version using rvm

    from ruby-2.2.1 to ruby-2.0.0 ,

    again this is not an issue with ruby version but incompatibility with gems,try and have good luck with that.

    0 讨论(0)
  • 2020-12-17 08:41

    This is an issue of Active Support and has been fixed with these two commits:

    • https://github.com/rails/rails/commit/8fd52705eda6a2cd7e9a8a5bc723fa094e359eb7
    • https://github.com/rails/rails/commit/3a30b12c774dfaa72acfe520e823374131631ea9

    Unfortunately, these commits have been never included into the 3.2 releases, because the current last release (v3.2.21) was out on 18 Nov 2014 and after that these commits were merged.

    If you don't want to see this warning message definitely, you should change your Gemfile like this:

    # gem 'rails', '3.2.21'
    gem 'rails', git: 'https://github.com/rails/rails.git', branch: '3-2-stable'
    

    Otherwise, you should downgrade ruby to 2.1 or wait the release of v3.2.22, which won't come until a grave security hole is found.

    After all, there is no easy way to avoid this issue. Changing Gemfile for such a trivial annoyance may be an overreaction in my view. It will delay your deployment process quite a lot.

    0 讨论(0)
提交回复
热议问题