Skip to content
This repository was archived by the owner on Jun 5, 2025. It is now read-only.

Handle exceptions in pipeline steps #201

Closed
jhrozek opened this issue Dec 4, 2024 · 1 comment · Fixed by #421
Closed

Handle exceptions in pipeline steps #201

jhrozek opened this issue Dec 4, 2024 · 1 comment · Fixed by #421
Assignees
@yrobla

Comments

@jhrozek
Copy link
Contributor

jhrozek commented Dec 4, 2024

At the moment, any exception in any pipeline step will just raise a 500 from codegate. This is not always desirable.

Ideas on how we could improve:

  • mark steps as critical or non-critical
  • if a non-critical step fails, log or even add a chunk to the context to be displayed to the user in the conversation but proceed.
@lukehinds
Copy link

@lukehinds plan for roadmap

@yrobla yrobla self-assigned this Dec 18, 2024
yrobla added a commit that referenced this issue Dec 19, 2024
@yrobla
fix: wrap provider error codes into HTTP Exceptions
f4280f7 
Different provides answer with different exceptions/error codes
depending on the type of failures. Those can be properly
captured and propagated as well known http exception errors

Partially-closes: #201
@yrobla yrobla mentioned this issue Dec 19, 2024
Merged
yrobla added a commit that referenced this issue Dec 19, 2024
@yrobla
fix: wrap provider error codes into HTTP Exceptions
3c35bb5 
Different provides answer with different exceptions/error codes
depending on the type of failures. Those can be properly
captured and propagated as well known http exception errors

Partially-closes: #201
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@yrobla yrobla

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: wrap provider error codes into HTTP Exceptions stacklok/codegate
3 participants
@jhrozek @yrobla @lukehinds