-
Notifications
You must be signed in to change notification settings - Fork 37
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
Conflicting dependencies with prometheus_ex
#11
Comments
yes, override will work |
@deadtrickster I hadn't seen #10 - I guess that will solve it as well |
@ecly what are the steps to override it? |
@epinault throw the following in your mix.exs, causing all others deps depending on prometheus to use the following version: |
ah thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Forgive me if there is a reason for this, but at the moment there is a dependency conflict for
prometheus
versions betweenprometheus_ex
andprometheus_process_collector
.Following deps:
{:prometheus_ex, "~> 3.0.2"}
{:prometheus_process_collector, "~> 1.3.1"}
Results in:
For the time being i'll try overriding it to 4.0 and see if that works.
The text was updated successfully, but these errors were encountered: