-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integrate Rails 5's new Interlock #2450
Comments
Wow! 馃帀 馃巿 |
mperham
added a commit
that referenced
this issue
Jul 22, 2015
looks amazing! 馃帀 馃専 |
馃憦 馃憦 馃憦 |
Coming in 4.2.0. |
This is so great. Thanks. Something is borken in rails though...sidekiq jobs reload reliably now, but controllers & helpers not so much. |
tigefa4u
pushed a commit
to tigefa4u/gitlabhq
that referenced
this issue
Nov 21, 2018
Now that Rails 5 supports thread-safe code reload (sidekiq/sidekiq#2450), we encounter errors when the Rails app code changes in development. We need to add `::` in one middleware so that Object.const_missing will be invoked instead of Metrics.const_missing. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/54320
tigefa4u
pushed a commit
to tigefa4u/gitlabhq
that referenced
this issue
Nov 21, 2018
Now that Rails 5 supports thread-safe code reload (sidekiq/sidekiq#2450), we encounter errors when the Rails app code changes in development. We need to add `::` in one middleware so that Object.const_missing will be invoked instead of Metrics.const_missing. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/54320
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Rails 5 now supports thread-safe code reloading!!!!!! 馃帀 馃嵃
Integrate the new Interlock into the Processor so we can reload Workers before executing them. This is Rails 5+ in development mode only so we'll need to keep the current code flow for Rails 3 and 4 and other environments.
The text was updated successfully, but these errors were encountered: