Skip to content

Conversation

bobcallaway
Copy link
Member

AddLeaf queues the proposed entry for inclusion into the Trillian log, and then polls to see that an inclusion proof exists for that hash. Finally, we need the integration timestamp to pass back along to the client as a timestamp, and the only way to get that value is to fetch the entire entry again. We currently do that by calling GetEntryAndProof, which results in a Trillian having to recompute the inclusion proof (which it's already given us) which is more expensive than just reading the leaf itself using GetLeavesByRange.

This swaps over to the less-complex GetLeavesByRange for a lower overhead implementation with equivalent function.

Signed-off-by: Bob Callaway <bcallaway@google.com>
@bobcallaway bobcallaway requested a review from a team as a code owner August 12, 2025 20:59
Copy link

codecov bot commented Aug 12, 2025

Codecov Report

❌ Patch coverage is 55.81395% with 19 lines in your changes missing coverage. Please review.
✅ Project coverage is 24.85%. Comparing base (488eb97) to head (305122e).
⚠️ Report is 488 commits behind head on main.

Files with missing lines Patch % Lines
pkg/trillianclient/trillian_client.go 55.81% 16 Missing and 3 partials ⚠️
Additional details and impacted files
@@             Coverage Diff             @@
##             main    #2580       +/-   ##
===========================================
- Coverage   66.46%   24.85%   -41.61%     
===========================================
  Files          92      189       +97     
  Lines        9258    24390    +15132     
===========================================
- Hits         6153     6063       -90     
- Misses       2359    17561    +15202     
- Partials      746      766       +20     
Flag Coverage Δ
e2etests 46.65% <55.81%> (-0.91%) ⬇️
unittests 15.96% <0.00%> (-31.73%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Copy link
Contributor

@haydentherapper haydentherapper left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I assume we have sufficient test coverage in the e2e tests?

@bobcallaway
Copy link
Member Author

I assume we have sufficient test coverage in the e2e tests?

yup, this would be covered by all of our existing e2e write tests.

@bobcallaway bobcallaway merged commit 9ea5d3a into sigstore:main Aug 13, 2025
16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants