VSCode timing out when running debugger

[mshannon-sil]

Multiple developers have encountered an issue where, some seconds after VSCode starts up the debugger, it quietly exits without beginning to step through the SILNLP repo code. It seems that the likely root cause of the issue is the default timeout in debugpy being too short. We've found that increasing the DEBUGPY_PROCESS_SPAWN_TIMEOUT in the ~/.profile of the container fixes the issue, so this environment variable should be added to the Dockerfiles.

[benjaminking]

I wonder if this will be improved by removing OpenNMT/Tensorflow? Anecdotally, I've noticed that Tensorflow takes a long time to load when starting SILNLP.

[mshannon-sil]

It might help, but I'm not entirely sure. In the cases I've seen, the debugger exits before logging anything about Tensorflow (or in general) to the console, so it's hard to know for certain. We could wait to see the results of that before adding this fix to the containers.

[TaperChipmunk32]

I could add this to my PR, since I am already updating the Dev container.

[mshannon-sil]

@TaperChipmunk32 that would be great.