-
Notifications
You must be signed in to change notification settings - Fork 0
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
Support list patterns #1
base: master
Are you sure you want to change the base?
Conversation
b0c3bec
to
5f8023b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me
e6b7762
to
3b772db
Compare
a26004a
to
12e270c
Compare
…ecution-engine remove ruby pipeline dependency
…ecution-engine fix bump version
* Fix: do not rely on redis.client anymore * Test: redo specs with 'real' Redis mocking * Refactor: cleanup plugin (internals) Co-authored-by: Ry Biesemeyer <[email protected]>
Redis doesn't wrap all of the errors e.g. (retriable) IOError might be raised from an IO write (logstash-plugins#88). With the refactored error handling we make sure these are logged and retried instead of causing pipeline crashes. Also not all specs from the suite were run on the CI, as some are tagged with redis. These require a real Redis server, no reason not to run them against CI as well.
a4fb749
to
40c52e9
Compare
This branch seems to hold the most up to date stuff from master (now main) even today. |
Well hello! Note btw that there's still an upstream PR open: logstash-plugins#81 . You might want to subscribe to it in case anyone ever picks it up 😅 |
Hi, any plans to add logstash-plugins#81 to master in the near future ? Its been a while waiting for merge now ? |
WIP