on develop help sign in
added trace to processIncoming
commit8d498964c94bb31a0eeb55dd2e3cea1478d8a2d9 authorOwen Shepherd <owen.shepherd@obsidian.systems> dateWed 22 Apr 2020, 14:35 (6 years ago) parent96ebc2b
1 file changed+1−1
src/Reflex/Requester/Base/Internal.hs+1−1
src/Reflex/Requester/Base/Internal.hs+1−1
@@ -287,7 +287,7 @@ matchResponsesWithRequests f send recv = withTagGen $ \tagGen -> mdo
287287 processIncoming incWaitingFor tagGen inc = flip push inc $ \(n, rawRsp) -> do
288288 waitingFor <- sample $ currentIncremental incWaitingFor
289289 case Map.lookup n waitingFor of
290− Nothing -> return Nothing -- TODO How should lookup failures be handled here? They shouldn't ever happen..
290+ Nothing -> return $ trace ("processIncoming: lookup failure for response key '" <> show n <> "'") Nothing
291291 Just (Decoder tag responseDecoder) ->
292292 return $ Just
293293 ( singletonResponseData tagGen (unsafeTagFromId n) (responseDecoder rawRsp)