Skip to content

Conversation

@kumar-zlai
Copy link
Contributor

@kumar-zlai kumar-zlai commented Jan 17, 2025

Summary

Migrated service module to Bazel from sbt.

Checklist

  • Added Unit Tests
  • Covered by existing CI
  • Integration tested
  • Documentation update

Summary by CodeRabbit

  • Build Configuration

    • Added new Bazel targets for Java library and test suite
    • Configured dependencies for library and testing
  • Test Improvements

    • Updated test code to use more concise collection initialization methods
    • Simplified test code structure without changing functionality
  • Dependency Management

    • Added Vert.x Unit testing library version 4.5.10

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jan 17, 2025

Walkthrough

This pull request introduces Bazel build configurations for a Java service, adding library and test suite targets in the service/BUILD.bazel file. The changes modernize the project's build setup by defining clear dependencies and test structures. Additionally, the test code for FetchHandlerTest.java was updated to use more concise collection initialization methods, and a new Vert.x testing dependency was added to the Maven repository.

Changes

File Change Summary
service/BUILD.bazel Added three Bazel targets: lib (Java library), test-lib (test library), and test (test suite)
service/src/test/java/.../FetchHandlerTest.java Modernized collection creation using Map.of() and List.of() methods
tools/build_rules/dependencies/maven_repository.bzl Added Vert.x Unit testing dependency io.vertx:vertx-unit:4.5.10

Possibly related PRs

Suggested reviewers

  • piyush-zlai
  • nikhil-zlai

Poem

🏗️ Bazel builds with grace and might,
Collections crisp, dependencies bright
Testing frameworks now align
Code flows smooth, almost divine
Build system's poetry takes flight! 🚀

Warning

Review ran into problems

🔥 Problems

GitHub Actions: Resource not accessible by integration - https://docs.github.com/rest/actions/workflow-runs#list-workflow-runs-for-a-repository.

Please grant the required permissions to the CodeRabbit GitHub App under the organization or repository settings.


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro (Legacy)

📥 Commits

Reviewing files that changed from the base of the PR and between f9b79d9 and 3099a04.

