-
**Describe the bug**
When validating an input with an incorrect type we get an `failed to decode json: json: cannot unmarshall...` error instead of a `validation failed` error with a `context` obje…
-
**Please describe the problem you have**
Evaluate whether standardizing on the stretchr/testify framework for unit tests is worth adding as an external dependency.
/cc @jpeach
-
```
03:43:31.629 NOTI minclient:gateway1: Starting graceful shutdown.
03:43:31.630 NOTI minclient:gateway1: Shutdown complete.
03:43:31.630 INFO catshadow: Shutting down now.
fatal error: bad map …
-
There's a good deal of issues related to inconsistencies (e.g: argument ordering in `assert`) and confusing configuration (e.g: `mock.Times(0)` meaning any number of times).
Fixing those would requir…
-
https://github.com/stretchr/testify/issues/1510#issuecomment-1915502355
with configurable fix:
```yml
equal-time:
fix: WithinDuration # or Truncate
```
-
### Description of the bug:
Running individual tests implemented as receiver methods of a struct through Run configurations auto-generated by the Bazel for IntelliJ plugin don't recognize the method…
-
The signature for [`assert.Regexp`](https://pkg.go.dev/github.com/stretchr/testify/assert#Regexp) (and associated methods) is:
```go
func Regexp(t TestingT, rx interface{}, str interface{}, msgAnd…
-
-
**Describe the bug**
When verifying only, it fails with UnexpectedDeviceException.
This happens because testify uses different Contexts to create the customKeys for naming the destination folders:…
-
The genesis bridge, when it goes in, will create a couple of tech debts:
- [ ] messy gerrs package hub used also in dymint
- [ ] duplicated json definitions in rdk and hub
Probably the RDK or t…
danwt updated
2 weeks ago