Closed rodrigues closed 8 years ago
Hehe, I know of these messages but they are actually not a "problem" per se.
If you look around some travis builds of various projects (phoenixframework, poison, earmark, ... -> google search) you can see them appear all over the place once HTTPS is involved. As far as I can tell mostly in combination with Mix.Utils.read_path/1,2
. Even mix hex.local --force
sometimes triggers these messages.
Once the file is returned mix calls :inets.stop(:httpc, :mix)
and that seems to trigger a race condition with the internal SSL session update. While that seems like something is wrong nothing happened but a failed update to a no longer existing session. The internal pattern match on { :ok, file_contents }
in the download module should catch any real error if one occurs.
I will look into a way around this by handling the :httpc
connection without mix. Until then you should be fine ignoring these messages as long as you see the "Download complete!" at the end.
Got it, thanks @mneudert!
In another machine, I didn't have any of these alerts btw. 👍
As some sort of fyi:
I have switched the method to download the database files from mix to hackney. This should work as previously (except you have to configure any proxies yourself) while preventing any log entries you encountered.
Files seems to be downloaded correctly in the end, but many errors are logged on console when running the database download.
Tried with latest version on hex, also with github master.