PGSync Dying on build

[GDeane]

Describe the bug

Sometimes, when attempting to build the app with docker-compose up --build, PGSync fails to index 2000 or so listings and exits with code 1. It looks as follows:

Sometimes it works, sometimes it doesn't. When it works, it works like a dream (search works with filtering, pagination, etc. and recommender tunes based on the search results all on the frontend):

When it works, I was able to add a listing on the frontend, and it immediately showed up in my searches afterwards, confirming that pagination was working.

To Reproduce

Steps to reproduce the behaviour:

1. Run docker-compose down
2. Run docker-compose up --build
3. Look for the following in the logs (this marks a failure):

May require a few tries to reproduce, and may depend on your computer.

Expected behaviour

This issue doesn't ever happen, or there is a retry mechanism to ensure it eventually works in a few tries

[GDeane]

Ideas (before all of them, nuke/remove all stopped containers)

• directly connect pgsync to the database (change the database endpojnt var in the docker compose for pgsync to point to "database" instead of "datalayer")
• start database, datalayer, cache, waiting 5 mins, start pgsync
• start all four above at same time, Docker down, nuke data volume on both cache and database, then rocker up