-
In the event of error occuring during the pipeline, netty catches the exception and logs the error. This works okay for the moment but we probably want to think about:
* error metrics
* ensuring …
-
Should think about errors, their types, where to handle, how to propagate it to user, logs and etc.
-
Hi, it would be useful if some error handling was added in case a PDF fails to parse. I earlier got this error after parsing 1000s of PDFs and had to restart from scratch (not a big deal of course I u…
-
Calling `.next()` multiple times without waiting for each other means we have multiple independent unresolved promises at the same time.
For all the methods in this proposal, but especially for somet…
-
Mattermost user `ali.farooq` from https://community-daily.mattermost.com has requested the following be documented:
```
Maybe this decision is worth documenting in https://developers.mattermost.co…
-
### Prerequisites
- [ ] I have carried out troubleshooting steps and I believe I have found a bug.
- [ ] I have searched for similar bugs in both open and closed issues and cannot find a duplicate…
-
We need a nice way to present errors to the user when something goes wrong.
Here's the full list of fwupd error codes for reference:
```
* @FWUPD_ERROR_INTERNAL: Internal error
* @FWUPD_ERRO…
-
We need to be helpful when things break
-
### [READ] Step 1: Are you in the right place?
* For issues or feature requests related to __the code in this repository__
file a GitHub issue.
* If this is a __feature request__ make s…
-
Libraries, especially messaging, have several subscribe() calls in the state machine. Sometimes, terminal errors from these calls are bypassed to the reactor's default onErrorDropped handlers, which i…