Pioreactor / Pioreactor/pioreactor
[what happened] UI wasn't connecting to server / "attempt to write a readonly database" in UI logs
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 149
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
I closed the mqtt_to_db_streaming job, and then refreshed the UI, and my API endpoints seemed to be dead. I restarted the server, and still same problem. I noticed that the -wal and -shm files were missing from .pioreactor/storage, and the server doesn't have permission to write to this directory. I had to manually recreate them with the correct permissions.
wal and shm files are deleted when closing the last connection to a database in WAL mode.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the mqtt_to_db_streaming shutdown and UI refresh, then inspect the .pioreactor/storage -wal and -shm lifecycle and the server's write permissions. Done means closing the job and refreshing or restarting the UI no longer leaves the API endpoints unusable or requires manually recreating those files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, sqlite
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100