Jens
Jens
It's definitely still an issue, experiencing it with AzureAd as well.
I have the same problem. I did some research on it and believe that it has something to do with the way that the DPS tries to connect to the...
@friimaind yeah, the issue is starting to become very clear here. Thanks for your report. I'd guess that it'll be an easy fix for someone with a solid knowledge of...
I guess, I know: `uuid.MustParse`. https://github.com/google/uuid/blob/0f11ee6918f41a04c201eceeadf612a377bc7fbc/uuid.go#L169 @ahloul use `uuid.MustParse` very wisely as it panics if the provided uuid.UUID is not parsable. Otherwise, use `uuid.Parse` and it returns an error if...
Just randomly stumbled across this. Looks like an [AI-generated PR (or at least AI-found error)](https://news.ycombinator.com/item?id=35357933) to me. I've gotten ChatGPT to find a pretty similar non-existent issue upon inspecting the...
Looking at [`uuid.Parse` func](https://github.com/google/uuid/blob/d55c313874fe007c6aaecc68211b6c7c7fc84aad/uuid.go#L73) and its doc block, this behaviour can be easily explained. Microsoft's encoding of UUIDs encloses the UUID in `{` and `}`. Like this: `{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}`. This UUID...
Oh, I just saw this is a duplicate of #60 and has been discussed already. TL;DR: Changing this behaviour in `uuid.Parse` could break existing implementations. Therefore, this is so far...
Well, I can only guess why that happens. Too little entropy might be the problem, AFAIK `crypto/rand` (used by `uuid.UUID`) uses syscalls and should typically not create duplicates. The comments...