Github user sekimura commented on the issue:
https://github.com/apache/trafficserver/pull/1221
@sidhuagarwal could you create a new JIRA issue with more info like
stacktrace?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as wel
Github user sidhuagarwal commented on the issue:
https://github.com/apache/trafficserver/pull/1221
@sekimura We are still seeing this issue with #1232
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user sekimura commented on the issue:
https://github.com/apache/trafficserver/pull/1221
It looks good so far with #1232. I'm going to close this PR since we don't
need this anymore.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user PSUdaemon commented on the issue:
https://github.com/apache/trafficserver/pull/1221
Ok, sounds good. I'll hold off on cutting 6.2.1 for a bit longer.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your pro
Github user sekimura commented on the issue:
https://github.com/apache/trafficserver/pull/1221
I hope we don't. Give me a bit more time to test a build with #1232
handling some traffic in the wild.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user PSUdaemon commented on the issue:
https://github.com/apache/trafficserver/pull/1221
Do we still need this now that #1232 is merged?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