📒 Files selected for processing (3)
  • service/BUILD.bazel (1 hunks)
  • service/src/test/java/ai/chronon/service/handlers/FetchHandlerTest.java (5 hunks)
  • tools/build_rules/dependencies/maven_repository.bzl (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (3)
  • tools/build_rules/dependencies/maven_repository.bzl
  • service/src/test/java/ai/chronon/service/handlers/FetchHandlerTest.java
  • service/BUILD.bazel

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (4)
service/BUILD.bazel (2)

26-45: Consider standardizing on JUnit 5.

Both JUnit 4 (junit:junit) and 5 (junit-jupiter-api) are included, which may cause confusion.


47-69: Reduce dependency duplication.

Most dependencies are duplicated from test-lib. Consider moving common deps to test-lib.

flink/BUILD.bazel (2)

26-62: Consider organizing test dependencies.

Similar to service/BUILD.bazel, consider moving common test dependencies to a central location.


64-101: Reduce dependency duplication.

Dependencies are duplicated from test-lib. Consider referencing test-lib's deps instead.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro (Legacy)

📥 Commits

Reviewing files that changed from the base of the PR and between d721f23 and f9b79d9.

📒 Files selected for processing (4)
  • flink/BUILD.bazel (1 hunks)
  • service/BUILD.bazel (1 hunks)
  • service/src/test/java/ai/chronon/service/handlers/FetchHandlerTest.java (5 hunks)
  • tools/build_rules/dependencies/maven_repository.bzl (1 hunks)
✅ Files skipped from review due to trivial changes (1)
  • service/src/test/java/ai/chronon/service/handlers/FetchHandlerTest.java
🔇 Additional comments (3)
service/BUILD.bazel (1)

1-24: LGTM! Add tests as mentioned in PR description.

Dependencies and configuration look correct for a Vert.x service.

tools/build_rules/dependencies/maven_repository.bzl (1)

60-68: LGTM! Dependencies are consistent.

Flink and Vert.x versions are aligned across artifacts.

Also applies to: 76-76

flink/BUILD.bazel (1)

1-24: LGTM! Dependencies are well-organized.

Flink streaming and core dependencies are properly configured.

Copy link
Contributor

@nikhil-zlai nikhil-zlai left a comment

Choose a reason for hiding this comment

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

refactor to re-use common array(s) of deps across targets.

put("feature_2", 23.3);
put("feature_3", "USD");
}};
Map<String, Object> featureMap = new HashMap<>(Map.of(
Copy link
Contributor

Choose a reason for hiding this comment

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

nit - just use map.of

Copy link
Contributor Author

Choose a reason for hiding this comment

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

done

add(mockResponse1);
add(mockResponse2);
}};
List<JavaResponse> mockResponseList = new ArrayList<>(List.of(
Copy link
Contributor

Choose a reason for hiding this comment

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

nit - just use list.of

Copy link
Contributor Author

Choose a reason for hiding this comment

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

done

@kumar-zlai
Copy link
Contributor Author

refactor to re-use common array(s) of deps across targets.

done

@kumar-zlai kumar-zlai merged commit 112d41c into main Jan 21, 2025
3 checks passed
@kumar-zlai kumar-zlai deleted the service-bazel-migration branch January 21, 2025 23:43
kumar-zlai added a commit that referenced this pull request Apr 25, 2025
## Summary
Migrated `service` module to Bazel from sbt.

## Checklist
- [ ] Added Unit Tests
- [x] Covered by existing CI
- [ ] Integration tested
- [ ] Documentation update



<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

- **Build Configuration**
	- Added new Bazel targets for Java library and test suite
	- Configured dependencies for library and testing

- **Test Improvements**
- Updated test code to use more concise collection initialization
methods
	- Simplified test code structure without changing functionality

- **Dependency Management**
	- Added Vert.x Unit testing library version 4.5.10
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Co-authored-by: nikhil-zlai <[email protected]>
Co-authored-by: Kumar Teja Chippala <[email protected]>
kumar-zlai added a commit that referenced this pull request Apr 29, 2025
## Summary
Migrated `service` module to Bazel from sbt.

## Checklist
- [ ] Added Unit Tests
- [x] Covered by existing CI
- [ ] Integration tested
- [ ] Documentation update



<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

- **Build Configuration**
	- Added new Bazel targets for Java library and test suite
	- Configured dependencies for library and testing

- **Test Improvements**
- Updated test code to use more concise collection initialization
methods
	- Simplified test code structure without changing functionality

- **Dependency Management**
	- Added Vert.x Unit testing library version 4.5.10
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Co-authored-by: nikhil-zlai <[email protected]>
Co-authored-by: Kumar Teja Chippala <[email protected]>
chewy-zlai pushed a commit that referenced this pull request May 15, 2025
## Summary
Migrated `service` module to Bazel from sbt.

## Checklist
- [ ] Added Unit Tests
- [x] Covered by existing CI
- [ ] Integration tested
- [ ] Documentation update



<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

- **Build Configuration**
	- Added new Bazel targets for Java library and test suite
	- Configured dependencies for library and testing

- **Test Improvements**
- Updated test code to use more concise collection initialization
methods
	- Simplified test code structure without changing functionality

- **Dependency Management**
	- Added Vert.x Unit testing library version 4.5.10
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Co-authored-by: nikhil-zlai <[email protected]>
Co-authored-by: Kumar Teja Chippala <[email protected]>
chewy-zlai pushed a commit that referenced this pull request May 15, 2025
## Summary
Migrated `service` module to Bazel from sbt.

## Checklist
- [ ] Added Unit Tests
- [x] Covered by existing CI
- [ ] Integration tested
- [ ] Documentation update



<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

- **Build Configuration**
	- Added new Bazel targets for Java library and test suite
	- Configured dependencies for library and testing

- **Test Improvements**
- Updated test code to use more concise collection initialization
methods
	- Simplified test code structure without changing functionality

- **Dependency Management**
	- Added Vert.x Unit testing library version 4.5.10
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Co-authored-by: nikhil-zlai <[email protected]>
Co-authored-by: Kumar Teja Chippala <[email protected]>
chewy-zlai pushed a commit that referenced this pull request May 16, 2025
## Summary
Migrated `service` module to Bazel from sbt.

## Cheour clientslist
- [ ] Added Unit Tests
- [x] Covered by existing CI
- [ ] Integration tested
- [ ] Documentation update



<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

- **Build Configuration**
	- Added new Bazel targets for Java library and test suite
	- Configured dependencies for library and testing

- **Test Improvements**
- Updated test code to use more concise collection initialization
methods
	- Simplified test code structure without changing functionality

- **Dependency Management**
	- Added Vert.x Unit testing library version 4.5.10
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Co-authored-by: nikhil-zlai <[email protected]>
Co-authored-by: Kumar Teja Chippala <[email protected]>
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.

4 participants