Closed benjroy closed 1 month ago
Undoing this commit seems to have fixed a similar issue for me.
https://github.com/McCloudS/subgen/commit/2a7bf3edbd7cad10ed9b54ba1fbbd8cbd77c96bb
Thanks all, I’ll revert it until I have more time to test it better.
Just restarted the subgen container and getting an error preventing the container from running:
I suspect that it it happening as a result of the latest commit because my initial setup was relying on env variables defined in my
docker-compose.yml
, then moved to asubgen.env
file and relied on defaults for things i didn't want to override:https://github.com/McCloudS/subgen/commit/2a7bf3edbd7cad10ed9b54ba1fbbd8cbd77c96bb
Does this seem plausible, that the removal of the
update_env_variables()
could have inadvertently removed the setting of expected defaults? Could the solution be to add CONCURRENT_TRANSCRIPTIONS=2 to mysubgen.env
file, or would I need to make sure to supply every env var with the documented default value in mysubgen.env
file?For reference, here are the contents of my
subgen.env
file: