logseq / logseq/db-test

More issues with search

Open
#917 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
28
Forks
2
PR merge metrics
No merged PRs in 30d

Description

### Search first

- [x] I searched and no similar issues were found

### What Happened?

I have some issues with search. In short, sometimes it doesnt find pages. This is not new to my graph, I have had this issue before, however Tienson personally fixed it with [this commit](https://github.com/logseq/logseq/commit/62eac11fe34e71915a19588db04996944c098dbe) (and [this PR](https://github.com/logseq/logseq/pull/12536) fixed some other issues I had with search before that).

This happens in all searches, however its a bit inconsistent, sometimes I find pages by searching for them in Node properties but if I search for the same page in Cmd K it doesnt find it

### Reproduce the Bug

Very specific with some pages

### Expected Behavior

_No response_

### Screenshots

On the first part I try to look up the page for my Mom, but it doesnt find it. Then I try to look for a block with Dan Mclellans Youtube channel in a Node property called "-YTchannel" which is specified to be of type #YTchannel, and yet it doesnt find it in the property, but when I go to the #YTchannel tag and search for Dan Mclellan there, it does find it.

(Sorry for the rather tiny amount of screen Im showing on the video, I couldnt find another quick way to protect my privacy)

https://github.com/user-attachments/assets/3e56ed79-1ef5-437c-9e27-299485215f27

### Files

_No response_

### Browser, Desktop or Mobile Platform Information

_No response_

### Additional Context

_No response_

### Are you willing to submit a PR? If you know how to fix the bug.

- [ ] I'm willing to submit a PR (Thank you!)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the missing results in Cmd K, node properties, and tag search using the page and Dan Mclellan examples from the video. Read the referenced commit 62eac11fe34e71915a19588db04996944c098dbe and PR #12536 for prior search fixes; done means the affected pages and blocks are found consistently across these search paths.

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
Active
Clarity
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.