SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-07-30 01:32:43 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

Karakeep: Version 0.27.0 breaks the workers #1864

New Issue
Closed
opened 2025-11-20 05:18:44 -05:00 by saavagebueno · 6 comments
saavagebueno commented 2025-11-20 05:18:44 -05:00
Owner
Copy Link

Originally created by @MohamedBassem on GitHub (Sep 7, 2025).

Originally assigned to: @CrazyWolf13 on GitHub.

✅ Have you read and understood the above guidelines?

yes

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

Karakeep

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

..

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

No response

📈 Which Proxmox version are you on?

8.4.6

📝 Provide a clear and concise description of the issue.

Opening this issue preemptively in before people open it here. I noticed it just after releasing the new version unfortunately.

In the last release of karakeep, the worker build path changed from index.mjs to index.js which will require updating the systemd configs for those apps.

🔄 Steps to reproduce the issue.

Upgrading (or installing) karakeep to version 0.27 will break the

❌ Paste the full error output (if available).

Node.js v22.19.0
node:internal/modules/cjs/loader:1386
  throw err;
  ^

Error: Cannot find module '/opt/karakeep/apps/workers/dist/index.js'
    at Function._resolveFilename (node:internal/modules/cjs/loader:1383:15)
    at defaultResolveImpl (node:internal/modules/cjs/loader:1025:19)
    at resolveForCJSWithHooks (node:internal/modules/cjs/loader:1030:22)
    at Function._load (node:internal/modules/cjs/loader:1192:37)
    at TracingChannel.traceSync (node:diagnostics_channel:322:14)
    at wrapModuleLoad (node:internal/modules/cjs/loader:237:24)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:171:5)
    at node:internal/main/run_main_module:36:49 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}

🖼️ Additional context (optional).

No response

Originally created by @MohamedBassem on GitHub (Sep 7, 2025). Originally assigned to: @CrazyWolf13 on GitHub. ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Karakeep ### 📂 What was the exact command used to execute the script? .. ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? _No response_ ### 📈 Which Proxmox version are you on? 8.4.6 ### 📝 Provide a clear and concise description of the issue. Opening this issue preemptively in before people open it here. I noticed it just after releasing the new version unfortunately. In the last release of karakeep, the worker build path changed from `index.mjs` to `index.js` which will require updating the systemd configs for those apps. ### 🔄 Steps to reproduce the issue. Upgrading (or installing) karakeep to version 0.27 will break the ### ❌ Paste the full error output (if available). ``` Node.js v22.19.0 node:internal/modules/cjs/loader:1386 throw err; ^ Error: Cannot find module '/opt/karakeep/apps/workers/dist/index.js' at Function._resolveFilename (node:internal/modules/cjs/loader:1383:15) at defaultResolveImpl (node:internal/modules/cjs/loader:1025:19) at resolveForCJSWithHooks (node:internal/modules/cjs/loader:1030:22) at Function._load (node:internal/modules/cjs/loader:1192:37) at TracingChannel.traceSync (node:diagnostics_channel:322:14) at wrapModuleLoad (node:internal/modules/cjs/loader:237:24) at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:171:5) at node:internal/main/run_main_module:36:49 { code: 'MODULE_NOT_FOUND', requireStack: [] } ``` ### 🖼️ Additional context (optional). _No response_
saavagebueno added the bug label 2025-11-20 05:18:44 -05:00
saavagebueno commented 2025-11-20 05:18:45 -05:00
Author
Owner
Copy Link

@MohamedBassem commented on GitHub (Sep 7, 2025):

And maybe in the context of this issue, we need to discuss how to bundle the installation script with every karakeep release so that it's versioned controlled along each release.

@MohamedBassem commented on GitHub (Sep 7, 2025): And maybe in the context of this issue, we need to discuss how to bundle the installation script with every karakeep release so that it's versioned controlled along each release.
saavagebueno commented 2025-11-20 05:18:45 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Sep 7, 2025):

Maybe it would be a possibility to deliver a complete prebuild (gh Action - many use this now, paperless and co.), or an NPM installation? (Example actualBudget).

Update the Service should not be an problem, this are 2-3 lines more Code.

@MickLesk commented on GitHub (Sep 7, 2025): Maybe it would be a possibility to deliver a complete prebuild (gh Action - many use this now, paperless and co.), or an NPM installation? (Example actualBudget). Update the Service should not be an problem, this are 2-3 lines more Code.
saavagebueno commented 2025-11-20 05:18:45 -05:00
Author
Owner
Copy Link

@MohamedBassem commented on GitHub (Sep 7, 2025):

Yeah, I think an NPM installation will probably be the way to go instead of a full build on every installation. Will try to look into that in the next release.

For now, we'll need a migration to migrate:

ExecStart=/usr/bin/node dist/index.mjs

to

ExecStart=/usr/bin/node dist/index.js

Really sorry about the hassle.

@MohamedBassem commented on GitHub (Sep 7, 2025): Yeah, I think an NPM installation will probably be the way to go instead of a full build on every installation. Will try to look into that in the next release. For now, we'll need a migration to migrate: ``` ExecStart=/usr/bin/node dist/index.mjs ``` to ``` ExecStart=/usr/bin/node dist/index.js ``` Really sorry about the hassle.
saavagebueno commented 2025-11-20 05:18:45 -05:00
Author
Owner
Copy Link

@michelroegl-brunner commented on GitHub (Sep 7, 2025):

Yeah, I think an NPM installation will probably be the way to go instead of a full build on every installation. Will try to look into that in the next release.

For now, we'll need a migration to migrate:

ExecStart=/usr/bin/node dist/index.mjs

to

ExecStart=/usr/bin/node dist/index.js

Really sorry about the hassle.

No worries, this is no big deal.
But i really apprechiate the heads up from you on this issue, we dont see that normaly :)

@michelroegl-brunner commented on GitHub (Sep 7, 2025): > Yeah, I think an NPM installation will probably be the way to go instead of a full build on every installation. Will try to look into that in the next release. > > For now, we'll need a migration to migrate: > > ``` > ExecStart=/usr/bin/node dist/index.mjs > ``` > to > ``` > ExecStart=/usr/bin/node dist/index.js > ``` > > Really sorry about the hassle. No worries, this is no big deal. But i really apprechiate the heads up from you on this issue, we dont see that normaly :)
saavagebueno commented 2025-11-20 05:18:46 -05:00
Author
Owner
Copy Link

@michelroegl-brunner commented on GitHub (Sep 7, 2025):

And thanks to @CrazyWolf13 the fix is allready merged.

@michelroegl-brunner commented on GitHub (Sep 7, 2025): And thanks to @CrazyWolf13 the fix is allready merged.
saavagebueno commented 2025-11-20 05:18:46 -05:00
Author
Owner
Copy Link

@MohamedBassem commented on GitHub (Sep 7, 2025):

The perks of having a user in the community-scripts team! ❤️ Really appreciate all the help @CrazyWolf13!

@MohamedBassem commented on GitHub (Sep 7, 2025): The perks of having a user in the community-scripts team! ❤️ Really appreciate all the help @CrazyWolf13!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
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
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#1864
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?