golang-github-mitchellh-hashstructure (2.0.2-1)
[PTS] [DDPO]
COMMITS: VCS has seen 23 commits since the debian/1.1.0-1 tag
- Git: https://salsa.debian.org/go-team/packages/golang-github-mitchellh-hashstructure.git
-
- Branch: debian/sid
- Path: debian/changelog
- Repo size: 282624
- Browser: https://salsa.debian.org/go-team/packages/golang-github-mitchellh-hashstructure
- Last scan: 2024-07-12 05:54:20+00
- Next scan: 2024-07-19 23:01:00+00
- CI pipeline status: success
- Debian changelog in Git:
golang-github-mitchellh-hashstructure (2.0.2-1) experimental; urgency=medium
* Team upload
* New upstream release
* Bump standards version
-- Reinhard Tartler <siretart@tauware.de> Mon, 20 May 2024 06:50:30 -0400
- This branch is 23 commits ahead of tag debian/1.1.0-1
- Git log:
commit 17568803ef90ae46f2bd89d416798b8fd3478012
Author: Reinhard Tartler <siretart@tauware.de>
Date: Mon May 20 06:48:30 2024 -0400
debian/changelog: update
commit 3727257ba93665e05b4c78d6eb4381e4cc57739a
Author: Reinhard Tartler <siretart@tauware.de>
Date: Mon May 20 06:50:18 2024 -0400
Bump standards version
commit 2d3891b2f333201e46fbbc11ea9b61817ead6d2e
Merge: 0f9830e 58a6092
Author: Reinhard Tartler <siretart@tauware.de>
Date: Mon May 20 06:48:20 2024 -0400
Update upstream source from tag 'upstream/2.0.2'
Update to upstream version '2.0.2'
with Debian dir cbeef066c3db5f3046450c0761d3d7e3e406b4d3
commit 58a6092e8d26af6c8df2810acd74251a5e292c74
Merge: b754451 a045b66
Author: Reinhard Tartler <siretart@tauware.de>
Date: Mon May 20 06:48:20 2024 -0400
New upstream version 2.0.2
commit 0f9830ecc2e80ddb046a96f1836babe6ed22e487
Author: Reinhard Tartler <siretart@tauware.de>
Date: Mon May 20 06:46:09 2024 -0400
debian/changelog: update
commit b754451576ab7bb34cdfa8dc3010637b8fbd4ec6
Merge: c76849b d072abf
Author: Reinhard Tartler <siretart@tauware.de>
Date: Mon May 20 06:45:44 2024 -0400
New upstream version 2.0.1
commit 27214f566a6ecb9c4dac7da0c7437e8569011ad4
Merge: ec1e571 b754451
Author: Reinhard Tartler <siretart@tauware.de>
Date: Mon May 20 06:45:44 2024 -0400
Update upstream source from tag 'upstream/2.0.1'
Update to upstream version '2.0.1'
with Debian dir 5bcb4bfb5f47ef405d40012870b69e5878b450ae
commit ec1e571ea2db39235c9b37e3894a4a052f346c14
Author: Reinhard Tartler <siretart@tauware.de>
Date: Mon May 20 06:45:38 2024 -0400
debian/watch: make it work with current github
commit 3dccfcf8de81b7c8a7262e53eea75c5783cb5b78
Author: Aloïs Micard <creekorful@debian.org>
Date: Wed Dec 1 11:46:32 2021 +0000
[skip ci] update debian/gitlab-ci.yml (using pkg-go-tools/ci-config)
See: https://salsa.debian.org/go-team/infra/pkg-go-tools
Gbp-Dch: Ignore
commit a045b665615f739329536a58c25ca6327abf1ec1
Merge: 7c1b705 68e777f
Author: Mitchell Hashimoto <xmitchx@gmail.com>
Date: Thu May 27 16:24:52 2021 -0700
Merge pull request #33 from mwhooker/master
Use built-in IsZero function
commit 68e777f4583a6ac5c2a99b0555887def67c3d20b
Author: Matthew Hooker <mwhooker@gmail.com>
Date: Thu May 27 16:01:12 2021 -0700
Use built-in `IsZero` function.
This replaces a different method of checking if a value is a zero value.
The other method worked by constructing the zero value of the type of
the value in question, and doing an interface comparison with it. This
does not work for certain types which are not comparable. We can work
around this issue by using the `IsZero` function which was added in go
1.13.
This crash was found using go-fuzz.
commit 2f61b189a917d5b6ec76db4eab5e9ea993c07cd8
Author: Matthew Hooker <mwhooker@gmail.com>
Date: Thu May 27 15:32:53 2021 -0700
Failing test showing panic
commit 7c1b705df6467e8d961b05c3619ebf3bde21657f
Merge: bbce34b 969c3e4
Author: Mitchell Hashimoto <xmitchx@gmail.com>
Date: Mon Dec 28 09:03:58 2020 -0800
Merge pull request #29 from matheus-meneses/master
update-readme-v2
commit 969c3e4b18ae969480db4d04bfd8973278409f79
Author: Matheus Lamounier de Meneses <meneses.matheus@gmail.com>
Date: Mon Dec 28 14:02:29 2020 -0300
update-readme-v2
Update Readme for v2
commit bbce34b45a45399bbcecbd12d6a6eb770e1426a2
Merge: d072abf e9a262e
Author: Mitchell Hashimoto <xmitchx@gmail.com>
Date: Sun Nov 29 21:20:05 2020 -0800
Merge pull request #28 from desimone/patch-1
Minor typos / clarification of doc strings
commit e9a262e34ca16dc11d49326f3155e79500efedf1
Author: bobby <1544881+desimone@users.noreply.github.com>
Date: Sun Nov 29 20:34:04 2020 -0800
Update hashstructure.go
I'm guessing a bit on `aways`--> `always` but it seems to match the implementation.
commit d072abffc64ced70298852edb0ea32e75b79df20
Author: Mitchell Hashimoto <mitchell.hashimoto@gmail.com>
Date: Sat Nov 21 18:17:03 2020 -0800
update go.mod for v2
commit 79a8728b24bcc14cd4437421753f6ea013cf4cff
Author: Mitchell Hashimoto <mitchell.hashimoto@gmail.com>
Date: Sat Nov 21 18:13:34 2020 -0800
docs for ErrFormat
commit 568c0533b2df0067ed5283c18d6f2c6f57ef135f
Author: Mitchell Hashimoto <mitchell.hashimoto@gmail.com>
Date: Sat Nov 21 18:11:06 2020 -0800
validate format
commit 7962ac49c9d5c00943bc39f18612595f5f1f3c24
Author: Mitchell Hashimoto <mitchell.hashimoto@gmail.com>
Date: Sat Nov 21 18:08:48 2020 -0800
support the v1 format, require formats in Hash
commit 93bb3474e96f244ab8899e3d7d820279d06ef8af
Author: Mitchell Hashimoto <mitchell.hashimoto@gmail.com>
Date: Sat Nov 21 17:58:18 2020 -0800
clarifying comments
commit d5de409d195bda66c116f5cb1235e8a4245b3b1b
Merge: 191a1e8 efa4282
Author: Mitchell Hashimoto <xmitchx@gmail.com>
Date: Sat Nov 21 17:56:53 2020 -0800
Merge pull request #20 from aaronlehmann/fix-set-hashing
Make set hashing robust to bitwise XOR cancellations
commit efa428270bb8183c2a184e7490894fa339c6a93a
Author: Aaron Lehmann <aaron.lehmann@blueowl.xyz>
Date: Mon Jan 14 11:17:16 2019 -0800
Make set hashing robust to bitwise XOR cancellations
The way sets (maps, structs, slices with the "set" tag) are hashed
relies on an XOR to mix the hashes of their elements. This allows
multiple independent items to interfere with each other through XOR
operations. For example, consider a "set" slice with the following two
structs:
[
{Key: "a", Value: "v1"},
{Key: "a", Value: "v2"}
]
Changing both keys from "a" to "b" will not change the hash value of the
overall object, since in either case the two keys will cancel out under
XOR arithmetic.
This change fixes the problem by adding a step after every set of
unordered hash operations that "hardens" the result by applying another
hash. It will prevent components of one unordered hashing operation (for
example, `Key: "a"` above) from interacting with the same data
encountered later in a different context.
Note that this changes hashes produced by the package for given inputs.
Closes: #18