Jimmy Reichley

Looks like a transient HTTP issue to me. Did you try it again since?

@MrBullfinsh I'm not very experience with Go but I think the go modules might be messing you up. Heres a command I had written down long ago when I built...

Sorry about that breakage, I didn't realize it was going to affect downstream immediately. As mentioned in that link, I am actually doing a sort of from scratch rewrite of...

1.4.6 is using the old `thegamesdb.net` API. You will need to build / run using [the most recent commit](https://github.com/sselph/scraper/tree/509443bf66d9fccb1d6aa2417902124bd48f2141) which should work against the new API.

Had to work on some contracting obligations, but finally got back to this. There were a lot of false-starts on things that ended up getting pretty ugly, but this is...

Hey @sselph just pinging to see if you had a chance to take a look at this.

Definitely understand the current code being the result of natural progression. Also, I agree with the batch-per-source idea. I'm between jobs at the moment so I've got time to put...

This is also the case when using `acbuild begin docker://debian:jessie-slim`

This bit me too, I had to resort to either doing a tmpdir on the host, or manually creating a pseudo-tmpdir in the container which I then clean up afterwards....

+1