Fix #445: guard log line in roll against unset what/details#453
Merged
Conversation
|
@bibonix Hi! Your branch name " |
|
@bibonix Thanks for the contribution! You've earned +20 points for this: +24 as a basis; -4 for contributing fewer than 30 hits-of-code (25 total). Please keep them coming! Your running score is +232; don't forget to check your Zerocracy account too. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
@yegor256 — this PR fixes #445 (
Fbe::Conclude#rollcrashing withRuntimeError: Can't find 'what' attributewhen thedrawblock returns a non-String).What changes
Per your direction in the issue ("the second option is better: roll should guard the log line against unset attributes"), the
@loog.info("#{n.what}: #{n.details}")line inroll(lib/fbe/conclude.rb) now first checksn.all_propertiesand only emits the log line when bothwhatanddetailsare present on the new fact. The behaviour offillis unchanged — it still only setswhat/detailswhen the block returns aString— so existing well-behaved judges keep their info-level log entries.Why this approach
Factbase::FactraisesRuntimeError(notNoMethodError) when reading an unset property, so a genericrescuewould be too broad. Using the publicall_propertiesaccessor (already used elsewhere in the codebase, e.g.lib/fbe/delete.rb:32) makes the guard explicit and side-effect-free.Reproduction
The new test
test_draw_block_returning_non_string_does_not_crashmirrors the minimal repro from the issue — adrawblock that only assignsn.score = 42. Without the fix this raisesRuntimeError: Can't find 'what' attribute out of [_id, _time, _version, score]. With the fix the new fact is inserted cleanly.Verification
bundle exec rake test— 255 tests, 0 failures.bundle exec rake rubocop— clean.bundle exec rake yard— clean.Closes #445.