Fix for local integration tests by ignoring warning#3172
Closed
Adam-D-Lewis wants to merge 4 commits intomainfrom
Closed
Fix for local integration tests by ignoring warning#3172Adam-D-Lewis wants to merge 4 commits intomainfrom
Adam-D-Lewis wants to merge 4 commits intomainfrom
Conversation
The recent release of google-api-core 2.28.0 introduced FutureWarnings about Python 3.10 EOL support that are causing the local integration test workflow to fail during the nebari init step. This change adds a warning filter in the main CLI module to suppress these warnings, allowing the package to stay up-to-date while avoiding CI failures. This approach is consistent with the warning filter already added to tests/conftest.py in commit d175fa2. Fixes the failure in: https://github.com/nebari-dev/nebari/actions/runs/18882140966/job/53887875554 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Adam-D-Lewis
requested review from
dcmcand and
marcelovilla
and removed request for
a team
Adam-D-Lewis
changed the title
Member
Author
|
They are still failing til we set the github-actions.nebari.dev DNS record. |
Adam-D-Lewis
changed the title
Member
Author
|
DNS record is now updated |
github-project-automation
bot
moved this from New 🚦
to Done 💪🏾
in 🪴 Nebari Project Management
Member
Author
|
Apparently this is not needed |
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
2 participants
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.
The recent release of google-api-core 2.28.0 introduced FutureWarnings about Python 3.10 EOL support that are causing the local integration test workflow to fail during the nebari init step.
This change adds a warning filter in the main CLI module to suppress these warnings, allowing the package to stay up-to-date while avoiding CI failures. This approach is consistent with the warning filter already added to tests/conftest.py in commit d175fa2.
Fixes the failure in: https://github.com/nebari-dev/nebari/actions/runs/18882140966/job/53887875554
🤖 Generated with Claude Code
Reference Issues or PRs
What does this implement/fix?
Put a
xin the boxes that applyDocumentation
Testing
How to test this PR?
Any other comments?