You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the call to client.Get exceeds 21 seconds (I don't know why this timeout value was chosen), the defer close(ch) closes the channel because the case for the timer finishes and returns.
After that, the background goroutine writes to the channel and panic occurs.
Although not directly related to this issue, the variable err may be assigned from multiple goroutines at the same times, so it seems to be a race condition.
johejo
added a commit
to johejo/kustomize
that referenced
this issue
Dec 16, 2020
Describe the bug
At 6bbc829#diff-867c23b9f5a4ba53f94117fdfeb7c9899f849e5e231fee3d720fab5ceae43b9f
A timeout has been added to the getter.
But, due to improper handling of channels, writing to closed channels occurs at some point.
kustomize/api/loader/getter.go
Lines 97 to 111 in 67e445c
If the call to
client.Get
exceeds 21 seconds (I don't know why this timeout value was chosen), thedefer close(ch)
closes the channel because the case for the timer finishes and returns.After that, the background goroutine writes to the channel and panic occurs.
It does not occur every time.
Files that can reproduce the issue
Expected output
Actual output
Kustomize version
Platform
LInux
Additional context
The text was updated successfully, but these errors were encountered: