Matthew Fala

The easiest way to reproduce may be to run fluent bit with the above config and send the following string payload with curl: ``` curl -X POST http://localhost:8888/app.log \ -H...

It looks like the crash is caused by a call to GetRecord() on the output_plugin's input which appears to contain encoded content from Fluent Bit's core. https://github.com/aws/amazon-cloudwatch-logs-for-fluent-bit/blob/mainline/fluent-bit-cloudwatch.go#L174 The scope of...

Please feel free to reach out to me if you have any questions on how to use the AWS networking mock api. Please just add @matthewfala to your messages to...

The check was originally added for developers out of concern that they might give the IMDS client some misconfigured upstream. I didn't realize that the proxy settings could alter the...

@zhenyami, this change is significant! It's clear you put effort into understanding the event loop system and making appropriate changes. @edsiper It seems that this is a legitimate problem with...

@leonardo-albertovich Is there any progress on reviewing this PR. Seems like an important fix to a bug in the event loop. Not sure how widespread issues that may arise might...

Please also see: https://github.com/fluent/fluent-bit/issues/4257

Alternately, compromising between options 1 and 2, we could write some middleware that handles chunk splitting and chunk fragment retries and wraps the flush function. This could potentially limit changes...

We concluded our Root Cause Analysis of the segfault issue. ## When does the problem happen The problem arises when tags are used in fluent bit with a length greater...

The solution which is the updated chunkio dependancy is merged to master, but not yet merged to 1.9. Please see: https://github.com/fluent/fluent-bit/pull/6027/files#diff-6d93018de0498b8880ec696aace9998ad0fe5a16008697f7a122910327c7ed30R78-R79 Looks like we're on track to release in 2.0,...