Github user PSUdaemon closed the pull request at:
https://github.com/apache/trafficserver/pull/1541
---
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 PSUdaemon closed the pull request at:
https://github.com/apache/trafficserver/pull/1543
---
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 PSUdaemon opened a pull request:
https://github.com/apache/trafficserver/pull/1543
Remove nullptr instance that was introduced from upstream backport anâ¦
â¦d replace it with NULL.
You can merge this pull request into a Git repository by running:
$ git pull https
Github user PSUdaemon commented on the issue:
https://github.com/apache/trafficserver/pull/1541
@vmamidi
---
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 PSUdaemon closed the pull request at:
https://github.com/apache/trafficserver/pull/1513
---
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 PSUdaemon closed the pull request at:
https://github.com/apache/trafficserver/pull/1539
---
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 PSUdaemon closed the pull request at:
https://github.com/apache/trafficserver/pull/1509
---
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 PSUdaemon closed the pull request at:
https://github.com/apache/trafficserver/pull/1276
---
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 PSUdaemon commented on a diff in the pull request:
https://github.com/apache/trafficserver/pull/1539#discussion_r104324677
--- Diff: iocore/eventsystem/I_EThread.h ---
@@ -56,7 +56,7 @@ enum ThreadType {
DEDICATED,
};
-extern volatile bool
GitHub user PSUdaemon opened a pull request:
https://github.com/apache/trafficserver/pull/1539
Signals fix
This fixed Ubuntu builds but also reverts a commit I just backported
because it was also reverted in master by @zwoop.
You can merge this pull request into a Git repository
Github user PSUdaemon commented on the issue:
https://github.com/apache/trafficserver/pull/1509
Can you rebase this so we can get the Intel build clear? 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
Github user PSUdaemon commented on the issue:
https://github.com/apache/trafficserver/pull/1513
Can you rebase this so we can get the Intel build clear? 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
Github user PSUdaemon closed the pull request at:
https://github.com/apache/trafficserver/pull/1485
---
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 PSUdaemon commented on the issue:
https://github.com/apache/trafficserver/pull/1276
@oknet I think these have been fixed in 6.2.x upstream and you need to
rebase.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user PSUdaemon commented on the issue:
https://github.com/apache/trafficserver/pull/1485
Is the double free related to ICC build issues too?
---
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
Github user PSUdaemon commented on the issue:
https://github.com/apache/trafficserver/pull/1485
[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 PSUdaemon commented on the issue:
https://github.com/apache/trafficserver/issues/1401
I'm not sure there is a core to look at in the case I pasted. It was on a
build host.
---
If your project is set up for it, you can reply to this email and have your
reply appe
Github user PSUdaemon commented on the issue:
https://github.com/apache/trafficserver/issues/1401
I think I am [seeing
this](https://ci.trafficserver.apache.org/job/ubuntu_14_04-6.2.x/compiler=clang,label=ubuntu_14_04,type=release/143/console)
in 6.2.x as well
Github user PSUdaemon closed the pull request at:
https://github.com/apache/trafficserver/pull/1440
---
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 PSUdaemon commented on a diff in the pull request:
https://github.com/apache/trafficserver/pull/1440#discussion_r100867264
--- Diff: lib/raft/raft_impl.h ---
@@ -338,8 +338,8 @@ template class RaftImpl : public
Raft
if (!i_am_leader())
return
GitHub user PSUdaemon opened a pull request:
https://github.com/apache/trafficserver/pull/1440
Remove nullptr instances that were introduced from upstream backportsâ¦
⦠and replace them with NULL.
You can merge this pull request into a Git repository by running:
$ git pull
Github user PSUdaemon commented on the issue:
https://github.com/apache/trafficserver/pull/1276
@oknet What is the plan with this 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
Github user PSUdaemon closed the pull request at:
https://github.com/apache/trafficserver/pull/1395
---
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 PSUdaemon commented on the issue:
https://github.com/apache/trafficserver/pull/1395
[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 PSUdaemon closed the pull request at:
https://github.com/apache/trafficserver/pull/1410
---
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 PSUdaemon commented on the issue:
https://github.com/apache/trafficserver/pull/1410
[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 PSUdaemon closed the pull request at:
https://github.com/apache/trafficserver/pull/1436
---
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 PSUdaemon commented on the issue:
https://github.com/apache/trafficserver/pull/1430
@shenzhang920 you need to rebase, not merge. I don't want to back port a
merge commit. I think your mistake is that you did this directly on the 6.2.x
branch. You really should
Github user PSUdaemon closed the pull request at:
https://github.com/apache/trafficserver/pull/1321
---
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 PSUdaemon commented on the issue:
https://github.com/apache/trafficserver/pull/1430
[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 PSUdaemon closed the pull request at:
https://github.com/apache/trafficserver/pull/1406
---
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 PSUdaemon commented on the issue:
https://github.com/apache/trafficserver/pull/1321
@jablko can you please rebase this?
---
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 PSUdaemon commented on the issue:
https://github.com/apache/trafficserver/pull/1395
@jaaju can you please rebase this?
---
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 PSUdaemon commented on the issue:
https://github.com/apache/trafficserver/pull/1321
[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 PSUdaemon commented on the issue:
https://github.com/apache/trafficserver/pull/1395
[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 PSUdaemon commented on the issue:
https://github.com/apache/trafficserver/pull/1410
@maskit can you please rebase this?
---
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 PSUdaemon commented on the issue:
https://github.com/apache/trafficserver/pull/1430
@shenzhang920 can you rebase this?
---
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 PSUdaemon commented on the issue:
https://github.com/apache/trafficserver/pull/1406
@jrushford Can you rebase this to 6.2.x?
---
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 PSUdaemon commented on the issue:
https://github.com/apache/trafficserver/pull/1430
[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 PSUdaemon commented on the issue:
https://github.com/apache/trafficserver/pull/1406
[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 PSUdaemon closed the pull request at:
https://github.com/apache/trafficserver/pull/1434
---
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 PSUdaemon opened a pull request:
https://github.com/apache/trafficserver/pull/1434
Clang fixes
This is a back-port PR of various clang-analyzer fixes.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/PSUdaemon
Github user PSUdaemon commented on the issue:
https://github.com/apache/trafficserver/pull/1293
Yes, it's essentially the same build process, it just catches bad commits
from getting into the tree instead of fixing them afterward. Makes things like
`git bisect` work better.
-
Github user PSUdaemon commented on the issue:
https://github.com/apache/trafficserver/pull/1293
No, that is correct. Though I noticed that CI never properly ran. We
usually make sure that runs successfully before merging.
---
If your project is set up for it, you can reply to this
Github user PSUdaemon commented on a diff in the pull request:
https://github.com/apache/trafficserver/pull/1294#discussion_r94471863
--- Diff: iocore/net/BIO_fastopen.cc ---
@@ -27,13 +27,26 @@
#include "BIO_fastopen.h"
+#if OPENSSL_VERS
Github user PSUdaemon commented on a diff in the pull request:
https://github.com/apache/trafficserver/pull/1294#discussion_r94472934
--- Diff: iocore/net/BIO_fastopen.cc ---
@@ -27,13 +27,26 @@
#include "BIO_fastopen.h"
+#if OPENSSL_VERS
Github user PSUdaemon commented on the issue:
https://github.com/apache/trafficserver/pull/1295
[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 PSUdaemon commented on the issue:
https://github.com/apache/trafficserver/pull/1294
[approve ci]
@zwoop shouldn't these be auto-running the CI for @jablko?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitH
Github user PSUdaemon commented on the issue:
https://github.com/apache/trafficserver/pull/1293
[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 PSUdaemon commented on a diff in the pull request:
https://github.com/apache/trafficserver/pull/1294#discussion_r94357370
--- Diff: iocore/net/BIO_fastopen.cc ---
@@ -27,13 +27,26 @@
#include "BIO_fastopen.h"
+#if OPENSSL_VERS
Github user PSUdaemon closed the pull request at:
https://github.com/apache/trafficserver/pull/1050
---
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 PSUdaemon commented on the issue:
https://github.com/apache/trafficserver/pull/1050
We feel this has been solved by #1097. Please open a new PR if you feel
this is not the case.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user PSUdaemon commented on the issue:
https://github.com/apache/trafficserver/pull/981
What was the underlying OS?
---
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 user PSUdaemon commented on the issue:
https://github.com/apache/trafficserver/pull/981
I'll try to rebase this soon.
---
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 fe
Github user PSUdaemon commented on the issue:
https://github.com/apache/trafficserver/pull/981
@jpeach can you elaborate on which platform it was that didn't have hwloc?
If not, we are going to try to get this in still.
---
If your project is set up for it, you can reply to
Github user PSUdaemon closed the pull request at:
https://github.com/apache/trafficserver/pull/966
---
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 PSUdaemon commented on the issue:
https://github.com/apache/trafficserver/pull/776
@caricaturecm Any update on this?
---
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 user PSUdaemon closed the pull request at:
https://github.com/apache/trafficserver/pull/1266
---
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 PSUdaemon opened a pull request:
https://github.com/apache/trafficserver/pull/1266
TS-5087: Updates the AL2 license on all .po files
Fixes for 6.2.x branch that were not upstream.
You can merge this pull request into a Git repository by running:
$ git pull https
Github user PSUdaemon closed the pull request at:
https://github.com/apache/trafficserver/pull/1265
---
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 PSUdaemon closed the pull request at:
https://github.com/apache/trafficserver/pull/1244
---
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 PSUdaemon commented on the issue:
https://github.com/apache/trafficserver/pull/1258
@jpeach, that doesn't sound like a bad idea, but I don't think it should be
a requirement to get this in. The Comcast implementation is entirely open
source as well, so this isn&
Github user PSUdaemon commented on the issue:
https://github.com/apache/trafficserver/pull/1242
I followed this into a rat hole trying to do it the right way. Seems like
an #ifdef hack is the best option at this point.
---
If your project is set up for it, you can reply to this
Github user PSUdaemon closed the pull request at:
https://github.com/apache/trafficserver/pull/1242
---
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 PSUdaemon opened a pull request:
https://github.com/apache/trafficserver/pull/1242
TS-5060: Switch to NS_MAXDNAME
This is a followup to #1241 that fixes a compile issue on OSX.
You can merge this pull request into a Git repository by running:
$ git pull https
Github user PSUdaemon commented on the issue:
https://github.com/apache/trafficserver/pull/1050
@zwoop: #1097 addresses it as best I think we can.
---
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
Github user PSUdaemon commented on the issue:
https://github.com/apache/trafficserver/pull/1050
Should we close this 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 this feature
enabled
Github user PSUdaemon closed the pull request at:
https://github.com/apache/trafficserver/pull/1236
---
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 PSUdaemon closed the pull request at:
https://github.com/apache/trafficserver/pull/1241
---
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 PSUdaemon commented on the issue:
https://github.com/apache/trafficserver/pull/1241
I'd squash these commits, but this looks good.
---
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
Github user PSUdaemon commented on the issue:
https://github.com/apache/trafficserver/pull/1221
Ok, sounds good. I'll hold off on cutting 6.2.1 for a bit longer.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user PSUdaemon commented on the issue:
https://github.com/apache/trafficserver/pull/1221
Do we still need this now that #1232 is merged?
---
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
Github user PSUdaemon closed the pull request at:
https://github.com/apache/trafficserver/pull/1232
---
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 PSUdaemon commented on the issue:
https://github.com/apache/trafficserver/pull/1232
[approve ci]
@shinrich can you give this a look over and check to see if you think it
looks ok as a backport?
Thanks.
---
If your project is set up for it, you can reply
Github user PSUdaemon closed the pull request at:
https://github.com/apache/trafficserver/pull/1231
---
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 PSUdaemon opened a pull request:
https://github.com/apache/trafficserver/pull/1231
TS-4720 back port
HttpTransact defaults content length to `-1`, meaning that if the request
has no content length header it will be `-1`. These checks weren't taking that
Github user PSUdaemon closed the pull request at:
https://github.com/apache/trafficserver/pull/1215
---
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 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
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
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
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
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
Github user PSUdaemon closed the pull request at:
https://github.com/apache/trafficserver/pull/1205
---
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 PSUdaemon closed the pull request at:
https://github.com/apache/trafficserver/pull/1204
---
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 PSUdaemon closed the pull request at:
https://github.com/apache/trafficserver/pull/1203
---
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 PSUdaemon closed the pull request at:
https://github.com/apache/trafficserver/pull/1200
---
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 PSUdaemon closed the pull request at:
https://github.com/apache/trafficserver/pull/1199
---
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 PSUdaemon closed the pull request at:
https://github.com/apache/trafficserver/pull/1206
---
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 PSUdaemon opened a pull request:
https://github.com/apache/trafficserver/pull/1206
TS-4838: CONNECT requests get forgotten across threads.
What happens here is that ProxyClientTransaction::adjust_thread
reschedules the transaction onto a new thread at the start of
Github user PSUdaemon commented on the issue:
https://github.com/apache/trafficserver/pull/1200
I mean don't add `(backport for 6.2.x)` to the existing commit message.
It's superfluous.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user PSUdaemon commented on the issue:
https://github.com/apache/trafficserver/pull/1200
When you do the backports can you leave the commit messages the same except
for the cherry pick comment and the conflicts?
---
If your project is set up for it, you can reply to this
Github user PSUdaemon commented on the issue:
https://github.com/apache/trafficserver/pull/1198
[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 PSUdaemon closed the pull request at:
https://github.com/apache/trafficserver/pull/1189
---
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 PSUdaemon closed the pull request at:
https://github.com/apache/trafficserver/pull/1183
---
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 PSUdaemon closed the pull request at:
https://github.com/apache/trafficserver/pull/1196
---
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 PSUdaemon closed the pull request at:
https://github.com/apache/trafficserver/pull/1195
---
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 PSUdaemon closed the pull request at:
https://github.com/apache/trafficserver/pull/1194
---
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 PSUdaemon commented on the issue:
https://github.com/apache/trafficserver/pull/1091
@jpeach you planning on doing any more with this?
---
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
Github user PSUdaemon closed the pull request at:
https://github.com/apache/trafficserver/pull/1182
---
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 PSUdaemon closed the pull request at:
https://github.com/apache/trafficserver/pull/1188
---
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
1 - 100 of 267 matches
Mail list logo
