Update all unattributed TODOs to TODO(mattklein123)#529
Update all unattributed TODOs to TODO(mattklein123)#529mattklein123 merged 7 commits intoenvoyproxy:masterfrom
Conversation
|
Though as I said in gitter, this information is available more accurately via "git blame", if you want to do this let's use accurate GH user names, so it would be "mattklein123". |
|
I'm lazy and shelling out and waiting for blame harshes my mojo. Plus this is refactor proof so you don't get blamed just because you moved some lines around. |
mattklein123
left a comment
There was a problem hiding this comment.
some typos and you need to run clang-format
source/common/filter/tcp_proxy.cc
Outdated
| // is about to go away. So to support this we need to either have a way for the downstream | ||
| // connection to stick around, or, we need to be able to pass this connection to a flush | ||
| // worker which will attempt to flush the remaining data with a timeout. | ||
| // TODO(mklein23): If we close without flushing here we may drop some data. The downstream |
| // TODO: If a filter returns StopIterationNoBuffer and then does a continue, we won't be able to | ||
| // end the stream if there is no buffered data. Need to handle this. | ||
| // TODO(mattklein123): If a filter returns StopIterationNoBuffer and then does a continue, we | ||
| // won't be able to end the stream if there is no buffered data. Need to handle this. |
source/common/filter/tcp_proxy.cc
Outdated
| // TODO(mklein23): If we close without flushing here we may drop some data. The downstream | ||
| // connection is about to go away. So to support this we need to either have a way for the | ||
| // downstream connection to stick around, or, we need to be able to pass this connection to a | ||
| // flush worker which will attempt to flush the remaining data with a timeout. |
| // it should be appended to. In that case, we would do an append here. We can do this in | ||
| // a follow up. | ||
| // TODO(mattklein123): Currently, for all of the inline headers, we don't support appending. The | ||
| // only inline header where we should be converting multiple headers into a comma delimited |
There was a problem hiding this comment.
typo extra space here and below
|
I'm bumbling my way through remembering the github workflow. Sorry you're on the receiving end. |
source/common/filter/tcp_proxy.cc
Outdated
| // connection is about to go away. So to support this we need to either have a way for the | ||
| // downstream connection to stick around, or, we need to be able to pass this connection to a | ||
| // flush worker which will attempt to flush the remaining data with a timeout. | ||
| // TODO(mattklein23): If we close without flushing here we may drop some data. The downstream |
source/common/filter/tcp_proxy.cc
Outdated
| // is about to go away. So to support this we need to either have a way for the downstream | ||
| // connection to stick around, or, we need to be able to pass this connection to a flush | ||
| // worker which will attempt to flush the remaining data with a timeout. | ||
| // TODO(mattklein23): If we close without flushing here we may drop some data. The downstream |
There was a problem hiding this comment.
mattklein23 -> mattklein123
test/integration/integration_test.cc
Outdated
| [&]() -> void { fake_upstream_connection->waitForData(10); }, | ||
| [&]() -> void { fake_upstream_connection->waitForDisconnect(); }}); | ||
| } | ||
| == network/connection_impl.cc == |
There was a problem hiding this comment.
You probably already saw this, but FYI some editor issue here.
There was a problem hiding this comment.
I just saw this. I have no idea what happened because I ran the CI before pushing but apparently totally scrambled the file between step 1 and 2. Sigh.
|
@tschroed there is still one typo then looks good. |
|
@tschroed also please sign the CLA: https://github.com/lyft/envoy/blob/master/CONTRIBUTING.md#cla |
|
CLA signed. Typo corrected. Thanks for your infinite patience. Next time will be smoother, promise. |
* Add 'fail_open' configuration option for Wasm plugins. Signed-off-by: John Plevyak <jplevyak@gmail.com>
Signed-off-by: Michael Rebello <me@michaelrebello.com> Signed-off-by: JP Simard <jp@jpsim.com>
Signed-off-by: Michael Rebello <me@michaelrebello.com> Signed-off-by: JP Simard <jp@jpsim.com>
**Commit Message** Fix APISchema to support response_format. **Related Issues/PRs (if applicable)** Related PR: #445 --------- Signed-off-by: Xiaolin Lin <xlin158@bloomberg.net>
Quoting the style guide:
TODOs should include the string TODO in all caps, followed by the username or b/buganizer_id of the person or issue with the best context about the problem referenced by the TODO. The main purpose is to have a consistent TODO that can be searched to find out how to get more details upon request. A TODO is not a commitment that the person referenced will fix the problem. Thus when you create a TODO with a name, it is almost always your name that is given.