-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Fix logrus dependency #10791
Fix logrus dependency #10791
Conversation
Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually? |
@sayden we are not using logrus directly, but it is a transitive dependency of some other packages we use, we should probably upgrade it if it has been fixed upstream. |
I think we should fix this so that we can unblock the usage of
But there are two other projects that would need to be updated because they depend on the
@exekias @jsoriano I vaguely recall some reason that updating the docker packages could cause problems? Do either of you know more? If going to the head of docker/docker is problematic maybe we could at least move forward to moby/moby@1009e6a. |
I think we are using a patched version with this commit? exekias/moby@83d94aa. I don't know about the status upstream |
@andrewkroh would the changes done by @kvch in #11330 fix this? |
My PR is fixing this issue, as I have completely removed |
@kvch I'm glad you fixed this. I was looking at an older tag and I didn't realize this was fixed on master. With that being said I'm still getting an error while attempting to use
|
Closing logrus was fixed by #11330. |
This will fix the issue #4642
As mentionned, the uppercase letter creates unexpected module path error using
go mod
command.As we can see from logrus repository sirupsen/logrus#570, others libraries have also fixed the issue at their side.