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

Fix bug where /retrieve endpoint returns wrong logIndex across shards #908

Merged
merged 1 commit into from
Jul 7, 2022

Conversation

priyawadhwa
Copy link
Contributor

This was working for get but not retrieve -- updated the code so that they both rely on the same function. This should guarantee the same behavior from both endpoints and make things easier to maintain.

fixes #900

Signed-off-by: Priya Wadhwa priya@chainguard.dev

Summary

Release Note

Documentation

@priyawadhwa priyawadhwa requested a review from a team as a code owner July 6, 2022 15:57
pkg/api/entries.go Outdated Show resolved Hide resolved
Signed-off-by: Priya Wadhwa <priya@chainguard.dev>
@asraa asraa merged commit f986c45 into sigstore:main Jul 7, 2022
@github-actions github-actions bot added this to the v1.0.0 milestone Jul 7, 2022
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.

api/v1/log/entries/retrieve returns incorrect virtual log index for entries in the inactive shard
3 participants