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

Introduce an error handling strategy #44

Open
schnelle opened this issue Jan 17, 2024 · 2 comments
Open

Introduce an error handling strategy #44

schnelle opened this issue Jan 17, 2024 · 2 comments
Assignees
@schnelle
Labels
architecture document interfaces document

Comments

@schnelle
Copy link
Collaborator

While interacting with services, data providers and IPA providers, errors may occur. The current architecture of interfaces document does not account for these error situations.

Extend the current drafts to also consider errors.
@schnelle schnelle self-assigned this Feb 7, 2024
schnelle added a commit that referenced this issue Mar 11, 2024
@schnelle
issue #44 introduced some first thought of error handling
87f0c19
schnelle added a commit that referenced this issue Mar 22, 2024
@schnelle
issue #44 first draft of showing an error to the user if ChatGPT fails
768f836
schnelle added a commit that referenced this issue Mar 22, 2024
@schnelle
issue #44 added first draft of error messages
409d4be
@schnelle
Copy link
Collaborator Author

Review comments

  • a human-readable error message for logging and debugging should be optional
  • other items should be MUST

@schnelle
Copy link
Collaborator Author

Rewrote bulletet list and allowed for separation of MUST and MAY items.

schnelle added a commit that referenced this issue Jul 18, 2024
@schnelle
issue #44 human readable error message is optional
0320b1f
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@schnelle schnelle

Labels
architecture document interfaces document
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@schnelle