Skip to content
This repository was archived by the owner on Dec 31, 2021. It is now read-only.

Database doesn't unlock when DVCS Error raised #132

Closed
ksurya opened this issue Jul 3, 2013 · 1 comment
Closed

Database doesn't unlock when DVCS Error raised #132

ksurya opened this issue Jul 3, 2013 · 1 comment

Comments

@ksurya
Copy link
Member

ksurya commented Jul 3, 2013

If for some strange reasons, scipy_central.filestorage.dvsc_wrapper.DVCRepo.run_dvcs_command() don't properly execute either by raising exception or does not respond while submitting an entry, submissions are still stored in database! For this we need to have TransactionMiddleware.

But upon adding Transaction Middleware, if DVCS Error is raised, database doesn't get unlocked. The server has to be restarted again..

Update: PostgreSQL seems to handle this database lock! Probably, concurrency problem with Sqlite.
However we need to optimize this feature

@ksurya
Copy link
Member Author

ksurya commented May 13, 2014

This bug does not happen to come back after #168

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant