appmap sometimes doesn't get enabled with uwsgi

Appmap didn't enable the remote recording routes when I tried to start uwsgi manually on the commandline with our test/data/django app. But it enabled the routes with chipy in its docker container running uwsgi. Why did it work in docker but not on my machine?

Also, the same command that fails to enable the routes on the command-line does work when called from the testsuite.

For more details see https://github.com/getappmap/board/issues/197#issuecomment-1289349059

Enables routes

APPMAP=true uwsgi --wsgi-file=app/wsgi.py --http-socket 0.0.0.0:8000 --threads=8 --env=DJANGO_SETTINGS_MODULE=app.settings

Doesn't enable routes

DEBUG=True uwsgi --wsgi-file=app/wsgi.py --http-socket 0.0.0.0:8000 --threads=8 --env=DJANGO_SETTINGS_MODULE=app.settings

When started from the command-line it doesn't enable routes (it demonstrates the bug) but when started from the testsuite it does enable routes (the test passes when it shouldn't.)

Saw this in this branch that added debugging statements.

Reproduce the discrepancy with test/data/django using the two uwsgi commands in the issue, then compare that behavior with the testsuite invocation. Review the debugging statements in the linked branch and the referenced board comment. Done means the command-line and testsuite cases agree about enabling the remote recording routes, with a regression test for the difference.