Skip to content

FIX: Fix HTTP Error 500 for Snapshots Page#26

Merged
zdomke merged 3 commits intomainfrom
zdomke/snapshots-500
Feb 21, 2026
Merged

FIX: Fix HTTP Error 500 for Snapshots Page#26
zdomke merged 3 commits intomainfrom
zdomke/snapshots-500

Conversation

@zdomke
Copy link
Copy Markdown
Contributor

@zdomke zdomke commented Feb 20, 2026

Description

Fix the alembic versioning for changing the snapshot table column 'comment' --> 'description'.

Motivation

Closes #23

@zdomke zdomke self-assigned this Feb 20, 2026
@zdomke
Copy link
Copy Markdown
Contributor Author

zdomke commented Feb 20, 2026

Converting to draft to figure out alembic version naming scheme.

@zdomke zdomke marked this pull request as ready for review February 20, 2026 23:43
@zdomke
Copy link
Copy Markdown
Contributor Author

zdomke commented Feb 20, 2026

For testing:

  1. Bring down your existing backend & volumes
    docker compose down -v
  2. Bring up the backend
    docker compose up -d --build
  3. Upgrade the database with alembic
    docker exec squirrel-api alembic upgrade head
  4. Check alembic version (should be '61476c608fc3')
    docker exec squirrel-api alembic current

@zdomke zdomke force-pushed the zdomke/snapshots-500 branch from cec99c5 to c783ea8 Compare February 20, 2026 23:54
Copy link
Copy Markdown
Collaborator

@YektaY YektaY left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This works for me! thanks!

@zdomke zdomke merged commit 8dee0ed into main Feb 21, 2026
2 checks passed
@shilorigins shilorigins deleted the zdomke/snapshots-500 branch February 27, 2026 18:04
@shilorigins
Copy link
Copy Markdown
Contributor

Trying to upgrade alembic without bringing down the volumes with -v, I got the following error:

INFO  [alembic.runtime.migration] Context impl PostgresqlImpl.
INFO  [alembic.runtime.migration] Will assume transactional DDL.
ERROR [alembic.util.messaging] Can't locate revision identified by '003_perf_indexes'
FAILED: Can't locate revision identified by '003_perf_indexes'

After bringing down the volumes, the commands worked. However, since bringing down the volumes destroys all of their data, we should look into options for running upgrades that preserve db data.

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.

[BUG] - 500 error on snapshot page

3 participants