it appears like UnpauseRead gets written to a concurrent queue followed by the inner waker having wake_by_ref called on it. It seems like while we are only running a single agent thread which handles both the reading off this queue and writing (barring the outside threads which can write to this queue via send_message).
Reading the wake_by_ref doc it seems like it can cause the current thread to yield and enter the poll cycle? is it possible that this logic gets run again but since requests.insert doesn't happen until like 366 there is a race where that request isn't in there yet?
Should this insertion happen at the top of this function?
Encountered the error when running some code with busy cpu usage:
2023-09-21T21:53:32.563521901Z [WARN] (isahc-agent-0): received unpause request for unknown request token: 0which implies that either
Looking more closely at this function https://github.com/sagebind/isahc/blob/master/src/agent/mod.rs#L332
it appears like
UnpauseReadgets written to a concurrent queue followed by the inner waker having wake_by_ref called on it. It seems like while we are only running a single agent thread which handles both the reading off this queue and writing (barring the outside threads which can write to this queue via send_message).Reading the wake_by_ref doc it seems like it can cause the current thread to yield and enter the poll cycle? is it possible that this logic gets run again but since requests.insert doesn't happen until like 366 there is a race where that request isn't in there yet?
Should this insertion happen at the top of this function?