Identify what's causing SQLite to be in an unwriteable state
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 12
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Why is the SQLite database unwritable on the server? (backend/manual-lookup.sqlite file/directory ownership after the weekly rsync; the generator uses default journal mode, not WAL). Until that is fixed, the manual lookup will simply fall back to the slower filesystem search: correct results, just without the SQLite optimization. Tracked separately.
https://github.com/php/web-php/pull/1969 adds functionality to handle an unwriteable database.
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
Start by examining how the weekly rsync handles backend/manual-lookup.sqlite and how the server sets ownership and write permissions. Check the generator's default journal mode and compare it with the behavior described in PR #1969. Done means identifying the cause of the unwritable state and documenting a reproducible fix without relying on the slower filesystem fallback.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sqlite
- Domain
- databases, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100