django db "duplicate column name"

[davidancalagon]

Getting this issue when upgrading to the latest docker image:

2023-02-20 01:39:43.486762+00:00File "/usr/local/lib/python3.9/dist-packages/MySQLdb/connections.py", line 254, in query
2023-02-20 01:39:43.486780+00:00_mysql.connection.query(self, query)
2023-02-20 01:39:43.486796+00:00django.db.utils.OperationalError: (1060, "Duplicate column name 'embed_metadata'")
2023-02-20 01:39:43.654574+00:00s6-rc: warning: unable to start service tubesync-init: command exited 1

Seems to be doing a migration, and fails here every time at connections.py.

Any help is greatly appreciated.

[meeb]

Odd. You can probably just drop the column and restart the container to fix this though. Something like:

ALTER TABLE sync_source DROP COLUMN embed_metadata;

and then immediately restart the container. Note this will reset all your sources to embed_metadata=False, but it should fix the issue you're experiencing.

If more people report this I'll investigate the issue further.

[davidancalagon]

sync_media does not seem to have a column for embed_metadata; however, sync_source does. Dropping embed_metadata fixes that issue, but it then gives the same error regarding embed_thumbnail. Dropping that then causes an error with enable_sponsorblock. Once I drop all three of the aforementioned columns, I get the following:

2023-02-20 02:16:27.559061+00:00File "/usr/local/lib/python3.9/dist-packages/MySQLdb/connections.py", line 254, in query
2023-02-20 02:16:27.559210+00:00_mysql.connection.query(self, query)
2023-02-20 02:16:27.559232+00:00django.db.utils.OperationalError: (1074, "Column length too big for column 'sponsorblock_categories' (max = 255); use BLOB or TEXT instead")
2023-02-20 02:16:27.736331+00:00s6-rc: warning: unable to start service tubesync-init: command exited 1

[meeb]

Ah right you are, sorry I pasted the wrong table name. I've edited the comment. As for the other issue I'll push a fix shortly.

[davidancalagon]

Thanks very much, I appreciate the quick response!

[meeb]

This should be fixed in :latest in 30 minutes or so once the image builds. Please test it then and let me know if this resolves your issue.

[davidancalagon]

Pulled latest, now we have:

2023-02-20 03:40:18.000707+00:00File "/usr/local/lib/python3.9/dist-packages/MySQLdb/connections.py", line 254, in query
2023-02-20 03:40:18.000725+00:00_mysql.connection.query(self, query)
2023-02-20 03:40:18.000741+00:00django.db.utils.OperationalError: (4161, "Unknown data type: 'TextField'")
2023-02-20 03:40:18.174891+00:00s6-rc: warning: unable to start service tubesync-init: command exited 1

[davidkylenz]

I'm seeing the same issue using a mysql container and haven't touch the database schema:
django.db.utils.OperationalError: (1060, "Duplicate column name 'embed_metadata'")

[meeb]

Thanks for the confirmation @davidkylenz .

@davidancalagon Just pushed another tweak, try :latest again once it's built.

[kuhnchris]

Regarding the "duplicate column name" - did you guys use master on bare host or used the :latest docker tag?

[davidancalagon]

I'm using :latest.

[davidancalagon]

It appears the latest push fixed the issue. I thank you for all your hard work.

[meeb]

@kuhnchris I'm guessing this only impacted people who use MySQL as a backend and also updated to the interim :latest between your two PRs being merged? If so this shouldn't impact anyone else.

@davidancalagon @davidkylenz you OK for this to be closed?

[davidancalagon]

Yes, issue fully resolved on this end.

[davidkylenz]

Yep, all good.