FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

sqlite: reject non-positive backup rates by trivikr · Pull Request #64893 · nodejs/node · GitHub

/ node Public

sqlite: reject non-positive backup rates - #64893

Merged
nodejs-github-bot merged 1 commit into
nodejs:mainfrom
trivikr:sqlite-backup-settle-rate-0
Aug 8, 2026
Merged

sqlite: reject non-positive backup rates#64893
nodejs-github-bot merged 1 commit into
nodejs:mainfrom
trivikr:sqlite-backup-settle-rate-0

Conversation

trivikr commented Aug 1, 2026

Copy link
Copy Markdown
Member

Fixes: #64892

Passing a rate of 0 to backup() causes sqlite3_backup_step() to copy no pages. The backup job then continually reschedules itself and the returned promise never settles.

This change requires backup rates to be positive integers to prevent zero-work backup jobs.


Assisted-by: codex:gpt-5.6-sol

Passing a rate of 0 to backup() causes sqlite3_backup_step() to copy
no pages. The backup job then continually reschedules itself and the
returned promise never settles.

Require backup rates to be positive integers to prevent zero-work
backup jobs.

Signed-off-by: Kamat, Trivikram <16024985+trivikr@users.noreply.github.com>
Assisted-by: codex:gpt-5.6-sol

Copy link
Copy Markdown
Collaborator

Review requested:

  • @nodejs/sqlite

nodejs-github-bot added c++ Issues and PRs that require attention from people who are familiar with C++. needs-ci PRs that need a full CI run. sqlite Issues and PRs related to the SQLite subsystem. labels Aug 1, 2026
trivikr added the request-ci Add this label to start a Jenkins CI on a PR. label Aug 1, 2026

codecov Bot commented Aug 1, 2026
edited
Loading

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.15%. Comparing base (8a1ca0f) to head (d666b94).
⚠️ Report is 134 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main   #64893      +/-   ##
==========================================
+ Coverage   90.14%   90.15%   +0.01%     
==========================================
  Files         746      746              
  Lines      242849   242851       +2     
  Branches    45771    45768       -3     
==========================================
+ Hits       218906   218939      +33     
+ Misses      15438    15390      -48     
- Partials     8505     8522      +17     
Files with missing lines Coverage Δ
src/node_sqlite.cc 80.92% <100.00%> (+0.03%) ⬆️

... and 40 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

araujogui 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.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

LGTM

github-actions Bot removed the request-ci Add this label to start a Jenkins CI on a PR. label Aug 2, 2026

This comment was marked as outdated.

Copy link
Copy Markdown
Collaborator

trivikr added the commit-queue Add this label to land a pull request using GitHub Actions. label Aug 8, 2026
nodejs-github-bot removed the commit-queue Add this label to land a pull request using GitHub Actions. label Aug 8, 2026
nodejs-github-bot merged commit f538f11 into nodejs:main Aug 8, 2026
83 checks passed

Copy link
Copy Markdown
Collaborator

Landed in f538f11

aduh95 pushed a commit that referenced this pull request Aug 13, 2026
Passing a rate of 0 to backup() causes sqlite3_backup_step() to copy
no pages. The backup job then continually reschedules itself and the
returned promise never settles.

Require backup rates to be positive integers to prevent zero-work
backup jobs.

Signed-off-by: Kamat, Trivikram <16024985+trivikr@users.noreply.github.com>
Assisted-by: codex:gpt-5.6-sol
PR-URL: #64893
Fixes: #64892
Reviewed-By: James M Snell <jasnell@gmail.com>
trivikr deleted the sqlite-backup-settle-rate-0 branch August 16, 2026 16:01
aduh95 pushed a commit that referenced this pull request Aug 25, 2026
Passing a rate of 0 to backup() causes sqlite3_backup_step() to copy
no pages. The backup job then continually reschedules itself and the
returned promise never settles.

Require backup rates to be positive integers to prevent zero-work
backup jobs.

Signed-off-by: Kamat, Trivikram <16024985+trivikr@users.noreply.github.com>
Assisted-by: codex:gpt-5.6-sol
PR-URL: #64893
Fixes: #64892
Reviewed-By: James M Snell <jasnell@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

c++ Issues and PRs that require attention from people who are familiar with C++. needs-ci PRs that need a full CI run. sqlite Issues and PRs related to the SQLite subsystem.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

sqlite: backup() never settles when rate is 0

4 participants


Back | FazBrowse Home | New Git URL