Comment 2 for bug 1336891

I have seen several panics like this, but not this specific one. There was a systemic fix make in the 1.19.x series to use the newer compiler and update many calls to be golang 1.2/3 compliant. I think this issue is fixes in trunk. If this issue is still present in 1.20.0, it will be escalated to be fixed in the next milestone.

If you can demonstrate this is an issue with 1.19.4, then we can assume the bug is still present in the code.