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
{{ message }}
This repository has been archived by the owner on Aug 23, 2023. It is now read-only.
Good find, that explanation makes sense.
I guess we could just add a q.wg.Wait() before the return from RunGetTags()here. Then it should not return before all the filterTagsFromChan() go routines have stopped (have not tested that).
Got a panic like:
further down:
I think it goes something like this:
FindTags
we acquire a Read lock hereRunGetTags
we determine that we can end early herestopCh
was closed and hit this map read hereWhile (3) is happening the read lock from (1) could be long gone and another thread can have acquired a write lock and be modifying the map.
The text was updated successfully, but these errors were encountered: