Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Avoid unnecessary copying when building Merkle trees. #17912

Closed
wants to merge 1 commit into from

Conversation

tjgq
Copy link
Contributor

@tjgq tjgq commented Mar 29, 2023

Instead of accumulating a single set of children in DirectoryTreeBuilder and later splitting it up into file, symlink and subdirectory sets, we can accumulate the latter directly.

@tjgq tjgq force-pushed the merkle-copying branch 4 times, most recently from a8d844b to 0a1e8bc Compare March 29, 2023 11:49
Instead of accumulating a single set of children in DirectoryTreeBuilder and
later splitting it up into file, symlink and subdirectory sets, we can
accumulate the latter directly.
@tjgq tjgq marked this pull request as ready for review March 29, 2023 14:12
@tjgq tjgq requested a review from a team as a code owner March 29, 2023 14:12
@github-actions github-actions bot added awaiting-review PR is awaiting review from an assigned reviewer team-Remote-Exec Issues and PRs for the Execution (Remote) team labels Mar 29, 2023
@coeuvre coeuvre added awaiting-PR-merge PR has been approved by a reviewer and is ready to be merge internally and removed awaiting-review PR is awaiting review from an assigned reviewer labels Mar 29, 2023
@fmeum
Copy link
Collaborator

fmeum commented Mar 29, 2023

@bazel-io flag

@keertk
Copy link
Member

keertk commented Mar 29, 2023

@bazel-io fork 6.2.0

@sgowroji sgowroji removed the awaiting-PR-merge PR has been approved by a reviewer and is ready to be merge internally label Mar 30, 2023
ShreeM01 pushed a commit to ShreeM01/bazel that referenced this pull request Mar 30, 2023
Instead of accumulating a single set of children in DirectoryTreeBuilder and later splitting it up into file, symlink and subdirectory sets, we can accumulate the latter directly.

Closes bazelbuild#17912.

PiperOrigin-RevId: 520585350
Change-Id: I02b26825976c72d59462a66ffd9afaec3d7c4176
ShreeM01 added a commit that referenced this pull request Mar 31, 2023
* Avoid unnecessary copying when building Merkle trees.

Instead of accumulating a single set of children in DirectoryTreeBuilder and later splitting it up into file, symlink and subdirectory sets, we can accumulate the latter directly.

Closes #17912.

PiperOrigin-RevId: 520585350
Change-Id: I02b26825976c72d59462a66ffd9afaec3d7c4176

* Update DirectoryTree.java

* Update DirectoryTree.java

---------

Co-authored-by: Tiago Quelhas <tjgq@google.com>
fweikert pushed a commit to fweikert/bazel that referenced this pull request May 25, 2023
Instead of accumulating a single set of children in DirectoryTreeBuilder and later splitting it up into file, symlink and subdirectory sets, we can accumulate the latter directly.

Closes bazelbuild#17912.

PiperOrigin-RevId: 520585350
Change-Id: I02b26825976c72d59462a66ffd9afaec3d7c4176
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
team-Remote-Exec Issues and PRs for the Execution (Remote) team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants