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.

Sign up for GitHub

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

Jump to bottom

Rich errors (retry-able vs fatal) #2530

Open
Tracked by #2442
matt2e opened this issue Aug 28, 2024 · 1 comment
Open
Tracked by #2442

Rich errors (retry-able vs fatal) #2530

matt2e opened this issue Aug 28, 2024 · 1 comment
Assignees
@jonathanj-square
Labels
core The core of FTL

Comments

@matt2e
Copy link
Collaborator

matt2e commented Aug 28, 2024 •
edited by alecthomas
Loading

Use cases:

  • Errors that can be handled properly by other modules
  • Errors that can result in specific error status codes in gRPC, HTTP, etc
  • Erros that define if they can be retried or if there is no use retrying

Design document is here: First-class error types
@matt2e matt2e mentioned this issue Aug 28, 2024
Open
19 tasks
@github-actions github-actions bot added the triage Issue needs triaging label Aug 28, 2024
@matt2e matt2e added core The core of FTL and removed triage Issue needs triaging labels Aug 28, 2024
@matt2e
Copy link
Collaborator Author

matt2e commented Aug 28, 2024 •
edited
Loading

@mistermoe has said this is a blocker for using FSM due to all errors currently being retryable

@ftl-robot ftl-robot mentioned this issue Sep 11, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jonathanj-square jonathanj-square

Labels
core The core of FTL
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@matt2e @jonathanj-square