Fix infinite recursion when the logger enters a loop#304
Merged
Conversation
This reverts commit ec61637.
… could be hidden if the category is disabled https://ruby-doc.org/3.3.6/Warning.html
… message could be hidden if the category is disabled" This reverts commit da5c3bc.
ArturT
commented
Jul 11, 2025
|
|
||
| if !knapsack_env_value.nil? && !ci_env_value.nil? && knapsack_env_value != ci_env_value.to_s | ||
| KnapsackPro.logger.info("You have set the environment variable #{knapsack_env_name} to #{knapsack_env_value} which could be automatically determined from the CI environment as #{ci_env_value}.") | ||
| warn("You have set the environment variable #{knapsack_env_name} to #{knapsack_env_value} which could be automatically determined from the CI environment as #{ci_env_value}.") |
Member
Author
There was a problem hiding this comment.
Regardless of
Warning[:deprecated] = falseor
Warning[:deprecated] = truethe following warning is printed to stderr:
warn("You have set the environment variable #{knapsack_env_name} to #{knapsack_env_value} which could be automatically determined from the CI environment as #{ci_env_value}.")This is fine. We expect it to be printed. After all, it's not a deprecation warning. It's a misconfiguration warning.
If we were to add the :deprecated category to the following message, then the suppression would be respected if Warning[:deprecated] = false:
# see the end of the line
warn("You have set the environment variable #{knapsack_env_name} to #{knapsack_env_value} which could be automatically determined from the CI environment as #{ci_env_value}.", category: :deprecated)References:
3v0k4
approved these changes
Jul 14, 2025
|
|
||
| ### 8.3.2 | ||
|
|
||
| * Fix infinite recursion when the logger gets into a loop |
Contributor
There was a problem hiding this comment.
plea
Please add more information here. The issue is a good starting point.
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.
Story
https://trello.com/c/yROeD8FX
Related
Description
Fix infinite recursion when the logger enters a loop. The issue occurs when
KNAPSACK_PRO_LOG_DIR=logis set and a conflict arises between the values of environment variables from the CI provider and those configured by the user (e.g.,KNAPSACK_PRO_CI_NODE_INDEX,KNAPSACK_PRO_CI_NODE_TOTAL).Changes:
Checklist reminder
UNRELEASEDsection of theCHANGELOG.md, including the needed bump (ie, patch, minor, major)lib/knapsack_pro/pure/queue/rspec_pure.rbcontains pure functions that are unit tested.lib/knapsack_pro/extensions/rspec_extension.rbencapsulates calls to RSpec internals and is integration and e2e tested.lib/knapsack_pro/runners/queue/rspec_runner.rbinvokes the pure code and the extension to produce side effects, which are integration and e2e tested.