Skip to content

Document that a restore ends subscriptions opened before it - #699

Merged
dawsontoth merged 3 commits into
mainfrom
docs/restore-ends-live-subscriptions
Sep 30, 2026
Merged

dawsontoth merged 3 commits into
mainfrom
docs/restore-ends-live-subscriptions

Conversation

@dawsontoth

@dawsontoth dawsontoth commented Sep 29, 2026 •

Copy link
Copy Markdown
Contributor

Documents HarperFast/harper#2914 (for harper#2451): an online restore_backup now ends every subscription to the database that was opened before the restore. When Harper reloads the database, each subscription's last message is a DatabaseGenerationChangedError (status code 409, code DATABASE_GENERATION_CHANGED), and the client resubscribes to resynchronize against the restored state. Before, such a subscription could stall silently, or start receiving the restored database's writes once another subscriber attached. A restore that fails before changing anything reloads the database as it was, and its subscriptions end with the retryable DatabaseClosingError (status code 503, code DATABASE_CLOSING) instead.

The reference says "As of v5.3.0" in plain text, since CONTRIBUTING.md reserves <VersionBadge> for placement after headings. 5.3.0 is still in beta (latest tag v5.3.0-beta.4), and harper#2914 is milestoned v5.3. Merge after harper#2914, which ships the behavior.

Verified with prettier --check on both files and npm run build (no broken links or anchors).

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the documentation to specify that database subscriptions opened before a restore do not carry over to the restored data, updating both the backup operations reference and the v5.3 release notes. The review feedback recommends avoiding the use of the <VersionBadge> component at the start of a paragraph in running prose, suggesting plain text instead.

Comment thread reference/backups/operations.md Outdated
@github-actions
github-actions Bot temporarily deployed to pr-699 September 29, 2026 19:52 Inactive
@github-actions

Copy link
Copy Markdown

🚀 Preview Deployment

Your preview deployment is ready!

🔗 Preview URL: https://preview.harper-documentation.harperfabric.com/pr-699

This preview will update automatically when you push new commits.

…tions with DATABASE_CLOSING

Follows HarperFast/harper#2914's review: a reopen under an unchanged generation now ends the subscriptions from before it with the retryable DatabaseClosingError.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions
github-actions Bot temporarily deployed to pr-699 September 29, 2026 21:29 Inactive
@github-actions

Copy link
Copy Markdown

🚀 Preview Deployment

Your preview deployment is ready!

🔗 Preview URL: https://preview.harper-documentation.harperfabric.com/pr-699

This preview will update automatically when you push new commits.

…he start of a paragraph

CONTRIBUTING.md reserves VersionBadge for standalone placement after headings; the reference pages phrase a mid-section change as "As of vX".

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown

🚀 Preview Deployment

Your preview deployment is ready!

🔗 Preview URL: https://preview.harper-documentation.harperfabric.com/pr-699

This preview will update automatically when you push new commits.

@github-actions
github-actions Bot temporarily deployed to pr-699 September 29, 2026 21:46 Inactive
@dawsontoth
dawsontoth marked this pull request as ready for review September 29, 2026 22:11
@dawsontoth
dawsontoth requested a review from a team as a code owner September 29, 2026 22:11

@cb1kenobi cb1kenobi left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The documentation consistently describes the subscription behavior after successful and unchanged restores. The prior formatting concern was addressed, and no blocking issues remain.

—
Reviewed fd54ac2

@dawsontoth
dawsontoth merged commit 10c0c80 into main Sep 30, 2026
17 checks passed
@dawsontoth
dawsontoth deleted the docs/restore-ends-live-subscriptions branch September 30, 2026 02:09
@github-actions

Copy link
Copy Markdown

🧹 Preview Cleanup

The preview deployment for this PR has been removed.

This branch was previously deployed

1 inactive deployment
pr-699 — fd54ac28 Deployed Sep 29, 2026 by github-actions[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants