starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 11 Packages Projects Releases 10 Wiki Activity

Palmr update fail #1619

New Issue
Closed
opened 2026-02-05 01:46:56 +03:00 by OVERLORD · 2 comments
OVERLORD commented 2026-02-05 01:46:56 +03:00
Owner
Copy Link

Originally created by @thieneret on GitHub (Sep 13, 2025).

Originally assigned to: @vhsdream on GitHub.

✅ Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

Palmr

📂 What was the exact command used to execute the script?

update

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📈 Which Proxmox version are you on?

pve-manager/9.0.6/49c767b70aeb6648 (running kernel: 6.14.11-1-pve)

📝 Provide a clear and concise description of the issue.

The update stops with an error. Palmr is not working.

🔄 Steps to reproduce the issue.

run update command in lxc console

❌ Paste the full error output (if available).

   / __ \____ _/ /___ ___  _____
  / /_/ / __ `/ / __ `__ \/ ___/
 / ____/ /_/ / / / / / / / /    
/_/    \__,_/_/_/ /_/ /_/_/     
                                

  ✔️   Stopped Services
  ✔️   Deployed: Palmr (3.2.1-beta)
  ✔️   Installed Node.js modules: pnpm@10.6.0
  ⏳   Updating PalmrLockfile is up to date, resolution step is skipped
Already up to date

   ╭───────────────────────────────────────────────────────────────────╮
   │                                                                   │
   │                Update available! 10.6.0 → 10.16.0.                │
   │   Changelog: https://github.com/pnpm/pnpm/releases/tag/v10.16.0   │
   │                 Run "pnpm add -g pnpm" to update.                 │
   │                                                                   │
   ╰───────────────────────────────────────────────────────────────────╯


╭ Warning ───────────────────────────────────────────────────────────────────────────────────╮
│                                                                                            │
│   Ignored build scripts: @prisma/client, @prisma/engines, esbuild, prisma, sharp.          │
│   Run "pnpm approve-builds" to pick which dependencies should be allowed to run scripts.   │
│                                                                                            │
╰────────────────────────────────────────────────────────────────────────────────────────────╯

Done in 1.2s using pnpm v10.6.0
Environment variables loaded from .env
Prisma schema loaded from prisma/schema.prisma

✔ Generated Prisma Client (v6.11.1) to ./node_modules/.pnpm/@prisma+client@6.11.1_prisma@6.11.1_typescript@5.8.3__typescript@5.8.3/node_modules/@prisma/client in 217ms

