Denis Kovalchuk wrote on Mon, 30 Mar 2020 23:48 +0300: > Speaking of the possible starvations, I would like to note, that since > the current 'build-repcache' implementation uses one SQL transaction > per revision, it seems to me that it should behave similarly to > concurrent commits, where a rep-cache.db is updated in the post commit > processing stage.
Agreed. Cheers, Daniel
