Code search exact makes not exact search 1.23.5

[gomanuke]

Description

Hi, guys. I'm about #33713 again.
1.23.5 is almost perfect in sense of exact searching!
But here You are the simplest file that's searched by pattern 'GetPrev' in exact search.

Test.txt

Should I reindex or make something to correct this?

Gitea Version

1.23.5

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

Debian 12

How are you running Gitea?

Was get binary and installed strictly by GiTea documentation.

Database

MySQL/MariaDB

[lunny]

I don't think you need to reindex since #33713 haven't change the index structure.

[wxiaoguang]

Should I reindex or make something to correct this?

I guess no. There are some unfixable problems in 1.23. A (hopefully) fix is done in main branch (will be 1.24) : Improve issue & code search #33860

If you are interested, you could try to use the nightly build to see whether the new code search works better:

• https://dl.gitea.com/gitea/main-nightly/
• https://hub.docker.com/r/gitea/gitea/tags?name=nightly

[gomanuke]

If you are interested, you could try to use the nightly build to see whether the new code search works better:

Would You clarify where I can get a ready nightly binary to test it? Sorry, I don't have competency to compile it.

[wxiaoguang]

If you are interested, you could try to use the nightly build to see whether the new code search works better:

Would You clarify where I can get a ready nightly binary to test it? Sorry, I don't have competency to compile it.

See the links in #33798 (comment)

• https://dl.gitea.com/gitea/main-nightly/
• https://hub.docker.com/r/gitea/gitea/tags?name=nightly

[gomanuke]

Appreciate for Your efforts, guys.
"Exact" approach definitely differs from "Words" one.

Test.txt

But still returns file (attached) with not exact search 'GetPrev'.

Gitea version 1.24.0+dev-479-g25b6f38865 built with GNU Make 4.3, go1.24.1 : bindata, sqlite, sqlite_unlock_notify

[wxiaoguang]

OK, I think I overall could understand the problem now.

The search result is provided by bleve's tokenizer, so GetPrev and get_prev are all treated as 2 tokens: get and prev.

That's the incorrect change from #22829, let's revert it.

After the fix:

[gomanuke]

Ready to test it! Where binary is? 8)

[wxiaoguang]

No binary yet, need to wait for 2 approvals

[wxiaoguang]

Now the night binaries are ready.

[gomanuke]

Well I've got after upgrading to 1 23 6:

2025/03/25 09:09:19 ...ations/migrations.go:481:Migrate() [F] Migration Error: Your database (migration version: 318) is for a newer Gitea, you can not use the newer dat
abase for this old Gitea release (312).
Gitea will exit to keep your database safe and unchanged. Please use the correct Gitea release, do not change the migration version manually (incorrect manual operation
may lose data).

[gomanuke]

But previous nightly release starts successfully. It seems Your nightly build has a newer DB version than 1 23 6 release.

[lunny]

Uh-oh! Your Gitea instance is now on the main branch.

[gomanuke]

Uh-oh! Your Gitea instance is now on the main branch.

Would You advice what should I do to move on releases? I mean 1 23 6 and further...

[lunny]

I will recommend you follow main branch until 1.24 is released and then follow 1.24. Manually downgrade is dangerous for non developer of Gitea.

[wxiaoguang]

https://docs.gitea.com/installation/upgrade-from-gitea

• Now (2025-03-25) main-nightly is the unreleased 1.24
• 1.23-nightly is for the 1.23.x (the latest stable release)

It's generally safe to use main-nightly (1.24) because many maintainers also use that edge version, any bug could be fixed in first time.