Update sqlite3 2.0.4 → 2.1.0 (minor)

[depfu]

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ sqlite3 (2.0.4 → 2.1.0) · Repo · Changelog

Release Notes

2.1.0

2.1.0 / 2024-09-24

Ruby

• This release drops support for Ruby 3.0. [#563] @flavorjones

Fork safety improvements

Sqlite itself is not fork-safe. Specifically, writing in a child process to a database connection that was created in the parent process may corrupt the database file. To mitigate this risk, sqlite3-ruby has implemented the following changes:

• All open writable database connections carried across a fork() will immediately be closed in the child process to mitigate the risk of corrupting the database file.
• These connections will be incompletely closed ("discarded") which will result in a one-time memory leak in the child process.

If it's at all possible, we strongly recommend that you close writable database connections in the parent before forking. If absolutely necessary (and you know what you're doing), you may suppress the fork safety warnings by calling SQLite3::ForkSafety.suppress_warnings!.

See the README's "Fork Safety" section and adr/2024-09-fork-safety.md for more information. [#558, #565, #566] @flavorjones

Improved

• Use sqlite3_close_v2 to close databases in a deferred manner if there are unclosed prepared statements. Previously closing a database while statements were open resulted in a BusyException. See https://www.sqlite.org/c3ref/close.html for more context. [#557] @flavorjones
• When setting a Database busy_handler, fire the write barrier to prevent potential crashes during the GC mark phase. [#556] @jhawthorn

Documentation

• The FAQ.md has been updated to fix some inaccuracies. [#562] @rickhull

New Contributors

• @jhawthorn made their first contribution in #556
• @rickhull made their first contribution in #562

Full Changelog: v2.0.4...v2.1.0

---

sha256 checksums:

6ed8c7edce2c4ec432152f548ffc80667bd774870d585bf5634d8e2e085fb70d  sqlite3-2.1.0-aarch64-linux-gnu.gem
b8330e67696ae9294b6e5da0d7ceb4e33e46462e1911b79fdf81eb20aa6f0dc7  sqlite3-2.1.0-aarch64-linux-musl.gem
577636e21e7373546f2f2e526316a53ed0ee0eeaa10960647e26479d1ebb49b9  sqlite3-2.1.0-arm64-darwin.gem
7bad1c60fd4e46c4c941bfc4d12c59254a9715b289655a606880e471e829c74c  sqlite3-2.1.0-arm-linux-gnu.gem
42ec543f593e0b3ddb5a944e15ede59dea3cc35acb27639e67bc6f819b1b5bcc  sqlite3-2.1.0-arm-linux-musl.gem
aea47c58078c274ca83195ce1686ee22c4641eb60ccab12918500e78c4babb4f  sqlite3-2.1.0.gem
0c7505899d8754c4cd73b02f0aec88028a0f282cdb426f3b2e5fa2c9dafd0dce  sqlite3-2.1.0-x64-mingw-ucrt.gem
e2be8fad85b6aee16f83baad378b3b3ab992c904e98592cccfd845ad56f4da1f  sqlite3-2.1.0-x86_64-darwin.gem
8993191e8304386d6a9bd76fe9ed161f323ddf857cc06f7f77a31e8b6ccb4d34  sqlite3-2.1.0-x86_64-linux-gnu.gem
cd6b7e6701b1110f033d3dbd156ac19bca011ed4e976c7897b402d578720b9c3  sqlite3-2.1.0-x86_64-linux-musl.gem
1a092fbe4b6cbf20bbeec239c95b8b9caa0d9faa0ad2431fa46ababcd3d91718  sqlite3-2.1.0-x86-linux-gnu.gem
ea377977a07031a6215a2d5ed1e0bd7fb77da0cbbca1af145533b10e0e11bc02  sqlite3-2.1.0-x86-linux-musl.gem

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 34 commits:

• version bump to v2.1.0
• version bump to v2.1.0.rc3
• Merge pull request #566 from sparklemotion/flavorjones-suppress-fork-warnings
• feat: SQLite3::ForkSafety.suppress_warnings!
• version bump to v2.1.0.rc2
• Merge pull request #565 from sparklemotion/flavorjones-optimize-discarded-db-check
• Optimize the statement check for a non-discarded database
• doc: update garbage collection description
• version bump to v2.1.0.rc1
• doc: add a note to CONTRIBUTING.md about the /adr dir
• Drop support for Ruby 3.0 (#563)
• Update FAQ.md (#562)
• Merge pull request #558 from sparklemotion/flavorjones-implement-discard
• Simplify discard tests
• Clean up docs, move discard tests to their own file
• Statements attached to a discarded db raise an exception
• Move the discard warning into ForkSafety
• SQLite::ForkSafety collection is thread-safe
• Automatically close any open writable connections after a fork.
• Call sqlite3_db_release_memory when we discard a connection.
• Make sure we close all database file descriptors.
• Database connections carried across fork() will not be fully closed
• dev: fixup .editorconfig
• Merge pull request #560 from sparklemotion/flavorjones-test-fixup
• test: unskip float test for issue fixed in 3.43.1
• test: use assert_nothing_raised
• doc: update CHANGELOG
• Merge pull request #557 from sparklemotion/flavorjones-use-close-v2
• Use sqlite3_close_v2 to close databases.
• Merge pull request #556 from jhawthorn/fix_write_barrier
• Remove @busy_handler = nil
• Use write barrier when setting busy_handler
• Merge pull request #555 from sparklemotion/dependabot/bundler/minitest-5.25.1
• build(deps-dev): update minitest requirement from 5.24.1 to 5.25.1

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)