-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
SRCH-5171 & SRCH-5140: Upgrade to Rails 7.1.0 - Remove ruby 3.0.6 from test matrix #252
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@luisgmetzger Once change request inline.
Also, I'm not sure why your tests are hanging because I your fork's runs, but we'll need to figure that out to get this merge eligible. Happy to help - hopefully it's just as simple as re-running them.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@luisgmetzger Comments in line.
photos.to_a.last.dateupload.to_i | ||
rescue StandardError => e | ||
Rails.logger.warn("Trouble getting oldest upload date from photo #{photos.to_a.last}: #{e}") | ||
photo_array = photos.respond_to?(:photos) ? photos.photos.to_a : photos.to_a |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why are these changes necessary? The change to the warning also seems more confusing/less helpful/less specific than the current version, while also seeming like a change in functionality? Ditto the changes starting on ln 56.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@lorawoodford - As for these updates ... I could seem to escape the changes here (especially the mocks) after the upgrade and rspec-rails version upgrade.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
* SRCH-5217 Set production log level through the env (#256) * SRCH-5217 SRCH-5168 Fix error `visit_Psych_Nodes_Alias' ... (Psych::BadAlias)`. Fix suid & sgid deletion, remove crontabs and init files (#257) * Set RAILS_LOG_TO_STDOUT=1 BUNDLE_WITHOUT=development (#258) * SRCH-5020 (#259) * SRCH-5171 & SRCH-5140: Upgrade to Rails 7.1.0 - Remove ruby 3.0.6 from test matrix (#252) * SRCH-5171: Upgrade to Rails 7.1.0 * Remove ruby 3.0.6 from test matrix
Summary
Checklist
Please ensure you have addressed all concerns below before marking a PR "ready for review" or before requesting a re-review. If you cannot complete an item below, replace the checkbox with the⚠️
:warning:
emoji and explain why the step was not completed.Functionality Checks
You have merged the latest changes from the target branch (usually
main
) into your branch.Your primary commit message is of the format SRCH-#### <description> matching the associated Jira ticket.
PR title is either of the format SRCH-#### <description> matching the associated Jira ticket (i.e. "SRCH-123 implement feature X"), or Release - SRCH-####, SRCH-####, SRCH-#### matching the Jira ticket numbers in the release.
Automated checks pass. If Code Climate checks do not pass, explain reason for failures:
Process Checks