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

Loads Rails environment so that Rails.logger.error() is available #2641

Merged
merged 1 commit into from
Aug 9, 2021

Conversation

hectorcorrea
Copy link
Member

Fixes #2639

Although the real error behind 2639 was a Solr error, the error reported by Honeybadger was because it crashed when it tried to log the error. This PR addresses only the error reported by Honeybadger (i.e. not the Solr error)

I did not add a test since the problem was the declaration of the Rake task, let me know if I should add a test for that kind of mis-declaration of a rake task.

Copy link
Member

@hackartisan hackartisan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍🏻 looks good, thank you!

@hackartisan
Copy link
Member

And yes we normally don't test rake tasks themselves. If there's enough logic in them we would pull out the logic into a function somewhere and test that function.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 96.954% when pulling d47e55a on issue_2639_rake_browse into 1d3839c on main.

@christinach christinach merged commit d8e3796 into main Aug 9, 2021
@christinach christinach deleted the issue_2639_rake_browse branch August 9, 2021 15:10
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.

Error in rake browse:call_numbers
4 participants