Project

General

Profile

Actions
Copy link

Bug #5627

open

Immediate re-run of rhodecode-index throws warnings on some repos (and suggests rebuild from scratch)

Added by Russell Warren about 3 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
02.07.2020
Due date:
% Done:

0%

Estimated time:
Sorting:
Commit Number:
Affected Version:

Description

I just ran rhodecode-index for the first time, and it completed successfully. To test how well RhodeCode indexing handles differential additions, I reran the index operation immediately, with no new commits, or any changes to the repos at all.

The second run of rhodecode-index (again, immediately after the first completed) reported several warnings, like the example below:

FETCH     [russ/pqml] repository configuration
FETCH     [russ/pqml] repository configuration [done in: 0.158s]
**** WARNING **** 
indexed commit number 624 is higher that repo `russ/pqml` commit number 587 consider rebuilding index for repo from scratch
**** WARNING **** 

SKIP      [russ/pqml] No new commits detected, skipping index build 
FETCH     [russ/pqml] file tree info (@commit_id: rev:tip:`042d3b61`) [243 done in: 1.419s]
FILES     [russ/pqml] marked for indexing: 0 
FILES     [russ/pqml] marked for re-indexing: 0
FILES     [russ/pqml] marked for removal: 0
PROCESSED [russ/pqml] 30/70 repo process limit:-1

This also happened on several other repos. Why would sync be lost immediately?

No data to display

Actions
Copy link

Also available in: Atom PDF