Open ispielma opened 1 year ago
Do you have any more info what happened? Precise error messages or something like that?
Without a reply by @ispielma this should just be closed, I think?
The bug seems (or seemed) to crop up when I have a slow internet connection (working with phone tethering in remote locations).
In those cases I was able to manually get the download to work using wget from the command line, but curl would fail. So this is really a curl issue. I would suggest either switching the default, or making it trivial for the user to select which is used (maybe such a change has already been made).
Ian B. Spielman
Fellow, Joint Quantum Institute National Institute of Standards and Technology and the University of Maryland
----- WEB ----- http://ultracold.jqi.umd.edu
----- EMAIL ----- @.***
----- ZOOM ----- https://umd.zoom.us/j/7984811536
----- PHONE ----- (301) 246-2482
----- MAIL ----- UMD: 2207 Computer & Space Sciences Bldg. College Park, MD 20742
NIST: 100 Bureau Drive, Stop 8424 Gaithersburg, MD 20899-8424 USA
----- OFFICE ----- UMD: Physical Sciences Complex, Room 2153 NIST: Building 216, Room B131
On Jan 5, 2024, at 07:25, Max Horn @.***> wrote:
Without a reply by @ispielma this should just be closed, I think? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>
Thanks for the explanation! Hmm, PR #780 might help a bit, as it enables --retry
for curl, which helps with flaky connections
Following the instructions on the git page to install on a fresh ubuntu image (VM running in vmware fusion on intel mac) failed (the curl download worked but the script failed in the downloader function).
I was able to resolve the issue by forcing the downloader function to use wget rather than the default curl. This odd because as noted above curl worked fine from the command line to pull the install script.