Troubleshooting
Database Lock
By default, LineaPy uses SQLite for artifact store, which keeps the package light and simple. However, SQLite has several limitations, one of which is that it does not support multiple concurrent writes to a database (it will result in a database lock). Such concurrent writes to a database can happen, for instance, when multiple scripts or notebook sessions are running at the same time. If your SQLite is locked, you can unlock it by terminating the exact process locking the file. Specifically, navigate to your home directory and run:
bash
fuser .lineapy/db.sqlite
which will list process ID(s) connecting to the database, like so:
.lineapy/db.sqlite: 78638
You can then terminate the troublesome process(es) with:
bash
kill 78638
which will unlock the database.
Warning
Be cautious about terminating a process as it may result in loss of ongoing work. For instance, if your notebook involved heavy computation and the database got locked while storing the result as an artifact, you may consider storing it in a different form (e.g., a Parquet file) before terminating the notebook's process.
If database locking is a persisting issue in your usage, we recommend you use a more robust database such as PostgreSQL, for which relevant instructions can be found here.
No Attribute Error for black
Lineapy uses the black library to format produced code. Make sure you have the version of black as specified in LineaPy's requirements.txt.