nextcloud / nextcloud/fulltextsearch
Warning. Invalid resolution 0 dpi. Using 70 instead.
Open
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 234
- Forks
- 64
- Avg merge
- 6h 18m
- Merged PRs (30d)
- 10
Description
Hello,
since the last update i get the following Message and the indexing Process take days:
Warning. Invalid resolution 0 dpi. Using 70 instead.
Estimating resolution as 516
OSD: Weak margin (4.67) for 70 blob text block, but using orientation anyway: 0
Thx
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 by reproducing the indexing slowdown using the warning text and the reported 0 dpi resolution. Trace the indexing path that emits or handles these messages, then identify the affected component and a testable expected behavior. Done means indexing no longer takes days and invalid resolution handling is covered by verification.
Written by the indexing model from the issue text.
Assessment
- Domain
- search
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100