Skip to content

Conversation

@cfsmp3
Copy link
Contributor

@cfsmp3 cfsmp3 commented Jan 18, 2026

Summary

  • Fix SQLAlchemy 2.0 compatibility issue in install/deploy/pre_deploy.sh
  • The database connection test was using raw SQL strings (conn.execute('SELECT 1')), which is not supported in SQLAlchemy 2.0

Problem

After the SQLAlchemy 2.0 upgrade (commit fb0a5c5 on Jan 4), all deployments have been failing with:

Database connection FAILED: Not an executable object: 'SELECT 1'

This left 6 commits undeployed on the production server, including critical fixes like d316b61 (verify GCP VM creation).

Fix

Use text() wrapper as required by SQLAlchemy 2.0:

from sqlalchemy import create_engine, text
conn.execute(text('SELECT 1'))

Test plan

  • After merging, manually apply the same fix to the server's pre_deploy.sh
  • Trigger deployment via workflow_dispatch
  • Verify deployment succeeds and server is updated to latest master

🤖 Generated with Claude Code

The pre_deploy.sh database connection test was using raw SQL strings
with conn.execute('SELECT 1'), which is not supported in SQLAlchemy 2.0.

This broke all deployments after the SQLAlchemy 2.0 upgrade (commit fb0a5c5),
leaving 6 commits undeployed on the production server.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@cfsmp3 cfsmp3 force-pushed the fix/pre-deploy-sqlalchemy2 branch from 6f1a9ef to 6daad75 Compare January 18, 2026 23:32
@sonarqubecloud
Copy link

@cfsmp3 cfsmp3 merged commit d8436e4 into master Jan 18, 2026
6 checks passed
@cfsmp3 cfsmp3 deleted the fix/pre-deploy-sqlalchemy2 branch January 18, 2026 23:36
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