github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-03-09 11:42:54 -05:00
Code Issues 250 Packages Projects Releases 53 Wiki Activity

[PR #5303] [MERGED] :electron: Fix early server-started signification message #5867

New Issue
Closed
opened 2026-02-28 21:20:07 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-02-28 21:20:07 -06:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/actualbudget/actual/pull/5303
Author: @MikesGlitch
Created: 7/7/2025
Status: ✅ Merged
Merged: 7/8/2025
Merged by: @MikesGlitch

Base: master ← Head: fix/server-notifying-too-early

📝 Commits (2)

  • 1e0fc5c fix issue where server was telling parent process it was ready but was not finished listening
  • 169bd8a release notes

📊 Changes

3 files changed (+31 additions, -16 deletions)

View changed files

📝 packages/desktop-client/src/components/manager/ConfigServer.tsx (+10 -6)
📝 packages/sync-server/src/app.ts (+15 -10)
➕ upcoming-release-notes/5303.md (+6 -0)

📄 Description

This was causing some flakey behaviour if you were on a slow PC and starting/stopping the server. If the server was slow to finish the listen, it would cause a network error when starting the server.

It's not a very common task which is probably why it hasn't been reported as a bug yet.

🔄 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/5303 **Author:** [@MikesGlitch](https://github.com/MikesGlitch) **Created:** 7/7/2025 **Status:** ✅ Merged **Merged:** 7/8/2025 **Merged by:** [@MikesGlitch](https://github.com/MikesGlitch) **Base:** `master` ← **Head:** `fix/server-notifying-too-early` --- ### 📝 Commits (2) - [`1e0fc5c`](https://github.com/actualbudget/actual/commit/1e0fc5c686759793d5075b799874c7df7e0c6dbf) fix issue where server was telling parent process it was ready but was not finished listening - [`169bd8a`](https://github.com/actualbudget/actual/commit/169bd8a6cb1fe9b33d6046f93ca684ddcc9a0d4d) release notes ### 📊 Changes **3 files changed** (+31 additions, -16 deletions) <details> <summary>View changed files</summary> 📝 `packages/desktop-client/src/components/manager/ConfigServer.tsx` (+10 -6) 📝 `packages/sync-server/src/app.ts` (+15 -10) ➕ `upcoming-release-notes/5303.md` (+6 -0) </details> ### 📄 Description <!-- Thank you for submitting a pull request! Make sure to follow the instructions to write release notes for your PR — it should only take a minute or two: https://github.com/actualbudget/docs#writing-good-release-notes. Try running yarn generate:release-notes *before* pushing your PR for an interactive experience. --> This was causing some flakey behaviour if you were on a slow PC and starting/stopping the server. If the server was slow to finish the `listen`, it would cause a network error when starting the server. It's not a very common task which is probably why it hasn't been reported as a bug yet. --- <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-02-28 21:20:07 -06: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#5867
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?