i noticed honeybadger panic`ed when some code asserted that the connection would be processing either it's server or client flow... however i wrote the connection pool using a bad "tcp ip flow" hash function that allowed a collision to a similar flow of a different connection. terrible... this here:
i noticed honeybadger panic`ed when some code asserted that the connection would be processing either it's server or client flow... however i wrote the connection pool using a bad "tcp ip flow" hash function that allowed a collision to a similar flow of a different connection. terrible... this here:
https://github.com/david415/HoneyBadger/blob/master/types/flow.go#L74-L84