backport: Don't account for cell dep for MAX_ANCESTORS_COUNT #4330
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What problem does this PR solve?
We met a scenario that a
cell dep
may have many transactions as descendants, and we can not submit a new transaction to consume the dep cell.Problem Summary:
What is changed and how it works?
cell dep
should be handled specially when calculating the entry'sancestors_count
.In this PR, we add a
direct_ancestors_count
to store the directed parent-child relationship between transactions.This is a short-term solution.
What's Changed:
Related changes
owner/repo
:Check List
Tests
Side effects
Release note