Start by importing your Prisma Client (See: https://pris.ly/d/importing-client)

Tip: Want to turn off tips and other hints? https://pris.ly/tip-4-nohints

Environment variables loaded from .env
Prisma schema loaded from prisma/schema.prisma
Datasource "db": SQLite database "palmr.db" at "file:/opt/palmr_data/palmr.db"

No migration found in prisma/migrations


┌─────────────────���───────────────────────────────────────┐
│  Update available 6.11.1 -> 6.16.1                      │
│  Run the following to update                            │
│    npm i --save-dev prisma@latest                       │
│    npm i @prisma/client@latest                          │
└─────────────────────────────────────────────────────────┘
No pending migrations to apply.
Environment variables loaded from .env
Prisma schema loaded from prisma/schema.prisma
Datasource "db": SQLite database "palmr.db" at "file:/opt/palmr_data/palmr.db"

🚀  Your database is now in sync with your Prisma schema. Done in 97ms

✔ Generated Prisma Client (v6.11.1) to ./node_modules/.pnpm/@prisma+client@6.11.1_prisma@6.11.1_typescript@5.8.3__typescript@5.8.3/node_modules/@prisma
/client in 182ms


> palmr-api@3.2.1-beta build /opt/palmr/apps/server
> tsc -p tsconfig.json

Lockfile is up to date, resolution step is skipped
Already up to date

╭ Warning ───────────────────────────────────────────────────────────────────────────────────╮
│                                                                                            │
│   Ignored build scripts: @tailwindcss/oxide, sharp, unrs-resolver.                         │
│   Run "pnpm approve-builds" to pick which dependencies should be allowed to run scripts.   │
│                                                                                            │
╰────────────────────────────────────────────────────────────────────────────────────────────╯

Done in 1.5s using pnpm v10.6.0

> palmr-web@3.2.1-beta build /opt/palmr/apps/web
> next build

   ▲ Next.js 15.3.4
   - Environments: .env

   Creating an optimized production build ...
 ✓ Compiled successfully in 84s
   Linting and checking validity of types  ...Failed to compile.

./src/app/files/components/empty-state.tsx:5:15
Type error: Module '"../types"' has no exported member 'EmptyStateProps'.

  3 |
  4 | import { Button } from "@/components/ui/button";
> 5 | import type { EmptyStateProps } from "../types";
    |               ^
  6 |
  7 | export function EmptyState({ onUpload }: EmptyStateProps) {
  8 |   const t = useTranslations();
Next.js build worker exited with code: 1 and signal: null
 ELIFECYCLE  Command failed with exit code 1.

[ERROR] in line 55: exit code 0: while executing command $STD pnpm build

🖼️ Additional context (optional).

No response

Originally created by @thieneret on GitHub (Sep 13, 2025). Originally assigned to: @vhsdream on GitHub. ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Palmr ### 📂 What was the exact command used to execute the script? update ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📈 Which Proxmox version are you on? pve-manager/9.0.6/49c767b70aeb6648 (running kernel: 6.14.11-1-pve) ### 📝 Provide a clear and concise description of the issue. The update stops with an error. Palmr is not working. ### 🔄 Steps to reproduce the issue. run update command in lxc console ### ❌ Paste the full error output (if available). ``` / __ \____ _/ /___ ___ _____ / /_/ / __ `/ / __ `__ \/ ___/ / ____/ /_/ / / / / / / / / /_/ \__,_/_/_/ /_/ /_/_/ ✔️ Stopped Services ✔️ Deployed: Palmr (3.2.1-beta) ✔️ Installed Node.js modules: pnpm@10.6.0 ⏳ Updating PalmrLockfile is up to date, resolution step is skipped Already up to date ╭───────────────────────────────────────────────────────────────────╮ │ │ │ Update available! 10.6.0 → 10.16.0. │ │ Changelog: https://github.com/pnpm/pnpm/releases/tag/v10.16.0 │ │ Run "pnpm add -g pnpm" to update. │ │ │ ╰───────────────────────────────────────────────────────────────────╯ ╭ Warning ───────────────────────────────────────────────────────────────────────────────────╮ │ │ │ Ignored build scripts: @prisma/client, @prisma/engines, esbuild, prisma, sharp. │ │ Run "pnpm approve-builds" to pick which dependencies should be allowed to run scripts. │ │ │ ╰────────────────────────────────────────────────────────────────────────────────────────────╯ Done in 1.2s using pnpm v10.6.0 Environment variables loaded from .env Prisma schema loaded from prisma/schema.prisma ✔ Generated Prisma Client (v6.11.1) to ./node_modules/.pnpm/@prisma+client@6.11.1_prisma@6.11.1_typescript@5.8.3__typescript@5.8.3/node_modules/@prisma/client in 217ms Start by importing your Prisma Client (See: https://pris.ly/d/importing-client) Tip: Want to turn off tips and other hints? https://pris.ly/tip-4-nohints Environment variables loaded from .env Prisma schema loaded from prisma/schema.prisma Datasource "db": SQLite database "palmr.db" at "file:/opt/palmr_data/palmr.db" No migration found in prisma/migrations ┌─────────────────���───────────────────────────────────────┐ │ Update available 6.11.1 -> 6.16.1 │ │ Run the following to update │ │ npm i --save-dev prisma@latest │ │ npm i @prisma/client@latest │ └─────────────────────────────────────────────────────────┘ No pending migrations to apply. Environment variables loaded from .env Prisma schema loaded from prisma/schema.prisma Datasource "db": SQLite database "palmr.db" at "file:/opt/palmr_data/palmr.db" 🚀 Your database is now in sync with your Prisma schema. Done in 97ms ✔ Generated Prisma Client (v6.11.1) to ./node_modules/.pnpm/@prisma+client@6.11.1_prisma@6.11.1_typescript@5.8.3__typescript@5.8.3/node_modules/@prisma /client in 182ms > palmr-api@3.2.1-beta build /opt/palmr/apps/server > tsc -p tsconfig.json Lockfile is up to date, resolution step is skipped Already up to date ╭ Warning ───────────────────────────────────────────────────────────────────────────────────╮ │ │ │ Ignored build scripts: @tailwindcss/oxide, sharp, unrs-resolver. │ │ Run "pnpm approve-builds" to pick which dependencies should be allowed to run scripts. │ │ │ ╰────────────────────────────────────────────────────────────────────────────────────────────╯ Done in 1.5s using pnpm v10.6.0 > palmr-web@3.2.1-beta build /opt/palmr/apps/web > next build ▲ Next.js 15.3.4 - Environments: .env Creating an optimized production build ... ✓ Compiled successfully in 84s Linting and checking validity of types ...Failed to compile. ./src/app/files/components/empty-state.tsx:5:15 Type error: Module '"../types"' has no exported member 'EmptyStateProps'. 3 | 4 | import { Button } from "@/components/ui/button"; > 5 | import type { EmptyStateProps } from "../types"; | ^ 6 | 7 | export function EmptyState({ onUpload }: EmptyStateProps) { 8 | const t = useTranslations(); Next.js build worker exited with code: 1 and signal: null  ELIFECYCLE  Command failed with exit code 1. [ERROR] in line 55: exit code 0: while executing command $STD pnpm build ``` ### 🖼️ Additional context (optional). _No response_
OVERLORD added the buginvestigation labels 2026-02-05 01:46:56 +03:00
OVERLORD commented 2026-02-05 01:47:02 +03:00
Author
Owner
Copy Link

@vhsdream commented on GitHub (Sep 13, 2025):

@thieneret Can confirm this also happens to me during an update, on PVE 8.4. But this looks like an issue with the build process; I suggest you create an issue in the Palmr repo.

@vhsdream commented on GitHub (Sep 13, 2025): @thieneret Can confirm this also happens to me during an update, on PVE 8.4. But this looks like an issue with the build process; I suggest you create an issue in the Palmr repo.
OVERLORD commented 2026-02-05 01:47:04 +03:00
Author
Owner
Copy Link

@vhsdream commented on GitHub (Sep 13, 2025):

@thieneret Spoke too soon. Update will need to delete the entire install folder to make sure there isn't anything left over.

You can test it yourself after running the update and letting it fail. cd into /opt/palmr/apps/web then rm src/app/files/components/empty-state.tsx and then run pnpm build and it will build.

Hotfix incoming.

@vhsdream commented on GitHub (Sep 13, 2025): @thieneret Spoke too soon. Update will need to delete the entire install folder to make sure there isn't anything left over. You can test it yourself after running the update and letting it fail. `cd` into `/opt/palmr/apps/web` then `rm src/app/files/components/empty-state.tsx` and then run `pnpm build` and it will build. Hotfix incoming.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label bug investigation
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#1619
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?