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

Repository navigation

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

Handle exceptions in pipeline steps #201

Closed

Assignees

opened

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 commented on Dec 9, 2024
lukehinds
on Dec 9, 2024
@lukehinds plan for roadmap
lukehinds
added
Should-Have
and removed
Should-Have
on Dec 16, 2024
yrobla
self-assigned this
on Dec 18, 2024
yrobla
added 2 commits that reference this issue on Dec 19, 2024
fix: wrap provider error codes into HTTP Exceptions
f4280f7
fix: wrap provider error codes into HTTP Exceptions
3c35bb5
yrobla
closed this as completedin #421 on Dec 19, 2024

to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

yrobla

Labels

No labels

No labels

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests