@BwL1289 can you check if the original issue (#71521) is still reproducible with recent SQLite versions please

I am experiencing this issue on the latest sqlite version.

Oh, so the original issue still exists, namely, the database is still locked?

Oh, so the original issue still exists, namely, the database is still locked?

For the original issue I opened, that's correct. TLDR: When using the latest version of sqlite, I encounter #143263

Sorry, I meant #71521, not your issue. I want to know whether the issue for which the regression test was added actually appeared again in more recent SQLite versions.

More precisely:

• The regression test is meant to catch the regression in [sqlite3] context manager leaves db locked if commit fails in __exit__ #71521.
• I am changing the regression test now.
• But is [sqlite3] context manager leaves db locked if commit fails in __exit__ #71521 actually correctly caught by that regression test even in modern SQLite? This is my question.

I don't know whether what I'm doing for recent SQLite version is relevant. If the test is not relevant for recent SQLite versions, it doesn't make sense to have it for them so I can put the test behind a guard as well and write a new test for the more recent versions that is closer to the original reproducer of #71521. Because with the relaxed test, AFAICT, we don't catch the "locking" state in the first place, and hence it may be better to have another test.