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

added dispatch functionality for scheduler #1447

Merged
merged 1 commit into from
Aug 22, 2024
Merged

Conversation

sfahad1414
Copy link
Collaborator

@sfahad1414 sfahad1414 commented Aug 22, 2024

Summary by CodeRabbit

  • New Features

    • Introduced a new method for dispatching scheduled events, enhancing event handling capabilities.
    • Added a new API endpoint for triggering scheduled event dispatching.
  • Tests

    • Implemented a new integration test to validate the dispatching of scheduled events through the API.

Copy link

coderabbitai bot commented Aug 22, 2024

Walkthrough

The updates introduce a new dispatch_event method in the KScheduler class to manage job addition events, along with a new API endpoint for triggering these events via a GET request. Additionally, a corresponding integration test is added to validate the dispatching functionality, ensuring proper interaction between components and confirming the success of the API change.

Changes

Files Change Summary
kairon/events/scheduler/kscheduler.py, New method dispatch_event added to handle job events.
kairon/events/server.py New GET endpoint /api/events/dispatch/{event_id} created.
tests/integration_test/event_service_test.py New test test_scheduled_event_request_dispatch added.

Poem

In the garden where events play,
A new dispatcher hops today.
With a flick and a bound,
Jobs take flight, all around,
Making schedules bright, come what may! 🐇✨


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
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>.
    • 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @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 as 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 resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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

@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: 2

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 9675380 and 403ad75.

Files selected for processing (3)
  • kairon/events/scheduler/kscheduler.py (2 hunks)
  • kairon/events/server.py (1 hunks)
  • tests/integration_test/event_service_test.py (2 hunks)
Additional context used
Ruff
kairon/events/server.py

144-144: Do not perform function call Path in argument defaults; instead, perform the call within the function, or read the default from a module-level singleton variable

(B008)

tests/integration_test/event_service_test.py

518-518: f-string without any placeholders

Remove extraneous f prefix

(F541)

Additional comments not posted (4)
kairon/events/scheduler/kscheduler.py (2)

74-76: LGTM! The dispatch_event method is correctly implemented.

The method correctly constructs and dispatches a JobEvent using the provided event_id.


74-76: Verify the use of the protected method _dispatch_event.

Using a protected method like _dispatch_event can be risky as it may change in future versions of the library. Ensure that this is the intended usage and that it won't cause issues with library updates.

Run the following script to verify the usage of _dispatch_event in the codebase:

kairon/events/server.py (1)

143-146: LGTM! The dispatch_scheduled_event endpoint is correctly implemented.

The endpoint correctly invokes the dispatch_event method of KScheduler with the provided event_id.

Tools
Ruff

144-144: Do not perform function call Path in argument defaults; instead, perform the call within the function, or read the default from a module-level singleton variable

(B008)

tests/integration_test/event_service_test.py (1)

516-534: LGTM! The test_scheduled_event_request_dispatch function is correctly implemented.

The test function effectively verifies the dispatching of scheduled events and checks the expected attributes of the dispatched event.

Tools
Ruff

518-518: f-string without any placeholders

Remove extraneous f prefix

(F541)

Comment on lines +143 to +145
@app.get("/api/events/dispatch/{event_id}", response_model=Response)
def dispatch_scheduled_event(event_id: Text = Path(description="Event id")):
KScheduler().dispatch_event(event_id)
Copy link

Choose a reason for hiding this comment

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

Avoid using Path in argument defaults.

The static analysis tool suggests not using Path directly in the argument defaults. Instead, perform the call within the function or use a module-level variable.

Apply this diff to address the issue:

-def dispatch_scheduled_event(event_id: Text = Path(description="Event id")):
+def dispatch_scheduled_event(event_id: Text):
+    event_id = Path(event_id, description="Event id")

Committable suggestion was skipped due to low confidence.

Tools
Ruff

144-144: Do not perform function call Path in argument defaults; instead, perform the call within the function, or read the default from a module-level singleton variable

(B008)

@patch("apscheduler.schedulers.base.BaseScheduler._dispatch_event", autospec=True)
def test_scheduled_event_request_dispatch(mock_dispatch_event):
response = client.get(
f"/api/events/dispatch/test",
Copy link

Choose a reason for hiding this comment

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

Remove the extraneous f prefix from the f-string.

The f-string on line 518 does not contain any placeholders, so the f prefix is unnecessary.

Apply this diff to address the issue:

-        f"/api/events/dispatch/test",
+        "/api/events/dispatch/test",
Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
f"/api/events/dispatch/test",
"/api/events/dispatch/test",
Tools
Ruff

518-518: f-string without any placeholders

Remove extraneous f prefix

(F541)

Copy link
Collaborator

@hiteshghuge hiteshghuge left a comment

Choose a reason for hiding this comment

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

reviewed

@hiteshghuge hiteshghuge merged commit 552f731 into master Aug 22, 2024
8 checks passed
@coderabbitai coderabbitai bot mentioned this pull request Sep 9, 2024
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