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

Actual Budget not updating #356

New Issue
Closed
opened 2026-02-04 18:10:18 +03:00 by OVERLORD · 9 comments
OVERLORD commented 2026-02-04 18:10:18 +03:00
Owner
Copy Link

Originally created by @infinitytec on GitHub (Jan 20, 2025).

✅ Have you read and understood the above guidelines?

yes

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

actualbudget-install

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

bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/actualbudget.sh)"

📝 Provide a clear and concise description of the issue.

When running the script to update, I got the following error message:

Image

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

No response

🔄 Steps to reproduce the issue.

Open the LXC.

Run the updater.

Confirm the update.

❌ Paste the full error output (if available).

[ERROR] in line 53: exit code 0: while executing command yarn install &> /dev/null

🖼️ Additional context (optional).

No response

Originally created by @infinitytec on GitHub (Jan 20, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? actualbudget-install ### 📂 What was the exact command used to execute the script? bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/actualbudget.sh)" ### 📝 Provide a clear and concise description of the issue. When running the script to update, I got the following error message: ![Image](https://github.com/user-attachments/assets/9e627023-9fd2-42bf-97bd-11b3984dc579) ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? _No response_ ### 🔄 Steps to reproduce the issue. Open the LXC. Run the updater. Confirm the update. ### ❌ Paste the full error output (if available). `[ERROR] in line 53: exit code 0: while executing command yarn install &> /dev/null` ### 🖼️ Additional context (optional). _No response_
OVERLORD commented 2026-02-04 18:10:35 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jan 20, 2025):

Execute yarn install in /opt/actualbudget. Whats the Output?

@MickLesk commented on GitHub (Jan 20, 2025): Execute yarn install in /opt/actualbudget. Whats the Output?
OVERLORD commented 2026-02-04 18:10:54 +03:00
Author
Owner
Copy Link

@infinitytec commented on GitHub (Jan 21, 2025):

Execute yarn install in /opt/actualbudget. Whats the Output?

➤ YN0065: Yarn will periodically gather anonymous telemetry: https://yarnpkg.com/advanced/telemetry
➤ YN0065: Run yarn config set --home enableTelemetry 0 to disable

➤ YN0000: · Yarn 4.3.1
➤ YN0000: ┌ Resolution step
➤ YN0000: └ Completed in 0s 253ms
➤ YN0000: ┌ Post-resolution validation
➤ YN0002: │ actual-sync@workspace:. doesn't provide @babel/core (p89c81), requested by @babel/preset-typescript.
➤ YN0086: │ Some peer dependencies are incorrectly met by your project; run yarn explain peer-requirements <hash> for details, where <hash> is the six-letter p-prefixed code.
➤ YN0086: │ Some peer dependencies are incorrectly met by dependencies; run yarn explain peer-requirements for details.
➤ YN0000: └ Completed
➤ YN0000: ┌ Fetch step
➤ YN0000: └ Completed in 0s 835ms
➤ YN0000: ┌ Link step
➤ YN0000: └ Completed in 0s 317ms
➤ YN0000: · Done with warnings in 1s 475ms```
@infinitytec commented on GitHub (Jan 21, 2025): > Execute yarn install in /opt/actualbudget. Whats the Output? ```root@actualbudget:/opt/actualbudget# yarn install ➤ YN0065: Yarn will periodically gather anonymous telemetry: https://yarnpkg.com/advanced/telemetry ➤ YN0065: Run yarn config set --home enableTelemetry 0 to disable ➤ YN0000: · Yarn 4.3.1 ➤ YN0000: ┌ Resolution step ➤ YN0000: └ Completed in 0s 253ms ➤ YN0000: ┌ Post-resolution validation ➤ YN0002: │ actual-sync@workspace:. doesn't provide @babel/core (p89c81), requested by @babel/preset-typescript. ➤ YN0086: │ Some peer dependencies are incorrectly met by your project; run yarn explain peer-requirements <hash> for details, where <hash> is the six-letter p-prefixed code. ➤ YN0086: │ Some peer dependencies are incorrectly met by dependencies; run yarn explain peer-requirements for details. ➤ YN0000: └ Completed ➤ YN0000: ┌ Fetch step ➤ YN0000: └ Completed in 0s 835ms ➤ YN0000: ┌ Link step ➤ YN0000: └ Completed in 0s 317ms ➤ YN0000: · Done with warnings in 1s 475ms```
OVERLORD commented 2026-02-04 18:11:09 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jan 21, 2025):

