3 ms·
I'm sorry you had this experience. I'm genuinely curious as to what the breakage was so hopefully we can prevent it for some other folks, hence why I asked if y
by steeve 6y ago
I'm sorry you had this experience. I'm genuinely curious as to what the breakage was so hopefully we can prevent it for some other folks, hence why I asked if you remembered the specifics.
- zaarn 6y agoBasically, x/crypto/blake2b received a patch to switch how it detects the presence of AVX and SSE at runtime, the symbols required for that to work with earlier versions where removed. While I understand this is technically covered in the compatibility promise, it's very frustrating when it happens with a library developed by google, especially when, at the time, the general recommendation was to vendor them so as to not suffer from breakage when they update.
- steeve 6y agoI believe this commit has background: https://github.com/golang/crypto/commit/d6449816ce06963d9d136eee5a56fca5b0616e7e#diff-08466c4c14798cc53ca7d9080070e62f https://github.com/golang/crypto/commit/d6449816ce06963d9d13... To be fair though, that package was depending on a private API to begin with.