Ah, yes, I should've mentioned. lang/py supports python3 in master and I am looking to deprecate lang/py3 eventually.
We also need to drop support for py27 at some point. But for now, lang/py supports 2.7, 3.5, and up. On Fri, Feb 14, 2020 at 13:15 Jacob Tolar <[email protected]> wrote: > I see that tox is set up for py2 but not py3. > > You might just try, from the lang/py3 directory: > > python3 setup.py test > > But, you probably want to make any changes to lang/py, not lang/py3. > Per AVRO-2656 and discussion on this list there are plans to deprecate > avro-python3. > > See: > https://issues.apache.org/jira/browse/AVRO-2656/ > https://github.com/apache/avro/pull/744 > > https://lists.apache.org/thread.html/3e1f8ddd4a29945fe226872ce1ae336f93083aca0c5220f08de12474%40%3Cdev.avro.apache.org%3E > > And in the 1.9.2 release notes: > > Work to unify Python2 and Python3 APIs in preparation for sunset. > > Jacob > > On Fri, Feb 14, 2020 at 11:18 AM Cris Ewing <[email protected]> > wrote: > > > Alright. The docker build is good. Full test suite is running as I > write > > this. Yay! > > > > It does not appear, however, that running tox in the py3 language > directory > > works (at least not as I expect it would). I see the following output > > > > cpe$ tox > > GLOB sdist-make: /Users/cpe/projects/tests/avro/lang/py3/setup.py > > python inst-nodeps: > > > > > /Users/cpe/projects/tests/avro/lang/py3/.tox/.tmp/package/1/avro-python3-1.10.0+snapshot.zip > > python installed: avro-python3==1.10.0+snapshot > > python run-test-pre: PYTHONHASHSEED='474647839' > > __________________________________________________________ summary > > ___________________________________________________________ > > python: commands succeeded > > congratulations :) > > > > Does not appear to me that any tests are run? > > > > c > > > > > > > > On Fri, Feb 14, 2020 at 9:04 AM Cris Ewing <[email protected]> > > wrote: > > > > > I followed this approach and called dig from my host machine. Then > > > realized that dig meant DNS was implicated and turned off my company > VPN. > > > Re-ran `./build.sh docker` and it succeeded. > > > > > > (and dig shows the same results inside and outside the container) > > > > > > c > > > > > > > > > > > > On Thu, Feb 13, 2020 at 4:48 PM Michael A. Smith <[email protected] > > > > > wrote: > > > > > >> OK, that is indeed the same image as I used, so the problem is > > >> elsewhere. What do you get for `dig security.debian.org`? What about > > >> when you run it from within the Docker build? (Try adding `apt-get -y > > >> update && apt-get -y install dnsutils && dig security.debian.org` > > >> before the `# Install nodejs 6` part.) > > >> > > >> On Thu, Feb 13, 2020 at 7:10 PM Cris Ewing <[email protected] > > > > >> wrote: > > >> > > > >> > I absolutely remember you Michael. It was great seeing your name on > > the > > >> > first thread I interacted with here. It's awesome to find an old > > >> friend in > > >> > a new place! > > >> > > > >> > I just ran `./build.sh docker` again. Here's what I see in the > output > > in > > >> > the terminal: > > >> > > > >> > ``` > > >> > Sending build context to Docker daemon 20.48kB > > >> > Step 1/27 : FROM openjdk:11-stretch > > >> > ---> 193af7392c2e > > >> > Step 2/27 : WORKDIR /root > > >> > ---> Using cache > > >> > ---> a628fb621a0f > > >> > Step 3/27 : ENV > > >> > APT_KEY_DONT_WARN_ON_DANGEROUS_USAGE=isolemnlysweariamuptonogood > > >> > DEBIAN_FRONTEND=noninteractive > > >> > ---> Using cache > > >> > ---> 12e5289d663f > > >> > ``` > > >> > > > >> > Admittedly, my docker-fu is not strong, but I don't think that > > >> 193af7392c2e > > >> > could be said to be anything like the SHA you posted. I'm assuming > > here > > >> > that the hex value posted after that step represents the SHA for the > > >> image > > >> > that the step uses. > > >> > > > >> > I have also run `docker image pull openjdk:11-stretch` and this is > > what > > >> I > > >> > see: > > >> > > > >> > ``` > > >> > ip-10-165-65-166:avro cpe$ docker image pull openjdk:11-stretch > > >> > 11-stretch: Pulling from library/openjdk > > >> > Digest: > > >> > > > sha256:04b4670ac7e90789932320ba849bda607d4edaba812b28570e946dd447e85041 > > >> > Status: Image is up to date for openjdk:11-stretch > > >> > docker.io/library/openjdk:11-stretch > > >> > ``` > > >> > > > >> > When I run `docker image ls` I find this entry for > openjdk:11-stretch: > > >> > > > >> > openjdk > > >> > 11-stretch 193af7392c2e 11 days ago > > >> 606MB > > >> > > > >> > I am still getting the same error when trying to use the `./build.sh > > >> > docker` command. So this is (at least on my end) 100% reliable. > > >> > > > >> > c > > >> > > > >> > On Thu, Feb 13, 2020 at 3:50 PM Michael A. Smith < > > [email protected]> > > >> > wrote: > > >> > > > >> > > Hi, Cris, > > >> > > > > >> > > Good to see you around these parts. (Idk if you remember me, but > we > > >> > > worked together a bit on Plone back in the day.) I just tried the > > same > > >> > > thing and wasn't able to reproduce the issue. Can you check if the > > >> > > openjdk:11-stretch image that the Dockerfile is based on has the > > >> > > digest > > >> > > > > >> > sha256:04b4670ac7e90789932320ba849bda607d4edaba812b28570e946dd447e85041 > > >> > > ? > > >> > > > > >> > > Cheers, > > >> > > Michael > > >> > > > > >> > > On Thu, Feb 13, 2020 at 12:44 PM Cris Ewing < > > >> [email protected]> > > >> > > wrote: > > >> > > > > > >> > > > Greetings, folks > > >> > > > > > >> > > > I am new to avro, eager to participate, and working on setting > up > > a > > >> dev > > >> > > > environment. I've been following the instructions from the > github > > >> > > > repository in BUILD.md, which instruct me to 'simplify this' by > > >> running a > > >> > > > docker container with all the dependencies. The instructions say > > to > > >> run > > >> > > > > > >> > > > `./build.sh docker`. > > >> > > > > > >> > > > I am doing so, but I get the following error: > > >> > > > > > >> > > > ``` > > >> > > > ## Populating apt-get cache... > > >> > > > > > >> > > > + apt-get update > > >> > > > Ign:1 http://deb.debian.org/debian stretch InRelease > > >> > > > Get:2 http://security.debian.org/debian-security > stretch/updates > > >> > > InRelease > > >> > > > [94.3 kB] > > >> > > > Get:3 http://deb.debian.org/debian stretch-updates InRelease > > [91.0 > > >> kB] > > >> > > > Ign:2 http://security.debian.org/debian-security > stretch/updates > > >> > > InRelease > > >> > > > Ign:3 http://deb.debian.org/debian stretch-updates InRelease > > >> > > > Get:4 http://security.debian.org/debian-security > > >> stretch/updates/main > > >> > > amd64 > > >> > > > Packages [517 kB] > > >> > > > Get:5 http://deb.debian.org/debian stretch Release [118 kB] > > >> > > > Get:6 http://deb.debian.org/debian stretch-updates/main amd64 > > >> Packages > > >> > > > [27.9 kB] > > >> > > > Get:7 http://deb.debian.org/debian stretch Release.gpg [2410 B] > > >> > > > Ign:7 http://deb.debian.org/debian stretch Release.gpg > > >> > > > Get:8 http://deb.debian.org/debian stretch/main amd64 Packages > > >> [7083 kB] > > >> > > > Fetched 7934 kB in 4s (1782 kB/s) > > >> > > > Reading package lists... > > >> > > > W: GPG error: http://security.debian.org/debian-security > > >> stretch/updates > > >> > > > InRelease: At least one invalid signature was encountered. > > >> > > > W: The repository 'http://security.debian.org/debian-security > > >> > > > stretch/updates InRelease' is not signed. > > >> > > > W: GPG error: http://deb.debian.org/debian stretch-updates > > >> InRelease: At > > >> > > > least one invalid signature was encountered. > > >> > > > W: The repository 'http://deb.debian.org/debian stretch-updates > > >> > > InRelease' > > >> > > > is not signed. > > >> > > > W: GPG error: http://deb.debian.org/debian stretch Release: At > > >> least one > > >> > > > invalid signature was encountered. > > >> > > > W: The repository 'http://deb.debian.org/debian stretch > Release' > > >> is not > > >> > > > signed. > > >> > > > > > >> > > > ## Installing packages required for setup: lsb-release... > > >> > > > > > >> > > > + apt-get install -y lsb-release > /dev/null 2>&1 > > >> > > > Error executing command, exiting > > >> > > > The command '/bin/sh -c curl -sSL > > >> https://deb.nodesource.com/setup_10.x > > >> > > | > > >> > > > bash - && apt-get -qqy install nodejs && apt-get -qqy clean > && > > >> rm -rf > > >> > > > /var/lib/apt/lists && npm install -g grunt-cli && npm cache > > clean > > >> > > > --force' returned a non-zero code: 1 > > >> > > > ``` > > >> > > > > > >> > > > I wonder if there is some step I'm missing here, or if anyone > can > > >> help me > > >> > > > get past this issue and on to the fun part. > > >> > > > > > >> > > > Thanks very much, > > >> > > > > > >> > > > Cris > > >> > > > > >> > > > > > >