Strange, no Error?

@MickLesk commented on GitHub (Jan 21, 2025): Strange, no Error?
OVERLORD commented 2026-02-04 18:11:12 +03:00
Author
Owner
Copy Link

@infinitytec commented on GitHub (Jan 21, 2025):

Strange, no Error?

I had rolled back! This is after I tried running update:

error This project's package.json defines "packageManager": "yarn@4.3.1". However the current global version of Yarn is 1.22.22.

Presence of the "packageManager" field indicates that the project is meant to be used with Corepack, a tool included by default with all official Node.js distributions starting from 16.9 and 14.19.
Corepack must currently be enabled by running corepack enable in your terminal. For more information, check out https://yarnpkg.com/corepack.
@infinitytec commented on GitHub (Jan 21, 2025): > Strange, no Error? I had rolled back! This is after I tried running `update`: ``` error This project's package.json defines "packageManager": "yarn@4.3.1". However the current global version of Yarn is 1.22.22. Presence of the "packageManager" field indicates that the project is meant to be used with Corepack, a tool included by default with all official Node.js distributions starting from 16.9 and 14.19. Corepack must currently be enabled by running corepack enable in your terminal. For more information, check out https://yarnpkg.com/corepack. ```
OVERLORD commented 2026-02-04 18:11:24 +03:00
Author
Owner
Copy Link

@infinitytec commented on GitHub (Jan 21, 2025):

Rolled back again.

Ran corepack enable

Then ran update

Looks like it may be working?

@infinitytec commented on GitHub (Jan 21, 2025): Rolled back again. Ran `corepack enable` Then ran `update` Looks like it may be working?
OVERLORD commented 2026-02-04 18:11:26 +03:00
Author
Owner
Copy Link

@infinitytec commented on GitHub (Jan 21, 2025):

OK: good news: it said it updated.
Bad news: I don't seem to be able to get to the page anymore...

@infinitytec commented on GitHub (Jan 21, 2025): OK: good news: it said it updated. Bad news: I don't seem to be able to get to the page anymore...
OVERLORD commented 2026-02-04 18:11:30 +03:00
Author
Owner
Copy Link

@infinitytec commented on GitHub (Jan 21, 2025):

Yeah, it seems that it didn't actually update after that.

@infinitytec commented on GitHub (Jan 21, 2025): Yeah, it seems that it didn't actually update after that.
OVERLORD commented 2026-02-04 18:11:31 +03:00
Author
Owner
Copy Link

@shuperluu commented on GitHub (Jan 22, 2025):

After that error my instance stop being capable to sync and I had to rollback to a backup. Lost a few records, as they were only at the phone, but got it working again.

Does that happen to you also?

@shuperluu commented on GitHub (Jan 22, 2025): After that error my instance stop being capable to sync and I had to rollback to a backup. Lost a few records, as they were only at the phone, but got it working again. Does that happen to you also?
OVERLORD commented 2026-02-04 18:11:35 +03:00
Author
Owner
Copy Link

@infinitytec commented on GitHub (Jan 22, 2025):

After that error my instance stop being capable to sync and I had to rollback to a backup. Lost a few records, as they were only at the phone, but got it working again.

Does that happen to you also?

Yes. The update did not work for me.

@infinitytec commented on GitHub (Jan 22, 2025): > After that error my instance stop being capable to sync and I had to rollback to a backup. Lost a few records, as they were only at the phone, but got it working again. > > Does that happen to you also? Yes. The update did not work for me.
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
question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label
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#356
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?