maybe it somehow was my fault but i got errors in log
remoteterm-1 | File "/app/.venv/lib/python3.13/site-packages/aiosqlite/core.py", line 223, in execute
remoteterm-1 | cursor = await self._execute(self._conn.execute, sql, parameters)
remoteterm-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
remoteterm-1 | File "/app/.venv/lib/python3.13/site-packages/aiosqlite/core.py", line 160, in _execute
remoteterm-1 | return await future
remoteterm-1 | ^^^^^^^^^^^^
remoteterm-1 | File "/app/.venv/lib/python3.13/site-packages/aiosqlite/core.py", line 63, in _connection_worker_thread
remoteterm-1 | result = function()
remoteterm-1 | sqlite3.OperationalError: no such column: telemetry_routed_hourly
not sure why that happened, looks like migration did not applied, so i go to sqlite3 binary and modified db by myself issuing
ALTER TABLE app_settings ADD COLUMN telemetry_routed_hourly INTEGER DEFAULT 0 as it written in migration scripts. now it's fine.
maybe it somehow was my fault but i got errors in log
remoteterm-1 | File "/app/.venv/lib/python3.13/site-packages/aiosqlite/core.py", line 223, in execute
remoteterm-1 | cursor = await self._execute(self._conn.execute, sql, parameters)
remoteterm-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
remoteterm-1 | File "/app/.venv/lib/python3.13/site-packages/aiosqlite/core.py", line 160, in _execute
remoteterm-1 | return await future
remoteterm-1 | ^^^^^^^^^^^^
remoteterm-1 | File "/app/.venv/lib/python3.13/site-packages/aiosqlite/core.py", line 63, in _connection_worker_thread
remoteterm-1 | result = function()
remoteterm-1 | sqlite3.OperationalError: no such column: telemetry_routed_hourly
not sure why that happened, looks like migration did not applied, so i go to sqlite3 binary and modified db by myself issuing
ALTER TABLE app_settings ADD COLUMN telemetry_routed_hourly INTEGER DEFAULT 0 as it written in migration scripts. now it's fine.
<!-- github-comment-id:4343370264 -->
Hm, our migrations look right. Maybe container startup got cancelled between migrations or had code modified to migrate a different/self-made migration 61, then went back to original code?
Hm, our migrations look right. Maybe container startup got cancelled between migrations or had code modified to migrate a different/self-made migration 61, then went back to original code?
<!-- github-comment-id:4346290708 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
maybe it somehow was my fault but i got errors in log
remoteterm-1 | File "/app/.venv/lib/python3.13/site-packages/aiosqlite/core.py", line 223, in execute
remoteterm-1 | cursor = await self._execute(self._conn.execute, sql, parameters)
remoteterm-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
remoteterm-1 | File "/app/.venv/lib/python3.13/site-packages/aiosqlite/core.py", line 160, in _execute
remoteterm-1 | return await future
remoteterm-1 | ^^^^^^^^^^^^
remoteterm-1 | File "/app/.venv/lib/python3.13/site-packages/aiosqlite/core.py", line 63, in _connection_worker_thread
remoteterm-1 | result = function()
remoteterm-1 | sqlite3.OperationalError: no such column: telemetry_routed_hourly
not sure why that happened, looks like migration did not applied, so i go to sqlite3 binary and modified db by myself issuing
ALTER TABLE app_settings ADD COLUMN telemetry_routed_hourly INTEGER DEFAULT 0 as it written in migration scripts. now it's fine.
Hm, our migrations look right. Maybe container startup got cancelled between migrations or had code modified to migrate a different/self-made migration 61, then went back to original code?
don't know :-/ probably some bad luck, if no one complains then it's only me