ooni-probe-cli/internal/errorsx
Simone Basso 8174d88bac
refactor(i/errorsx): always use the same error reporting pattern (#478)
For consistency and also because the SafeErrorWrapperBuilder seems
to be the building pattern than the original code assumed.

New code should not use it, but I'd rather keep legacy code consistent
formally and with its own original assumptions.

In particular, it matters that SafeErrorWrapperBuilder assigns the
most relevant operation that failed. We were not doing that when we
were manually creating a new ErrWrapper.

Part of https://github.com/ooni/probe/issues/1591
2021-09-07 17:23:24 +02:00
..
dialer_test.go refactor: split errorsx in good and legacy (#477) 2021-09-07 17:09:30 +02:00
dialer.go refactor(i/errorsx): always use the same error reporting pattern (#478) 2021-09-07 17:23:24 +02:00
errorsx_test.go refactor: split errorsx in good and legacy (#477) 2021-09-07 17:09:30 +02:00
errorsx.go refactor: split errorsx in good and legacy (#477) 2021-09-07 17:09:30 +02:00
integration_test.go refactor: split errorsx in good and legacy (#477) 2021-09-07 17:09:30 +02:00
quic_test.go refactor: split errorsx in good and legacy (#477) 2021-09-07 17:09:30 +02:00
quic.go refactor(i/errorsx): always use the same error reporting pattern (#478) 2021-09-07 17:23:24 +02:00
resolver_test.go refactor: split errorsx in good and legacy (#477) 2021-09-07 17:09:30 +02:00
resolver.go refactor: split errorsx in good and legacy (#477) 2021-09-07 17:09:30 +02:00
tls_test.go refactor: split errorsx in good and legacy (#477) 2021-09-07 17:09:30 +02:00
tls.go refactor: split errorsx in good and legacy (#477) 2021-09-07 17:09:30 +02:00