-
Notifications
You must be signed in to change notification settings - Fork 100
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
Error while upgrading from v1.10.0 to 1.10.1 #150
Comments
As the versions has several commits, I tried to check by commit individually :
And the error occur at b742e39 So my it's not related to OTP (#138). I'll check to get a better understanding on what happen. From the console : iex(0)>NewRelic.Config.enabled?()
false
iex(1)>payload = NewRelic.Harvest.Collector.Connect.payload()
iex(2)>NewRelic.Harvest.Collector.Protocol.connect(payload)
{:error, :harvest_disabled} Seem that this error is not handle |
Thanks, I'll take a look today |
Hi, I was able to reproduce this by running against OTP 20. It's caused because I'll see what I can do to get the OTP version requirements front and center so this can't happen... Can you upgrade your OTP version? |
This PR will raise a helpful error if the app is started pre OTP 21 #151 |
Thank you. I get a better understanding now. I wondering what was the
😱 😢 😨 I'm afraid but this will not be possible in my case. I'll try to find an alternative solution (maybe fork the gem and reimplement the AgentRun to OTP 20). |
FYI, the upcoming Elixir |
Environment :
elixir -v
):Describe the bug
Error while upgrading from v1.10.0 to 1.10.1 with a minimal configuration (just the minimal on the readme) without changing anything except the following :
Changes :
mix deps | grep new_relic_agent
):mix deps | grep new_relic_agent
):Generate the following error :
Any ideas ?
Can it be related to #138 ?
The text was updated successfully, but these errors were encountered: