Update README for migration to travis-ci.com, and copyright #442
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pulltab
previously approved these changes
Jun 8, 2018
pulltab
approved these changes
Jun 8, 2018
Codecov Report
@@ Coverage Diff @@
## master #442 +/- ##
==========================================
+ Coverage 92.07% 92.09% +0.02%
==========================================
Files 29 29
Lines 4037 4037
==========================================
+ Hits 3717 3718 +1
+ Misses 320 319 -1 |
pulltab
added a commit
that referenced
this pull request
Jun 12, 2018
* Open up 0.8.18-pre development This commit contains a small update to the Dockerfile but is otherwise just here to bump the Cargo.toml version number. Signed-off-by: Brian L. Troutwine <blt@postmates.com> * Remove the kinesis and firehose sink (#437) This commit removes the Kinesis and Firehose sinks, long since disused by and cernan users I was able to find. The primary motivation is not the lack of use but the difficulty of upgrading to a new version of rusoto as we've let this sit for a while. This commit opens the 0.9.0 series. These sinks will continue to be supported in the 0.8 series. Signed-off-by: Brian L. Troutwine <blt@postmates.com> * Adjust hyper -> reqwest, introduce file source byte limits I'm hunting a leak folks are reporting in k8s-land. The leak, maybe, is a result of us tracking file limits by lines, rather than by specific byte totals. The configuration of the file source is now adjusted to use 'max_read_bytes' and not 'max_lines_read' as in 0.8. Also, I have now removed the explicit dependency on hyper. We rely entirely on reqwest in the influxdb sink. Signed-off-by: Brian L. Troutwine <blt@postmates.com> * Clippy fiddling This commit contains suggestions from clippy, no actual changes or leak results. I'm being told that the file change, while helpful, is not resolving the issue. Which, that implies some other area of unbounded growth. Signed-off-by: Brian L. Troutwine <blt@postmates.com> * Cap nonblocking::BufferedPayload allocations The BufferedPayload reader would allocate any size the user requested, no matter how large. This is not great, it turns out, when the user is sending us nonsense. The payloads are now capped at 1Mb. This should be made configurable. Signed-off-by: Brian L. Troutwine <blt@postmates.com> * Explicitly set timestamps for kafka record producer (#441) * Update README for migration to travis-ci.com, and copyright (#442) * Bump to 0.9.0. (#443)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.