UN-3448 [FIX] Remove vestigial uv pip install line in uv-lock-automation workflow#1941
Merged
jaseemjaskp merged 3 commits intomainfrom May 6, 2026
Merged
Conversation
…on workflow Modern uv requires uv pip install to run inside a virtual environment OR with the explicit --system flag. The workflow currently has neither, so it errors out: error: No virtual environment found for Python 3.12.9; run `uv venv` to create an environment, or pass `--system` to install into a non-virtual environment This breaks every PR that touches a pyproject.toml (the workflow's paths filter triggers on those). Last successful run was 2026-04-01, before a behaviour change in uv or astral-sh/setup-uv@v7. The --system flag is exactly what the error message suggests and is correct here — we install pip into the runner's system Python; the downstream uv-lock.sh script creates its own venvs as needed. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
💤 Files with no reviewable changes (1)
Summary by CodeRabbit
WalkthroughThe GitHub Actions workflow ChangesCI Workflow Change
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Contributor
|
| Filename | Overview |
|---|---|
| .github/workflows/uv-lock-automation.yaml | Removes the unused uv pip install pip step; the downstream uv-lock.sh script uses uv sync exclusively and never calls pip, so the removal is correct and unblocks the workflow. |
Sequence Diagram
sequenceDiagram
participant GH as GitHub Actions Runner
participant UV as setup-uv@v7
participant SH as uv-lock.sh
participant UVS as uv sync (per dir)
participant GC as git-auto-commit-action
GH->>UV: Install uv 0.6.14 + Python 3.12.9
Note over GH: ~~uv pip install pip~~ (removed — unused)
GH->>SH: chmod +x && ./uv-lock.sh
loop For each directory
SH->>UVS: uv sync (generates uv.lock)
UVS-->>SH: lock file written
end
SH-->>GH: All lock files updated
GH->>GC: Commit uv.lock changes
Prompt To Fix All With AI
Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.
---
### Issue 1 of 1
.github/workflows/uv-lock-automation.yaml:39
**PR description doesn't match the actual change**
The PR title says "Add --system flag to uv pip install" and the description shows a `+` line with `--system` added, but the actual diff removes the `uv pip install --python=3.12.9 pip` step entirely rather than modifying it. The removal is correct — `uv-lock.sh` only calls `uv sync` and never invokes `pip` — but the commit message and PR description will mislead anyone reading the git history who expects to see the `--system` flag added rather than the step removed. Worth updating the PR description to reflect what was actually done.
Reviews (2): Last reviewed commit: "Merge branch 'main' into fix/UN-3448-FIX..." | Re-trigger Greptile
muhammad-ali-e
requested review from
chandrasekharan-zipstack,
harini-venkataraman,
jaseemjaskp,
johnyrahul and
pk-zipstack
pk-zipstack
approved these changes
May 5, 2026
jaseemjaskp
requested changes
May 5, 2026
Contributor
jaseemjaskp
left a comment
jaseemjaskp
left a comment
There was a problem hiding this comment.
uv-lock.shonly usesuv sync(line 74). It never invokespipdirectly, anduv syncmanages its own environments via uv. There's no reason to pre-install pip into the system Python at all. Confirmed by grepping —pipis referenced nowhere indocker/scripts/uv-lock-gen/`.
The line looks vestigial. The cleaner fix is to delete the line entirely rather than paper over with --system:
Per @jaseemjaskp's review: the pre-step `uv pip install ... pip` does nothing useful for this workflow. The downstream uv-lock.sh script uses uv sync at line 74, which manages its own venvs internally and never invokes pip directly: $ grep -rn 'pip' docker/scripts/uv-lock-gen/ docker/scripts/uv-lock-gen/uv-lock.sh:2:set -o pipefail Only match is pipefail (shell option), no real pip references. Removing the line entirely is cleaner than papering over with --system. The line was likely copy-pasted from a sibling workflow that legitimately needed pip in the system Python. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
muhammad-ali-e
changed the title
uv pip install line in uv-lock-automation workflow
|
Contributor
Test ResultsSummary
Runner Tests - Full Report
SDK1 Tests - Full Report
|
Contributor
Author
|
Good catch — verified |
jaseemjaskp
approved these changes
May 6, 2026
11 tasks
muhammad-ali-e
added a commit
that referenced
this pull request
May 6, 2026
…1945) UN-3449 [FIX] Refresh root uv.lock — fix malformed banks entry The root uv.lock had a malformed banks entry that prevented uv from parsing it: error: Failed to parse `uv.lock` Caused by: The entry for package `banks` v2.4.1 has wheel `banks-2.2.0-py3-none-any.whl` with inconsistent version: v2.2.0 The version field claimed v2.4.1 but the sdist/wheel filenames were both v2.2.0. The PyPI upload-time on the wheel matches banks 2.2.0's release date, so the artifacts really are 2.2.0 — most likely a manual edit or a partial-write bug in an older uv version. banks is a transitive dependency pulled in by llama-index-core v0.14.16 (LlamaIndex's prompt-templating library). Unstract code does not import banks directly. Fix: regenerate via `rm uv.lock && uv lock`. After regen, banks resolves to v2.4.2 with consistent artifacts. Why 1,557 lines change: the auto-update workflow has been broken since 2026-04-01 (now fixed in UN-3448 / PR #1941), so the root lock has been 5 weeks stale. `uv lock` re-resolves everything against current PyPI, picking up minor/patch bumps the workflow would have applied over those 5 weeks. So the diff is: - banks 2.4.1 → 2.4.2 (the actual fix) - ~271 other packages with incidental drift (what the workflow would have done anyway) Surgical hand-editing was considered and rejected — fragile, and a future pyproject.toml-touching PR would trigger this same refresh once the workflow runs again. Verified: `uv lock --check` exits 0 (Resolved 272 packages in 3ms). Unblocks the `Update UV lock in all directories` check on PR #1940 and any future PRs that touch a pyproject.toml. Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
11 tasks
athul-rs
added a commit
that referenced
this pull request
May 7, 2026
…ages (#1940) * UN-3447 [MISC] Expand workers coverage scope to all 11 packages Coverage configuration in workers/pyproject.toml previously measured only 5 of 11 worker packages (shared, api_deployment, general, file_processing, callback). This left ~2,843 statements unmeasured, including the executor worker (labs E1 C-prep) and the pluggable_worker slot — both central to the upcoming PG Queue migration (Epic UN-3445). Added executor, pluggable_worker, notification, scheduler, log_consumer, and ide_callback to both pytest --cov= flags and [tool.coverage.run].source. Non-regressive: only adds measurement scope. First task under Story UN-3446 (Phase 1 — Test Infrastructure). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * UN-3447 [MISC] Add missing workers to isort known_first_party Greptile flagged the same 6 packages we added to coverage scope are also missing from [tool.isort].known_first_party. Without this, isort won't treat imports from executor/, pluggable_worker/, notification/, scheduler/, log_consumer/, and ide_callback/ as first-party — they'd get mis-grouped on format runs against those packages' files. Same fix, same file — keeping config consistent. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * UN-3449 [FIX] Refresh root `uv.lock` — fix malformed `banks` entry (#1945) UN-3449 [FIX] Refresh root uv.lock — fix malformed banks entry The root uv.lock had a malformed banks entry that prevented uv from parsing it: error: Failed to parse `uv.lock` Caused by: The entry for package `banks` v2.4.1 has wheel `banks-2.2.0-py3-none-any.whl` with inconsistent version: v2.2.0 The version field claimed v2.4.1 but the sdist/wheel filenames were both v2.2.0. The PyPI upload-time on the wheel matches banks 2.2.0's release date, so the artifacts really are 2.2.0 — most likely a manual edit or a partial-write bug in an older uv version. banks is a transitive dependency pulled in by llama-index-core v0.14.16 (LlamaIndex's prompt-templating library). Unstract code does not import banks directly. Fix: regenerate via `rm uv.lock && uv lock`. After regen, banks resolves to v2.4.2 with consistent artifacts. Why 1,557 lines change: the auto-update workflow has been broken since 2026-04-01 (now fixed in UN-3448 / PR #1941), so the root lock has been 5 weeks stale. `uv lock` re-resolves everything against current PyPI, picking up minor/patch bumps the workflow would have applied over those 5 weeks. So the diff is: - banks 2.4.1 → 2.4.2 (the actual fix) - ~271 other packages with incidental drift (what the workflow would have done anyway) Surgical hand-editing was considered and rejected — fragile, and a future pyproject.toml-touching PR would trigger this same refresh once the workflow runs again. Verified: `uv lock --check` exits 0 (Resolved 272 packages in 3ms). Unblocks the `Update UV lock in all directories` check on PR #1940 and any future PRs that touch a pyproject.toml. Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com> Co-authored-by: Athul <89829560+athul-rs@users.noreply.github.com>
kirtimanmishrazipstack
added a commit
that referenced
this pull request
May 7, 2026
* UN-3439 [FIX] Accept wildcard subdomain origins in SocketIO and Django CORS (#1938) * UN-3439 [FIX] Accept wildcard subdomain origins in SocketIO and Django CORS Production socket connections were failing for `*.env.us-central.unstract.com` because python-socketio does exact-string comparison on `cors_allowed_origins`, so a literal `*` pattern silently rejected every real subdomain. - Add `CORS_ALLOWED_ORIGIN_REGEXES` derived from `WEB_APP_ORIGIN_URL_WITH_WILD_CARD`. - Wire SocketIO via `_RegexOrigin` whose `__eq__` does the regex match — single list entry covers all wildcard subdomains, no library subclass needed. - Normalize `WEB_APP_ORIGIN_URL` through `urlparse` so trailing slashes / paths in env are stripped (also fixes the `…com//oauth-status/` double-slash). - Add startup guard for malformed env values. Resolves item #1 of UN-3439. Items #2/#3 (decoupling indexing from Socket.io, fallback) are owned separately. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * UN-3439 [FIX] Address PR review: canonical origin, fullmatch, unhashable RegexOrigin, tests Addresses five review comments on #1938: 1. coderabbitai (Major) — RFC 6454 canonicalization. Browsers serialize `Origin` headers with a lowercase host and no explicit default ports; `parsed_url.netloc` preserved both, so `https://APP.EXAMPLE.COM:443` would silently fail to match the browser's `https://app.example.com`. Switch to `parsed_url.hostname` + drop default ports, and reject non-http(s) schemes at startup. 2. greptile (P2) — `re.fullmatch` instead of `re.match`. With `re.match` plus `$`, a candidate ending in `\n` matches because `$` is allowed before an optional trailing newline. `fullmatch` removes the ambiguity. 3. self — `_RegexOrigin.__hash__` violated `a == b ⇒ hash(a) == hash(b)` (one fixed pattern hash vs. many matching strings). Today this is masked because python-socketio uses linear `__eq__` on a list, but if the allow-list is ever wrapped in a set, every legitimate subdomain would silently be rejected — exactly the failure mode UN-3439 closes. Make instances unhashable so the contract can't be broken. 4. self — No regression tests. Add `backend/utils/tests/test_cors_origin.py` (33 cases) covering: regex match/no-match, lookalike spoofing, scheme mismatch, trailing-newline rejection, non-string equality protocol, unhashability, ReDoS bounds, URL normalization (case, default ports, trailing slash, paths, queries), startup-guard rejections (empty, no-scheme, non-browser-scheme, no-host), and end-to-end via the same `RegexOrigin` path SocketIO uses. 5. self — Over-clever wildcard-to-regex builder. The `split('*').join(re.escape, ...)` construction generalised to N wildcards but the input has exactly one; replace with a direct rf-string that's self-evident on review. Refactor for testability: extract `RegexOrigin` and `normalize_web_app_origin` into `backend/utils/cors_origin.py` (Django-free, importable from settings and tests). Settings now delegates to one helper call; `log_events.py` imports `RegexOrigin`. No behavioural change beyond what each comment fixes. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * UN-3439 [FIX] Address SonarCloud quality gate The Sonar quality gate failed with C reliability + 5 security hotspots, all on the new test file: - S905 (Bug, Major) — `{ro}` flagged as no-side-effect statement (Sonar doesn't see the implicit `__hash__` call). Drove the C reliability rating. Fix: use `len({ro})` so the side effect is via an explicit function call; test still asserts the same `TypeError`. - S5727 (Code Smell, Critical) — `assert ro != None` is tautological and doesn't exercise `__eq__`. Switch to `(ro == None) is False` which directly tests that `NotImplemented` falls back to identity-equality. - S5332 × 5 (Hotspots) — `http://` and `ftp://` literals in test data. These are intentional inputs proving the rejection logic. Annotate with `# NOSONAR` and an explanatory comment so the hotspots can be marked reviewed. No production code changed; tests still 33/33 passing. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * UN-3439 [FIX] Remove last S5727 code smell — test __eq__ via dunder Sonar S5727 correctly inferred that ``ro == None`` is statically always False (NotImplemented falls back to identity), making the assertion look tautological. The intent is to lock the protocol contract: ``__eq__`` must return the ``NotImplemented`` sentinel for non-strings. Test that directly via ``ro.__eq__(None) is NotImplemented`` instead of going through ``==``. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * UN-3439 [FIX] Address remaining CodeRabbit nits — port validation, ReDoS bound Two minor follow-ups from the second CodeRabbit pass: - `parsed.port` is a property that raises ValueError on malformed/out-of-range inputs (e.g. `:abc`, `:99999`). That bypassed our normalized config-error message and surfaced as a stack trace. Wrap the access and re-raise with the same actionable text. Adds two test cases (`https://example.com:abc`, `https://example.com:99999`) to lock the new behaviour. - The 50ms ReDoS timing bound is too tight for noisy CI runners. Loosen to 500ms — still orders of magnitude below what catastrophic backtracking would produce. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * ReverseMerge: V0.161.4 hotfix (#1943) * Change csp to report only * [HOTFIX] Bool-parse ENABLE_HIGHLIGHT_API_DEPLOYMENT env var (v0.161.4) (#1939) [HOTFIX] Bool-parse ENABLE_HIGHLIGHT_API_DEPLOYMENT env var (#1937) [FIX] Bool-parse ENABLE_HIGHLIGHT_API_DEPLOYMENT env var os.environ.get returns the raw string when the variable is set, so ENABLE_HIGHLIGHT_API_DEPLOYMENT="False" was truthy in Python (any non-empty string is truthy). Wrap in CommonUtils.str_to_bool so "False" / "false" / "0" actually evaluate to False. The setting is consumed by the cloud configuration plugin's spec default (ConfigSpec.default in plugins/configuration/cloud_config.py) on cloud and on-prem builds. With this fix, an admin who explicitly sets the env var to a falsy string sees highlight data stripped as expected. Co-authored-by: vishnuszipstack <117254672+vishnuszipstack@users.noreply.github.com> Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Deepak K <89829542+Deepak-Kesavan@users.noreply.github.com> Co-authored-by: vishnuszipstack <117254672+vishnuszipstack@users.noreply.github.com> Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * UN-3448 [FIX] Remove vestigial `uv pip install` line in uv-lock-automation workflow (#1941) * UN-3448 [FIX] Add --system flag to uv pip install in uv-lock-automation workflow Modern uv requires uv pip install to run inside a virtual environment OR with the explicit --system flag. The workflow currently has neither, so it errors out: error: No virtual environment found for Python 3.12.9; run `uv venv` to create an environment, or pass `--system` to install into a non-virtual environment This breaks every PR that touches a pyproject.toml (the workflow's paths filter triggers on those). Last successful run was 2026-04-01, before a behaviour change in uv or astral-sh/setup-uv@v7. The --system flag is exactly what the error message suggests and is correct here — we install pip into the runner's system Python; the downstream uv-lock.sh script creates its own venvs as needed. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * UN-3448 [FIX] Remove vestigial `uv pip install` line per review Per @jaseemjaskp's review: the pre-step `uv pip install ... pip` does nothing useful for this workflow. The downstream uv-lock.sh script uses uv sync at line 74, which manages its own venvs internally and never invokes pip directly: $ grep -rn 'pip' docker/scripts/uv-lock-gen/ docker/scripts/uv-lock-gen/uv-lock.sh:2:set -o pipefail Only match is pipefail (shell option), no real pip references. Removing the line entirely is cleaner than papering over with --system. The line was likely copy-pasted from a sibling workflow that legitimately needed pip in the system Python. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * ReverseMerge: V0.163.2 hotfix (#1946) * [HOTFIX] Use importlib.util.find_spec for pluggable worker discovery (#1918) * [FIX] Use importlib.util.find_spec for pluggable worker discovery _verify_pluggable_worker_exists() previously checked for the literal file `pluggable_worker/<name>/worker.py` on disk, which breaks when the plugin has been compiled to a .so (Nuitka, Cython, or any C extension) — the module is perfectly importable but the pre-check rejects it because only the .py extension is considered. Replace the filesystem check with importlib.util.find_spec(), which is Python's standard way to ask "is this module resolvable by the import system?". It honors every registered finder — source .py, compiled .so, bytecode .pyc, namespace packages, zipimports — so the function now matches what its docstring claims: verifying the module can be loaded, not that a specific file extension is present. Behavior is preserved for existing deployments: - Images with no `pluggable_worker/<name>/` subpackage → find_spec raises ModuleNotFoundError (ImportError subclass) → returns False. - Images with source .py → find_spec resolves the .py → returns True. - Images with compiled .so → find_spec resolves the .so → returns True. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * [FIX] Handle ValueError from find_spec in pluggable worker verification Greptile-flagged edge case: importlib.util.find_spec() can raise ValueError (not just ImportError) when sys.modules has a partially initialised module entry with __spec__ = None from a prior failed import. Broaden the except to catch both. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * [FIX] Resolve api-deployment worker directory from enum import path worker.py:452 did worker_type.value.replace("-", "_") to derive the on-disk dir name. All WorkerType enum values already use underscores, so the replace was a no-op; for API_DEPLOYMENT whose dir is "api-deployment" (hyphen), it resolved to "api_deployment" and the os.path.exists() check failed. Boot then logged a spurious "❌ Worker directory not found: /app/api_deployment" at ERROR level. The task registration path (builder + celery autodiscover via to_import_path) is unaffected, so this was purely log noise — but noise at ERROR level that masks real failures in log scans. Fix: derive the directory from the authoritative to_import_path() which already handles the hyphen case (api_deployment -> api-deployment). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * [HOTFIX] Add IAM Role / Instance Profile auth mode to AWS Bedrock adapter (#1944) * [FEAT] Allow Bedrock to fall through to boto3's default credential chain Match the S3/MinIO connector pattern: when AWS access keys are left blank on the Bedrock LLM and embedding adapter forms, drop them from the kwargs dict so boto3's default credential chain handles authentication. This unlocks IAM role / instance profile / IRSA / AWS Profile scenarios on hosts that already have ambient AWS credentials (e.g. EKS workers with IRSA, EC2 with an instance profile). - llm1/static/bedrock.json: clarify access-key descriptions to mention IRSA and instance profile (already non-required at v0.163.2 base). - embedding1/static/bedrock.json: drop aws_access_key_id and aws_secret_access_key from top-level required; same description fix; expose aws_profile_name for parity with the LLM form. - base1.py: AWSBedrockLLMParameters and AWSBedrockEmbeddingParameters now strip empty access-key values from the validated kwargs before returning, so empty strings don't override boto3's default chain. AWSBedrockEmbeddingParameters fields gain explicit None defaults and an aws_profile_name field. Backward-compatible: existing adapters with access keys filled in continue to work unchanged. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * [FEAT] Add Authentication Type selector to Bedrock adapter form Add an explicit `auth_type` selector with two options, making the auth choice clear to users: - "Access Keys" (default): existing flow, keys required - "IAM Role / Instance Profile (on-prem AWS only)": no fields; relies on boto3's default credential chain (IRSA on EKS, task role on ECS, instance profile on EC2). Description on the selector explicitly notes this option is only for AWS-hosted Unstract deployments. The form-only auth_type field is stripped before LiteLLM validation in both AWSBedrockLLMParameters.validate() and AWSBedrockEmbeddingParameters. validate(). Empty access keys continue to be stripped so boto3 falls through to the default chain even when the access_keys arm is selected without values (matches the S3/MinIO connector pattern). Backward-compatible: legacy adapters without auth_type behave as "Access Keys" mode (the default), and existing keys are forwarded unchanged. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * [REVIEW] Address Bedrock auth_type review feedback Fixes the P0/P1 issues raised by greptile-apps and jaseemjaskp on PR #1944. Behaviour fixes: - Stale-key leak in IAM Role mode: switching an existing adapter from Access Keys to IAM Role would carry truthy stored access keys through the strip-empty-only loop, so boto3 silently authenticated with the old long-lived credentials instead of falling through to the host's IRSA / instance-profile identity. Both LLM and embedding paths were affected. - Silent acceptance of unknown auth_type: a typo (e.g. "access_key") or a malformed payload from a non-UI client passed through the dict comprehension untouched, with no enum guard. - Cross-field validation gap: explicit Access Keys mode with blank or whitespace-only values silently fell through to the default credential chain instead of surfacing the misconfiguration. Implementation: - Add a module-level _resolve_bedrock_aws_credentials helper used by both AWSBedrockLLMParameters.validate() and AWSBedrock EmbeddingParameters.validate(), so the auth-type contract is expressed once. - Validates auth_type against an allowlist (None | "access_keys" | "iam_role"); raises ValueError on anything else. - iam_role: unconditionally drops aws_access_key_id and aws_secret_access_key. - access_keys (explicit): requires non-blank values; raises ValueError if either is empty or whitespace-only. - Legacy (auth_type absent): retains the lenient strip behaviour so pre-PR adapter configurations continue to deserialise unchanged. - Restore aws_region_name as required (no `= None` default) on AWSBedrockEmbeddingParameters; only credentials may legitimately be absent. - Drop the orphan aws_profile_name field from embedding1/static/bedrock.json: it was added for parity with the LLM form but lives outside the auth_type oneOf and contradicts the selector's "no further input" semantics. The LLM form already had aws_profile_name pre-PR and is left alone for backwards compatibility. Tests: - New tests/test_bedrock_adapter.py covers 15 cases across LLM and embedding adapters: legacy-no-auth-type, explicit access_keys with valid/blank/whitespace keys, iam_role with stale/no keys, unknown auth_type rejection, cross-field validation, and preservation of unrelated params (model_id, aws_profile_name, region, thinking). Skipped (P2 nice-to-have): - Comment-scope clarification, MinIO reference rewording, validate-mutates-caller'\''s-dict, and the LLM form description nit about aws_profile_name visibility. These don'\''t change behaviour and can be addressed in a follow-up. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * [pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com> Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com> --------- Co-authored-by: Chandrasekharan M <117059509+chandrasekharan-zipstack@users.noreply.github.com> Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com> Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com> Co-authored-by: Athul <89829560+athul-rs@users.noreply.github.com> * batch notification --------- Co-authored-by: ali <117142933+muhammad-ali-e@users.noreply.github.com> Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com> Co-authored-by: Ritwik G <100672805+ritwik-g@users.noreply.github.com> Co-authored-by: Deepak K <89829542+Deepak-Kesavan@users.noreply.github.com> Co-authored-by: vishnuszipstack <117254672+vishnuszipstack@users.noreply.github.com> Co-authored-by: Praveen Kumar <praveen@zipstack.com> Co-authored-by: Chandrasekharan M <117059509+chandrasekharan-zipstack@users.noreply.github.com> Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com> Co-authored-by: Athul <89829560+athul-rs@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
3 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.
What
uv pip install --python=3.12.9 pipline from.github/workflows/uv-lock-automation.yaml.Why
The line was failing the workflow on every PR that touches
pyproject.tomlsince 2026-04-01:The error appeared because
1997ce31e(PR #1883) bumpedsetup-uv@v5 → @v7, and v7 installs a uv-managed Python that isn't seen as system Python.Initial fix proposed: add
--systemflag (matching the pattern applied to other workflows in1997ce31e).Better fix per review: the line itself is vestigial. The downstream
docker/scripts/uv-lock-gen/uv-lock.shusesuv syncat line 74, which manages its own venvs internally and never invokespipdirectly:Only match is
pipefail(shell option), no realpipreferences. Pre-installing pip into the system Python serves no purpose for this workflow — the line was likely copy-pasted from a sibling workflow that legitimately needed pip.Reference: UN-3448.
How
- name: Install uv uses: astral-sh/setup-uv@v7 with: # Install a specific version of uv. version: "0.6.14" python-version: 3.12.9 - - run: uv pip install --python=3.12.9 pip - - name: Generate UV lockfilesTwo-line deletion. No replacement needed.
Can this PR break any existing features. If yes, please list possible items. If no, please explain why.
No. The deleted line did not contribute to the workflow's purpose:
pip(verified by grep).The workflow itself is non-blocking (other required checks gate merges), so worst case is "still broken" — but verification above shows the workflow will now successfully run
uv syncfor each directory.Database Migrations
None.
Env Config
None.
Related Issues or PRs
1997ce31e(PR [CHORE] Upgrade GitHub Actions to Node.js 24 compatible versions #1883)uv pip installline in uv-lock-automation workflow #1941, review4227913262Dependencies Versions
None changed.
Notes on Testing
pyproject.toml. This PR modifies a workflow file, not a pyproject, so the trigger won't fire here. The next PR that touches anypyproject.tomlafter this merges will be the real validation.workflow_dispatchis available on this workflow — a maintainer can run it post-merge to confirm.Screenshots
N/A — workflow file change.
Checklist
🤖 Generated with Claude Code