Mercurial > p > roundup > code
view website/www/code.txt @ 6917:fba76e0bba98
set journal mode to wal when creating db.
Trying to work around sqlite3.OperationalError: disk I/O error
errors in CI that I can't reproduce locally.
Also this allows reads to happen while writes are occurring.
This should permit using the web interface for browsing while
a large write load (e.g. bulk data loading from another tracker)
is happening. Right now autogenerating issues locks up the tracker
for reading with an error that the database is locked.
| author | John Rouillard <rouilj@ieee.org> |
|---|---|
| date | Tue, 06 Sep 2022 11:32:13 -0400 |
| parents | 45e8d10a9609 |
| children | 6f5054751fb6 |
line wrap: on
line source
Code ==== Project history is maintained in `CHANGES.txt <https://sourceforge.net/p/roundup/code/ci/tip/tree/CHANGES.txt>`_ file in code repository of Roundup, which can also be viewed online through SourceForge `web interface <https://sourceforge.net/p/roundup/code/ci/default/tree/>`_. Get sources ----------- Official **read-only access** to Mercurial repository is provided through :: hg clone http://hg.code.sf.net/p/roundup/code roundup **Read/write access** requires SSH password or SSH key authorization (see `SourceForge.net docs for details <https://sourceforge.net/p/forge/documentation/Mercurial/>`_) :: hg clone ssh://USERNAME@hg.code.sf.net/p/roundup/code roundup You also need to be added as a Roundup developer for write access - ask for it on the :doc:`roundup-devel list <contact>`. Run demo -------- Roundup doesn't need any dependencies and works out of the box. Demo is accessible at http://localhost:8917/demo/ by default :: cd roundup python demo.py Execute tests ------------- :: python run_tests.py See repository `README.txt <https://sourceforge.net/p/roundup/code/ci/tip/tree/README.txt>`_ for more info.