"'Merge conflict' Status Disappeared from Status Columns"

113 views
Skip to first unread message

Dasari vamshipriya

unread,
Jul 9, 2025, 2:44:56 AMJul 9
to Repo and Gerrit Discussion

We are experiencing an issue where the 'merge conflict' information is visible when opening a change directly, but this information does not appear in the UI views such as the dashboard or search queries. This problem occurs only for a subset of changes that have merge conflicts.

Our setup includes:

  • Gerrit version: 3.4.8

  • Configuration: mergeabilityComputationBehavior=API_REF_UPDATED_AND_CHANGE_REINDEX

We would appreciate any insights or suggestions to resolve why the 'merge conflict' status is missing in these UI contexts despite being present when viewing changes individually.

Dasari vamshipriya

unread,
Jul 15, 2025, 6:43:04 AMJul 15
to Repo and Gerrit Discussion
Hi All,

We have observed that the mergeability status is correctly reported when using the Get Change endpoint of the Gerrit REST API, 

for example:

curl -fsSL https://<gerrit-server>/a/changes/<change-id> | sed 1d | jq '.mergeable' 
false

However, when using the Query Changes endpoint (which is used by the dashboard and search features in the Web UI), the mergeability status is incorrect:

curl -fsSL https://<gerrit-server>/a/changes/?q=<change-id> | sed 1d | jq '.[].mergeable' 
true


Would appreciate any further suggestions or fixes from the community.

Thanks!


Dasari vamshipriya

unread,
Aug 25, 2025, 2:41:18 AM (13 days ago) Aug 25
to Repo and Gerrit Discussion
Hi All,

Can you please share any further suggestions or fixes from the community.


Matthias Sohn

unread,
Aug 25, 2025, 4:17:09 AM (13 days ago) Aug 25
to Dasari vamshipriya, Repo and Gerrit Discussion
On Mon, Aug 25, 2025 at 8:41 AM Dasari vamshipriya <vamshipr...@gmail.com> wrote:
Hi All,

Can you please share any further suggestions or fixes from the community.


On Tuesday, 15 July 2025 at 16:13:04 UTC+5:30 Dasari vamshipriya wrote:
Hi All,

We have observed that the mergeability status is correctly reported when using the Get Change endpoint of the Gerrit REST API, 

for example:

curl -fsSL https://<gerrit-server>/a/changes/<change-id> | sed 1d | jq '.mergeable' 
false

However, when using the Query Changes endpoint (which is used by the dashboard and search features in the Web UI), the mergeability status is incorrect:

curl -fsSL https://<gerrit-server>/a/changes/?q=<change-id> | sed 1d | jq '.[].mergeable' 
true

Did you try to reindex the affected changes ?
Queries are executed against the search indexes not on the primary data stored in git (notedb).
If an index entry is stale the query result might be outdated/wrong. This may happen since indexing 
in Gerrit is typically done asynchronously. 

Would appreciate any further suggestions or fixes from the community.

Thanks!


On Wednesday, 9 July 2025 at 12:14:56 UTC+5:30 Dasari vamshipriya wrote:

We are experiencing an issue where the 'merge conflict' information is visible when opening a change directly, but this information does not appear in the UI views such as the dashboard or search queries. This problem occurs only for a subset of changes that have merge conflicts.

Our setup includes:

  • Gerrit version: 3.4.8


3.4.8 is EOL since Nov 2022
You should consider upgrading to a supported version 3.10.8, 3.11.5 or 3.12.2.
  • Configuration: mergeabilityComputationBehavior=API_REF_UPDATED_AND_CHANGE_REINDEX

We would appreciate any insights or suggestions to resolve why the 'merge conflict' status is missing in these UI contexts despite being present when viewing changes individually.

--
--
To unsubscribe, email repo-discuss...@googlegroups.com
More info at http://groups.google.com/group/repo-discuss?hl=en

---
You received this message because you are subscribed to the Google Groups "Repo and Gerrit Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to repo-discuss...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/repo-discuss/c9ec7e36-8d69-4167-948c-1608caf18745n%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages