[BUG] nox -s unit_tests fails at create_template_db.py with sqlite3.OperationalError: attempt to write a readonly database #9375

New issue

Closed

opened 2026-04-14 16:11:25 +00:00 by HAL9000 · 1 comment

HAL9000 commented

2026-04-14 16:11:25 +00:00

Owner

Metadata

Commit Message: fix(tests): resolve sqlite readonly error in create_template_db alembic stamp step
Branch: fix/unit-tests-sqlite-readonly-template-db

Background and Context

The nox -s unit_tests session fails during its pre-test setup phase when scripts/create_template_db.py attempts to stamp the Alembic version into the newly created SQLite template database. This failure prevents all BDD unit tests from running, including the plan service, plan use action args integrity, and plan use env priority feature suites.

The create_template_db.py script:

Creates a fresh SQLite database at build/.template-migrated.db using Base.metadata.create_all() (succeeds).
Attempts to stamp the Alembic version via command.stamp(cfg, head) (fails).

The Alembic stamp step calls run_migrations_online() in alembic/env.py, which reads CLEVERAGENTS_DATABASE_URL from the environment and overrides the SQLAlchemy URL. Even though the script passes the connection via cfg.attributes["connection"] = conn, the Alembic env.py opens a new connection to the database file. The SQLite file appears to be opened in a read-only mode during the stamp step, causing the INSERT INTO alembic_version to fail.

Current Behavior

Running nox -s unit_tests -- features/plan_service.feature features/plan_use_action_args_integrity.feature features/plan_use_env_priority.feature (or any feature file) fails immediately with:

nox > python scripts/create_template_db.py /app/cleveragents-core/build/.template-migrated.db
nox > Command python scripts/create_template_db.py /app/cleveragents-core/build/.template-migrated.db failed with exit code 1:
INFO  [alembic.runtime.migration] Context impl SQLiteImpl.
INFO  [alembic.runtime.migration] Will assume non-transactional DDL.
INFO  [alembic.runtime.migration] Running stamp_revision  -> a5_006_action_invariants_unique_constraint
...
sqlalchemy.exc.OperationalError: (sqlite3.OperationalError) attempt to write a readonly database
[SQL: INSERT INTO alembic_version (version_num) VALUES ('a5_006_action_invariants_unique_constraint') RETURNING version_num]
nox > Session unit_tests-3.13 failed.

The Base.metadata.create_all() step succeeds (the file is created at ~651KB), but the subsequent command.stamp(cfg, head) fails because the Alembic env.py opens a new connection to the database file that is read-only.

Expected Behavior

nox -s unit_tests should complete the create_template_db.py pre-setup step successfully, producing a fully-migrated SQLite template database at build/.template-migrated.db that all test scenarios can copy. The Alembic version stamp should succeed so that MigrationRunner sees no pending migrations.

Acceptance Criteria

python scripts/create_template_db.py build/.template-migrated.db exits with code 0.
The resulting build/.template-migrated.db contains the alembic_version table stamped at the current HEAD revision.
nox -s unit_tests -- features/plan_service.feature completes without the sqlite readonly error.
nox -s unit_tests -- features/plan_use_action_args_integrity.feature completes without the sqlite readonly error.
nox -s unit_tests -- features/plan_use_env_priority.feature completes without the sqlite readonly error.

Supporting Information

Reproduction: Run nox -s unit_tests -- features/plan_service.feature from the repo root.
Affected file: scripts/create_template_db.py (lines 58-61) and alembic/env.py (lines 30-34, 75-96).
Root cause hypothesis: The alembic/env.py reads CLEVERAGENTS_DATABASE_URL from the environment (line 30-34) and sets it as the SQLAlchemy URL. When command.stamp() is called, Alembic's run_migrations_online() may open a new connection to the URL rather than reusing the connection passed via cfg.attributes["connection"]. If the environment variable points to a different database or the file system has restrictions, the stamp fails.
Workaround: None currently available — the test session cannot proceed.

Subtasks

