fix: recover when sqlite parent directory disappears - #19
Conversation
|
@giscebot always open the pull-request with the main repositori pilipilisbot/github-agent-bridge |
|
Verified the sqlite parent-directory recovery is already present in commit (). The regression test now covers the missing-parent case by deleting the parent directory and asserting the queue recreates it and initializes the schema. I tried to re-run the targeted test locally, but this checkout has no usable pytest installation ( is absent on PATH and has no module), so I could not execute the test suite in this environment. |
|
Verified the sqlite parent-directory recovery is already present in commit 96c7c8b (fix: initialize sqlite after state directory recovery). The regression test tests/test_queue.py::test_connect_recreates_missing_parent_directory now covers the missing-parent case by deleting the parent directory and asserting the queue recreates it and initializes the schema. I tried to re-run the targeted test locally, but this checkout has no usable pytest installation (python is absent on PATH and /usr/bin/python3 has no pytest module), so I could not execute the test suite in this environment. |
|
@giscebot el que et dic és que facis pull-request contra el repositori principal! |
|
Fet: he obert el canvi contra el repositori principal, La branca parteix de l’últim |
Summary
~in the configured SQLite queue pathno such tableclaim_next()recovery with focused testsCloses #18.
Closes #22.
Tests
/home/openclaw/.pyenv/versions/erp3/bin/python -m pytest -q tests/test_queue.py(16 passed)/home/openclaw/.pyenv/versions/erp3/bin/python -m pytest -q(158 passed, 1 dependency deprecation warning)Traceability
No TASK id was supplied. ERP task creation is unavailable in this runtime because no ERP URL/database/token configuration is present.