Sam Whited

Right, so in an example like the following: ``` r := strings.NewReader(``) d := xml.NewDecoder(r) tok, _ := d.Token() start := tok.(xml.StartElement) switch start.Name.Space { case "foo": FooHandler(Middleware(d), start) case...

> First, this changes the behavior so that if there's an error returned from ExportKeyingMaterial, it will not set any channel binding. It also doesn't notify anyone about this error....

I am not sure if it's the same, but I'm seeing similar behavior (the file name is a cached file) but what's actually triggering it is a `_test.go` file with...

I just ran into a deploy issue because I naively had swapped golint out for staticcheck on the Go team's recommendation. Turns out it's not a superset (which is fine),...

Thank you for reconsidering this. Would it be possible to force it to cause a CI failure? General best practices are to document everything and I suspect you'll find many...

> nor can I stop you from exiting non-zero from a script if it detects output from Staticcheck I'd be worried about output detection being brittle, it feels like a...

A few things: I have OpenTracks set to the default app to open GPX files on my device. If it can't open them initially, I can't use its built in...

> RFC 9266 is silent about tls-server-end-point so it appears it's not defined for TLS 1.3, unless there's some other RFC that I've overlooked My apologies for being vague there;...

Oops, yes indeed, `tls-server-end-point`.

I went back and refreshed myself on this as well, you're correct, `tls-server-end-point` would have prevented the recent attack that the previous poster was mentioning for TLS 1.2. It's weaknesses...