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

[FEAT]: Improved error msg #62

Open
XuhuiZhou opened this issue Apr 28, 2024 · 4 comments
Open

[FEAT]: Improved error msg #62

XuhuiZhou opened this issue Apr 28, 2024 · 4 comments
Labels
enhancement New feature or request

Comments

@XuhuiZhou
Copy link
Member

Description

We currently have no error msg when

async def agenerate_action(

fails.

I suggest we get rid of the try, except behavior

Additional Information

No response

@XuhuiZhou XuhuiZhou added the enhancement New feature or request label Apr 28, 2024
@ProKil
Copy link
Member

ProKil commented May 15, 2024

Then how should we handle the exception? Can you propose a taxonomy of different kinds of exceptions?

@XuhuiZhou
Copy link
Member Author

async def agenerate(

I think we should really focus on this function instead and give error msg for each step if it fails

@ProKil
Copy link
Member

ProKil commented May 15, 2024

Yeah, so what are the possible errors and how we should deal with each of them?

@ProKil
Copy link
Member

ProKil commented May 15, 2024

For examples, we should deal with parsing errors (not outputting correct schema) and API errors (rate limit, end point not available) differently.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants