You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by keith2008 <gi...@git.apache.org> on 2016/08/23 01:09:16 UTC
[GitHub] trafficserver pull request #901: TS-4745: pRecord.failCount not init inParen...
GitHub user keith2008 opened a pull request:
https://github.com/apache/trafficserver/pull/901
TS-4745: pRecord.failCount not init inParentRecord::ProcessParents
pRecord.failCount not init inParentRecord::ProcessParents
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/keith2008/trafficserver TS-4745
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/trafficserver/pull/901.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #901
----
commit 8a76d21f5194cb31e514860319b8fcae2d2648be
Author: keith2008 <56...@qq.com>
Date: 2016-08-23T00:42:30Z
TS-4743: parent use consistent_hash Strategy may cause crash while first parent is not set
commit 3deb52397b047455ba8aba3e5132e3daafa980ad
Author: keith2008 <56...@qq.com>
Date: 2016-08-23T00:51:44Z
TS-4744: ParentConsistentHash::selectParent may select the unavailable parent
commit 49beaa5b5fd712c1d8383b081fc8479ec680ae0a
Author: keith2008 <56...@qq.com>
Date: 2016-08-23T00:58:54Z
TS-4745: pRecord.failCount not init in ParentRecord::ProcessParents
----
---
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 feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] trafficserver pull request #901: TS-4745: pRecord.failCount not init inParen...
Posted by jrushford <gi...@git.apache.org>.
Github user jrushford closed the pull request at:
https://github.com/apache/trafficserver/pull/901
---
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 feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] trafficserver issue #901: TS-4745: pRecord.failCount not init inParentRecord...
Posted by zwoop <gi...@git.apache.org>.
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/901
Looks good. Maybe I suggest a slightly cleaner commit message:
TS-4745 Initializes pRecord.failCount in ParentRecord::ProcessParents
:+1:
---
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 feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] trafficserver issue #901: TS-4745: pRecord.failCount not init inParentRecord...
Posted by jrushford <gi...@git.apache.org>.
Github user jrushford commented on the issue:
https://github.com/apache/trafficserver/pull/901
keith2008 has asked me to fix this PR and submit the change on his behalf.
---
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 feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] trafficserver issue #901: TS-4745: pRecord.failCount not init inParentRecord...
Posted by jrushford <gi...@git.apache.org>.
Github user jrushford commented on the issue:
https://github.com/apache/trafficserver/pull/901
submitting new pr.
---
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 feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---