Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1517
clang-analyzer build *successful*!
https://ci.trafficserver.apache.org/job/clang-analyzer-github/267/
---
If your project is set up for it, you can reply to this email and have your
GitHub user mlibbey opened an issue:
https://github.com/apache/trafficserver/issues/1553
Consistent hashing in parent.config can use suboptimal URL for hash
(was TS-4025 https://issues.apache.org/jira/browse/TS-4025)
--
original description:
In a setup, where the same
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1551
clang-analyzer build *successful*!
https://ci.trafficserver.apache.org/job/clang-analyzer-github/265/
---
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/1550
clang-analyzer build *successful*!
https://ci.trafficserver.apache.org/job/clang-analyzer-github/266/
---
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/1517
Linux build *successful*!
https://ci.trafficserver.apache.org/job/linux-github/1599/
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1517
FreeBSD11 build *failed*!
https://ci.trafficserver.apache.org/job/freebsd-github/1704/
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1517
Intel CC build *successful*!
https://ci.trafficserver.apache.org/job/icc-github/135/
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1551
Linux build *successful*!
https://ci.trafficserver.apache.org/job/linux-github/1598/
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1550
FreeBSD11 build *failed*!
https://ci.trafficserver.apache.org/job/freebsd-github/1703/
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1550
Intel CC build *successful*!
https://ci.trafficserver.apache.org/job/icc-github/134/
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1550
The AU check failure is as expected (for now).
---
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
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1551
Intel CC build *successful*!
https://ci.trafficserver.apache.org/job/icc-github/133/
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1550
Linux build *successful*!
https://ci.trafficserver.apache.org/job/linux-github/1597/
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1551
AU check *failed*! https://ci.trafficserver.apache.org/job/autest-github/7/
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1551
FreeBSD11 build *failed*!
https://ci.trafficserver.apache.org/job/freebsd-github/1702/
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1517
RAT check *successful*!
https://ci.trafficserver.apache.org/job/RAT-github/22/
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1517
clang-format check *successful*! See
https://ci.trafficserver.apache.org/job/clang-format-github/9/ for details.
---
If your project is set up for it, you can reply to this email and
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1517
AU check *successful*! See
https://ci.trafficserver.apache.org/job/autest-github/8/ for details.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1550
AU check *failed*! See
https://ci.trafficserver.apache.org/job/autest-github/6/ for details.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1517
Lets re-run this with the new Github builders: [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
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1551
RAT check *successful*! See
https://ci.trafficserver.apache.org/job/RAT-github/20/ for details.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1551
clang-format check *successful*! See
https://ci.trafficserver.apache.org/job/clang-format-github/7/ for details.
---
If your project is set up for it, you can reply to this email and
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1550
RAT check *successful*! See
https://ci.trafficserver.apache.org/job/RAT-github/21/ for details.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1550
clang-format check *successful*! See
https://ci.trafficserver.apache.org/job/clang-format-github/8/ for details.
---
If your project is set up for it, you can reply to this email and
Github user masaori335 commented on the issue:
https://github.com/apache/trafficserver/pull/1551
[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
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/issues/1538
I had the same problem until I ran the tests with --sandbox ~/sb
---
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 commented on the issue:
https://github.com/apache/trafficserver/pull/1550
[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 so,
GitHub user taoyunxing opened a pull request:
https://github.com/apache/trafficserver/pull/1552
rectify a minor error in file test_intercept.lua
line 34:
return resp
should be modified as
ts.say(resp)
You can merge this pull request into a Git repository by
GitHub user taoyunxing opened a pull request:
https://github.com/apache/trafficserver/pull/1551
rectify a minor error in test_server_intercept.lua
line 33:
return resp
should modified as
ts.say(resp)
You can merge this pull request into a Git repository by running:
GitHub user taoyunxing opened a pull request:
https://github.com/apache/trafficserver/pull/1550
rectify a minor error in healthchecks.c
line 316:
snprintf(filename, sizeof(filename), "%s/%s", fname, TSConfigDirGet());
should be modified as
snprintf(filename,
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1534
clang-analyzer build *successful*! See
https://ci.trafficserver.apache.org/job/clang-analyzer-github/264/ 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/1534
Linux build *successful*! See
https://ci.trafficserver.apache.org/job/linux-github/1596/ 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/1534
Intel CC build *successful*! See
https://ci.trafficserver.apache.org/job/icc-github/132/ 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/1534
AU check *failed*! See
https://ci.trafficserver.apache.org/job/autest-github/5/ for details.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1534
FreeBSD11 build *failed*! See
https://ci.trafficserver.apache.org/job/freebsd-github/1701/ 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/1534
clang-format check *successful*! See
https://ci.trafficserver.apache.org/job/clang-format-github/6/ for details.
---
If your project is set up for it, you can reply to this email and
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1534
RAT check *successful*! See
https://ci.trafficserver.apache.org/job/RAT-github/19/ for details.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1534
Gonna build it again anyways ... [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
Github user zwoop closed the pull request at:
https://github.com/apache/trafficserver/pull/1521
---
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 atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1534
clang-analyzer build *successful*! See
https://ci.trafficserver.apache.org/job/clang-analyzer-github/263/ for details.
---
If your project is set up for it, you can reply to this email
Github user scw00 commented on the issue:
https://github.com/apache/trafficserver/issues/1531
Based on #1522 we need to ensure that all the handler should handle read
error event and write error event at same time.
I'll track it !
---
If your project is set up for it, you
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1534
Intel CC build *successful*! See
https://ci.trafficserver.apache.org/job/icc-github/131/ 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/1534
Linux build *successful*! See
https://ci.trafficserver.apache.org/job/linux-github/1595/ 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/1534
AU check *successful*! See
https://ci.trafficserver.apache.org/job/autest-github/4/ for details.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1534
RAT check *successful*! See
https://ci.trafficserver.apache.org/job/RAT-github/18/ for details.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1534
clang-format check *successful*! See
https://ci.trafficserver.apache.org/job/clang-format-github/5/ for details.
---
If your project is set up for it, you can reply to this email and
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1534
FreeBSD11 build *failed*! See
https://ci.trafficserver.apache.org/job/freebsd-github/1700/ for details.
---
If your project is set up for it, you can reply to this email and have your
Github user SolidWallOfCode closed the pull request at:
https://github.com/apache/trafficserver/pull/1537
---
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
Github user SolidWallOfCode commented on the issue:
https://github.com/apache/trafficserver/pull/1534
Upon further review of this, #1520, and #1506, I think this is just a bug
fix, in that there was already code in place to report the protocol stack in
the VIA header. Therefore this
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1521
clang-analyzer build *successful*! See
https://ci.trafficserver.apache.org/job/clang-analyzer-github/262/ for details.
---
If your project is set up for it, you can reply to this email
Github user bryancall closed the pull request at:
https://github.com/apache/trafficserver/pull/1522
---
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 atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1521
Linux build *successful*! See
https://ci.trafficserver.apache.org/job/linux-github/1594/ 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/1521
clang-analyzer build *successful*! See
https://ci.trafficserver.apache.org/job/clang-analyzer-github/261/ 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/1521
Intel CC build *successful*! See
https://ci.trafficserver.apache.org/job/icc-github/130/ 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/1521
FreeBSD11 build *successful*! See
https://ci.trafficserver.apache.org/job/freebsd-github/1699/ 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/1521
AU check *successful*! See
https://ci.trafficserver.apache.org/job/autest-github/3/ for details.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1521
RAT check *successful*! See
https://ci.trafficserver.apache.org/job/RAT-github/17/ for details.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1521
clang-format check *successful*! See
https://ci.trafficserver.apache.org/job/clang-format-github/4/ for details.
---
If your project is set up for it, you can reply to this email and
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1521
[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 so,
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1521
Linux build *successful*! See
https://ci.trafficserver.apache.org/job/linux-github/1593/ 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/1521
Intel CC build *successful*! See
https://ci.trafficserver.apache.org/job/icc-github/129/ for details.
---
If your project is set up for it, you can reply to this email and have your
Github user scw00 commented on the issue:
https://github.com/apache/trafficserver/pull/1522
Agree!!
---
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
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1521
FreeBSD11 build *successful*! See
https://ci.trafficserver.apache.org/job/freebsd-github/1698/ 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/1547
AU check *successful*! See
https://ci.trafficserver.apache.org/job/autest-github/2/ for details.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1548
AU check *successful*! See
https://ci.trafficserver.apache.org/job/autest-github/1/ for details.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1521
RAT check *successful*! See
https://ci.trafficserver.apache.org/job/RAT-github/16/ for details.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1521
clang-format check *successful*! See
https://ci.trafficserver.apache.org/job/clang-format-github/3/ for details.
---
If your project is set up for it, you can reply to this email and
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1521
[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 so,
GitHub user pipps opened an issue:
https://github.com/apache/trafficserver/issues/1549
traffic_ctl command to display remap rules
Please add to the **traffic_ctl** command to show remap rules and perhaps
other configuration files, as they are currently loaded by the running
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1537
clang-analyzer build *successful*! See
https://ci.trafficserver.apache.org/job/clang-analyzer-github/260/ 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/1537
Intel CC build *successful*! See
https://ci.trafficserver.apache.org/job/icc-github/128/ 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/1537
Linux build *successful*! See
https://ci.trafficserver.apache.org/job/linux-github/1592/ 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/1537
FreeBSD11 build *successful*! See
https://ci.trafficserver.apache.org/job/freebsd-github/1697/ 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/1537
clang-format check *successful*! See
https://ci.trafficserver.apache.org/job/clang-format-github/2/ for details.
---
If your project is set up for it, you can reply to this email and
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1537
RAT check *successful*! See
https://ci.trafficserver.apache.org/job/RAT-github/15/ for details.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user scw00 commented on the issue:
https://github.com/apache/trafficserver/pull/1522
I believe all of these issue have the same reason. the reproduct is easy.
Run jtest and press Control + C, repeat until you see this assert.
I think, if we merge this pr, that means
Github user SolidWallOfCode commented on the issue:
https://github.com/apache/trafficserver/pull/1537
@maskit For future reference, in your `.bashrc`.
```
function findrst {
find . -name '*.rst' -exec grep "$1" {} \; -print
}
```
Then `findrst basic-auth` in
Github user scw00 commented on the issue:
https://github.com/apache/trafficserver/issues/1544
7.1.0
---
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
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1540
clang-analyzer build *successful*! See
https://ci.trafficserver.apache.org/job/clang-analyzer-github/259/ 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/1540
Intel CC build *successful*! See
https://ci.trafficserver.apache.org/job/icc-github/127/ 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/1540
Linux build *successful*! See
https://ci.trafficserver.apache.org/job/linux-github/1591/ 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/1516
clang-analyzer build *successful*! See
https://ci.trafficserver.apache.org/job/clang-analyzer-github/258/ 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/1540
FreeBSD11 build *successful*! See
https://ci.trafficserver.apache.org/job/freebsd-github/1696/ 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/1540
RAT check *successful*! See
https://ci.trafficserver.apache.org/job/RAT-github/14/ for details.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1540
clang-format check *successful*! See
https://ci.trafficserver.apache.org/job/clang-format-github/1/ for details.
---
If your project is set up for it, you can reply to this email and
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1540
[approve ci] to test the new Github builds jobs configs.
---
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 atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1516
Intel CC build *successful*! See
https://ci.trafficserver.apache.org/job/icc-github/126/ 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/1516
Linux build *successful*! See
https://ci.trafficserver.apache.org/job/linux-github/1590/ 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/1516
clang-analyzer build *successful*! See
https://ci.trafficserver.apache.org/job/clang-analyzer-github/257/ 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/1516
FreeBSD build *successful*! See
https://ci.trafficserver.apache.org/job/freebsd-github/1695/ 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/1546
clang-analyzer build *successful*! See
https://ci.trafficserver.apache.org/job/clang-analyzer-github/256/ 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/1516
RAT check *successful*! See
https://ci.trafficserver.apache.org/job/RAT-github/13/ for details.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user danobi commented on the issue:
https://github.com/apache/trafficserver/pull/1516
@shukitchan, I've updated the documentation.
@SolidWallOfCode @shukitchan, What's the consensus on the max-age change &
private change? For max age, @shukitchan is right, the age
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1516
FreeBSD build *successful*! See
https://ci.trafficserver.apache.org/job/freebsd-github/1693/ 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/1516
Intel CC build *successful*! See
https://ci.trafficserver.apache.org/job/icc-github/125/ for details.
---
If your project is set up for it, you can reply to this email and have your
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1516
I think the FreeBSD failure is because of me, but the Linux failure is
because of clang-format. I'm going to move the clang-format "test" to a
separate build job, which will make this a lot
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1516
FreeBSD build *failed*! See
https://ci.trafficserver.apache.org/job/freebsd-github/1694/ 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/1546
Linux build *successful*! See
https://ci.trafficserver.apache.org/job/linux-github/1588/ 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/1546
Intel CC build *successful*! See
https://ci.trafficserver.apache.org/job/icc-github/124/ 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/1516
RAT check *successful*! See
https://ci.trafficserver.apache.org/job/RAT-github/12/ for details.
---
If your project is set up for it, you can reply to this email and have your
reply
1 - 100 of 155 matches
Mail list logo
