Skip to content

[AINode] Avoid stale Poetry metadata when regenerating dependency locks - #18329

Merged
CRZbulabula merged 1 commit into
apache:masterfrom
CRZbulabula:yongzao/ainode-poetry-lock-no-cache
Jul 28, 2026
Merged

CRZbulabula merged 1 commit into
apache:masterfrom
CRZbulabula:yongzao/ainode-poetry-lock-no-cache

Conversation

@CRZbulabula

Copy link
Copy Markdown
Contributor

Description

AINode packaging regenerates poetry.lock on every build. Poetry release metadata is cached persistently, so if the cache is populated while a package release is still uploading platform artifacts, later builds can keep generating a lock file with an incomplete artifact list. This can make installation fail even after compatible wheels are available.

This change runs poetry lock --no-cache --regenerate so each packaging build fetches current source metadata and recreates the lock file from scratch. This prevents persistent self-hosted runner caches from poisoning subsequent AINode builds.

Verification

  • Confirmed that Poetry 2.2.1 supports both --no-cache and --regenerate for poetry lock.
  • Ran python -m py_compile build_binary.py.
  • Ran black --check build_binary.py.
  • Ran isort --check-only --profile black build_binary.py.

This PR has:

  • been self-reviewed.
  • added comments explaining the why and intent of the code.

Key changed/added classes
  • iotdb-core/ainode/build_binary.py

@CRZbulabula
CRZbulabula merged commit 98a7d51 into apache:master Jul 28, 2026
42 checks passed
@CRZbulabula
CRZbulabula deleted the yongzao/ainode-poetry-lock-no-cache branch July 28, 2026 06:48
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.

1 participant