Details
-
Suggestion
-
Resolution: Unresolved
-
None
Description
Seems like in confluence-git someone just rewritten the history, master is pointed back to the state from few hours before, several changesets are orphaned now.
Each time incremental scanner runs now I see the following status updates:
2015-12-02 09:22:43,423 DEBUG [11689:StdErrHandler confluence-git ] fisheye RepositoryStatus-setMessage - Status change [confluence-git]: Auto packing the repository for optimum performance. You may also 2015-12-02 09:22:43,424 DEBUG [11689:StdErrHandler confluence-git ] fisheye RepositoryStatus-setMessage - Status change [confluence-git]: run "git gc" manually. See "git help gc" for more information. 2015-12-02 09:22:44,889 DEBUG [11736:StdOutHandler confluence-git ] fisheye RepositoryStatus-setMessage - Status change [confluence-git]: Nothing new to pack. 2015-12-02 09:23:01,106 DEBUG [11689:StdErrHandler confluence-git ] fisheye RepositoryStatus-setMessage - Status change [confluence-git]: warning: There are too many unreachable loose objects; run 'git prune' to remove them.
We'd rather don't want to run gc prune - although the changesets are orphaned, they are indexed, available in activity streams and search results they may also be part of reviews created in the system. Running gc prune would cause the FishEye to stop rendering content source. This is why FE-5664 was done in the past.
Perhaps we should avoid showing those messages as status updates?
