Pip scanning fails with message

[imbeyondboredom]

Issue template

Expected behavior

• Pip scanning completes successfully

  Actual behavior

• Pip scanning fails with this message:

  Running executable >/usr/bin/python /root/blackduck/shared/pip/pip-inspector.py --projectname=toscan
  2018-09-10 19:51:21 INFO  [main-Executable_Stream_Thread] --- Traceback (most recent call last):
  2018-09-10 19:51:21 INFO  [main-Executable_Stream_Thread] ---   File "/root/blackduck/shared/pip/pip-inspector.py", line 30, in <module>
  2018-09-10 19:51:21 INFO  [main-Executable_Stream_Thread] ---     pip_major_version = int(pip.__version__[:2])
  2018-09-10 19:51:21 INFO  [main-Executable_Stream_Thread] --- ValueError: invalid literal for int() with base 10: '1.'
  2018-09-10 19:51:21 INFO  [main] --- Executable finished: 1
  2018-09-10 19:51:21 INFO  [main] --- ------------------------------------------------------------------------------------------------------
  2018-09-10 19:51:21 INFO  [main] --- Finished extraction: FAILURE
  2018-09-10 19:51:21 INFO  [main] --- Code locations found: 0
  2018-09-10 19:51:21 INFO  [main] --- The Pip Inspector tree parser failed to produce output

  Steps to Reproduce

• Below is a dockerfile that will replicate it

Version

4.2.1

Language Version: Python 2.7 Pip 1.5.4

OS:

• Ubuntu

**Here is the docker file that will reproduce it:

FROM openjdk:8-jdk-slim

RUN apt-get update \
    && apt-get upgrade -y \
    && apt-get install -y \
    build-essential \
    ca-certificates \
    gcc \
    git \
    libpq-dev \
    make \
    python-pip \
    python2.7 \
    python2.7-dev \
    ssh \
    && apt-get autoremove \
    && apt-get clean

RUN pip install -U "setuptools==3.4.1"
RUN pip install -U "pip==1.5.4"
RUN pip install -U "Mercurial==2.9.1"
RUN pip install -U "virtualenv==1.11.4"

[stavvy-akamen]

@JakeMathews thoughts on what may cause that type of error? Docker related?

[imbeyondboredom]

I just tried running this again and it looks like it was fixed with https://github.com/blackducksoftware/hub-detect/commit/c10d36c30714f1d18341a8af77608f6d8690a831 but that fix hadn't gone out yet.

I'll close this as I think with the new release it's fixed.