nextcloud / nextcloud/serverinfo
Binlog cache spilled to disk
Open
Nobody has claimed this yet.
0. Needs triage
bug
- Dominant language
- JavaScript
- Stars
- 130
- Forks
- 64
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 49
Description
It is already set to 4M.
Seems that DB Doctor cannot see/check that setting?
Contributor guide
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 at the DB Doctor check for the binlog cache setting and reproduce the report shown in the attached image. Trace how the check reads the configured value and make sure it can detect the existing 4M setting; done means DB Doctor reports the setting correctly instead of treating it as unavailable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- databases, observability
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100