You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
hab pkg install conal/iaccess will not download from bldr.habitat.sh. We believe this is related to the size of the package @ ~2.6 GB. Watching the process and network traffic shows that hab never actually starts to pull the package from bldr.
Steps to Reproduce:
hab pkg install conal/iaccess
Expected Result:
This package should download and install successfully like any other package.
This is something we'll investigate for the longer term along with features such as resumable downloads. One option is to use the on-prem builder and configure package sizes to be larger based on individual needs.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you.
I know this is a bit of an older issue ticket, but we discovered that one could bypass the default hab pkg install timeout via setting the HAB_CLIENT_SOCKET_TIMEOUT parameter (in seconds).
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you.
hab
CLI versionhab 0.83.0/20190712231714
Platform Details
Windows 2016 1607 build 14393.3025
Scenario:
hab pkg install conal/iaccess
will not download from bldr.habitat.sh. We believe this is related to the size of the package @ ~2.6 GB. Watching the process and network traffic shows thathab
never actually starts to pull the package from bldr.Steps to Reproduce:
hab pkg install conal/iaccess
Expected Result:
This package should download and install successfully like any other package.
Actual Result:
https://gist.github.com/jmery/f2b758aedef768b6798e99b11106c0ad
The text was updated successfully, but these errors were encountered: