Code search exact makes not exact search

[gomanuke]

Description

Here You are a file that returns by "GetPrev" search string.
IMHO exact searching must not return it.

prompt --application/shared_components/user_interface/shortcuts/ok_to_get_next_prev_pk_value begin -- Manifest -- SHORTCUT: OK_TO_GET_NEXT_PREV_PK_VALUE -- Manifest End wwv_flow_imp.component_begin ( p_version_yyyy_mm_dd=>'2024.05.31' ,p_release=>'24.1.7' ,p_default_workspace_id=>1202104075024633 ,p_default_application_id=>401 ,p_default_id_offset=>8704503425691951 ,p_default_owner=>'OBLAKO_PRINT' ); wwv_flow_imp_shared.create_shortcut( p_id=>wwv_flow_imp.id(26669283042465176847) ,p_shortcut_name=>'OK_TO_GET_NEXT_PREV_PK_VALUE' ,p_shortcut_type=>'TEXT_ESCAPE_JS' ,p_version_scn=>1 ,p_shortcut=>'Are you sure you want to leave this page without saving?' ); wwv_flow_imp.component_end; end; /

Gitea Version

1.23.4

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?

systemctl daemon

Database

MySQL/MariaDB

[wxiaoguang]

@6543 need to remove the "fuzzy"?

[gomanuke]

Exact is by default:

[jpraet]

Possibly resolved by #33628 which restores the search mode for bleve from MatchQuery back to MatchPhraseQuery, as it was in 1.22.

On the main branch though, it is still using MatchQuery, but with #33590 a "literal search mode" was added (by using quotes).

[gomanuke]

Appreciate You for explanation. Using quotes is definitely solution.
Would You clarify about release practice: when we can get binary with #33590 ?

[lunny]

#33628 will be released in v1.23.5 and #33590 will be released in v1.24.0 .