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

Use of overly broad exception class complicates error handling #4964

Open
auto-d opened this issue Jan 9, 2025 · 1 comment
Open

Use of overly broad exception class complicates error handling #4964

auto-d opened this issue Jan 9, 2025 · 1 comment

Comments

@auto-d
Copy link

auto-d commented Jan 9, 2025

What I did

Sent a message to an agent before the runtime had actually been created. Caught an Exception object from this line as neither my agent or the runtime had been properly set up.

What I was expecting

A more specific Exception object that I could target to handle this case. I currently need to check for this specific error string to avoid catching every Exception that might by raised by the runtime.

@jackgerrits
Copy link
Member

Can you please provide a code example of what you are describing?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants