ddrimport entity hanging on Identifier

[sarabeckman]

ddrimport entity is not moving past the first DDR.identifier.Identifier collection step. The process doesn't stop and I have to manually cancel out of the operation.

I'm running master version 2.6.1 on my local VM. My local VM is also running stretch.

[gjost]

I confirmed that contents of the log on kinkura agree with the screenshot. I copied the CSV to my local dev environment and ran it on a local copy of that collection but was not able to duplicate the error.

Before we do anything else, can you update your copy of ddrlocal? It's a couple versions behind.

[sarabeckman]

I updated my copy to version 2.6.3 and I tried running the same ddrimport entity command and I got the same result.

[gjost]

I've downloaded both the CSV (ddr-csujad-14-entities-20180501-1049.csv) and the repository itself from kinkura to my local system. I also rolled back all the DDR components (ddr-defs, ddr-cmdln, ddr-local) to the where they are in 2.6.3 and recompiled everything from scratch. Unfortunately I still haven't been able to duplicate this bug.
Next I'll look through the source code and see what's going on at the point where it seems to get stuck.
If that doesn't work I'll install on a Debian Stretch system and see if that makes a difference.

[gjost]

In future bug reports, it's better to cut-and-paste text from the terminal rather than take screenshots. This makes it a lot easier to work with paths and stuff, cut-and-paste rather than squint and type.

Thanks for including the version number and the host OS.

[gjost]

I notice the command does not include the ID service username or password. Did you have these in environment variables, e.g. export IDSERVICE_ENVIRONMENT_USERNAME=redacted?

I ask because the very next thing that happens after the collection identifier gets printed (the last thing before it hangs) is the ID service login. If username is not in an environment variable, you'll get a username prompt.

Once ddrimport has a username/password, it attempts to contact the ID service. What happens if you run elinks https://idservice.densho.org on that VM? You should see a popup, where you should select "show header". You should then see some JSON. If you can't see this, you have a bad connection with the ID service.

[sarabeckman]

Aha! okay I added my ID service username and password to the command and the command worked!

[gjost]

Awesome! I guess i need to make it complain and quit if it doesnt have that info.

…

On September 7, 2018 11:51:56 AM PDT, Sara Beckman ***@***.***> wrote: Aha! okay I added my ID service username and password to the command and the command worked! -- You are receiving this because you were assigned. Reply to this email directly or view it on GitHub: #90 (comment)

-- "Work as if you live in the early days of a better national. --Alasdair Gray

[gjost]

Fixed in 9906b50.

[gjost]

Fixed in ea770a6.