Bump solid_queue from 1.2.2 to 1.2.4#13
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Conversation
Bumps [solid_queue](https://github.com/rails/solid_queue) from 1.2.2 to 1.2.4. - [Release notes](https://github.com/rails/solid_queue/releases) - [Commits](rails/solid_queue@v1.2.2...v1.2.4) --- updated-dependencies: - dependency-name: solid_queue dependency-version: 1.2.4 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
Author
|
Looks like solid_queue is up-to-date now, so this is no longer needed. |
dkam
added a commit
that referenced
this pull request
Jun 21, 2026
…ctStore active-id (#13) #12 — auto_vacuum=INCREMENTAL never applied on fresh deploys: it can only be set on an empty DB or via VACUUM, but `db:schema:load` marks the enable_incremental_vacuum migration applied without running it, so fresh DBs stayed auto_vacuum=NONE and Maintenance::RetentionJob's `PRAGMA incremental_vacuum` was a silent no-op (files only grow). A connect-time `pragmas: { auto_vacuum: }` doesn't work either — the foreign_keys/journal_mode pragmas read the schema first, after which SQLite ignores the change until a VACUUM (verified). Enforce it in an after_initialize hook that sets the pragma + VACUUMs the two data DBs when the mode isn't already INCREMENTAL: a cheap pragma-check-and-skip thereafter, and an instant VACUUM on the empty DB a fresh deploy produces. database.yml documents why auto_vacuum is intentionally absent. #13 — DictStore.active_id cached the "no active dict" result forever per process: an ingest worker that started before the first dict was promoted kept writing plain-zstd (dict_id NULL) rows until restart, never picking up the dict. Give the active-id cache a 60s TTL so cross-process promotions are picked up without a restart (in-process promotion still calls invalidate_active for an instant swap). Both verified against real data (auto_vacuum=2 on the data DBs after boot, primary untouched; active_id re-reads and returns the promoted id after TTL expiry). Suite green apart from the 4 pre-existing main-branch failures. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.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
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps solid_queue from 1.2.2 to 1.2.4.
Release notes
Sourced from solid_queue's releases.
Commits
c09de47Bump solid_queue to 1.2.44fcd81bFix error class name in README.mdac912ddReducing flakiness oftest/integration/concurrency_controls_test.rb4b6159cIncreaseretention-daysfor failed CI logsa6ac0c6Ensure dispatcher is stopped after assertion1a2e380print warning on startup if path to configuration file does not exist (#661)68d4ebbFix testing against Rails main5c6d4b0Add wrap_in_app_executor in a few necessary places6b36dccBump solid_queue to 1.2.31f45b80Revert "Wrap Supervisor#start and stop with the app executor"Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)