vendor: resenje.org/singleflight v0.4.3#48930
Conversation
full diff: https://resenje.org/singleflight/compare/v0.4.1...v0.4.3 Changes: - Fix incorrect `Forget` behavior - Make panic behavior consistent with x/sync package Signed-off-by: Paweł Gronowski <[email protected]>
|
oh! the diff link doesn't work with the vanity URL, so you need the one from github; |
| if panicErr != nil { | ||
| panic(panicErr) | ||
| } |
There was a problem hiding this comment.
Is there any situation where we could trip up a panic now, or would that already be such an exception that it already panicked through other ways, or a panic is the only right thing to do?
There was a problem hiding this comment.
The singleflight behavior for the same key should produce the same result, so it's very likely that the panic would happen again.
The x/sync/singleflight also does the same thing: https://cs.opensource.google/go/x/sync/+/refs/tags/v0.9.0:singleflight/singleflight.go;l=102
|
This one is definitely flaky now with runc 1.2.2; I think there were some patches in WIP branches that didn't get merged, and I'm trying to dig them up; |
full diff: janos/singleflight@v0.4.1...v0.4.3
Changes:
Forgetbehavior