Fix bug where attr_writer was overriding the key_root= method. #4097
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.
Extracted from #4082
@kbrock please review...@Fryguy and I fixed an issue where the
key_root=
class method was being✌️ whacked ✌️
by the
attr_writer
, causing the v*_key caches to not be reset viakey_root=
, particularly during tests.I ran into this "bug" locally for seemingly unrelated tests and couldn't track it down previously:
bin/rspec gems/pending/spec/util/miq-password_spec.rb spec/models/miq_server/rhn_mirror_spec.rb --seed 46323
It's weird to run gems/pending tests with models but I was doing it for changes that affected all of miq_server and util.
This test would run the miq-password spec first, reset the
key_root
, not clear out the v*_key, and subsequent tests that runMiqDatabase.seed
such as rhn_mirror_spec.rb would fail with seemingly cryptic errors like:Or
These tests now don't randomly fail with this PR.