Key | Value |
---|---|
FileName | ./usr/share/gocode/src/go.uber.org/zap/stacktrace_ext_test.go |
FileSize | 7546 |
MD5 | 8EA30E498EBCD42DFF1412F72C9A9058 |
SHA-1 | 007D3A5AFAA828DEEF538A1A5F675B751F8EBCC2 |
SHA-256 | 83E0B57F3F185C4CC0FE3BB15C8A43088630FB532E2084920586A1FB66C6184E |
SHA-512 | FB11310B1BAA52A1E429A3861DE9A33020DA1001442C04CAF54F03493D039B5D6C62FD186A3B4BCDDDAA83186BE205F0C032CE215F02907AB7EB08660266343B |
SSDEEP | 192:dwQHNzomirRk67epNmnhOkvZY2SY1BABMWGk9Ft:dwYkrRk6ENmntv+2h1KSWG0t |
TLSH | T1F0F1D984A7DC131F09043264F6459BED7BA6E4D64E25A868F8EDB4CD212C07F43BF661 |
insert-timestamp | 1659226546.7375126 |
mimetype | text/plain |
source | snap:mdTwaNga8m8NrBqqSH4FVIbtUwLWAhWj_15 |
hashlookup:parent-total | 4 |
hashlookup:trust | 70 |
The searched file hash is included in 4 parent files which include package known and seen by metalookup. A sample is included below:
Key | Value |
---|---|
SHA-1 | 03BD1018751C915F71C1E2AE51345C94CA1942ED |
snap-authority | canonical |
snap-filename | mdTwaNga8m8NrBqqSH4FVIbtUwLWAhWj_15.snap |
snap-id | mdTwaNga8m8NrBqqSH4FVIbtUwLWAhWj_15 |
snap-name | axiom |
snap-publisher-id | 1gYihke6YA9pGfV8JRS1Ohe64f0Qs5nG |
snap-signkey | BWDEoaqyr25nF5SNCvEv2v7QnM9QsfCc0PBMYD_i2NGSQ32EF2d4D0hqUel3m8ul |
snap-timestamp | 2021-10-01T17:34:13.464567Z |
source-url | https://api.snapcraft.io/api/v1/snaps/download/mdTwaNga8m8NrBqqSH4FVIbtUwLWAhWj_15.snap |
Key | Value |
---|---|
MD5 | 649BD8D3AD412F6DD0B1D3D684E2A32C |
PackageArch | noarch |
PackageDescription | Package Zap provides fast, structured, leveled logging. For applications that log in the hot path, reflection-based serialization and string formatting are prohibitively expensive - they're CPU-intensive and make many small allocations. Put differently, using json.Marshal and fmt.Fprintf to log tons of interface{} makes your application slow. Zap takes a different approach. It includes a reflection-free, zero-allocation JSON encoder, and the base Logger strives to avoid serialization overhead and allocations wherever possible. By building the high-level SugaredLogger on that foundation, zap lets users choose when they need to count every allocation and when they'd prefer a more familiar, loosely typed API. This package contains the source code needed for building packages that reference the following Go import paths: – go.uber.org/zap |
PackageMaintainer | Fedora Project |
PackageName | golang-uber-zap-devel |
PackageRelease | 2.fc34~bootstrap |
PackageVersion | 1.16.0 |
SHA-1 | 80D16CFC670AB202DFEF8DD8CC523D969EE7AFF4 |
SHA-256 | 84E5783B51661AADD1999AE2EEDEAD23D2562BB15A9FE3FDBEBBAA2E71453458 |
Key | Value |
---|---|
MD5 | 2843D52B720A5785EC1E4D57E0FDC5EC |
PackageArch | noarch |
PackageDescription | Package Zap provides fast, structured, leveled logging. For applications that log in the hot path, reflection-based serialization and string formatting are prohibitively expensive - they're CPU-intensive and make many small allocations. Put differently, using json.Marshal and fmt.Fprintf to log tons of interface{} makes your application slow. Zap takes a different approach. It includes a reflection-free, zero-allocation JSON encoder, and the base Logger strives to avoid serialization overhead and allocations wherever possible. By building the high-level SugaredLogger on that foundation, zap lets users choose when they need to count every allocation and when they'd prefer a more familiar, loosely typed API. This package contains the source code needed for building packages that reference the following Go import paths: – go.uber.org/zap |
PackageMaintainer | pterjan <pterjan> |
PackageName | golang-uber-zap-devel |
PackageRelease | 1.mga8 |
PackageVersion | 1.16.0 |
SHA-1 | 67550E2A2CDC3260BE44D531112828FFB36D3595 |
SHA-256 | FA4B01EA521E2AA3E2F82425F9E81A2DF25168EC4B96D487C31EE2A1287046C7 |
Key | Value |
---|---|
MD5 | 2458C40B8127863CC0B72879B7D4B5E8 |
PackageArch | noarch |
PackageDescription | Package Zap provides fast, structured, leveled logging. For applications that log in the hot path, reflection-based serialization and string formatting are prohibitively expensive - they're CPU-intensive and make many small allocations. Put differently, using json.Marshal and fmt.Fprintf to log tons of interface{} makes your application slow. Zap takes a different approach. It includes a reflection-free, zero-allocation JSON encoder, and the base Logger strives to avoid serialization overhead and allocations wherever possible. By building the high-level SugaredLogger on that foundation, zap lets users choose when they need to count every allocation and when they'd prefer a more familiar, loosely typed API. This package contains the source code needed for building packages that reference the following Go import paths: – go.uber.org/zap |
PackageMaintainer | umeabot <umeabot> |
PackageName | golang-uber-zap-devel |
PackageRelease | 2.mga9 |
PackageVersion | 1.18.1 |
SHA-1 | 11147AE851C6901D835A2C94C47CF524B2F87FA8 |
SHA-256 | F67AE07372C5905A0CEF9018A02E22E0E5779C981F1937C566E37A00B0E9A5BA |