Skip to content
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

Fix loading issue of ActionMailer::MessageDelivery #32473

Conversation

yujideveloper
Copy link
Contributor

@yujideveloper yujideveloper commented Apr 6, 2018

I had an error NameError (uninitialized constant #<Class:ActionMailer::Base>::MessageDelivery) that is difficult to reproduce.
I'm sending some mails in some action of ActionController using ActionMailer.

I think this is concurrency issue that is occurred when using thread-base app server like Puma.

This occurs in Rails 5.0.7 and earlier, but not occurs in Rails 5.1.0 and later.
I was using Rails 5.0.6 and Ruby 2.3.1 when this is occurred.

Before 5.0.7, ActionMailer::MessageDelivery is only used in ActionMailer::Base#method_missing.
So, ActionMailer::MessageDelivery will be loaded when mail method is called.
https://github.com/rails/rails/blob/v5.0.7/actionmailer/lib/action_mailer.rb#L50
https://github.com/rails/rails/blob/v5.0.7/actionmailer/lib/action_mailer/base.rb#L563

After 5.1.0, ActionMailer::MessageDelivery is used in the module definition of ActionMailer::Parameterized inclueded in ActionMailer::Base.
So, ActionMailer::MessageDelivery will be loaded when defining a class that inherited ActionMailer::Base.
https://github.com/rails/rails/blob/v5.1.0/actionmailer/lib/action_mailer.rb#L51
https://github.com/rails/rails/blob/v5.1.0/actionmailer/lib/action_mailer/base.rb#L438
https://github.com/rails/rails/blob/v5.1.0/actionmailer/lib/action_mailer/parameterized.rb#L122

I think this is similar to #27849.

Thanks.

@rails-bot
Copy link

Thanks for the pull request, and welcome! The Rails team is excited to review your changes, and you should hear from @rafaelfranca (or someone else) soon.

If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.

This repository is being automatically checked for code quality issues using Code Climate. You can see results for this analysis in the PR status below. Newly introduced issues should be fixed before a Pull Request is considered ready to review.

Please see the contribution instructions for more information.

@rails-bot
Copy link

warning Warning warning

  • Pull requests are usually filed against the master branch for this repo, but this one is against 5-0-stable. Please double check that you specified the right target!

@rafaelfranca
Copy link
Member

5.0 is not maintained anymore for bug fixes. 5.0.7 was the last release.

@rafaelfranca rafaelfranca reopened this Apr 6, 2018
@rafaelfranca
Copy link
Member

Sorry, we still have some core members maintaining that version. I'll merge this PR.

@rafaelfranca rafaelfranca merged commit 9e5656e into rails:5-0-stable Apr 6, 2018
@yujideveloper yujideveloper deleted the fix/load-issue-of-am-message-delivery branch April 6, 2018 23:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants