Skip to content

Conversation

@iancmcc
Copy link

@iancmcc iancmcc commented Feb 3, 2018

Fixes #187. May or may not be worthwhile to merge this until it's clear whether or not the
breaking change upstream will be reverted. Hopefully if it's reverted it's done
in a backward-compatible way for those who already worked around it, if
possible.

@rmconsole-wf rmconsole-wf changed the title Fixes #187: Update to the new go.uuid API RM-25125 Fixes #187: Update to the new go.uuid API Feb 3, 2018
@aviary-wf
Copy link

aviary-wf commented Feb 3, 2018

Security Insights

No security relevant content was detected by automated scans.

Action Items

  • Review PR for security impact; comment "security review required" if needed or unsure
  • Verify aviary.yaml coverage of security relevant code

Questions or Comments? Reach out on HipChat: InfoSec Forum.

@brianshannan-wf
Copy link
Collaborator

@iancmcc It looks like our travis build is still pulling in an old version of uuid, could you update that version so the tests pass?

rsc added a commit to rsc/go-datastructures that referenced this pull request May 25, 2018
The only call was uuid.NewV4().Bytes(), which really means
"get me 16 random bytes".

uuid.NewV4 changed at some point to return an error in addition
to the UUID, which made this code no longer compile.

There's no need to depend on a uuid package to get 16 random bytes.
Do what the old package did, namely read from crypto/rand.Reader
and expect it to succeed (or else panic), but without the dependency.

Fixes Workiva#187.
Fixes Workiva#188.
@rsc
Copy link
Contributor

rsc commented May 25, 2018

I sent replacement PR #192, which removes go.uuid entirely. Then it doesn't matter what Travis is supplying.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants