Jason Dellaluce
Jason Dellaluce
refactor!(userspace/falco): remove output rate limiter and make output engine explicitly thread-safe
/milestone 0.33.0
refactor!(userspace/falco): remove output rate limiter and make output engine explicitly thread-safe
> Isn't this a breaking change since stuff from the config file was deleted? I'd expect the "!" in the release notes! You're right. Even if the configuration parsing function...
refactor!(userspace/falco): remove output rate limiter and make output engine explicitly thread-safe
Opened https://github.com/falcosecurity/falco/pull/2139 as an alternative to this PR that puts the rate limiter as optional instead of removing it.
/milestone 0.33.0
Hey @developer-guy, out of curiosity, does this happen on Falco 0.31.0 too?
@developer-guy, did you try leaving a space after `-D`? And also, can you report the error message you're getting? My gut feeling is that this derives from the new library...
I endorse Leo's comment. What do you all think, should we close this?
/milestone 0.33.0
I think Falco 0.33.0 (released in few days) should have this solved! Looking forward to hear more once the release is available!
/kind feature /area engine