fix(analyze): warn before GNU date fallback#6879
Open
nanookclaw wants to merge 2 commits into
Open
Conversation
Signed-off-by: Nanook <nanookclaw@users.noreply.github.com>
Signed-off-by: Nanook <nanookclaw@users.noreply.github.com>
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
1 participant
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.
Summary
Adds a transitional warning when
cloud-init analyze dumpfalls back to GNUdate/gdatefor timestamp parsing. The warning includes the unrecognized timestamp format and the selected binary so maintainers can collect formats that still need native Python support before removing the shell-out path.The no-GNU-date behavior is unchanged: unsupported formats still raise
ValueErrorwhen neitherdatenorgdateis available.Fixes #4357.
Testing
PYTEST_DISABLE_PLUGIN_AUTOLOAD=1 pytest -q tests/unittests/analyze/test_dump.pygit diff --checkPlain
pytestin this environment auto-loads a missing external plugin (evalcraft), so I disabled plugin autoload for the focused test run.