pony.orm.dbapiprovider.OperationalError: no such column: ChannelNode.num_entries

[sentry-for-tribler]

Sentry Issue: TRIBLER-1HH

CoreCrashedError: The Tribler core has unexpectedly finished with exit code 1 and status: 0.

Error message: Application error
pony.orm.dbapiprovider.OperationalError: no such column: ChannelNode.num_entries[<relief>-core PID:9796] 2024-01-10 17:00:01,239 - ERROR <exception_handler:138> CoreExceptionHandler.unhandled_error_observer(): Call report callback

[qstokkink]

Failing line from Sentry (7.13.1):

tribler/src/tribler/core/components/metadata_store/db/store.py

Lines 228 to 230 in e6d2c58

	self.db.generate_mapping(
	create_tables=create_db, check_tables=check_tables
	) # Must be run out of session scope

Failing line on current main branch (after move refactoring):

tribler/src/tribler/core/components/database/db/store.py

Lines 183 to 185 in 5923954

	self.db.generate_mapping(
	create_tables=create_db, check_tables=check_tables
	) # Must be run out of session scope

[kozlovsky]

The error is from the application tester. If I understand correctly, the error happened the following way: first, tables in the database were created using the main branch (without the num_entries column), and then the repo was switched to the release branch, which expects the num_entries column in the database. In that case, it is not an error; it is just necessary to re-create the database with the correct columns.

But, the num_entries column, while removed from the main branch, is still mentioned in the json2pony_columns dict; it looks like it should be removed.

[sentry-for-tribler]

Sentry issue: TRIBLER-1HR