Github user jablko commented on the pull request:
https://github.com/apache/trafficserver/pull/63#issuecomment-38999285
Pulled as ad6806e, thanks!
---
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 h
Github user jablko commented on the pull request:
https://github.com/apache/trafficserver/pull/63#issuecomment-38952957
The metalink/test/pipeliningDisconnect script in commit 45393e reproduces
the crash two out of three times on my system, but if it's a race condition it
might manife
Github user Humbedooh closed the pull request at:
https://github.com/apache/trafficserver/pull/63
---
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 this feature
enabled and wishes so, or if the featur
Github user bgaff commented on the pull request:
https://github.com/apache/trafficserver/pull/63#issuecomment-38756233
Also, do you have instructions on how to reproduce this issue?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user jpeach commented on the pull request:
https://github.com/apache/trafficserver/pull/63#issuecomment-38756086
jablko, can you please make a new branch from master for this pull request?
I think that we should also have a new Jira ticket, since TS-2553 is long
closed.
---
I
GitHub user jablko opened a pull request:
https://github.com/apache/trafficserver/pull/63
TS-2553 metalink: Fix crash if INKVConnInternal::do_io_close() gets called
after a message is already complete
You can merge this pull request into a Git repository by running:
$ git pul
