github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-07 04:18:51 -05:00
Code Issues 1.6k Packages Projects Releases 55 Wiki Activity

[GH-ISSUE #1702] [Bug]: Incorrect color for errored bank-sync account #26427

New Issue
Closed
opened 2026-04-18 02:36:11 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-18 02:36:11 -05:00
Owner
Copy Link

Originally created by @MatissJanis on GitHub (Sep 15, 2023).
Original GitHub issue: https://github.com/actualbudget/actual/issues/1702

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

This is a master branch (edge) issue. The tagged release seems to be OK.

Most likely a darkmode regression (cc @carkom)

--

When bank-sync fails the status color currently is white. The failure color should instead be red.

Screenshot 2023-09-15 at 20 10 05

What error did you receive?

No response

Where are you hosting Actual?

None

What browsers are you seeing the problem on?

No response

Operating System

None

Originally created by @MatissJanis on GitHub (Sep 15, 2023). Original GitHub issue: https://github.com/actualbudget/actual/issues/1702 ### Verified issue does not already exist? - [X] I have searched and found no existing issue ### What happened? This is a `master` branch (edge) issue. The tagged release seems to be OK. Most likely a darkmode regression (cc @carkom) -- When bank-sync fails the status color currently is white. The failure color should instead be red. <img width="235" alt="Screenshot 2023-09-15 at 20 10 05" src="https://github.com/actualbudget/actual/assets/886567/eb57cfe7-97b0-4d3d-9e75-9f2f8f534f4b"> ### What error did you receive? _No response_ ### Where are you hosting Actual? None ### What browsers are you seeing the problem on? _No response_ ### Operating System None
GiteaMirror added the regressionbuguser interface labels 2026-04-18 02:36:12 -05:00
GiteaMirror commented 2026-04-18 02:36:15 -05:00
Author
Owner
Copy Link

@carkom commented on GitHub (Sep 15, 2023):

Any idea where this resides?

<!-- gh-comment-id:1721771734 --> @carkom commented on GitHub (Sep 15, 2023): Any idea where this resides?
GiteaMirror commented 2026-04-18 02:36:15 -05:00
Author
Owner
Copy Link

@carkom commented on GitHub (Sep 15, 2023):

I got it. I'll open a PR to fix

<!-- gh-comment-id:1721785460 --> @carkom commented on GitHub (Sep 15, 2023): I got it. I'll open a PR to fix
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 regression user interface
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#26427
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?