Make bluepymm resistant against db lock

Open
#155 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
databases

Research direction

Start by locating BluePyMM's sqlite3 database access and reproduce the failure by opening the database with the sqlite3 command while BluePyMM is running. Done means BluePyMM remains resistant to the locked database instead of crashing, with the resulting behavior verified against this scenario.

Written by the indexing model from the issue text.

Description

If one opens the sqlite3 db with e.g. the 'sqlite3' command, it locks the db. If bluepymm is running at that point on that db, it crashes.
We should make bluepymm more resistant against a locked db.

Dominant language
Python
Stars
13
Forks
9
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from BlueBrain/BluePyMM

All issues in BlueBrain/BluePyMM

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.