mirror of
https://github.com/actualbudget/actual.git
synced 2026-07-15 22:54:03 -05:00
Closed
opened 2026-05-14 04:34:16 -05:00 by GiteaMirror
·
0 comments
No Branch/Tag Specified
master
dependabot/npm_and_yarn/npm_and_yarn-cd62b4b37a
enforce-append-only-migrations-ci
claude/error-codes-worker-boundary-26i5uu
api-browser-custom-data-dir
tabedzki/feat/replacing-month-picker-with-day-picker
delay-initial-sync-until-loaded
jfdoming/mobile-app-build
cross-version-sync-compat
jfdoming/api-tokens-part-1
jfdoming/api-tokens-part-2
jfdoming/api-tokens-part-3
jfdoming/mobile-app-updates
claude/budget-version-migration-compat-151jlr
claude/worker-error-serialization-9iqtl7
claude/react-table-library-research-afx83z
claude/issue-8401-regression-test-9nw9l3
jfdoming/mobile-app-foundation-part-1
jfdoming/mobile-app-scaffold
release
ai-fix-cleanup-def-8290
claude/relaxed-shannon-jusywa
claude/fervent-keller-s6f2fq
claude/determined-feynman-st1y9z
claude/wizardly-einstein-vi2wce
claude/sweet-albattani-7nseio
feat/bank-sync-per-budget-file
claude/affectionate-cannon-y0kc82
claude/dependabot-findings-m9pgmb
claude/mac-app-ios-publish-zjs1lz
claude/vigilant-tesla-aiiyos
depot-migrate-secrets-1781296330308
claude/quirky-cerf-v5qck7
claude/animation-removal-alternative-2etfh1
claude/netlify-preview-comments-consolidate-9XPYa
osc/7391-error-boundaries-reports
claude/pensive-dijkstra-7DYui
claude/server-app-version-mismatch-HTCGv
claude/pr-8027-review-feedback-mELuO
claude/zealous-wozniak-e5pO0
claude/intelligent-heisenberg-BSHJq
claude/translation-download-refactor-jFRsO
claude/mobile-performance-ideas-G9PAO
claude/github-issue-7988-5A5ly
blacksmith-migration-ff70d2d
claude/great-mayer-KRvOk
claude/react-native-ios-compilation-fcJh5
claude/serene-goldberg-58xv0
claude/kind-euler-LVG3K
release-automation/edge-nightly
7710-bundle-migrations
claude/fix-docker-build-error-WMfed
claude/llm-compatible-release-notes-t20Nr
7710-tests-tdd
cursor/transaction-table-rewrite-f077
claude/plan-ci-secure-context-OtEe1
claude/fix-issue-7667-DPXi3
cursor/resolve-pr-7449-ee11
claude/fix-typescript-build-error-JPtZ5
copilot/add-repository-configs-to-packages
worktree-compressed-drifting-ritchie
claude/api-consumer-verification-kfz1K
pr-7454
claude/fix-issue-7410-LLLQ4
revert-7281-generate-icons
react-query-useSchedules
copilot/sub-pr-6140
package-upgrades
v26.7.0
v26.6.0
v26.5.2
v26.5.1
v26.5.0
v26.4.0
v26.3.0
v26.2.1
v26.2.0
v26.1.0
v25.12.0
v25.11.0
v25.10.0
v25.9.0
v25.8.0
v25.7.1
v25.7.0
v25.6.1
v25.6.0
v25.5.0
v25.4.0
v25.3.1
v25.3.0
v25.2.1
v25.2.0
v25.1.0
v24.12.0
v24.11.0
v24.10.1
v24.10.0
v24.9.0
v24.8.0
v24.7.0
v24.6.0
v24.5.0
v24.4.0
v24.3.0
v24.2.0
v24.1.0
v23.12.0
v23.11.0
v23.10.0
v23.9.0
v23.8.1
v23.8.0
v23.7.2
v23.7.1
v23.7.0
v23.6.0
v23.5.0
v23.4.2
v23.4.1
v23.4.0
v23.3.2
v23.3.0
v23.2.9
v23.2.5
v23.1.12
v22.12.9
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
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
Mirrored from GitHub Pull Request
No Label
pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#69681
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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?
📋 Pull Request Information
Original PR: https://github.com/actualbudget/actual/pull/7656
Author: @jfdoming
Created: 4/29/2026
Status: ✅ Merged
Merged: 4/30/2026
Merged by: @jfdoming
Base:
master← Head:jfdoming/sharedworker-resume-split📝 Commits (4)
5dca064[AI] Fix SharedWorker tab resume recoveryb441135[AI] Fix SharedWorker reload readinessd486f40Add release notes964ba5aUpdate packages/desktop-client/src/shared-browser-server-core.ts📊 Changes
4 files changed (+418 additions, -27 deletions)
View changed files
📝
packages/desktop-client/src/browser-preload.js(+63 -9)📝
packages/desktop-client/src/shared-browser-server-core.test.ts(+203 -5)📝
packages/desktop-client/src/shared-browser-server-core.ts(+146 -13)➕
upcoming-release-notes/7656.md(+6 -0)📄 Description
Description
Note: I used AI pretty aggressively for this PR since I wasn't familiar with this part of the codebase. I understand the architecture a bit better now as well as the solution, but very open to input on the PR since the code is not mine.
This PR fixes two bugs with multi-tab coordination that could leave tabs loading forever in certain cases.
First, in Safari, tabs are naturally suspended after a certain amount of time. When a tab is suspended, it is no longer able to keep up with heartbeats to the coordinator, which means it will be removed from the coordinator's internal state. When such a tab resumes, it uses the same
MessagePortit was already assigned, but with no other tabs open, the coordinator wouldn't know which budget the port refers to, leaving the tab waiting forever. (This was the bug found by Claude in the other thread.) Fixed by adding explicit logic for resuming the shared worker connection, and attempting to reattach to the same budget group only if it still exists on the same port.Second, when the leader tab is disconnected, the coordinator will fail the budget over to a new tab. In the specific scenario of a tab reload (encountered a lot during my testing), the failover process and the reloaded-tab reconnection logic occur in close succession, meaning that the reloaded tab would likely be told the backend is ready before the newly-promoted leader actually had a chance to load the budget. This meant that the reloaded tab would likely hang forever due to the connection error. Fixed by delaying the worker connect message until the new leader has actually finished loading.
Related issue(s)
Fixes https://github.com/actualbudget/actual/issues/7598
Testing
Would love some help testing this further! But I tested this in two ways:
(a) I found a process locally with Safari that reproduced the initial issue semi-reliably: I enabled the Safari Debug menu, then toggled "Always Suspend WebProcesses Aggressively" under "Miscellaneous Flags". (Not 100% sure this was necessary.) Then opened a bunch of tabs, unfocused the Actual window, and waited ~5 minutes. Without this PR, that reproduced the linked issue semi-reliably; with this PR, I was no longer able to reproduce.
(b) I opened two tabs next to each other, and tried various combinations of reloading the tabs and making changes. This is how I discovered the second bug, and with this PR I was no longer able to reproduce that bug.
Checklist
Bundle Stats
View detailed bundle stats
desktop-client
Total
Changeset
src/browser-preload.jsView detailed bundle breakdown
Added
No assets were added
Removed
No assets were removed
Bigger
Smaller
No assets were smaller
Unchanged
loot-core
Total
View detailed bundle breakdown
Added
No assets were added
Removed
No assets were removed
Bigger
No assets were bigger
Smaller
No assets were smaller
Unchanged
api
Total
View detailed bundle breakdown
Added
No assets were added
Removed
No assets were removed
Bigger
No assets were bigger
Smaller
No assets were smaller
Unchanged
cli
Total
View detailed bundle breakdown
Added
No assets were added
Removed
No assets were removed
Bigger
No assets were bigger
Smaller
No assets were smaller
Unchanged
crdt
Total
View detailed bundle breakdown
Added
No assets were added
Removed
No assets were removed
Bigger
No assets were bigger
Smaller
No assets were smaller
Unchanged
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.