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

exception handler draft #1

Draft
wants to merge 14 commits into
base: main
Choose a base branch
from

Conversation

benedikt-bartscher
Copy link
Owner

@benedikt-bartscher benedikt-bartscher commented Feb 19, 2024

No description provided.

Copy link

coderabbitai bot commented Feb 19, 2024

Important

Auto Review Skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository.

To trigger a single review, invoke the @coderabbitai review command.

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-tests 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 tests 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 tests.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

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

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • The JSON schema for the configuration file is available here.
  • 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

Copy link
Owner Author

@benedikt-bartscher benedikt-bartscher left a comment

Choose a reason for hiding this comment

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

Thanks Riyad, you are on the right track!

Btw, this part only takes care of exceptions thrown by event handlers. Client errors like in rx.call_script are still not handled. However, that's not as trivial to implement. If you want to collect some bonus points, also catch those errors and send them back to the backend. If you do not fully understand this, no worries, I am always here to answer all your questions or create an example for you.

reflex/app.py Outdated Show resolved Hide resolved
reflex/state.py Outdated Show resolved Hide resolved
reflex/state.py Outdated Show resolved Hide resolved
reflex/utils/exceptions.py Outdated Show resolved Hide resolved
reflex/state.py Outdated

@classmethod
def _handle_exception(cls, exception):
if cls._exception_handler:
Copy link
Owner Author

Choose a reason for hiding this comment

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

You should add a default exception handler which replicates the old behavior (just print() errors) and drop this check

@benedikt-bartscher
Copy link
Owner Author

Btw @tanvirriyad please also take a look on those failing tests (pre-commit and unit-tests). The benchmarking job is expected to fail

@tanvir-riyad
Copy link

Btw @tanvirriyad please also take a look on those failing tests (pre-commit and unit-tests). The benchmarking job is expected to fail

I looked at pre-commit failure. It happened for some docstring issues. I updated those. One unit test is failing because of return type issues.

@tanvir-riyad
Copy link

Thanks Riyad, you are on the right track!

Btw, this part only takes care of exceptions thrown by event handlers. Client errors like in rx.call_script are still not handled. However, that's not as trivial to implement. If you want to collect some bonus points, also catch those errors and send them back to the backend. If you do not fully understand this, no worries, I am always here to answer all your questions or create an example for you.

I have a small question regarding rx.call_script(). this function executes front-end code, right? when a user writes frontend code, they would be able to pass a custom exception handler as an argument like rx.App()?

@benedikt-bartscher
Copy link
Owner Author

benedikt-bartscher commented Feb 20, 2024

Thanks Riyad, you are on the right track!
Btw, this part only takes care of exceptions thrown by event handlers. Client errors like in rx.call_script are still not handled. However, that's not as trivial to implement. If you want to collect some bonus points, also catch those errors and send them back to the backend. If you do not fully understand this, no worries, I am always here to answer all your questions or create an example for you.

I have a small question regarding rx.call_script(). this function executes front-end code, right? when a user writes frontend code, they would be able to pass a custom exception handler as an argument like rx.App()?

I wanted to review your changes later this evening, but since you seem to be interested in the rx.call_script exception handling, I will give you some hints.
Here are the related reflex docs: https://reflex.dev/docs/api-reference/browser_javascript/#inline-scripts
rx.call_script is used to trigger JavaScript execution from the backend. You can use it in event handlers, reflex then sends the script over websockets to the client and executes it.
That's why your implementation will not work. There are no python exceptions to try/catch, the exceptions happen in the client's browser.

This is an example reflex app which throws such an error in the frontend. You can just run it, open your chrome dev tools and checkout the JS console while pressing the test button.

import reflex as rx


class State(rx.State):
    def test_handler(self):
        print("test_handler called")
        yield rx.call_script("error")


def index() -> rx.Component:
    return rx.button(
        "Test",
        on_click=State.test_handler,  # type: ignore
    )


app = rx.App()
app.add_page(index)

As already mentioned the implementation is not trivial, you would have to send this error to the backend and pass it to the exception handler there.

@@ -668,19 +667,23 @@ def call_script(
callback_kwargs = {
"callback": f"({arg_name}) => queueEvents([{format.format_event(event_spec)}], {constants.CompileVars.SOCKET})"
}
wrapped_code = f"""

This comment was marked as resolved.

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.

3 participants