github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-06 20:15:33 -05:00
Code Issues 1.5k Packages Projects Releases 55 Wiki Activity

[PR #1750] [MERGED] [Bug] End of month cleanup error #10990

New Issue
Closed
opened 2026-04-10 20:49:10 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-10 20:49:10 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/actualbudget/actual/pull/1750
Author: @shall0pass
Created: 9/29/2023
Status: ✅ Merged
Merged: 10/6/2023
Merged by: @shall0pass

Base: master ← Head: cleanup_error

📝 Commits (3)

📊 Changes

2 files changed (+10 additions, -0 deletions)

View changed files

📝 packages/loot-core/src/server/budget/cleanup-template.ts (+4 -0)
➕ upcoming-release-notes/1750.md (+6 -0)

📄 Description

This feels like a hack. There's probably a more elegant way to handle this condition. The report is correct in that the carryover isn't created initially. To replicate the error:

  1. Start a fresh budget
  2. Add an account with a starting balance
  3. Add a single transaction and assign a category
  4. DO NOT FILL ANY BUDGET CELLS
  5. Enable goal templates
  6. Run the end of the month cleanup script.

The master branch will show the error that is reported. What I have done here is check for the null value. If a null value is found, set the budget cell to it's current value. By doing this, the database tables get updated and carryover will no longer be reported as null.

https://github.com/actualbudget/actual/issues/1748

🔄 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/actualbudget/actual/pull/1750 **Author:** [@shall0pass](https://github.com/shall0pass) **Created:** 9/29/2023 **Status:** ✅ Merged **Merged:** 10/6/2023 **Merged by:** [@shall0pass](https://github.com/shall0pass) **Base:** `master` ← **Head:** `cleanup_error` --- ### 📝 Commits (3) - [`d9944c4`](https://github.com/actualbudget/actual/commit/d9944c43756609d170931ad4fc991b77a25069c9) check for null carryover - [`743625a`](https://github.com/actualbudget/actual/commit/743625a9a74d86a76cd3e30a5e7c2041398194e9) release note - [`420548a`](https://github.com/actualbudget/actual/commit/420548a0e4b4a3f1a5968c9ebd1e757555d7cb2e) simplify logic ### 📊 Changes **2 files changed** (+10 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `packages/loot-core/src/server/budget/cleanup-template.ts` (+4 -0) ➕ `upcoming-release-notes/1750.md` (+6 -0) </details> ### 📄 Description This feels like a hack. There's probably a more elegant way to handle this condition. The report is correct in that the carryover isn't created initially. To replicate the error: 1. Start a fresh budget 2. Add an account with a starting balance 3. Add a single transaction and assign a category 4. DO NOT FILL ANY BUDGET CELLS 5. Enable goal templates 6. Run the end of the month cleanup script. The master branch will show the error that is reported. What I have done here is check for the null value. If a null value is found, set the budget cell to it's current value. By doing this, the database tables get updated and carryover will no longer be reported as null. https://github.com/actualbudget/actual/issues/1748 --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-10 20:49:10 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
Mirrored from GitHub Pull Request
 regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#10990
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?