Filterx function framework + example #18
Closed
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
Signed-off-by: Balazs Scheidler <[email protected]>
Signed-off-by: Balazs Scheidler <[email protected]>
Signed-off-by: Balazs Scheidler <[email protected]>
Signed-off-by: Balazs Scheidler <[email protected]>
The lexer drops whitespace and leading commas but they should not make it into token values. Signed-off-by: Balazs Scheidler <[email protected]>
…xer level Previously everything was captured as LL_IDENTIFIER, operators as well, and then mapped to tokens using the keyword mechanism. Since I'd like to make the LL_IDENTIFIER pattern stricter, that wouldn't allow typical operator characters into LL_IDENTIFIERS, so these should be recognized at the lexer level. NOTE: this does not include the spelled out operators like "lt" for "<", those remain LL_IDENTIFIER and are continued to be mapped using the keyword mechanism. Signed-off-by: Balazs Scheidler <[email protected]>
Signed-off-by: Balazs Scheidler <[email protected]>
Signed-off-by: Balazs Scheidler <[email protected]>
Signed-off-by: Balazs Scheidler <[email protected]>
Some objects can be used by multiple threads (e.g. the ones created as literals during configuration parsing). Our ref count is not atomic and I don't intend to make it one. By making an object "frozen" it's reference count is set to an extremal value and from then on, ref/unref does not change the refcount. Signed-off-by: Balazs Scheidler <[email protected]>
Signed-off-by: Balazs Scheidler <[email protected]>
Signed-off-by: Balazs Scheidler <[email protected]>
Signed-off-by: Balazs Scheidler <[email protected]>
Signed-off-by: Balazs Scheidler <[email protected]>
Signed-off-by: Balazs Scheidler <[email protected]>
Signed-off-by: Balazs Scheidler <[email protected]>
Signed-off-by: Balazs Scheidler <[email protected]>
Signed-off-by: Balazs Scheidler <[email protected]>
Signed-off-by: Balazs Scheidler <[email protected]>
Signed-off-by: Balazs Scheidler <[email protected]>
Signed-off-by: Balazs Scheidler <[email protected]>
Signed-off-by: Balazs Scheidler <[email protected]>
Signed-off-by: Balazs Scheidler <[email protected]>
Signed-off-by: Balazs Scheidler <[email protected]>
Signed-off-by: Balazs Scheidler <[email protected]>
Signed-off-by: Balazs Scheidler <[email protected]>
These objects may be used by multiple threads, as they are allocated at parsing time. Make sure they don't get freed, nor do we race on their ref_cnt by freezing them. Signed-off-by: Balazs Scheidler <[email protected]>
Signed-off-by: Balazs Scheidler <[email protected]>
Signed-off-by: Balazs Scheidler <[email protected]>
`node_to_insert` seems to only contain a single patterndb expression in all other examples, so align with them. Signed-off-by: Romain Tartière <[email protected]>
When parsing a message, NLSTRING stops when it finds a `\n` char. If the message does not contain any `\n` char, the matching fail and the message portion is not matched. However, the documentation says that: > For single-line messages, NLSTRING is equivalent with ANYSTRING In order to match what the documentation say, we need to not return an error when `\n` is not found, and instead capture the end of the message. Signed-off-by: Romain Tartière <[email protected]>
Sometimes we are casting strings with an explicit length value, but the type hinting code simply assumed that everything was NUL terminated, which is not the case for indirect values. Signed-off-by: Balazs Scheidler <[email protected]> Signed-off-by: shifter <[email protected]>
… to follow Signed-off-by: Balazs Scheidler <[email protected]>
Signed-off-by: Balazs Scheidler <[email protected]>
Signed-off-by: Balazs Scheidler <[email protected]>
As it has significant overhead. Do it a few times every second. Signed-off-by: Balazs Scheidler <[email protected]>
Signed-off-by: Balazs Scheidler <[email protected]>
Signed-off-by: Balazs Scheidler <[email protected]>
Signed-off-by: shifter <[email protected]>
Signed-off-by: shifter <[email protected]>
Signed-off-by: shifter <[email protected]>
Signed-off-by: shifter <[email protected]>
bazsi
force-pushed
the
filter-expr-language
branch
5 times, most recently
from
1681932
to
b29ccba
Compare
bazsi
pushed a commit
that referenced
this pull request
May 17, 2024
axosyslog-collector: add image.extraArgs
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.