-
Notifications
You must be signed in to change notification settings - Fork 125
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
Allow the rails method to be called and change the result only when called from the migration #776
Merged
Fryguy
merged 2 commits into
ManageIQ:master
from
jrafanie:fix-rails-7-1-plus-test-failure
Jan 3, 2025
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,8 @@ | ||
def require_migration | ||
spec_name = caller_locations.first.path | ||
migration_name = spec_name.sub("spec/migrations", "db/migrate").sub("_spec.rb", ".rb") | ||
require migration_path | ||
end | ||
|
||
require migration_name | ||
def migration_path | ||
spec_name = caller_locations.detect {|loc| loc.path.end_with?("_spec.rb")}.path | ||
spec_name.sub("spec/migrations", "db/migrate").sub("_spec.rb", ".rb") | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @Fryguy finally came back to this... see my commit details below... (the second commit)
|
||
end |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Let me explain this... the reason it's called 10 times here is because rails itself is calling it in rails 7.0. Previously, we called the original rails method as is 10 times, then, we change the result on the 11th call to inject a password if it wasn't configured, or in the case of the second test remove the password.
This changed in rails 7.1 as it's only called 1 time and it was in our migration probably due to internal rails changes. To support both versions, I'm checking if the caller locations shows it coming from the migration file and only then change the result for the test scenario.
I guess we could also do a rails version check but felt that it's brittle to expect or not expect a rails method to be called or worse, to modify the result from it if it's originating from rails itself. In fact, my first try at this PR had this failing in CI because on CI the password wasn't configured as I guess it's allowing local socket connections.