github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-06 07:01:45 -05:00
Code Issues 1.5k Packages Projects Releases 54 Wiki Activity

[GH-ISSUE #5729] [Bug]: Fatal error while configuring Spending Analysis widget in Reports #9416

New Issue
Closed
opened 2026-04-10 19:41:18 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-04-10 19:41:18 -05:00
Owner
Copy Link

Originally created by @kcollett on GitHub (Sep 15, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/5729

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

I was trying to configure the Spending Analysis widget in Reports to compare the current month to last January when I got a fatal error. When I show the error, this is the stack trace that is shown:

Error: safeNumber: number is not an integer: null at ODe (https://judicious-polecat.pikapod.net/static/js/index.CR1EQXCX.js:58:90314) at ma (https://judicious-polecat.pikapod.net/static/js/index.CR1EQXCX.js:58:90586) at y9e (https://judicious-polecat.pikapod.net/static/js/index.CR1EQXCX.js:69:295829) at https://judicious-polecat.pikapod.net/static/js/index.CR1EQXCX.js:69:296669 at Bp (https://judicious-polecat.pikapod.net/static/js/ReportRouter.DNxZKHWY.chunk.js:11:148551) at qw (https://judicious-polecat.pikapod.net/static/js/index.CR1EQXCX.js:57:34271) at em (https://judicious-polecat.pikapod.net/static/js/index.CR1EQXCX.js:57:63088) at Hb (https://judicious-polecat.pikapod.net/static/js/index.CR1EQXCX.js:57:73752) at AS (https://judicious-polecat.pikapod.net/static/js/index.CR1EQXCX.js:57:107997) at H_ (https://judicious-polecat.pikapod.net/static/js/index.CR1EQXCX.js:57:107050)

How can we reproduce the issue?

I added a Spending Analysis widget. Then I clicked into the widget to configure it, change the compare to month from August of this year to January of this year.

Where are you hosting Actual?

PikaPods

What browsers are you seeing the problem on?

I'm using Microsoft Edget

Operating System

Windows 11

Originally created by @kcollett on GitHub (Sep 15, 2025). Original GitHub issue: https://github.com/actualbudget/actual/issues/5729 ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? I was trying to configure the Spending Analysis widget in Reports to compare the current month to last January when I got a fatal error. When I show the error, this is the stack trace that is shown: Error: safeNumber: number is not an integer: null at ODe (https://judicious-polecat.pikapod.net/static/js/index.CR1EQXCX.js:58:90314) at ma (https://judicious-polecat.pikapod.net/static/js/index.CR1EQXCX.js:58:90586) at y9e (https://judicious-polecat.pikapod.net/static/js/index.CR1EQXCX.js:69:295829) at https://judicious-polecat.pikapod.net/static/js/index.CR1EQXCX.js:69:296669 at Bp (https://judicious-polecat.pikapod.net/static/js/ReportRouter.DNxZKHWY.chunk.js:11:148551) at qw (https://judicious-polecat.pikapod.net/static/js/index.CR1EQXCX.js:57:34271) at em (https://judicious-polecat.pikapod.net/static/js/index.CR1EQXCX.js:57:63088) at Hb (https://judicious-polecat.pikapod.net/static/js/index.CR1EQXCX.js:57:73752) at AS (https://judicious-polecat.pikapod.net/static/js/index.CR1EQXCX.js:57:107997) at H_ (https://judicious-polecat.pikapod.net/static/js/index.CR1EQXCX.js:57:107050) ### How can we reproduce the issue? I added a Spending Analysis widget. Then I clicked into the widget to configure it, change the compare to month from August of this year to January of this year. ### Where are you hosting Actual? PikaPods ### What browsers are you seeing the problem on? I'm using Microsoft Edget ### Operating System Windows 11
GiteaMirror added the reportsbug labels 2026-04-10 19:41:18 -05:00
GiteaMirror commented 2026-04-10 19:41:19 -05:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Sep 15, 2025):

That sounds like you somehow got a bad value in your database in January. You probably could manually fix it by editing the database if you felt like going that route.

<!-- gh-comment-id:3292663681 --> @youngcw commented on GitHub (Sep 15, 2025): That sounds like you somehow got a bad value in your database in January. You probably could manually fix it by editing the database if you felt like going that route.
GiteaMirror commented 2026-04-10 19:41:20 -05:00
Author
Owner
Copy Link

@kcollett commented on GitHub (Sep 16, 2025):

I see the same problem if I compare to any month that's more than three months back:

September -> August, July, or Jun: works
September -> any earlier month: fatal error

I see the same pattern comparing April to an earlier month; April -> January works, April -> December has the fatal error.

This doesn't seem like bad data in a particular month.

<!-- gh-comment-id:3294480827 --> @kcollett commented on GitHub (Sep 16, 2025): I see the same problem if I compare to any month that's more than three months back: September -> August, July, or Jun: works September -> any earlier month: fatal error I see the same pattern comparing April to an earlier month; April -> January works, April -> December has the fatal error. This doesn't seem like bad data in a particular month.
GiteaMirror commented 2026-04-10 19:41:20 -05:00
Author
Owner
Copy Link

@matt-fidd commented on GitHub (Sep 16, 2025):

@misu-dev this sounds similar to https://github.com/actualbudget/actual/pull/5283#issuecomment-3157169843, would you mind taking a look please?

<!-- gh-comment-id:3294504527 --> @matt-fidd commented on GitHub (Sep 16, 2025): @misu-dev this sounds similar to https://github.com/actualbudget/actual/pull/5283#issuecomment-3157169843, would you mind taking a look please?
GiteaMirror commented 2026-04-10 19:41:21 -05:00
Author
Owner
Copy Link

@unknownuserisknown commented on GitHub (Sep 16, 2025):

I see the same problem if I compare to any month that's more than three months back:

September -> August, July, or Jun: works September -> any earlier month: fatal error

I see the same pattern comparing April to an earlier month; April -> January works, April -> December has the fatal error.

This doesn't seem like bad data in a particular month.

I currently experiencing this same problem.

<!-- gh-comment-id:3294583340 --> @unknownuserisknown commented on GitHub (Sep 16, 2025): > I see the same problem if I compare to any month that's more than three months back: > > September -> August, July, or Jun: works September -> any earlier month: fatal error > > I see the same pattern comparing April to an earlier month; April -> January works, April -> December has the fatal error. > > This doesn't seem like bad data in a particular month. I currently experiencing this same problem.
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 bug reports
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#9416
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?