-
Notifications
You must be signed in to change notification settings - Fork 119
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
Remove setting that's no longer needed #127
Conversation
I'm expecting CI to fail until the Kibana change is available in the Docker image. So let's keep this PR open and re-run CI until it passes consistently. |
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.
I'm happy to see if it fixes the issue!
/test |
Unfortunately not yet :( |
/test |
@ycombinator Shouldn't this PR be passing? It's already a couple of days. |
@mtojek It looks like the backport of the Kibana PR was merged 2 days ago: elastic/kibana#79657. I pulled down the latest Kibana |
/test |
CI is failing with this error:
Will investigate tomorrow (Monday). |
Looks like I fixed it in #133 /test |
/test |
It looks like it's still failing:
I'm confused with the release cycle here... |
Yeah, I don't know why this is still failing. Looks like |
@nchaulet Would you mind taking a look again at this? |
Could you please rebase it against master? There were couple of breaking changes in the mean time. |
7a8794b
to
4d0899f
Compare
Closing in favor of #139. |
Now that elastic/kibana#77613 has been resolved, we can get rid of the workaround added in #111.