Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When searching for code, options Match and Fuzzy are switched #30435

Closed
esbennn opened this issue Apr 12, 2024 · 2 comments
Closed

When searching for code, options Match and Fuzzy are switched #30435

esbennn opened this issue Apr 12, 2024 · 2 comments
Labels
issue/needs-feedback For bugs, we need more details. For features, the feature must be described in more detail type/bug

Comments

@esbennn
Copy link

esbennn commented Apr 12, 2024

Description

When searching for code under Explore, selecting Fuzzy as search type performs a matched search, while selecting Matchperforms a fuzzy search.

For example, in my organization, searching for flightcase with Fuzzy yields 3 results, but flightcas yields none.
Searching for flightcase with Match yields 3 results, as does searching for flightcas.

See attached screenshots

Gitea Version

1.21.5

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

Screenshot from 2024-04-04 09-06-22
Screenshot from 2024-04-04 09-06-15
Screenshot from 2024-04-04 09-06-10

Git Version

2.30.2

Operating System

Raspbian GNU/Linux 11 (bullseye)

How are you running Gitea?

Running official arm release with systemd on raspbian

Database

MySQL/MariaDB

@lng2020
Copy link
Member

lng2020 commented Apr 14, 2024

Not sure if it's a bug of 1.21.x, but for 1.22

  1. The default indexer was changed to git grep via Support repo code search without setting up an indexer #29998
  2. Determine fuzziness of bleve indexer by keyword length #29706 is about fixing the fuzziness of the former default indexer bleve.

I haven't tested it so I can't guarantee the result. But it may be fixed.

@lunny lunny added the issue/needs-feedback For bugs, we need more details. For features, the feature must be described in more detail label Apr 14, 2024
@GiteaBot
Copy link
Contributor

We close issues that need feedback from the author if there were no new comments for a month. 🍵

@go-gitea go-gitea locked as resolved and limited conversation to collaborators Aug 12, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/needs-feedback For bugs, we need more details. For features, the feature must be described in more detail type/bug
Projects
None yet
Development

No branches or pull requests

4 participants