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.

issue にある 2 つの uwsgi コマンドを使って test/data/django で不一致を再現し、その後、その動作を testsuite の呼び出しと比較します。リンクされた branch のデバッグ用ステートメントと、参照されている board のコメントを確認します。コマンドラインの場合と testsuite の場合で、リモート記録ルートの有効化について動作が一致し、その違いに対する回帰テストがあれば完了です。