[PR #340] [MERGED] core: remove uv cache clean | remove log rotation #370

Closed
opened 2026-02-26 12:41:09 +03:00 by kerem · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/community-scripts/ProxmoxVE-Local/pull/340
Author: @MickLesk
Created: 11/24/2025
Status: Merged
Merged: 11/24/2025
Merged by: @MickLesk

Base: mainHead: MickLesk-patch-1


📝 Commits (2)

  • eccad85 core: remove uv cache clean
  • 5e8cf1f Initialize functions on core.func source

📊 Changes

1 file changed (+0 additions, -3 deletions)

View changed files

📝 scripts/core/core.func (+0 -3)

📄 Description

✍️ Description

Removed the cache clean command for uv.
UV uses aggresive cache methods, so it can be only cleared with --force, thats in my opinion to unsafe for productive usage:

Example:
root@paperless-ngx:~# uv cache prune
Cache is currently in-use, waiting for other uv processes to finish (use --force to override)

Example with force:
root@paperless-ngx:~# uv cache clean --force
Clearing cache at: .cache/uv
Removed 118567 files (1.4GiB)


remove log rotation, because some apps need the journalctl to get login data or api key

Link: Upstream: https://github.com/community-scripts/ProxmoxVE/pull/9413/

Prerequisites (X in brackets)

  • Self-review completed – Code follows project standards.
  • Tested thoroughly – Changes work as expected.
  • No security risks – No hardcoded secrets, unnecessary privilege escalations, or permission issues.

Screenshot for frontend Change


🛠️ Type of Change (X in brackets)

  • 🐞 Bug fix – Resolves an issue without breaking functionality.
  • New feature – Adds new, non-breaking functionality.
  • 💥 Breaking change – Alters existing functionality in a way that may require updates.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/community-scripts/ProxmoxVE-Local/pull/340 **Author:** [@MickLesk](https://github.com/MickLesk) **Created:** 11/24/2025 **Status:** ✅ Merged **Merged:** 11/24/2025 **Merged by:** [@MickLesk](https://github.com/MickLesk) **Base:** `main` ← **Head:** `MickLesk-patch-1` --- ### 📝 Commits (2) - [`eccad85`](https://github.com/community-scripts/ProxmoxVE-Local/commit/eccad85f916b7c26d718b5f5b9c4459c32657495) core: remove uv cache clean - [`5e8cf1f`](https://github.com/community-scripts/ProxmoxVE-Local/commit/5e8cf1f68560b37a6cba4dc1dfd1956e8ca06a80) Initialize functions on core.func source ### 📊 Changes **1 file changed** (+0 additions, -3 deletions) <details> <summary>View changed files</summary> 📝 `scripts/core/core.func` (+0 -3) </details> ### 📄 Description <!--🛑 All Pull Requests need to made against the development branch. PRs against main will get closed. --> ## ✍️ Description Removed the cache clean command for uv. UV uses aggresive cache methods, so it can be only cleared with --force, thats in my opinion to unsafe for productive usage: Example: root@paperless-ngx:~# uv cache prune Cache is currently in-use, waiting for other uv processes to finish (use --force to override) Example with force: root@paperless-ngx:~# uv cache clean --force Clearing cache at: .cache/uv Removed 118567 files (1.4GiB) _______________ remove log rotation, because some apps need the journalctl to get login data or api key ## 🔗 Related PR / Issue Link: Upstream: https://github.com/community-scripts/ProxmoxVE/pull/9413/ ## ✅ Prerequisites (**X** in brackets) - [x] **Self-review completed** – Code follows project standards. - [x] **Tested thoroughly** – Changes work as expected. - [x] **No security risks** – No hardcoded secrets, unnecessary privilege escalations, or permission issues. ## Screenshot for frontend Change --- ## 🛠️ Type of Change (**X** in brackets) - [x] 🐞 **Bug fix** – Resolves an issue without breaking functionality. - [ ] ✨ **New feature** – Adds new, non-breaking functionality. - [ ] 💥 **Breaking change** – Alters existing functionality in a way that may require updates. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
kerem 2026-02-26 12:41:09 +03:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ProxmoxVE-Local#370
No description provided.