leonardo-albertovich
leonardo-albertovich
I think some of those settings catered some very specific corner cases and weren't meant for general usage.
Yes @nkinkade that setting would cause fluent-bit to prefer ipv4 records any time both ipv4 and ipv6 records are available. It **doesn't** mean it it will stop using ipv6 if...
This seemed correct to me at the time and think it makes no sense to keep stalling it. Could we do a quick recap so we can give it closure?...
Good news everyone! In order to be confident enough to back your PR I wrote a quick PoC to demonstrate the value expansion issue I commented in my previous message...
I noticed that you are running in TRACE level but I don't see much there, would you be able to share the complete log file? Also, maybe someone else remembers...
I don't know about the PR but a while ago while working in the downstream provider I created both a UDS and UDP input plugins. These were created for testing...
This should get you going : ``` [INPUT] name udp listen 127.0.0.1 port 9990 [INPUT] name udp listen 127.0.0.1 port 9991 format none [INPUT] name udp listen 127.0.0.1 port 9992...
I'm sure it would be highly appreciated.
I'll take a look, thanks for letting us know it's still a problem.
Definitely, it'd be great if you can double check it since that'd save me a bit of time trying to reproduce it in case it's fixed. Thanks for staying on...