nextcloud / nextcloud/fulltextsearch
Locking Process: Fail
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 234
- Forks
- 64
- Avg merge
- 6h 18m
- Merged PRs (30d)
- 10
Description
Hi i have the problem that new files arent indexed and i dont know why.
When i run a fulltextsearch:test i get
Testing your current setup:
Creating mocked content provider. ok
Testing mocked provider: get indexable documents. (2 items) ok
Loading search platform. (Elasticsearch) ok
Testing search platform. ok
Locking process fail
In RunningService.php line 86:
Index is already running
When i run a fulltextsearch:reset i get
In RunningService.php line 86:
Index is already running
Dont know whats the point i followed all the instructions imo.
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
Read RunningService.php around line 86 and reproduce the failure with fulltextsearch:test and fulltextsearch:reset. Trace the index-running state involved in both commands; done means the commands no longer report “Index is already running” and new files can be indexed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elasticsearch, php
- Domain
- backend, search
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100