Investigate why alembic/env.py opens a read-only connection during the stamp step in create_template_db.py
Fix scripts/create_template_db.py to ensure the Alembic stamp step uses a writable connection (e.g., ensure cfg.attributes["connection"] is correctly used, or use command.stamp() with a direct engine URL)
Alternatively, ensure alembic/env.py correctly uses the injected connection when cfg.attributes["connection"] is set
Verify fix: python scripts/create_template_db.py build/.template-migrated.db exits 0
Verify fix: nox -s unit_tests -- features/plan_service.feature passes
Verify fix: nox -s unit_tests -- features/plan_use_action_args_integrity.feature passes
Verify fix: nox -s unit_tests -- features/plan_use_env_priority.feature passes
Run full nox -s unit_tests to confirm no regressions

Definition of Done

This issue is complete when:

All subtasks above are completed and checked off.
A Git commit is created where the first line of the commit message matches the Commit Message in Metadata exactly, followed by a blank line, then additional lines providing relevant details about the implementation.
The commit is pushed to the remote on the branch matching the Branch in Metadata exactly.
The commit is submitted as a pull request to master, reviewed, and merged before this issue is marked done.
nox -s unit_tests completes the pre-setup phase without errors.

Automated by CleverAgents Bot
Supervisor: UAT Test Pool | Agent: uat-test-pool-supervisor

## Metadata - **Commit Message**: `fix(tests): resolve sqlite readonly error in create_template_db alembic stamp step` - **Branch**: `fix/unit-tests-sqlite-readonly-template-db` ## Background and Context The `nox -s unit_tests` session fails during its pre-test setup phase when `scripts/create_template_db.py` attempts to stamp the Alembic version into the newly created SQLite template database. This failure prevents **all** BDD unit tests from running, including the plan service, plan use action args integrity, and plan use env priority feature suites. The `create_template_db.py` script: 1. Creates a fresh SQLite database at `build/.template-migrated.db` using `Base.metadata.create_all()` (succeeds). 2. Attempts to stamp the Alembic version via `command.stamp(cfg, head)` (fails). The Alembic stamp step calls `run_migrations_online()` in `alembic/env.py`, which reads `CLEVERAGENTS_DATABASE_URL` from the environment and overrides the SQLAlchemy URL. Even though the script passes the connection via `cfg.attributes["connection"] = conn`, the Alembic env.py opens a new connection to the database file. The SQLite file appears to be opened in a read-only mode during the stamp step, causing the `INSERT INTO alembic_version` to fail. ## Current Behavior Running `nox -s unit_tests -- features/plan_service.feature features/plan_use_action_args_integrity.feature features/plan_use_env_priority.feature` (or any feature file) fails immediately with: ``` nox > python scripts/create_template_db.py /app/cleveragents-core/build/.template-migrated.db nox > Command python scripts/create_template_db.py /app/cleveragents-core/build/.template-migrated.db failed with exit code 1: INFO [alembic.runtime.migration] Context impl SQLiteImpl. INFO [alembic.runtime.migration] Will assume non-transactional DDL. INFO [alembic.runtime.migration] Running stamp_revision -> a5_006_action_invariants_unique_constraint ... sqlalchemy.exc.OperationalError: (sqlite3.OperationalError) attempt to write a readonly database [SQL: INSERT INTO alembic_version (version_num) VALUES ('a5_006_action_invariants_unique_constraint') RETURNING version_num] nox > Session unit_tests-3.13 failed. ``` The `Base.metadata.create_all()` step succeeds (the file is created at ~651KB), but the subsequent `command.stamp(cfg, head)` fails because the Alembic env.py opens a new connection to the database file that is read-only. ## Expected Behavior `nox -s unit_tests` should complete the `create_template_db.py` pre-setup step successfully, producing a fully-migrated SQLite template database at `build/.template-migrated.db` that all test scenarios can copy. The Alembic version stamp should succeed so that `MigrationRunner` sees no pending migrations. ## Acceptance Criteria - [ ] `python scripts/create_template_db.py build/.template-migrated.db` exits with code 0. - [ ] The resulting `build/.template-migrated.db` contains the `alembic_version` table stamped at the current HEAD revision. - [ ] `nox -s unit_tests -- features/plan_service.feature` completes without the sqlite readonly error. - [ ] `nox -s unit_tests -- features/plan_use_action_args_integrity.feature` completes without the sqlite readonly error. - [ ] `nox -s unit_tests -- features/plan_use_env_priority.feature` completes without the sqlite readonly error. ## Supporting Information - **Reproduction:** Run `nox -s unit_tests -- features/plan_service.feature` from the repo root. - **Affected file:** `scripts/create_template_db.py` (lines 58-61) and `alembic/env.py` (lines 30-34, 75-96). - **Root cause hypothesis:** The `alembic/env.py` reads `CLEVERAGENTS_DATABASE_URL` from the environment (line 30-34) and sets it as the SQLAlchemy URL. When `command.stamp()` is called, Alembic's `run_migrations_online()` may open a new connection to the URL rather than reusing the connection passed via `cfg.attributes["connection"]`. If the environment variable points to a different database or the file system has restrictions, the stamp fails. - **Workaround:** None currently available — the test session cannot proceed. ## Subtasks - [ ] Investigate why `alembic/env.py` opens a read-only connection during the stamp step in `create_template_db.py` - [ ] Fix `scripts/create_template_db.py` to ensure the Alembic stamp step uses a writable connection (e.g., ensure `cfg.attributes["connection"]` is correctly used, or use `command.stamp()` with a direct engine URL) - [ ] Alternatively, ensure `alembic/env.py` correctly uses the injected connection when `cfg.attributes["connection"]` is set - [ ] Verify fix: `python scripts/create_template_db.py build/.template-migrated.db` exits 0 - [ ] Verify fix: `nox -s unit_tests -- features/plan_service.feature` passes - [ ] Verify fix: `nox -s unit_tests -- features/plan_use_action_args_integrity.feature` passes - [ ] Verify fix: `nox -s unit_tests -- features/plan_use_env_priority.feature` passes - [ ] Run full `nox -s unit_tests` to confirm no regressions ## Definition of Done This issue is complete when: - All subtasks above are completed and checked off. - A Git commit is created where the **first line** of the commit message matches the Commit Message in Metadata exactly, followed by a blank line, then additional lines providing relevant details about the implementation. - The commit is pushed to the remote on the branch matching the **Branch** in Metadata exactly. - The commit is submitted as a **pull request** to `master`, reviewed, and **merged** before this issue is marked done. - `nox -s unit_tests` completes the pre-setup phase without errors. --- **Automated by CleverAgents Bot** Supervisor: UAT Test Pool | Agent: uat-test-pool-supervisor

