i noticed what i thought was an issue with our docker image, where any invocation of optic would hang without output and require a kill -9 to stop. after some stracing and validating where it first sprung up i narrowed it down to the seemingly innocuous way we walk the file tree to find a config.
when $PWD is / the walk enters an infinite loop. this most noticeable in the image because we leave its WORKDIR set at the root, /. you can however replicate this on macOS as well with,
cd / && optic --version
just be ready to grab the pid so you can kill it :)
📚 References
Links to relevant docs (Notion, Twist, GH issues, etc.), if applicable.
👹 QA
How can other humans verify that this PR is correct?
🍗 Description
What does this PR do? Anything folks should know?
i noticed what i thought was an issue with our docker image, where any invocation of optic would hang without output and require a
kill -9to stop. after some stracing and validating where it first sprung up i narrowed it down to the seemingly innocuous way we walk the file tree to find a config.when
$PWDis/the walk enters an infinite loop. this most noticeable in the image because we leave itsWORKDIRset at the root,/. you can however replicate this on macOS as well with,just be ready to grab the pid so you can kill it :)
📚 References
Links to relevant docs (Notion, Twist, GH issues, etc.), if applicable.
👹 QA
How can other humans verify that this PR is correct?