Closed stephentu closed 9 years ago
picos is a new package i'm trying to create. its meta.yaml looks like
package:
name: picos
version: !!str 1.0.1
source:
fn: PICOS-1.0.1.tar.gz
url: http://picos.zib.de/dist/PICOS-1.0.1.tar.gz
md5: f499ca5ef81118a84ddf68eb4caf3547
requirements:
build:
- python
- setuptools
run:
- python
- numpy
- cvxopt
test:
imports:
- picos
about:
home: http://picos.zib.de/index.html
license: GPL
summary: 'Python Interface for Conic Optimization Solvers'
I think this happens when the headers for the file give the wrong file size. We should probably protect against it.
I can also recreate this problem. This is non-essential information that is breaking conda build. Perhaps we can ignore when we exceeding the limit and instead set the value to self.maxvalue when it is in violation? Perhaps a logging.WARN message when this happens so it is still noted?
https://github.com/conda/conda/blob/master/conda/progressbar/__init__.py#L268-L271
if (self.maxval is not UnknownLength
and not 0 <= value <= self.maxval):
raise ValueError('Value out of range')
@stephentu The current workaround is to use conda build --quiet <recipe>
to disable the progressbar output.
For reference, this is coming up for mpc, at the URL http://www.multiprecision.org/mpc/download/mpc-1.0.1.tar.gz, which has the headers:
{
'Content-Encoding': 'gzip',
'Content-Length': '624125',
'Content-Type': 'application/x-tar',
}
The length is correct, but it's the gzipped bytes, and requests is helpfully unzipping them. So the content size is the gzipped size, but the counter is updating the tar size, which is the actual file conda is downloading.
Hi there, thank you for your contribution!
This issue has been automatically locked because it has not had recent activity after being closed.
Please open a new issue if needed.
Thanks!
output of
conda info