-
Notifications
You must be signed in to change notification settings - Fork 134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Patch RFC3339 formatting to remove incomplete writer type #541
Conversation
Sorry about that! I'm not a Go programmer, as it's plenty obvious. |
@mterron No worries, it is the nature of programming.
You are correct, and I also believe the In my PR so far I've removed the extra 0-byte writes by doing the timestamp replace in line but I'm actually duplicating the timestamp right now. I need to fix that before merging. I feel like we're going to rip out |
I've added a configurable attribute for the timestamp (for future clarification). The following Dtrace confirms the 0-byte writes are gone and fluentd logging is functioning properly.
|
Ok, this is going to get released ASAP. |
Ref: #540
I believe this patch fixes the issues surrounding an incomplete community contribution. The problem is that the bytes returned from the buffer are never actually utilized (the buffer is only init'd as 0-byte and never used). Also, logging (
fmt.Print
) was being handled by the defunct writer type itself and not properly through Logrus as it was before the commit. I've removed the cruft and attempted to keep the formatting.I need to run tests and verify that this doesn't have any other residuals first but this will make a quick patch release for 3.6.2 by EOW.