LCORE-1062: Updated deps

[tisnik]

Description

LCORE-1062: Updated deps

Type of change

• Refactor
• New feature
• Bug fix
• CVE fix
• Optimization
• Documentation Update
• Configuration Update
• Bump-up service version
• Bump-up dependent library
• Bump-up library or tool used for development (does not change the final image)
• CI configuration change
• Konflux configuration change
• Unit tests improvement
• Integration tests improvement
• End to end tests improvement

Tools used to create PR

• Assisted-by: N/A
• Generated by: N/A

Related Tickets & Documents

• Related Issue #LCORE-1062

Summary by CodeRabbit

• Chores
  • Updated aiosqlite to version 0.22.1
  • Updated psutil to version 7.2.0

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Two architecture-specific requirements files (aarch64 and x86_64) are updated with dependency version bumps: aiosqlite from 0.22.0 to 0.22.1 and psutil from 7.1.3 to 7.2.0, along with corresponding hash updates for integrity verification.

Changes

Cohort / File(s)	Summary
Dependency version upgrades requirements.aarch64.txt, requirements.x86_64.txt	Updated aiosqlite to 0.22.1 with new hash entries and psutil to 7.2.0 with expanded hash set

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

• LCORE-1062: updated deps #911: Modifies the same requirements files and includes an earlier aiosqlite bump from 0.22.0, representing a prior incremental update in the dependency chain.

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'LCORE-1062: Updated deps' is vague and generic, using non-descriptive terms like 'Updated deps' that do not convey specific information about which dependencies were updated or their versions.	Consider making the title more specific, such as 'Update aiosqlite to 0.22.1 and psutil to 7.2.0' to clearly indicate which dependencies were bumped and their target versions.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3929189 and 1a20c9b.

⛔ Files ignored due to path filters (1)

• uv.lock is excluded by !**/*.lock

📒 Files selected for processing (2)

• requirements.aarch64.txt
• requirements.x86_64.txt

🧰 Additional context used

🧠 Learnings (1)

📚 Learning: 2025-08-18T10:58:14.951Z

Learnt from: matysek
Repo: lightspeed-core/lightspeed-stack PR: 292
File: pyproject.toml:47-47
Timestamp: 2025-08-18T10:58:14.951Z
Learning: psycopg2-binary is required by some llama-stack providers in the lightspeed-stack project, so it cannot be replaced with psycopg v3 or moved to optional dependencies without breaking llama-stack functionality.

Applied to files:

• requirements.aarch64.txt
• requirements.x86_64.txt

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (8)

• GitHub Check: build-pr
• GitHub Check: Konflux kflux-prd-rh02 / lightspeed-stack-on-pull-request
• GitHub Check: E2E: library mode / vertexai
• GitHub Check: E2E: server mode / ci
• GitHub Check: E2E: server mode / vertexai
• GitHub Check: E2E: library mode / ci
• GitHub Check: E2E: server mode / azure
• GitHub Check: E2E: library mode / azure

🔇 Additional comments (4)

requirements.aarch64.txt (2)

143-145: aiosqlite bump looks fine; verify cross-platform lock consistency

The pin and hashes for aiosqlite==0.22.1 look consistent with a uv‑generated file. Just make sure:

• The same version is used across all requirements/lock artifacts (x86_64, dev/prod images, CI).
• There are no upstream constraints in pyproject.toml or transitive deps that still expect 0.22.0.

---

2411-2432: psutil upgrade to 7.2.0 with expanded wheels set – confirm runtime compatibility

The psutil==7.2.0 pin and hash set look mechanically correct for a uv compile on aarch64. Given psutil’s low-level OS integrations and your use under accelerate/peft/stack runtime, please:

• Run the usual test/health check suite on aarch64 images (CPU load, memory, GPU telemetry if applicable).
• Confirm that images/builds for other architectures were re‑compiled with the same version so you don’t drift between platform‑specific requirement files.

requirements.x86_64.txt (2)

143-145: aiosqlite patch bump looks consistent with uv output

The version pin and hashes for aiosqlite==0.22.1 look syntactically correct and aligned with the existing style. No issues from the requirements file perspective; just ensure this patch release is validated in the dev/llama-stack flows that exercise async DB usage.

Please confirm against pyproject.toml / uv pip compile and upstream aiosqlite release notes that 0.22.1 is the intended target and has no breaking or security concerns for your use cases.

---

2411-2432: psutil minor version bump appears correct; validate on target platforms

The psutil==7.2.0 pin and its hash set are well-formed and consistent with the rest of the file. Given psutil’s OS-integration, it’s worth running CI and a quick manual smoke test on the main deployment platforms to catch any behavioral changes.

Please double‑check that:

• The aarch64 requirements file pins the same psutil version and hashes, and
• CI passes for components relying on psutil (resource monitoring, health checks, etc.), and review upstream changelog for any platform‑specific caveats.

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}