Github user ykopel closed the pull request at:
https://github.com/apache/trafficserver/pull/1470
---
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
GitHub user ykopel opened a pull request:
https://github.com/apache/trafficserver/pull/1470
Fix for tr-pass handling
The commit of
https://github.com/apache/trafficserver/commit/497e4755d7773590204b89b6c262f6605a9c8e21
Caused to all the cases that will go into this "if" to be
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1468
clang-analyzer build *successful*! See
https://ci.trafficserver.apache.org/job/clang-analyzer-github/153/ for details.
---
If your project is set up for it, you can reply to this email
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1469
clang-analyzer build *successful*! See
https://ci.trafficserver.apache.org/job/clang-analyzer-github/152/ for details.
---
If your project is set up for it, you can reply to this email
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1468
Linux build *successful*! See
https://ci.trafficserver.apache.org/job/linux-github/1482/ for details.
---
If your project is set up for it, you can reply to this email and have your
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1468
clang-analyzer build *successful*! See
https://ci.trafficserver.apache.org/job/clang-analyzer-github/151/ for details.
---
If your project is set up for it, you can reply to this email
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1468
Intel CC build *successful*! See
https://ci.trafficserver.apache.org/job/icc-github/21/ for details.
---
If your project is set up for it, you can reply to this email and have your
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1468
FreeBSD build *successful*! See
https://ci.trafficserver.apache.org/job/freebsd-github/1588/ for details.
---
If your project is set up for it, you can reply to this email and have
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1469
Intel CC build *successful*! See
https://ci.trafficserver.apache.org/job/icc-github/20/ for details.
---
If your project is set up for it, you can reply to this email and have your
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1469
FreeBSD build *successful*! See
https://ci.trafficserver.apache.org/job/freebsd-github/1587/ for details.
---
If your project is set up for it, you can reply to this email and have
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1469
Linux build *successful*! See
https://ci.trafficserver.apache.org/job/linux-github/1480/ for details.
---
If your project is set up for it, you can reply to this email and have your
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1468
Linux build *successful*! See
https://ci.trafficserver.apache.org/job/linux-github/1481/ for details.
---
If your project is set up for it, you can reply to this email and have your
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1468
Intel CC build *successful*! See
https://ci.trafficserver.apache.org/job/icc-github/19/ for details.
---
If your project is set up for it, you can reply to this email and have your
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1468
FreeBSD build *successful*! See
https://ci.trafficserver.apache.org/job/freebsd-github/1586/ for details.
---
If your project is set up for it, you can reply to this email and have
GitHub user jpeach opened a pull request:
https://github.com/apache/trafficserver/pull/1469
Introduce a Result error object.
Introduce a `Result` object to carry an abstract error with a corresponding
message. We already had `config_parse_error`, but this is slightly more
general.
GitHub user jpeach opened a pull request:
https://github.com/apache/trafficserver/pull/1468
Allow overriding proxy.config.config_dir.
Explicitly check whether proxy.config.config_dir has been overridden in
the environment before trying to load any configuration files.
Github user zwoop closed the pull request at:
https://github.com/apache/trafficserver/pull/1457
---
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
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1457
I've tested this with leak detection, and it seems to still work (it
reports quite a few leaks). So I'm going to land this :).
---
If your project is set up for it, you can reply to this
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1455
I cherry-picked this to 7.1.x, so no need to make an additional 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
Github user zwoop closed the pull request at:
https://github.com/apache/trafficserver/pull/1455
---
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
Github user zwoop closed the pull request at:
https://github.com/apache/trafficserver/pull/1467
---
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
21 matches
Mail list logo