-
Some production error or deserialization error can be retriable.
The production error handler and the deserialization error handler should handle these errors.
-
**Describe the bug**
Could not parse Sun, Sep 15, 10:00 AM (Exception)
**Steps to Reproduce**
1. Open an instance (tested on my self-hosted and `inv.tux.pizza`. both U.S. servers)
2. S…
-
### Describe the bug
One of the tasks in our pipeline is to create a new variable in a variable group
```
- script: |
az extension add --name azure-devops --allow-preview false
…
-
*Issue migrated from trac ticket # 1770*
**component:** client | **priority:** minor
#### 2018-02-17 07:14:18: antoine created the issue
___
> Follow up from #1769: register a callback function on…
-
The current best solution is:
``` elixir
def handle_message(message)
try do
:a + 1
rescue
e ->
# do soemthing
raise e
end
end
```
@snehaso suggested that we …
-
```
Right now it's up to the callbacks to deal with exceptions. Even with those
which are truly... well.. exceptional. It is pretty common not to handle
exceptions you don't expect to occur. Usually…
-
```
Right now it's up to the callbacks to deal with exceptions. Even with those
which are truly... well.. exceptional. It is pretty common not to handle
exceptions you don't expect to occur. Usually…
-
Today exception handlers spin the DSP and emit an IPC error. We can do better. (pls add other items here)
- [x] Call Zephyr stack and context dump
- [x] Write stack and context to SRAM Window (and…
-
https://github.com/Twingate/kubernetes-operator/pull/397#discussion_r1746313282
Design change for update mutation calls to throw a specific exception when the entity being updated is not found rath…
-
## Summary
Create a "good" (TBD) crash/exception handler for BT5 (or rather for `inject` and `launcher`).
## Detailed description
We have had various bug reports in the past that were just about …
icex2 updated
7 months ago