The bot build ran from master, there is a bug there
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Jun 30 2020
@bot build-ubsan
Can you rename the UBSAN exception accordingly ? See D6784
In D6782#164841, @deadalnix wrote:Think about cleaning up the old activation.
rebase
Think about cleaning up the old activation.
Ok. Seems I was on the right track.
Add missing comment
It gives you how much "space" is taken in term of slots but not allocated to any slot. See https://en.wikipedia.org/wiki/Fragmentation_(computing)
Jun 29 2020
rebase
rebase
rebase
This change seems fine, but there isn't enough info in the summary to get a good picture for why this particular implementation was selected over other possible implementations. Regardless, it appears to do some job and is tested.
What does this fragmentation score give you in the future? It's not clear what this is building towards and the rest of the stack does not clarify in regards to the fragmentation. Since the fragmentation is essentially a loosely-tracked sum of gaps between entries, is it intended as a cleanup trigger once the sum exceeds some threshold? If not, then how will it be used?
added the missing link
sorry about that, fixed now
The description is innacurate
Description is not correct.
[Bot Message]
One or more PR numbers were detected in the summary.
Links to those PRs have been inserted into the summary for reference.
changed library order in CMakeLists.tx
rebased
[Bot Message]
One or more PR numbers were detected in the summary.
Links to those PRs have been inserted into the summary for reference.
[Bot Message]
One or more PR numbers were detected in the summary.
Links to those PRs have been inserted into the summary for reference.
Relayout the usage comment
Rebase
[Bot Message]
One or more PR numbers were detected in the summary.
Links to those PRs have been inserted into the summary for reference.