Failed: trafficserver (17d4c15b)

Build Failed for trafficserver (latest) You can find out more about this failure here: https://readthedocs.org/projects/trafficserver/builds/4643128/ If you have questions, a good place to start is the FAQ: https://docs.readthedocs.org/en/latest/faq.html Keep documenting, Read the Docs --

Failed: trafficserver (17d4c15b)

Build Failed for trafficserver (latest) You can find out more about this failure here: https://readthedocs.org/projects/trafficserver/builds/4643118/ If you have questions, a good place to start is the FAQ: https://docs.readthedocs.org/en/latest/faq.html Keep documenting, Read the Docs --

Failed: trafficserver (latest)

Build Failed for trafficserver (latest) Error: Version locked, retrying in 5 minutes. You can find out more about this failure here: https://readthedocs.org/projects/trafficserver/builds/4643128/ If you have questions, a good place to start is the FAQ:

[jira] [Resolved] (TS-5040) Forward CONNECT methods without parent proxying.

[ https://issues.apache.org/jira/browse/TS-5040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Peach resolved TS-5040. - Resolution: Fixed Fix Version/s: 7.1.0 > Forward CONNECT methods without parent proxying. >

[jira] [Work logged] (TS-5040) Forward CONNECT methods without parent proxying.

[ https://issues.apache.org/jira/browse/TS-5040?focusedWorklogId=31910=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-31910 ] ASF GitHub Bot logged work on TS-5040: -- Author: ASF GitHub Bot Created

[GitHub] trafficserver pull request #1202: TS-5040: Forward CONNECT without parent pr...

Github user jpeach closed the pull request at: https://github.com/apache/trafficserver/pull/1202 --- 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

[jira] [Resolved] (TS-5045) Add ws and wss scheme constants.

[ https://issues.apache.org/jira/browse/TS-5045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Peach resolved TS-5045. - Resolution: Fixed Fix Version/s: 7.1.0 > Add ws and wss scheme constants. >

[jira] [Work logged] (TS-5045) Add ws and wss scheme constants.

[ https://issues.apache.org/jira/browse/TS-5045?focusedWorklogId=31909=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-31909 ] ASF GitHub Bot logged work on TS-5045: -- Author: ASF GitHub Bot Created

[GitHub] trafficserver pull request #1211: TS-5045: Add ws and wss scheme constants.

Github user jpeach closed the pull request at: https://github.com/apache/trafficserver/pull/1211 --- 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

[jira] [Work logged] (TS-4728) Null pointer error in LogHost.cc.

[ https://issues.apache.org/jira/browse/TS-4728?focusedWorklogId=31908=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-31908 ] ASF GitHub Bot logged work on TS-4728: -- Author: ASF GitHub Bot Created

[jira] [Updated] (TS-4728) Null pointer error in LogHost.cc.

[ https://issues.apache.org/jira/browse/TS-4728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Sorber updated TS-4728: Backport to Version: (was: 6.2.1) > Null pointer error in LogHost.cc. > - >

[jira] [Updated] (TS-4728) Null pointer error in LogHost.cc.

[ https://issues.apache.org/jira/browse/TS-4728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Sorber updated TS-4728: Fix Version/s: 6.2.1 > Null pointer error in LogHost.cc. > - > >

[GitHub] trafficserver pull request #1213: TS-4728 Null pointer error in LogHost.cc (...

Github user PSUdaemon closed the pull request at: https://github.com/apache/trafficserver/pull/1213 --- 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

[jira] [Work logged] (TS-4728) Null pointer error in LogHost.cc.

[ https://issues.apache.org/jira/browse/TS-4728?focusedWorklogId=31907=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-31907 ] ASF GitHub Bot logged work on TS-4728: -- Author: ASF GitHub Bot Created

[GitHub] trafficserver issue #1213: TS-4728 Null pointer error in LogHost.cc (backpor...

Github user atsci commented on the issue: https://github.com/apache/trafficserver/pull/1213 FreeBSD build *successful*! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/1198/ for details. --- If your project is set up for it, you can reply to this email and have

[jira] [Work logged] (TS-4728) Null pointer error in LogHost.cc.

[ https://issues.apache.org/jira/browse/TS-4728?focusedWorklogId=31906=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-31906 ] ASF GitHub Bot logged work on TS-4728: -- Author: ASF GitHub Bot Created

[GitHub] trafficserver issue #1213: TS-4728 Null pointer error in LogHost.cc (backpor...

Github user atsci commented on the issue: https://github.com/apache/trafficserver/pull/1213 Linux build *successful*! See https://ci.trafficserver.apache.org/job/Github-Linux/1091/ for details. --- If your project is set up for it, you can reply to this email and have your

[GitHub] trafficserver issue #1215: TS-5027: Replace readdir_r with readdir.

Github user atsci commented on the issue: https://github.com/apache/trafficserver/pull/1215 FreeBSD build *successful*! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/1197/ for details. --- If your project is set up for it, you can reply to this email and have

[jira] [Work logged] (TS-5027) Replace readdir_r with readdir

[ https://issues.apache.org/jira/browse/TS-5027?focusedWorklogId=31905=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-31905 ] ASF GitHub Bot logged work on TS-5027: -- Author: ASF GitHub Bot Created

[jira] [Work logged] (TS-5027) Replace readdir_r with readdir

[ https://issues.apache.org/jira/browse/TS-5027?focusedWorklogId=31904=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-31904 ] ASF GitHub Bot logged work on TS-5027: -- Author: ASF GitHub Bot Created

[GitHub] trafficserver issue #1215: TS-5027: Replace readdir_r with readdir.

Github user atsci commented on the issue: https://github.com/apache/trafficserver/pull/1215 Linux build *successful*! See https://ci.trafficserver.apache.org/job/Github-Linux/1090/ for details. --- If your project is set up for it, you can reply to this email and have your

[jira] [Updated] (TS-4514) Transaction hangs when no_dns_just_forward is configured but parent proxy is unresolvable

[ https://issues.apache.org/jira/browse/TS-4514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Sorber updated TS-4514: Fix Version/s: 6.2.1 > Transaction hangs when no_dns_just_forward is configured but parent proxy is >

[jira] [Updated] (TS-4514) Transaction hangs when no_dns_just_forward is configured but parent proxy is unresolvable

[ https://issues.apache.org/jira/browse/TS-4514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Sorber updated TS-4514: Backport to Version: (was: 6.2.1) > Transaction hangs when no_dns_just_forward is configured but parent

[jira] [Work logged] (TS-4514) Transaction hangs when no_dns_just_forward is configured but parent proxy is unresolvable

[ https://issues.apache.org/jira/browse/TS-4514?focusedWorklogId=31903=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-31903 ] ASF GitHub Bot logged work on TS-4514: -- Author: ASF GitHub Bot Created

[GitHub] trafficserver pull request #1208: TS-4514: Transaction hangs when no_dns_jus...

Github user PSUdaemon closed the pull request at: https://github.com/apache/trafficserver/pull/1208 --- 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

[jira] [Work logged] (TS-4728) Null pointer error in LogHost.cc.

[ https://issues.apache.org/jira/browse/TS-4728?focusedWorklogId=31902=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-31902 ] ASF GitHub Bot logged work on TS-4728: -- Author: ASF GitHub Bot Created

[GitHub] trafficserver issue #1213: TS-4728 Null pointer error in LogHost.cc (backpor...

Github user PSUdaemon commented on the issue: https://github.com/apache/trafficserver/pull/1213 [approve ci] --- 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

[jira] [Commented] (TS-4801) Are we marking parents down too aggressively?

[ https://issues.apache.org/jira/browse/TS-4801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15652696#comment-15652696 ] Phil Sorber commented on TS-4801: - [~jrushford] said that this was backported with TS-3419 back port so I am

[jira] [Updated] (TS-4801) Are we marking parents down too aggressively?

[ https://issues.apache.org/jira/browse/TS-4801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Sorber updated TS-4801: Fix Version/s: 6.2.1 > Are we marking parents down too aggressively? >

[jira] [Updated] (TS-4801) Are we marking parents down too aggressively?

[ https://issues.apache.org/jira/browse/TS-4801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Sorber updated TS-4801: Backport to Version: (was: 6.2.1) > Are we marking parents down too aggressively? >

[jira] [Work logged] (TS-5027) Replace readdir_r with readdir

[ https://issues.apache.org/jira/browse/TS-5027?focusedWorklogId=31901=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-31901 ] ASF GitHub Bot logged work on TS-5027: -- Author: ASF GitHub Bot Created

[GitHub] trafficserver issue #1215: TS-5027: Replace readdir_r with readdir.

Github user PSUdaemon commented on the issue: https://github.com/apache/trafficserver/pull/1215 @zwoop & @jpeach - can you guys give this a thumbs up if it looks like I did the backport correctly? Mostly `nullptr` and `{}` that was providing conflicts. Thanks. --- If your

[GitHub] trafficserver pull request #1215: TS-5027: Replace readdir_r with readdir.

GitHub user PSUdaemon opened a pull request: https://github.com/apache/trafficserver/pull/1215 TS-5027: Replace readdir_r with readdir. Glibc deprecated readdir_r(3), so replace it with readdir(3). We were already using readdir(3) in many places so this is just accepting the

[jira] [Work logged] (TS-5027) Replace readdir_r with readdir

[ https://issues.apache.org/jira/browse/TS-5027?focusedWorklogId=31900=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-31900 ] ASF GitHub Bot logged work on TS-5027: -- Author: ASF GitHub Bot Created

Failed: trafficserver (6fd307f0)

Build Failed for trafficserver (latest) You can find out more about this failure here: https://readthedocs.org/projects/trafficserver/builds/4642101/ If you have questions, a good place to start is the FAQ: https://docs.readthedocs.org/en/latest/faq.html Keep documenting, Read the Docs --

[jira] [Resolved] (TS-5047) Unmapped url log fields sometimes do not have a host

[ https://issues.apache.org/jira/browse/TS-5047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan M. Carroll resolved TS-5047. - Resolution: Fixed > Unmapped url log fields sometimes do not have a host >

[jira] [Work logged] (TS-5047) Unmapped url log fields sometimes do not have a host

[ https://issues.apache.org/jira/browse/TS-5047?focusedWorklogId=31895=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-31895 ] ASF GitHub Bot logged work on TS-5047: -- Author: ASF GitHub Bot Created

[GitHub] trafficserver pull request #1214: TS-5047: Fix unmapped URL logging tags.

Github user SolidWallOfCode closed the pull request at: https://github.com/apache/trafficserver/pull/1214 --- 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

[jira] [Resolved] (TS-4872) clang-analyzer: Memory leak LogObject.cc _checkout_write

[ https://issues.apache.org/jira/browse/TS-4872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Peach resolved TS-4872. - Resolution: Fixed > clang-analyzer: Memory leak LogObject.cc _checkout_write >

[jira] [Resolved] (TS-4927) Coverity issues in passthru example plugin

[ https://issues.apache.org/jira/browse/TS-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Peach resolved TS-4927. - Resolution: Fixed > Coverity issues in passthru example plugin > --

[jira] [Resolved] (TS-4840) Crash when reattaching to C++ API Stats.

[ https://issues.apache.org/jira/browse/TS-4840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Peach resolved TS-4840. - Resolution: Fixed > Crash when reattaching to C++ API Stats. > > >

[jira] [Work logged] (TS-5047) Unmapped url log fields sometimes do not have a host

[ https://issues.apache.org/jira/browse/TS-5047?focusedWorklogId=31881=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-31881 ] ASF GitHub Bot logged work on TS-5047: -- Author: ASF GitHub Bot Created

[jira] [Updated] (TS-5028) ATS 6.2.0 don't start with read-only /etc

[ https://issues.apache.org/jira/browse/TS-5028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Call updated TS-5028: --- Affects Version/s: 6.2.0 > ATS 6.2.0 don't start with read-only /etc > -

[GitHub] trafficserver issue #1214: TS-5047: Fix unmapped URL logging tags.

Github user atsci commented on the issue: https://github.com/apache/trafficserver/pull/1214 FreeBSD build *successful*! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/1196/ for details. --- If your project is set up for it, you can reply to this email and have

[GitHub] trafficserver issue #1214: TS-5047: Fix unmapped URL logging tags.

Github user atsci commented on the issue: https://github.com/apache/trafficserver/pull/1214 Linux build *successful*! See https://ci.trafficserver.apache.org/job/Github-Linux/1089/ for details. --- If your project is set up for it, you can reply to this email and have your

[jira] [Work logged] (TS-5047) Unmapped url log fields sometimes do not have a host

[ https://issues.apache.org/jira/browse/TS-5047?focusedWorklogId=31880=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-31880 ] ASF GitHub Bot logged work on TS-5047: -- Author: ASF GitHub Bot Created

[jira] [Created] (TS-5049) Parent.config keynames are confusing

Miles Libbey created TS-5049: Summary: Parent.config keynames are confusing Key: TS-5049 URL: https://issues.apache.org/jira/browse/TS-5049 Project: Traffic Server Issue Type: Improvement

[jira] [Updated] (TS-5048) parent.config: add weighting to other selection strategies

[ https://issues.apache.org/jira/browse/TS-5048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miles Libbey updated TS-5048: - Issue Type: Improvement (was: Bug) > parent.config: add weighting to other selection strategies >

[jira] [Created] (TS-5048) parent.config: add weighting to other selection strategies

Miles Libbey created TS-5048: Summary: parent.config: add weighting to other selection strategies Key: TS-5048 URL: https://issues.apache.org/jira/browse/TS-5048 Project: Traffic Server Issue

[jira] [Resolved] (TS-5023) Allow diags.log and traffic.out to be rotated by size or time

[ https://issues.apache.org/jira/browse/TS-5023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan M. Carroll resolved TS-5023. - Resolution: Fixed > Allow diags.log and traffic.out to be rotated by size or time >

[jira] [Work logged] (TS-5023) Allow diags.log and traffic.out to be rotated by size or time

[ https://issues.apache.org/jira/browse/TS-5023?focusedWorklogId=31879=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-31879 ] ASF GitHub Bot logged work on TS-5023: -- Author: ASF GitHub Bot Created

[GitHub] trafficserver pull request #1165: TS-5023 Allow diags.log and traffic.out to...

Github user SolidWallOfCode closed the pull request at: https://github.com/apache/trafficserver/pull/1165 --- 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

[jira] [Work logged] (TS-5023) Allow diags.log and traffic.out to be rotated by size or time

[ https://issues.apache.org/jira/browse/TS-5023?focusedWorklogId=31878=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-31878 ] ASF GitHub Bot logged work on TS-5023: -- Author: ASF GitHub Bot Created

[GitHub] trafficserver issue #1165: TS-5023 Allow diags.log and traffic.out to be rot...

Github user SolidWallOfCode commented on the issue: https://github.com/apache/trafficserver/pull/1165 Ship it. --- 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

[jira] [Work logged] (TS-5030) Proposal: Add API to get the client request UUID directly from a TSHttpTx

[ https://issues.apache.org/jira/browse/TS-5030?focusedWorklogId=31877=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-31877 ] ASF GitHub Bot logged work on TS-5030: -- Author: ASF GitHub Bot Created

[GitHub] trafficserver issue #1184: TS-5030: Add API to get the unique client request...

Github user calavera commented on the issue: https://github.com/apache/trafficserver/pull/1184 I made some changes to not use the TS API internally and use the arena for memory allocation. I'd really appreciate another review. I tagged the issue in Jira with `TS API`, should

[GitHub] trafficserver pull request #1210: Create log_requests plugin

Github user danobi commented on a diff in the pull request: https://github.com/apache/trafficserver/pull/1210#discussion_r87227079 --- Diff: plugins/experimental/log_requests/log_requests.c --- @@ -0,0 +1,301 @@ +/** @file + + Logs full request/response headers on an

[GitHub] trafficserver pull request #1210: Create log_requests plugin

Github user SolidWallOfCode commented on a diff in the pull request: https://github.com/apache/trafficserver/pull/1210#discussion_r87219292 --- Diff: plugins/experimental/log_requests/log_requests.c --- @@ -0,0 +1,301 @@ +/** @file + + Logs full request/response

[jira] [Work logged] (TS-5047) Unmapped url log fields sometimes do not have a host

[ https://issues.apache.org/jira/browse/TS-5047?focusedWorklogId=31874=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-31874 ] ASF GitHub Bot logged work on TS-5047: -- Author: ASF GitHub Bot Created

[GitHub] trafficserver issue #1214: TS-5047: Fix unmapped URL logging tags.

Github user atsci commented on the issue: https://github.com/apache/trafficserver/pull/1214 Linux build *successful*! See https://ci.trafficserver.apache.org/job/Github-Linux/1088/ for details. --- If your project is set up for it, you can reply to this email and have your

[jira] [Work logged] (TS-5047) Unmapped url log fields sometimes do not have a host

[ https://issues.apache.org/jira/browse/TS-5047?focusedWorklogId=31873=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-31873 ] ASF GitHub Bot logged work on TS-5047: -- Author: ASF GitHub Bot Created

[GitHub] trafficserver issue #1214: TS-5047: Fix unmapped URL logging tags.

Github user zwoop commented on the issue: https://github.com/apache/trafficserver/pull/1214 I'm going to test this on Docs. --- 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

[GitHub] trafficserver issue #1214: TS-5047: Fix unmapped URL logging tags.

Github user atsci commented on the issue: https://github.com/apache/trafficserver/pull/1214 FreeBSD build *successful*! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/1195/ for details. --- If your project is set up for it, you can reply to this email and have

[jira] [Work logged] (TS-5047) Unmapped url log fields sometimes do not have a host

[ https://issues.apache.org/jira/browse/TS-5047?focusedWorklogId=31872=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-31872 ] ASF GitHub Bot logged work on TS-5047: -- Author: ASF GitHub Bot Created

[jira] [Work logged] (TS-5047) Unmapped url log fields sometimes do not have a host

[ https://issues.apache.org/jira/browse/TS-5047?focusedWorklogId=31871=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-31871 ] ASF GitHub Bot logged work on TS-5047: -- Author: ASF GitHub Bot Created

[GitHub] trafficserver pull request #1214: TS-5047: Fix unmapped URL logging tags.

GitHub user SolidWallOfCode opened a pull request: https://github.com/apache/trafficserver/pull/1214 TS-5047: Fix unmapped URL logging tags. You can merge this pull request into a Git repository by running: $ git pull https://github.com/SolidWallOfCode/trafficserver ts-5047

[jira] [Commented] (TS-5047) Unmapped url log fields sometimes do not have a host

[ https://issues.apache.org/jira/browse/TS-5047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15651118#comment-15651118 ] Leif Hedstrom commented on TS-5047: --- I agree. This would also nicely make certain log entries be a lot more

[jira] [Updated] (TS-5047) Unmapped url log fields sometimes do not have a host

[ https://issues.apache.org/jira/browse/TS-5047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan M. Carroll updated TS-5047: Priority: Minor (was: Major) > Unmapped url log fields sometimes do not have a host >

[jira] [Updated] (TS-5047) Unmapped url log fields sometimes do not have a host

[ https://issues.apache.org/jira/browse/TS-5047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-5047: -- Fix Version/s: 7.1.0 > Unmapped url log fields sometimes do not have a host >

[jira] [Commented] (TS-5047) Unmapped url log fields sometimes do not have a host

[ https://issues.apache.org/jira/browse/TS-5047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15651094#comment-15651094 ] Alan M. Carroll commented on TS-5047: - Long discussion with [~zwoop] about this. I now think the correct

[jira] [Created] (TS-5047) Unmapped url log fields sometimes do not have a host

Alan M. Carroll created TS-5047: --- Summary: Unmapped url log fields sometimes do not have a host Key: TS-5047 URL: https://issues.apache.org/jira/browse/TS-5047 Project: Traffic Server Issue