github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-07-11 11:59:55 -05:00
Code Issues 3.0k Packages Projects Releases 58 Wiki Activity

[GH-ISSUE #2545] [Bug]: Fatal Error coping a report #7961

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

Originally created by @edersong on GitHub (Apr 3, 2024).
Original GitHub issue: https://github.com/actualbudget/actual/issues/2545

Verified issue does not already exist?

  • I have searched and found no existing issue

Is this related to GoCardless, Simplefin or another bank-sync provider?

  • I have checked my server logs and could not see any errors there
  • I will be attaching my server logs to this issue
  • I will be attaching my client-side (browser) logs to this issue
  • I understand that this issue will be automatically closed if insufficient information is provided

What happened?

When coping a report changing date range from last month to this month, Actual Server crashed with the following error:
image

By clicking at Restart app didn't solve.

What error did you receive?

By clicking at the show error button, it reports the following:

RangeError: Invalid time value at ke
 (https://actual.whatever.com/static/js/index.MAk9r4yg.js:114:99862) at sf 
 (https://actual.whatever.com/static/js/ReportRouter.mLx3JUh2.chunk.js:65:32413) at Kx  
 (https://actual.whatever.com/static/js/index.MAk9r4yg.js:56:19539) at gI  
 (https://actual.whatever.com/static/js/index.MAk9r4yg.js:58:44045) at fI  
 (https://actual.whatever.com/static/js/index.MAk9r4yg.js:58:39777) at Q4  
 (https://actual.whatever.com/static/js/index.MAk9r4yg.js:58:39705) at Mh  
 (https://actual.whatever.com/static/js/index.MAk9r4yg.js:58:39557) at L0  
 (https://actual.whatever.com/static/js/index.MAk9r4yg.js:58:35921) at uI  
 (https://actual.whatever.com/static/js/index.MAk9r4yg.js:58:34870) at E  
 (https://actual.whatever.com/static/js/index.MAk9r4yg.js:43:1552)

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Chrome

Operating System

Linux

Originally created by @edersong on GitHub (Apr 3, 2024). Original GitHub issue: https://github.com/actualbudget/actual/issues/2545 ### Verified issue does not already exist? - [X] I have searched and found no existing issue ### Is this related to GoCardless, Simplefin or another bank-sync provider? - [X] I have checked my server logs and could not see any errors there - [ ] I will be attaching my server logs to this issue - [ ] I will be attaching my client-side (browser) logs to this issue - [ ] I understand that this issue will be automatically closed if insufficient information is provided ### What happened? When coping a report changing date range from last month to this month, Actual Server crashed with the following error: ![image](https://github.com/actualbudget/actual/assets/64137913/3ae46243-72d9-4ce8-ac92-bd645b92131c) By clicking at `Restart app` didn't solve. ### What error did you receive? By clicking at the show error button, it reports the following: ``` RangeError: Invalid time value at ke (https://actual.whatever.com/static/js/index.MAk9r4yg.js:114:99862) at sf (https://actual.whatever.com/static/js/ReportRouter.mLx3JUh2.chunk.js:65:32413) at Kx (https://actual.whatever.com/static/js/index.MAk9r4yg.js:56:19539) at gI (https://actual.whatever.com/static/js/index.MAk9r4yg.js:58:44045) at fI (https://actual.whatever.com/static/js/index.MAk9r4yg.js:58:39777) at Q4 (https://actual.whatever.com/static/js/index.MAk9r4yg.js:58:39705) at Mh (https://actual.whatever.com/static/js/index.MAk9r4yg.js:58:39557) at L0 (https://actual.whatever.com/static/js/index.MAk9r4yg.js:58:35921) at uI (https://actual.whatever.com/static/js/index.MAk9r4yg.js:58:34870) at E (https://actual.whatever.com/static/js/index.MAk9r4yg.js:43:1552) ``` ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Chrome ### Operating System Linux
GiteaMirror added the bug label 2026-04-10 18:06:00 -05:00
GiteaMirror commented 2026-04-10 18:06:04 -05:00
Author
Owner
Copy Link

@Sal-Romano commented on GitHub (Apr 5, 2024):

Same issue with the same install/environment parameters listed above. I'm unable to get into the reports tab without it crashing and the last action taken was duplicating a custom report.

<!-- gh-comment-id:2038879085 --> @Sal-Romano commented on GitHub (Apr 5, 2024): Same issue with the same install/environment parameters listed above. I'm unable to get into the reports tab without it crashing and the last action taken was duplicating a custom report.
GiteaMirror commented 2026-04-10 18:06:05 -05:00
Author
Owner
Copy Link

@carkom commented on GitHub (Apr 5, 2024):

Do either of you have reports with "static" dates you've created in the last 2 weeks? If so, delete those reports and remake them after this fix has been merged. #2556

<!-- gh-comment-id:2040473953 --> @carkom commented on GitHub (Apr 5, 2024): Do either of you have reports with "static" dates you've created in the last 2 weeks? If so, delete those reports and remake them after this fix has been merged. #2556
GiteaMirror commented 2026-04-10 18:06:06 -05:00
Author
Owner
Copy Link

@edersong commented on GitHub (Apr 5, 2024):

Yes, I had static date reports from three last months and when I copied last month to create a new one for the current month, it crashed

<!-- gh-comment-id:2040491826 --> @edersong commented on GitHub (Apr 5, 2024): Yes, I had static date reports from three last months and when I copied last month to create a new one for the current month, it crashed
GiteaMirror commented 2026-04-10 18:06:08 -05:00
Author
Owner
Copy Link

@Sal-Romano commented on GitHub (Apr 5, 2024):

I can confirm that the issue occurs when you set the Date Filter to "Static", click "Update report" in the top right, and then refresh the /reports endpoint.

I was able to unbrick my custom reports tab by manually modifying the database. I changed each record in the custom_reports table to have a 0 value in the "date_static" column.

<!-- gh-comment-id:2040533973 --> @Sal-Romano commented on GitHub (Apr 5, 2024): I can confirm that the issue occurs when you set the Date Filter to "Static", click "Update report" in the top right, and then refresh the /reports endpoint. I was able to unbrick my custom reports tab by manually modifying the database. I changed each record in the custom_reports table to have a 0 value in the "date_static" column.
GiteaMirror commented 2026-04-10 18:06:09 -05:00
Author
Owner
Copy Link

@carkom commented on GitHub (Apr 5, 2024):

Anyone else with this issue can go to /reports/custom and choose the offending graph and delete it. No need to edit the db.

<!-- gh-comment-id:2040595311 --> @carkom commented on GitHub (Apr 5, 2024): Anyone else with this issue can go to /reports/custom and choose the offending graph and delete it. No need to edit the db.
GiteaMirror commented 2026-04-10 18:06:10 -05:00
Author
Owner
Copy Link

@carkom commented on GitHub (Apr 6, 2024):

Fixed by #2556

<!-- gh-comment-id:2040898446 --> @carkom commented on GitHub (Apr 6, 2024): Fixed by #2556
GiteaMirror commented 2026-04-10 18:06:12 -05:00
Author
Owner
Copy Link

@edersong commented on GitHub (Apr 6, 2024):

Why it was closed?
I'm not able to go to Reports section since it's crashing when entering, as explained before.
No way to delete report created.

<!-- gh-comment-id:2041065784 --> @edersong commented on GitHub (Apr 6, 2024): Why it was closed? I'm not able to go to Reports section since it's crashing when entering, as explained before. No way to delete report created.
GiteaMirror commented 2026-04-10 18:06:14 -05:00
Author
Owner
Copy Link

@carkom commented on GitHub (Apr 6, 2024):

Why it was closed?
I'm not able to go to Reports section since it's crashing when entering, as explained before.
No way to delete report created.

Don't click the reports link in the sidebar. Type "/reports/custom" on the end of your actual address to access the graphs and delete the offending reports.

Its closed because it's not something we can change from the code. You have a saved report with a bug in it. It's a localized issue.

If that doesn't work then you have to manipulate the sqlite db file (as explained above).

<!-- gh-comment-id:2041074685 --> @carkom commented on GitHub (Apr 6, 2024): > Why it was closed? > I'm not able to go to Reports section since it's crashing when entering, as explained before. > No way to delete report created. Don't click the reports link in the sidebar. Type "/reports/custom" on the end of your actual address to access the graphs and delete the offending reports. Its closed because it's not something we can change from the code. You have a saved report with a bug in it. It's a localized issue. If that doesn't work then you have to manipulate the sqlite db file (as explained above).
GiteaMirror commented 2026-04-10 18:06:15 -05:00
Author
Owner
Copy Link

@edersong commented on GitHub (Apr 6, 2024):

Thank you!!

<!-- gh-comment-id:2041107766 --> @edersong commented on GitHub (Apr 6, 2024): Thank you!!
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
tech-support
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label bug
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#7961
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?