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

Refactor repositories API #631

Merged
merged 1 commit into from
Nov 20, 2024
Merged

Refactor repositories API #631

merged 1 commit into from
Nov 20, 2024

Conversation

fweikert
Copy link
Member

This commit merges ReleaseRepo with CandidateRepo into a single type called LTSRepo.

  1. The new behavior more closely resembles reality.
  2. It will be much easier to implement N.x version pattern should match release candidates #630.

Progress towards #630.

This commit merges ReleaseRepo with CandidateRepo into a single type called LTSRepo.

1. The new behavior more closely resembles reality.
2. It will be much easier to implement bazelbuild#630.

Progress towards bazelbuild#630.
@meteorcloudy
Copy link
Member

FYI @fmeum

Copy link
Member

@meteorcloudy meteorcloudy left a comment

Choose a reason for hiding this comment

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

Awesome, thanks!!

@fweikert fweikert merged commit e81f342 into bazelbuild:master Nov 20, 2024
2 checks passed
fweikert added a commit to fweikert/bazelisk that referenced this pull request Nov 25, 2024
The refactoring in bazelbuild#631 introduced a performance regression: With latest and last_rc the code traversed *all* GCS buckets for *every* Bazel track.
This commit restores the previous, correct behavior: Traversal will be stopped as soon as a matching version as been found.

Moreover, this commit adds a test to prevent similar problems in the future.

Fixes bazelbuild#640

Drive-by fix: Replaced \"%s\" with %q.
fweikert added a commit to fweikert/bazelisk that referenced this pull request Nov 25, 2024
The refactoring in bazelbuild#631 introduced a performance regression: With latest and last_rc the code traversed *all* GCS buckets for *every* Bazel track.
This commit restores the previous, correct behavior: Traversal will be stopped as soon as a matching version has been found.

Moreover, this commit adds a test to prevent similar problems in the future.

Fixes bazelbuild#640

Drive-by fix: Replaced \"%s\" with %q.
fweikert added a commit to fweikert/bazelisk that referenced this pull request Nov 25, 2024
The refactoring in bazelbuild#631 introduced a severe performance regression: With latest and last_rc the code traversed *all* GCS buckets for *every* Bazel track.
Since we send one HTTP request per bucket, this behavior led to a significant increase in HTTP requests ( >140 instead of 2-3 requests).

This commit restores the previous, correct behavior: Traversal will be stopped as soon as a matching version has been found.

Moreover, this commit adds a test to prevent similar regressions in the future.

Fixes bazelbuild#640

Drive-by fix: Replaced \"%s\" with %q.
fweikert added a commit to fweikert/bazelisk that referenced this pull request Nov 25, 2024
The refactoring in bazelbuild#631 introduced a severe performance regression: With latest and last_rc the code traversed *all* GCS buckets for *every* existing Bazel version.
Since we send one HTTP request per bucket, this behavior led to a significant increase in HTTP requests ( >140 instead of 2-3 requests).

This commit restores the previous, correct behavior: Traversal will be stopped as soon as a matching version has been found.

Moreover, this commit adds a test to prevent similar regressions in the future.

Fixes bazelbuild#640

Drive-by fix: Replaced \"%s\" with %q.
meteorcloudy pushed a commit that referenced this pull request Nov 25, 2024
* Avoid unnecessary HTTP requests for latest/last_rc

The refactoring in #631 introduced a severe performance regression: With latest and last_rc the code traversed *all* GCS buckets for *every* existing Bazel version.
Since we send one HTTP request per bucket, this behavior led to a significant increase in HTTP requests ( >140 instead of 2-3 requests).

This commit restores the previous, correct behavior: Traversal will be stopped as soon as a matching version has been found.

Moreover, this commit adds a test to prevent similar regressions in the future.

Fixes #640

Drive-by fix: Replaced \"%s\" with %q.

* Apply minimal indentation principle
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