Comparing
alextzimas/catch-error-when-unable-to-resolve-suinsdomain
(0dfa82c
) withmain
(7c96149
)0%
- Improvements
- 0
- Regressions
- 0
- Untouched
- 3
- New
- 0
- Dropped
- 0
- Ignored
- 0
Benchmarks
Passed
decompress deflate encoding
portal/common/lib/decompress_data.bench.ts::decompressData::decompress deflate encoding+1%
249.1 µs
247.5 µs
decompress plaintext encoding
portal/common/lib/decompress_data.bench.ts::decompressData::decompress plaintext encoding+1%
16.1 µs
16 µs
decompress gzip encoding
portal/common/lib/decompress_data.bench.ts::decompressData::decompress gzip encoding0%
254.4 µs
254.5 µs
Commits
Click on a commit to change the comparison rangeBase
main
7c96149
0%
fix(common-lib): remove error from subdomainToObjectId
The error from the logger would show up as
something crucial on Sentry, which is not.
Actually this is not even an error, because
the code will always "fail", e.g. return null
for suins domains
0dfa82c
2 months ago
by Tzal3x