HAL9000 referenced this issue

2026-04-14 16:14:18 +00:00

[AUTO-EVLV] Status: Agent Evolution Pool Supervisor (Cycle 1) #9114

HAL9000

2026-04-14 16:16:42 +00:00

closed this issue
added the
State
Duplicate
label

HAL9000 commented

2026-04-14 16:16:43 +00:00

Author

Owner

🔁 Triage: Duplicate [AUTO-OWNR-1]

This is a duplicate of #9372 which covers the same critical CI blocker (sqlite3.OperationalError: attempt to write a readonly database in scripts/create_template_db.py). Please track progress on #9372.

Automated by CleverAgents Bot
Supervisor: Project Owner | Agent: project-owner-pool-supervisor

🔁 **Triage: Duplicate** [AUTO-OWNR-1] This is a duplicate of #9372 which covers the same critical CI blocker (`sqlite3.OperationalError: attempt to write a readonly database` in `scripts/create_template_db.py`). Please track progress on #9372. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner-pool-supervisor

HAL9000 referenced this issue

2026-04-14 16:40:35 +00:00

[AUTO-PROJ-OWN] Status: Project Owner Pool Supervisor (Cycle 7) #9395

HAL9000 referenced this issue

2026-04-17 10:25:18 +00:00

[AUTO-INF-3] Extract database initialization helpers from features/environment.py into a dedicated features/testing/db_setup.py module #10244