-
-
Notifications
You must be signed in to change notification settings - Fork 297
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NameError: undefined method append_info_to_payload' for class
ActionCable::Channel::Base'
#285
Comments
I am also facing the same issue. # config/initializers/lograge.rb
config.lograge.base_controller_class = 'ActionController::Base' |
I'm getting this error as well, but only when I run the asset precompile rake task in a Docker container. The application and rake tasks work fine locally. Weird. Adding the initializer allows me to precompile assets in the container, but I had to tweak it a little to define the config: # frozen_string_literal: true
Rails.application.config.lograge.base_controller_class = "ActionController::Base" It seems to work fine. I am not using ActionCable in this app. Thanks for the tip @decoch |
Sorry about this folks. I’m working on a fix. |
I have the same issue. Everything works fine on |
…om_payload Remove ActionCable::Channel::Base from base classes when setting custom_payload Fixes roidrage#285
Sorry guys, that's my fault, I did overlook the As for the option itself, we should figure out the way |
…om_payload Remove ActionCable::Channel::Base from base classes when setting custom_payload Fixes roidrage#285
…om_payload Remove ActionCable::Channel::Base from base classes when setting custom_payload Fixes roidrage#285
This reverts commit 1907376 pending the resolution of roidrage/lograge#285.
I still see this under 0.11.0 -- a quick look shows the code in the 0.11.0 tag doesn't have the fix from #286 in it (see Lines 169 to 172 in 244ce40
|
I've just released 0.11.1 including this fix. |
If what I referenced above is the problematic code, it's unchanged in 0.11.1 and I'm still getting the error. |
Likewise error is still occurring here 😢 This needs to be reopened @benlovell. |
Ugh. I’ll get this resolved properly tomorrow. Apologies folks. |
Hey, it's open source on a Friday afternoon. Don't apologize too hard 😄 |
Just want to bring this one back up. Can we get #286 merged? Thanks for your work on this! |
@benlovell please let us know if there's anything preventing #286 from being merged 🙂 |
I'm not 100% convinced this resolves the issue. It has no test that verifies the behaviour so I have to set up a project myself to verify it manually and I'm reluctant to do this as something previously touted as a fix was not. If someone adds a spec for it I'll merge it right away. I've just not had the bandwidth to take care of it myself :( |
@xlts It works locally, if you could add a spec when you get a moment that would help. I'll cut a release with the fix now. |
After upgraded
0.11.0
.Got a below error.
with this setting
The text was updated successfully, but these errors were encountered: