Skip to content

Conversation

@geo-mathijs
Copy link

Describe your changes:

Fixes #25158

This fixes a required dependency missing from the base requirements because it was implicitly there through google-auth, which no longer works. They removed it due to it being an unnecessary dependency for just using a simple LRUCache, which I think makes sense, but that would be a different PR. Right now this breaks OpenMetadata so just adding the expected dependency should fix that.

Type of change:

  • Bug fix
  • Improvement
  • New feature
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation

Checklist:

  • I have read the CONTRIBUTING document.
  • My PR title is Fixes <issue-number>: <short explanation>
  • I have commented on my code, particularly in hard-to-understand areas.
  • For JSON Schema changes: I updated the migration scripts or explained why it is not needed.

@github-actions
Copy link
Contributor

github-actions bot commented Feb 3, 2026

Hi there 👋 Thanks for your contribution!

The OpenMetadata team will review the PR shortly! Once it has been labeled as safe to test, the CI workflows
will start executing and we'll be able to make sure everything is working as expected.

Let us know if you need any help!

@gitar-bot
Copy link

gitar-bot bot commented Feb 3, 2026

🔍 CI failure analysis for f2d3066: All CI jobs are failing because the PR is missing the 'safe to test' label required by the repository's security policy.

Issue

All 14 CI jobs are failing at the pre-flight label check stage and never execute actual tests.

Root Cause

The repository enforces a security policy requiring PRs to have the safe to test label before CI workflows can execute. This prevents potentially malicious code from external contributors from running in the CI environment.

Evidence

Every failing job shows the same error:

Error! This pull request does not contain any of the valid labels: ['safe to test']
Exiting with an error code

This occurs in:

  • Python test jobs (py-run-tests for 3.10 and 3.11, py-run-build-tests)
  • Python linting (py-checkstyle)
  • Java linting (java-checkstyle)
  • Build jobs (build-and-scan)
  • All 6 Playwright test shards (playwright-ci-postgresql 1-6 of 6)

Details

The label check happens early in each workflow, before any actual build, test, or lint operations begin. Currently, this PR has no labels applied. The security control prevents workflow execution until a maintainer with appropriate permissions adds the safe to test label.

Code Review ✅ Approved

Clean bug fix that correctly promotes cachetools from plugin-specific to base requirements, addressing the missing dependency issue when google-auth removed it as a transitive dependency.

Tip

Comment Gitar fix CI or enable auto-apply: gitar auto-apply:on

Options

Auto-apply is off → Gitar will not commit updates to this branch.
Display: compact → Showing less information.

Comment with these commands to change:

Auto-apply Compact
gitar auto-apply:on         
gitar display:verbose         

Was this helpful? React with 👍 / 👎 | Gitar

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Missing python dependency in openmetadata-ingestion : cachetools

1 participant