-
Despite the recent backend improvements, the errors are still all over the place. Catching all default errors and throwing custom ones in their place (and creating mappers so the front end gets a desc…
-
The sendEncodedTransaction function’s error handling is incomplete, missing essential fields like name, error code. This omission prevents the isSolanaError check from working as intended, limiting er…
-
### Context
We have a few definitions that are lazily realized when they are actually used (equational theorems, functional induction theorem, the splitter, and there are more to come). For some of…
-
In the case of the sink failing to interact with the API we bail out with an error. This doesn't seem ideal and instead we should probably HANG until the API is back?
-
Steps to reproduce:
1. Enter `addlesson 1 l/Monday 0900-110` or `addlesson 2 l/Sunday 0900-110` in the command box
Expected behaviour:
Error thrown for invalid time formatting
Actual behaviour:
No…
-
Problem:
There is no character limit as to how long the name should be, so even when the name (input) is ridiculously long, the product accepts what is inputted.
Suggestion:
Moving forward, the deve…
-
Not sure if this is the right spot for my request.
**Starting from the following issue:**
We use our own error classes. These have an ID which is a number and a code which is an enumeration.
When…
-
Draft requirement:
`Verify that transient errors are handled with a retry mechanism that includes backoff and jitter, ensuring retries are spaced effectively to prevent overwhelming the system or e…
-
For public visibility, I'm collecting here issues and tweaks relevant to error handling in QCElemental schema models and QCEngine harnesses. No changes for v1; these are for v2. See #323 for v2 plans.…
-
Hi,
We use ripunzip as a crate in our app, and wanted to suggest propagating ripunzip errors using an enum instead of anyhow, it would allow us to handle them and show appropriate error messages to t…