golang-go.uber-zap 1.20.0-1 source package in Ubuntu
Changelog
golang-go.uber-zap (1.20.0-1) unstable; urgency=medium
[ Nobuhiro Iwamatsu ]
* Team upload.
* New upstream release (1.20.0).
* Update d/control.
- Add golang-github-benbjohnson-clock-dev to Depends and B-D.
- Add golang-uber-goleak-dev to Depends and B-D.
- Update Standards-Version to 4.6.0.1 (no changes).
- Add golang-gopkg-yaml.v2-dev to B-D and Depends.
- Add golang-google-grpc-dev to B-D.
* Update d/gbp.conf.
- Set debian-branch to debian/sid for DEP-14 conformance.
* Remove unnecessary d/lintian-overrides.
* Update d/watch
- Update to version 4.
-- Nobuhiro Iwamatsu <email address hidden> Mon, 07 Feb 2022 17:59:58 +0900
Upload details
- Uploaded by:
- Debian Go Packaging Team
- Uploaded to:
- Sid
- Original maintainer:
- Debian Go Packaging Team
- Architectures:
- all
- Section:
- golang
- Urgency:
- Medium Urgency
See full publishing history Publishing
| Series | Published | Component | Section | |
|---|---|---|---|---|
| Kinetic | release | universe | misc | |
| Jammy | release | universe | misc |
Downloads
| File | Size | SHA-256 Checksum |
|---|---|---|
| golang-go.uber-zap_1.20.0-1.dsc | 2.3 KiB | 27febf59bfb5a54948033b801d0f64c8e56ef41272db066a22c45d1876162031 |
| golang-go.uber-zap_1.20.0.orig.tar.gz | 177.2 KiB | 13921dc099b5790bd4fcb06c18c2767c80f4ba4c7c0a29659d9126ba04dfc9e5 |
| golang-go.uber-zap_1.20.0-1.debian.tar.xz | 4.0 KiB | 001849e151d0fd667742a553bd48eeb6c452c86d21fadcb67a3cbb9868d5dd38 |
Available diffs
- diff from 1.15.0-3 to 1.20.0-1 (89.1 KiB)
No changes file available.
Binary packages built by this source
- golang-go.uber-zap-dev: Blazing fast, structured, leveled logging in Go
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.
